iManager version 2.x runs on top of the exteNd DirectorTM, Standard Edition (DEX) portal framework. For iManager to function properly, configuration of DEX needs to be performed in both eDirectory and on the Web server where iManager is running.
The DEX configuration is typically performed silently during the iManager 2.x install on most platforms. However, you might find it necessary to manually configure these settings if there were errors during the silent configuration or if you require custom configuration. iManager provides the exteNd Director Configuration Wizard to allow easy configuration or reconfiguration of these settings.
The eDirectory configuration information is largely stored on the CN=PCO,OU=Extend object, which is usually found in your servers container. The Web server configuration information is stored in the PortalServlet.properties file located in $TOMCAT_HOME$/webapps/nps/WEB-INF.
The PCO object allows multiple iManager Web servers (Portal Heads) to synchronize content and to share Role-Based Services configuration and other settings. While running the exteNd Director Configuration Wizard, if one or more iManager servers have previously been installed into the tree, you are prompted to select to Install into an Existing PCO Object or to Create a New PCO Object. Be aware that if you select to create a new PCO object, the configured iManager cannot be associated in any way with the other iManager servers in the tree.
WARNING: Running the exteNd Director Configuration Wizard can destroy data. Do not complete the steps in the following sections unless you have been instructed to do so in either Installing iManager or Troubleshooting.
Get the PCO password seed.
If you are configuring to an existing PCO object, you are required to know the password seed for that PCO object. The password seed can be found in the System.Password entry in the PortalServlet.properties file of any iManager that has been configured to that PCO.
To find the list of all iManagers that are configured to an existing PCO, look at the bhLocation attribute on the PCO object.
Unconfigure the portal on the web server by renaming the PortalServlet.properties file. For example:
PortalServlet.properties.OLD
The exteNd Director Configuration Wizard contains an Unconfigure feature; however, in case you ever need to revert to the previous configuration, we recommend that you rename the PortalServlet.properties file instead of using the Unconfigure feature.
Restart Tomcat.
Run exteNd Director Configuration Wizard, based upon your iManager configuration. Enter
http://server_ip_address/nps/servlet/configure
or
https://server_ip_address/nps/servlet/configure
Click Start.
Type the IP address or DNS name of your eDirectory LDAP server and credentials for administration access.
You need to authenticate to the LDAP directory with admin rights before you install iManager. Use LDAP syntax for the authentication credentials. Passwords are case sensitive.
LDAP syntax refers to only the Distinguished name. For example, cn=admin,ou=mydepartment,o=mycompany.
IMPORTANT: If you select SSL, you must use an SSL port such as 636. The port number 389 is not an SSL port. We recommend you use SSL; otherwise, your password information will be sent over the wire in a clear text format.
Select the platform.xar from the list or browse for the platform.xar file.
Accept the license agreement, then click Next.
Select Typical, then click Next.
If a previous install exists, there is an option to connect to the existing PCO or create a new one.
IMPORTANT: Be aware that if you select to create a new PCO object, the configured iManager cannot be associated in any way with the other iManager servers in the tree.
Click Next.
After the configure is completed, restart Tomcat.
Log in to iManager, based upon your iManager configuration:
http://server_ip_address/nps/iManager.html
or
https://server_ip_address/nps/iManager.html