Requirements for Integration Server to Use Central User Management
My webMethods Server must be installed and configured to use an external database.
My webMethods Server clustering must be configured even if
Integration Server connects to a standalone
My webMethods Server. This is because the client-side common directory services APIs used by
Integration Server to communicate with
My webMethods Server functions as a cluster node.
My webMethods Server must be started at least once to enable
My webMethods Server clustering.
Note:
Beginning with My webMethods Server 10.0, My webMethods Server must use a Universal Messaging server as its JMS provider. My webMethods Server uses a JMS provider for cluster communication and synchronization.
Integration Server must have a JDBC connection pool that points to the
My webMethods Server database component, and the CentralUsers functional alias must point to that connection pool. On the
Settings > Resources page,
MWS SAML Resolver URL field must point to your
My webMethods Server host and port.
Note:
When Integration Server is successfully configured to use central user management, and the logging level for the server log facility 0024 User Manager is set to at least Info, Integration Server logs the message [ISS.0024.0012I] Central User Management initialized successfully upon startup.
If you later want to stop using central user management, follow the instructions in
Connecting
Integration Server to Database Components in an External RDBMS, but in the
Associated Pool Alias list, click
None for the
CentralUsers function, and then restart
Integration Server.
Note:Integration Server updates the Anonymous ACL automatically to include the My webMethods Users Role from My webMethods Server.
For more information about configuring My webMethods Server for common directory services and clustering, see Administering My webMethods Server.
Note:
If Central User Management is configured to use LDAP over SSL, set the javax.net.ssl properties in the custom_wrapper.conf file.