Augment a dmgr profile on IBM i
An existing dmgr profile can be augmented with the configuration settings required to set up an IBM WebSphere Portal cluster.Augmenting the dmgr profile enables your dmgr to manage portal nodes and to modify the following values to fit the portal usage:
- The HTTP connection timeout for read and write are set to 180.
- If less than 300 MB, the minimum Heap Size are set to 300 MB.
- If less than 1000 MB, the maximum Heap Size are set to 1024 MB.
- If not already active, the application security are turned on.
- The group cn=wpsadmins are created in the file-based registry and the IBM WAS administrative ID are added to it. This change will have no effect if security is already changed to something other than the file-based repository.
- The com.ibm.SOAP.requestTimeout property are set to 6000 in the soap.client.props file to allow for longer timeouts.
- SWAMAuthentication are added to the available authentication mechanisms.
- The com.ibm.portal.auth.tai.HTTPBasicAuthTAI class are registered as TAInterceptor.
- trustAssociation are enabled.
Complete the following steps to augment an existing dmgr profile:
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.