Prepare the WAS Deployment Manager on i5/OS

WebSphere Portal provides a customized installation package (CIP) that includes IBM WAS Network Deployment and all required maintenance packages. Use the supplied discs to install WAS Network Deployment on a dedicated system.

To prepare the WAS Deployment Manager:

  1. Install WAS Network Deployment or use the CIP to upgrade an existing installation. Run the following command:

    cd_root/ISERIES/architecture/ifpackage/WAS/install.

  2. Use the manageprofile commands to create a deployment manager profile; see Profile concepts.

  3. Run the following command to start the deployment manager: startManager, from the DMGR_PROFILE/bin.

  4. Launch the admin console:

      http://dmgr_hostname:9060/ibm/console

  5. Log into the deployment manager administrative console.

  6. Increase the HTTP connection timeouts for the deployment manager.

    1. Click System Administration > Deployment Manager > Web container transport chains.

    2. For the WCInboundAdmin and WCInboundAdminSecure entries listed in the web container transport chains section, complete the following steps to increase the timeout values:

      1. Click HTTP Inbound Channel.

      2. Change the Read timeout value to 180.

      3. Change the Write timeout value to 180.

      4. Save the configuration changes.

  7. Change the timeout request period for the JMX connector.

    1. Click System administration > Deployment Manager > Administration Services > JMX connectors > SOAPConnector > Custom Properties.

    2. Select the requestTimeout property, and increase the value from 600 to 6000.

    3. Save the configuration changes.

  8. Update the maximum Java heap size used by the deployment manager:

    1. Click System administration > Deployment manager > Java and Process Management > Process Definition > Java Virtual Machine.

    2. Update the value in the Maximum Heap Size field.

      For 32-bit OS, set the heap size to a lower size than a 64-bit operating system.

    3. Click OK.

  9. Click Security > Global security and select Enable Application Security. Then save the configuration changes.

    If security is not enabled on your deployment manager, see Enabling security for information before performing this step.

  10. Verify that the WebSphere Portal administrative users and administrative group exist in the Deployment Manager cell's user registry.

    Perform the following steps if creating the administrative users and group:

    These steps are required if you plan to use a federated repository for the user registry or if the Administrator ID on the node does not match the Administrator ID on the Deployment Manager, where the ID is the distinguished name.

    1. Click...

        Users and Groups | Manage Users | Create

    2. Type the information for the WebSphere Portal administrative users; for example wpsadmin and wpsbind, and then click Create.

    3. Click...

        Users and Groups | Manage Groups | Create

    4. Type the name of the WebSphere Portal administrative group; for example, wpsadmins, and then click Create.

    5. Click the group you just created; for example wpsadmins.

    6. Click the Members tab.

    7. Click Add Users.

    8. Search for the users.

    9. Select the users you want to add to the group.

    10. Click Add to add the users to the group.

    11. Click Close when you are done adding users to the group.

    12. Log out of the administrative console.

  11. Edit...

      Dmgr_profile/properties/soap.client.props
    Set:

      com.ibm.SOAP.requestTimeout=6000

    Cycle the deployment manager...

    1. stopManager-username admin_userid -password admin_password, from the DMGR_PROFILE/bin

    2. startManager, from the DMGR_PROFILE/bin


Parent topic:

Prepare prerequisite and corequisite software on i5/OS


Next topic:

Prepare the Web server when portal is installed on i5/OS


Related tasks


Backing up the Deployment Manager profile on i5/OS
Restoring the Deployment Manager profile