Enterprise Administration Guide › Planning Your PUPM Implementation › Implementation Considerations › Connector Servers › Connector Xpress Overview › Connector Xpress Example: Load the Endpoint Type to the Enterprise Management Server

Connector Xpress Example: Load the Endpoint Type to the Enterprise Management Server

In this example, the system administrator Steve loads the new endpoint type that was created to the Enterprise Management Server. After Steve loads the new endpoint type, Steve is able to configure and manage the endpoint from CA Access Control Enterprise Management. Steve does the following:

1. Stops the JBoss application server.
2. Does one of the following:
   • (JDBC) Edits the file conXpressnamespace_config.xml.template.
   • (SUN One) Edits the iplanetnamespace_config.xml

   You can find the files in the following directory, where JBOSS_HOME indicates the directory where you installed JBoss:

   JBOSS_HOME/server/default/deploy/IdentityMinder.ear/custom/ppm/namespaceConfigs/
   

3. Locates the <endpointType> parameter and removes the default value: ‘REPLACE_WITH_ENDPOINT_TYPE’.
4. Enters the endpoint type name as specified in Connector Xpress.
5. Saves the file under the name conXpress_Endpoint_Type_namespace_config.xml in the following directory:

   JBOSS_HOME/server/default/deploy/IdentityMinder.ear/custom/ppm/namespaceConfigs/
   

6. Starts the JBoss application server.

Steve has loaded the new endpoint type to the Enterprise Management Server. Steve can now define endpoints of this type in CA Access Control Enterprise Management and discovers the privileged accounts on the endpoint.