Create an extended WAS instance

 

+
Search Tips   |   Advanced Search

 

Overview

To configure WebSphere Portal, create a WAS instance with the additional functionality provided by WAS V5.0 Enterprise Enablement. Pre-existing WAS instances, or those otherwise created without the extended functionality, will not be able to run WebSphere Portal.

If you use the WebSphere Portal configuration wizard included with IBM Web Administration for iSeries (recommended), the wizard will create an extended WAS instance for you. Before attempting to create an instance using the instructions below, be sure to review the Installation scenarios topic to determine whether or not it is necessary.

This topic also includes instructions on removing an extended WAS instance. The WebSphere Portal uninstall script does not automatically remove extended WAS instances.

  1. Create an extended WAS instance
  2. Removing an extended WAS instance

 

Create an extended WAS instance:

  1. Open an OS/400 command prompt and start the Qshell Interpreter... 

    STRQSH

  2. Change to...

    /qibm/proddata/webas5/pme/bin

    If creating a Network Deployment instance, change to..

    /qibm/proddata/webas5/pmend/bin

  3. Run... 

     crtwasinst -instance <instance> -portblock <portblock>

    ...where instance is the name of the new WAS instance and portblock is the first of 12 ports on the iSeries system that are available for use with the new WAS instance. For example, entering a portblock of 20001 would designate ports 20001-20012 as WAS ports.

    When the instance has been created, a confirmation message listing the port assignments will be displayed. Note the ports associated with the administrative console and the snoop servlet.

    If you are using an external HTTP server with the WAS instance, an additional parameter (exthttp) is required to specify the external server's port number. In that case, the command would be: 

    crtwasinst -instance <instance> -portblock <portblock> -exthttp <port>

    ...where port is the port number of the external HTTP server.

  4. Configure the HTTP server to use the new WAS instance.

    When prompted for a WebSphere domain, select the newly created WAS instance.

  5. If the Qshell interpreter is not running, restart it using the STRQSH command, and change to...

    /qibm/proddata/webas5/pme/bin.

    If creating a Network Deployment instance, instead change to...

    /qibm/proddata/webas5/pmend/bin

  6. Start the new WAS server by entering the following command: 

    startServer -instance <instance> <app_server>

    where instance is the name of the WAS instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

  7. Verify that you can bring up the administrative console and snoop servlet of the new instance by entering the following into the address bar of a Web browser: 

    http://<your.server.com>:<admin_port>/admin
http://<your.server.com>:<snoop_port>/snoop

    where your.server.com is the name of the iSeries system, admin_port is the port to which the administrative console is assigned, and snoop_port is the port to which the snoop servlet is assigned.

  8. (Optional) If you intend to manually configure WebSphere Portal, you might wish to add WebSphere Portal to the WAS instance at this point. For instructions, see Adding WebSphere Portal to a WAS instance

 

Removing an extended WAS instance:

  1. Start the Qshell Interpreter by entering the following from on OS/400 command line: 

    STRQSH

  2. Change to the directory /qibm/proddata/webas5/pme/bin

    If removing a Network Deployment instance, instead change to directory /qibm/proddata/webas5/pmend/bin

  3. Stop the server by entering the following command: 

    stopServer -instance <instance> <app_server>

    where instance is the name of the WAS instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

  4. Change to the directory /qibm/proddata/portalserver5/config

  5. De-configure the WAS instance by entering the following command: 

    wpsconfig.sh -instance <instance> remove-was-cfg

  6. Remove WebSphere Portal from the instance by entering the following command: 

    rmvwpsinst.sh -instance <instance>

  7. Change to the directory /qibm/proddata/webas5/pme/bin

    If removing a Network Deployment instance, instead change to directory /qibm/proddata/webas5/pmend/bin

  8. Delete the instance by entering the following command: 

    dltwasinst -instance <instance>

 

See also