Augment a Deployment Manager profile on IBM i
After running the enable-profiles task, you can augment existing Deployment Manager profiles based on the existing template.
Augment the Deployment Manager profile enables Deployment Manager to manage portal nodes and to modify the following values to fit the portal usage:
Augment an existing Deployment Manager profile:
- The HTTP connection timeout for read and write will be set to 180.
- If below 300 MB, the minimum Heap Size will be set to 300 MB.
- If below 1000 MB, the maximum Heap Size will be set to 1024 MB.
- If not already active, the application security will be turned on.
- The group cn=wpsadmins will be created in the file based registry and the IBM WebSphere Application Server administrative ID will be 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 will be set to 6000 in the soap.client.props file to allow for longer timeouts.
- SWAMAuthentication will be added to the available authentication mechanisms.
- The com.ibm.portal.auth.tai.HTTPBasicAuthTAI class will be registered as TAInterceptor.
- trustAssociation will be enabled.
Run the following command from the WAS_HOME/bin directory:
manageprofiles.sh -augment -templatePath /QIBM/ProdData/WebSphere/AppServer/V7/ND/profileTemplates/management.portal.augment -profileName Dmgr01If you have a long command, use the continuation character "/" to avoid seeing the "not found" error message.
In this example, the portal profile template is installed under the /QIBM/ProdData/WebSphere/AppServer/V7/ND/profileTemplates directory. The existing Deployment Manager profile is named Dmgr01 and is located under the /QIBM/ProdData/WebSphere/AppServer/V7/ND/profiles/Dmgr01 directory.
Parent
Create or augment profiles on IBM i