Creating and augmenting a new Deployment Manager profile on IBM i

For a production environment you should install your Deployment Manager on a server that is remote from your IBM® WebSphere® Portal Express® installation. Use the Profile Management Tool or the manageprofiles command to create the remote Deployment Manager profile. In a test or development environment, you can install your Deployment Manager locally using the IBM Installation Manager. Complete the steps to creating and augmenting a new Deployment Manager profile if you are installing a remote Deployment Manager profile. Skip these steps if you are using the Installation Manager to install a local Deployment Manager profile on your primary node.

Choose the appropriate installation option to install your Deployment Manager profile:
Complete the following steps to create and augment the Deployment Manager profile:
  1. Complete the following steps if IBM WebSphere Application Server is not installed on the system you plan to use for the Deployment Manager:
    1. Click the appropriate link under "Prerequisites" for installation instructions.
    2. Install or update the IBM Installation Manager on your Deployment Manager server.
    3. Add the same repositories that you used when installing WebSphere Portal Express on your primary node.
    4. Begin the installation process.
    5. Select the WebSphere Application Server Network Deployment installation package only and complete the installation process.
  2. You can either use an existing Deployment Manager profile or you can run the following command from the AppServer_root/bin directory:
    manageprofiles -create -templatePath AppServer_root/profileTemplates/management 
    		-hostName hostname
    		-profileName Dmgr01 
    		-profilePath AppServer_root/Dmgr01 
    		-enableAdminSecurity true 
    		-adminUserName dmgradmin 
    		-adminPassword dmgrpass
    
    Restriction: If you plan to use the back up and restore task documented in the product documentation, you must use the default profile path for the deployment manager profile; otherwise, the back up and restore tasks cannot locate the profile.
  3. Complete the following steps to collect files from the primary node and copy them to the remote deployment manager:
    1. An archive or compressed file is placed in the PortalServer_root/filesForDmgr directory during installation; the file is called filesForDmgr.zip. Copy the filesForDmgr.zip file to the remote Deployment Manager server.
    2. Stop the deployment manager.
    3. Expand the filesForDmgr.zip file into the installation root directory of the Deployment Manager; for example this may be a subdirectory under the AppServer directory and it contains the bin and profileTemplates directories.
      Note: If the Deployment Manager profile was not created in the default AppServer\profiles\Dmgr01 directory, then the metadata_wkplc.xml file, located in the AppServer/profiles/Dmgr01/config/.repository\metadata_wkplc.xml directory in the compressed file, must be copied into the config/.repository subdirectory under the Deployment Manager profile directory.
    4. Start the deployment manager.
  4. Run the following command from the AppServer_root/bin directory:
    manageprofiles.sh -augment -templatePath AppServer_root/profileTemplates/management.portal.augment 
    			-profileName dmgr
    Tip: If 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 AppServer_root/profileTemplates directory. The existing Deployment Manager profile is named dmgr and is located under the AppServer_root/profiles/Dmgr01 directory.

  5. Stop and restart the Deployment Manager server; see "Starting and stopping servers, deployment managers, and node agents" for information.
  6. Complete the following steps if there are common shortnames between the default Deployment Manager security configuration and the LDAP server:
    1. Log on to the Deployment Manager WebSphere Integrated Solutions 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 WebSphere Integrated Solutions Console.
  7. Complete the following steps if you changed the context root on the Configuration for IBM WebSphere Portal: Profile configuration details: Advanced panel during installation:
    1. Log on to the Deployment Manager WebSphere Integrated Solutions 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 Deployment Manager WebSphere Integrated Solutions Console.