If you’re trying to setup Adobe’s Digital Enterprise Platform (ADEP 10) and the ADEP configuration manager reports any of the following errors while bootstrapping, then I might have the solution for you.
com.adobe.pof.schema.ObjectTypeNotFoundException: Object Type: dsc.sc_property_editor not found
com.adobe.pof.schema.ObjectTypeNotFoundException: Object Type: dsc.sc_service_configuration not found
It took me days of experimenting until I figured this out by sheer luck. If you select UDP based cluster caching in the configuration manager, the document service component will use the specified UDP port while bootstrapping the core configuration. If another cluster is communicating over the same multicast port, bootstrapping the core component will fail with obscure error messages.
The official documentation says:
Note: The value for <port number> can be any available port between 1025 and 65535. The multicast port must be unique to the Document Services cluster (that is, the port must not be used by any other cluster on the same network, any attempt to use the same port by any other cluster on the same network would result in bootstrap failure). It is recommended that you configure the same <port number>
on all nodes in the Document Services cluster, as in this example: -Dadobe.cache.multicast-port=33456
I missed this section (as real programmers don’t read manuals :) and assumed that it is okay to use the same UDP cluster cache port number for different clusters in the same network. Obviously that’s not the case. I’m now using different port numbers for every ADEP cluster and haven’t seen a bootstrapping problem ever since.
If the configuration manager reports this error (Oracle WebLogic only):
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=, on Resource AdobeService
Operation: set , Target: EnableSSL
Try to hit the initialize button again. I was able to get rid of the error this way. A more proper way would be to adjust the JMX security policies in WebLogic’s security realm configuration in the JMX Policy Editor. The affected properties are “Attributes: Permission to Write” and “Unregister instances of this
MBean using MBean server”, both need to have its role set to Anonymous. The exact steps are detailed in the ADEP installation instructions using WebLogic (see “Creating JMX policies for database initialization”). Make sure you remove those properties after the installation went through. Looks like a security hole to me if you leave them in.