Create and augment a new dmgr profile on IBM i

For a production environment you should install the dmgr on a server that is remote from the portal installation. Use pmt.sh or manageprofiles.sh to create the remote dmgr profile. In a test or dev environment, we can install the dmgr locally using the Installation Manager. Skip these steps if we are using the Installation Manager to install a local dmgr profile on the primary node.

Prerequisites

Prepare the IBM i operating system in a clustered environment

Prepare the primary node on IBM i

Clustered environment: Install with Installation Manager response file on IBM i

Create and augment the dmgr profile

1. If IBM WAS is not installed on the system you plan to use for the dmgr:

   1. Click the appropriate link under "Prerequisites" for installation instructions.

   2. Install Installation Manager on the dmgr server.
   3. Add WebSphere Portal repositories
   4. Install WAS ND only

2. We can either use an existing dmgr profile or we can run the following command from the WAS_HOME/bin directory:

   manageprofiles -create -templatePath WAS_HOME/profileTemplates/management    -hostName hostname
     -profileName Dmgr01    -profilePath WAS_HOME/Dmgr01    -enableAdminSecurity true    -adminUserName dmgradmin    -adminPassword dmgrpass
   
   

   Restriction: To use the back up and restore task documented in the product documentation, use the default profile path for the dmgr profile; otherwise, the back up and restore tasks cannot locate the profile.

3. Collect files from the primary node and copy them to the remote dmgr:

   1. Copy...
      PORTAL_HOME/filesForDmgr/filesForDmgr.zip

      ...to the remote dmgr server.

   2. Stop the dmgr.

   3. Expand the filesForDmgr.zip file into the installation root directory of the dmgr; for example this may be a subdirectory under the AppServer directory and it contains the bin and profileTemplates directories.

      If the dmgr profile was not created in the default Appserver/profiles/Dmgr01 directory, then...

      Appserver/profiles/Dmgr01/config/.repository/metadata_wkplc.xml

      ...in the compressed file, must be copied into

      DMGR_PROFILE/config/.repository

   4. Start the dmgr.

4. cd WAS_HOME/bin
   manageprofiles.sh -augment -templatePath WAS_HOME/profileTemplates/management.portal.augment -profileName dmgr

   Use the continuation character "\" to avoid seeing the "not found" error message.

   In this example, the portal profile template is installed under the WAS_HOME/profileTemplates directory. The existing dmgr profile is named dmgr and is located under the WAS_HOME/profiles/Dmgr01 directory.

5. Stop and restart the dmgr server; see "Starting and stopping servers, dmgrs, and node agents" for information.

6. If there are common shortnames between the default dmgr security configuration and the LDAP server:

   1. Log on to the dmgr console.

   2. Navigate to Security > Global security.

   3. Under User account repository, click Configure.

   4. In the Primary administrative user name field, alter the user ID so that is using the full distinguished user name. For the default file user registry, the syntax is...
      uid=userID,o=defaultWIMFileBasedRealm

      for example: uid=wpadmin,o=defaultWIMFileBasedRealm.

   5. Click Apply.

   6. Enter the password for the user and then confirm the password.

   7. Save all changes.

   8. Log out of the WAS admin console.

7. If you changed the context root on the panel...
   Configuration for IBM WebSphere Portal: Profile configuration details: Advanced

   ...during installation:

   1. Log on to the dmgr console.

   2. Go to Security > Global security.

   3. Click Trust association in the Web and SIP security section.

   4. Click Interceptors in the Additional Properties section.

   5. Click com.ibm.portal.auth.tai.HTTPBasicAuthTAI.

   6. Edit the urlBlackList and urlWhiteList parameters with the new context path; for example:

      • urlBlackList: /wpsmodified/myportal*

      • urlWhiteList: /wpsmodified/mycontenthandler*

   7. Click Apply.

   8. Save all changes.

   9. Log out of the dmgr console.

Parent: Set up a cluster on IBM i
Previous: Prepare the primary node on IBM i
Next: Create the cluster on IBM i
Related:
Start and stop servers, dmgrs, and node agents
Start and stop servers, dmgrs, and node agents