Prepare the WAS Deployment Manager on Windows

 

+

Search Tips   |   Advanced Search

 

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.
   cd_root/windows/ia32/ifpackage/WAS/install.exe
   cd_root/windows/amd64/ifpackage/WAS/install.exe

   ...where cd_root is the root directory of the disc.

2. Choose one of the following options to create a default dmgr profile:
   • Profile Management Tool
   • manageprofile.sh

   If you have a 64-bit environment, only the manageprofiles command is supported when creating profiles.

   When creating the default dmgr profile, enable administrative security. For the Profile Management Tool, check the enable administrative security check box. For manageprofile.sh, add the parameter...

   -enableAdminSecurity=true

3. Start the dmgr:
   cd dmgr_profile_root/bin
   startManager.bat

4. Launch the network deployment administrative console:
   http://dmgr_hostname:9060/ibm/console,

5. Log into the dmgr administrative console.

6. Increase the HTTP connection timeouts for the dmgr. Go to....
   System Administration | Deployment Manager | Web container transport chains

   For both WCInboundAdmin and WCInboundAdminSecure click HTTP Inbound Channel and change...

   • Read timeout value to 180
   • Write timeout value to 180

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

   System administration | Deployment Manager | Administration Services | JMX connectors | SOAPConnector | Custom Properties

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

8. Update the maximum heap size used by the dmgr. Go to...

   System administration | Deployment manager | Java and Process Management | Process Definition | Java Virtual Machine

   ...and 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.

9. Enable security on the dmgr

   • For WAS v6.1:

     Security | Secure administration, applications and infrastructure | Enable Application Security

   • For WAS v7.0:

     Security | Global security | Enable Application Security

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...
       Members tab | Add Users

    7. Search for the users.

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

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

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

    11. Log out of the administrative console.

11. Change the timeout request period for the SOAP client.

    Edit...

    Dmgr_profile/properties/soap.client.props

    Change the line to:

    com.ibm.SOAP.requestTimeout=6000

12. Cycle the dmgr:

    cd dmgr_profile_root/bin
    stopManager.bat -username admin_userid -password admin_password
    startManager.bat

Parent topic:

Prepare prerequisite and corequisite software on Windows

Next topic:

Prepare a remote Web server when portal is installed on Windows