Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Preparing WebSphere Application Server Network Deployment on Linux

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

Prerequisites

Preparing databases

Preparing user registries on Linux

1. Install WebSphere Application Server Network Deployment or use the CIP to upgrade an existing installation. Run the following command: cd_root/Linux/architecture/ifpackage/WAS/install, where cd_root is the root directory of the disc and architecture is the system's processor architecture.
2. Choose one of the following options to create a default deployment manager profile:

   Option	Description
   Profile Creation wizard	See Creating a deployment manager profile for information.
   manageprofile commands	See manageprofile commands for information.Note: If you have a 64-bit environment, only the manageprofiles command is supported when creating profiles.

3. Run the following command to start the deployment manager: ./startManager.sh, located in the wp_profile_root/bin directory.
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 WebSphere Application Server Network Deployment.
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 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 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. A value of at least 1024 MB is recommended.
   3. Click OK, and then save your changes.
9. Click Security > Secure administration, applications and infrastructure and select Enable Application Security. Then save the configuration changes.
10. Change the timeout request period for the Simple Object Access Protocol (SOAP) client. Edit the soap.client.props file, located in the wp_profile/properties directory:

    Change the line to: com.ibm.SOAP.requestTimeout=6000.

11. Run the following tasks to stop and restart the deployment manager:

    1. ./stopManager.sh, located in the wp_profile_root/bin directory
    2. ./startManager.sh, located in the wp_profile_root/bin directory