Prepare the WAS Network Deployment on Windows

 

+

Search Tips   |   Advanced Search

 

IBM WebSphere Portal provides a customized installation package (CIP) that installs both IBM WAS ND and all required maintenance packages.

Use the supplied discs if you need to install WAS ND on a dedicated system.

To install WAS Network Deployment:

1. Install WAS Network Deployment or use the CIP to upgrade an existing installation...

   cd_root\windows\ia32\ifpackage\WAS\install.exe

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

2. To create a default deployment manager profile:
   • Profile Creation wizard
   • manageprofile commands

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

3. Start the deployment manager:

   cd dmgr_profile_root/bin
   startManager.bat

4. Use the following URL to launch the network deployment administrative console:
   http://dmgr_hostname:9060/ibm/console

   ...where dmgr_hostname is the fully qualified host.name for the WAS ND.

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. Increase the timeout values.

      For entries...

      • WCInboundAdmin
      • WCInboundAdminSecure

      ...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 Java Management Extensions (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 information about appropriate heap sizes see the documentation for your operating system and the Performance Guides located on the WebSphere Portal and WCM Product Documentation page.

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

   3. Click OK, and then save your changes.

9. Click...
   Security | Secure administration, applications and infrastructure | Enable Application Security

   ...then save the configuration changes.

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 you plan to use a federated repository for your user registry and need to create the administrative users and group:

    1. Log in to the WAS Network Deployment Administrative Console.

    2. Click...
       Users and Groups | Manage Users | Create

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

    4. Click...
       Users and Groups | Manage Groups | Create

    5. Type the name of the WebSphere Portal administrative group. For example wpsadmins, and then click Create

11. Change the timeout request period for SOAP client.

    Edit...

    Dmgr_profile/properties/soap.client.props

    Change the line to:

    com.ibm.SOAP.requestTimeout=6000

12. To stop and restart the deployment manager:

    1. stopManager.bat, from the dmgr_profile_root\bin directory

    2. startManager.bat, from the dmgr_profile_root\bin directory

 

Parent topic

Preparing prerequisite and corequisite software on Windows

Next topic:

Preparing a remote Web server when portal is installed on Windows

---