Augmenting a Deployment Manager profile on Linux

An existing Deployment Manager profile can be augmented with the configuration settings required to set up an IBM® WebSphere® Portal cluster.

About this task

Augmenting the Deployment Manager profile enables your Deployment Manager to manage portal nodes and to modify the following values to fit your 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 WebSphere Application Server 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 Deployment Manager profile:

Procedure

Choose one of the following methods to augment a deployment manager profile:
Table 1. Choosing between the Profile Management Tool and the manageprofiles task to augment a deployment manager profile.
Option Steps
Profile Management Tool Complete the following steps to use the Profile Management Tool:
  1. Run the ./pmt.sh command from the AppServer_root/bin/ProfileManagement directory.
  2. Click Launch Profile Management Tool.
  3. Select your Deployment Manager profile and then click Augment.
  4. On the Augment Selection panel, select Deployment Manager for Portal, and then click Next.
  5. On the Profile Augmentation Summary panel, review the information collected by the wizard, and then click Augment to augment the Deployment Manager profile with WebSphere Portal.
  6. Click Finish to exit PMT.
manageprofiles command Run the following command from the AppServer_root/bin directory:
./manageprofiles.sh -augment -templatePath 
AppServer_root/profileTemplates/management.portal.augment
			-profileName dmgr01
Tip: If you have a long command, use the continuation character "\" to avoid seeing the "not found" error message.

In this example, the profile template is installed under the AppServer_root/profileTemplates directory. The existing Deployment Manager profile is named dmgr and is located under the AppServer_root/profiles/dmgr directory.