Install coexisting WebSphere Portal products on the same machine

 


Contents

  1. Overview
  2. Install the first copy of WAS and WebSphere Portal
  3. Configure the WebSphere Portal ports for coexistence
  4. Install the next copy of WAS and WebSphere Portal
  5. Install additional copies of WAS and WebSphere Portal


Overview

To install more than one copy of WebSphere Portal on the same machine and have each WebSphere Portal operate independently of the others, each copy of WebSphere Portal must be installed on a separate installation of WAS. Running multiple instances of WebSphere Portal on the same installation of WAS is not supported.

WebSphere Portal V4.x and WebSphere Portal V5.x can coexist, as well as multiple installations of WebSphere Portal V5.x.

WAS users or WebSphere Portal V4.x users: If one of the following criteria is true, skip to Install another copy of WAS and WebSphere Portal:

  • You have a copy of WAS already installed without WebSphere Portal, and you do not intend to install WebSphere Portal on that instance of WAS.

  • You have a copy of WebSphere Portal V4.x already installed.

 

Install the first copy of WAS and WebSphere Portal

To install the first copy of WAS and WebSphere Portal...

  1. Follow the instructions in Install WebSphere Portal, just as if you were only installing a single copy of WebSphere Portal.

  2. Verify that you can start and access the WAS administrative server and the WebSphere_Portal appserver:

    cd $WAS_HOME/bin
    startServer server1
    startServer WebSphere_Portal

  3. Access the Administrative Console for WAS by requesting the following URL from a browser:

    http://<hostname>:9090/admin/

    ...where hostname is the fully-qualified host.name of the machine where WAS is installed. For example, http://www.setgetweb.com:9090/admin/.

  4. Access WebSphere Portal by requesting the following URL from a browser:

    http://<hostname.setgetweb.com>:<port_number>/wps/portal

    ...where hostname.setgetweb.com is the fully-qualified host.name of the machine where WebSphere Portal is running and port_number is the transport port created by WAS. For example,...

    http://www.setgetweb.com:9081/wps/portal

Troubleshoot if you are unable to access either WebSphere Portal or the administrative server for WAS.

 

Configure the WebSphere Portal ports for coexistence

To avoid port conflicts between installations of WebSphere Portal, configure the ports used by the WebSphere_Portal application.

  1. Edit the appserver configuration:

    cd $PORTAL_HOME/bin
    stopServer server1
    stopServer WebSphere_Portal

  2. Edit...

    $PORTAL_HOME/config/cells/cell/nodes/node/serverindex.xml

  3. Locate the serverEntries element for the WebSphere_Portal appserver. It can be identified by a line similar to the following:

    <serverEntries xmi:id="ServerEntry_2" 
                   serverName="WebSphere_Portal" 
                   serverType="APPLICATION_SERVER">
    

  4. Within the serverEntries element for WebSphere_Portal, modify the port numbers for the specialEndpoints elements as shown below:
    
      <specialEndpoints xmi:id="NamedEndPoint_9" 
                        endPointName="SOAP_CONNECTOR_ADDRESS">
    
        <endPoint xmi:id="EndPoint_9" 
                        host="www.setgetweb.com" 
                        port="12000"/>
    
      </specialEndpoints>
    
      <specialEndpoints xmi:id="NamedEndPoint_10" 
                        endPointName="BOOTSTRAP_ADDRESS>
    
        <endpoint xmi:id="EndPoint_10" 
                  host="www.setgetweb.com" port="12001"/>
    
      </specialEndpoints>
    
      <specialEndpoints xmi:id="NamedEndPoint_11" 
                        endPointName="JMSSERVER_DIRECT_ADDRESS">
    
        <endpoint xmi:id="EndPoint_11" 
                  host="www.setgetweb.com" port="12002"/>
    
      </specialEndpoints>
    
      <specialEndpoints xmi:id="NamedEndPoint_12" 
                        endPointName="JMSSERVER_QUEUED_ADDRESS">
    
        <endpoint xmi:id="EndPoint_12" 
                  host="www.setgetweb.com" 
                  port="12003"/>
    
      </specialEndpoints>
    

    Use port numbers that are not being used by other programs. On UNIX systems, run netstat -r to see what port numbers are being used.

  5. Save your changes.

  6. Edit...

    $PORTAL_HOME/config/cells/cell/nodes/node/servers/WebSphere_Portal/server.xml

  7. Modify the port numbers for the HTTP transports as shown below. The WebSphere_Portal appserver uses the first two ports, and the next two are used by the administrative console deployed into the portal.

    
      <transports xmi:type="applicationserver.webcontainer:HTTPTransport" 
                  xmi:id="HTTPTransport_1" 
                  sslEnabled="false">
    
        <address xmi:id="EndPoint_1" 
                 host="" 
                 port="13000"/>
    
      </transports>
    
      <transports xmi:type="applicationserver.webcontainer:HTTPTransport" 
                  xmi:id="HTTPTransport_2" 
                  sslEnabled="true" 
                  sslConfig="troilus2/DefaultSSLSettings">
    
        <address xmi:id="EndPoint_2" 
                 host="" 
                 port="13001"/>
    
      </transports>
    
      <transports xmi:type="applicationserver.webcontainer:HTTPTransport" 
                  xmi:id="HTTPTransport_3" 
                  sslEnabled="false">
        <address xmi:id="EndPoint_3" host="" port="13002"/>
    
      </transports>
    
      <transports xmi:type="applicationserver.webcontainer:HTTPTransport" 
                  xmi:id="HTTPTransport_4" 
                  sslEnabled="true" 
                  sslConfig="troilus2/DefaultSSLSettings">
    
        <address xmi:id="EndPoint_4" 
                 host="" 
                 port="13003"/>
    
        <properties xmi:id="Property_9" 
                    name="MaxKeepAliveConnections" 
                    value="0" 
                    required="false"/>
    
      </transports>
    
    

    Use port numbers that are not likely to be used by other installations of WAS or other programs. In the example above, the ports are numbered beginning with 13000 for the first installation of WebSphere Portal. When modifying these ports for a second installation of WebSphere Portal, we would start numbering at 13010, and continue at similar increments for additional installations.

  8. Save your changes.

  9. Edit...

    $PORTAL_HOME/config/cells/cell/virtualhosts.xml

  10. Locate the host:VirtualHost element for the default_host virtual host. It can be identified by a line similar to the following:

    <host:VirtualHost xmi:id="VirtualHost_1" name="default_host">

  11. Within the default host section, modify the port number for the last aliases element to match the value of the port number you specified as the first transport port in the server.xml file above:

    <host:VirtualHost xmi:id="VirtualHost_1" name="default_host">
    .
    .
    .
    <aliases xmi:id="HostAlias_1" hostname="*" port="9080"/>
    <aliases xmi:id="HostAlias_2" hostname="*" port="80"/>
    <aliases xmi:id="HostAlias_3" hostname="*" port="9443"/>
    <aliases xmi:id="HostAlias_6" hostname="*" port="13000"/>
    </host:VirtualHost>

  12. Locate the host:VirtualHost element for the admin_host virtual host. It can be identified by a line similar to the following:

    <host:VirtualHost xmi:id="VirtualHost_2" name="admin_host">

  13. Within the admin_host section, modify the port numbers for the last two aliases elements to match the values of the third and fourth port numbers you specified in the server.xml file for the administrative server deployed into the WebSphere_Portal appserver:

    <host:VirtualHost xmi:id="VirtualHost_2" name="admin_host">
    .
    .
    .
    <aliases xmi:id="HostAlias_7" hostname="*" port="13002"/>
    <aliases xmi:id="HostAlias_8" hostname="*" port="13003"/>
    </host:VirtualHost>

  14. Save your changes.

  15. Edit...

    <wp_copy_x_root>/config/wpconfig.properties

  16. Modify the WpsHostPort property to match the value of the port number you specified as the first transport port in the server.xml file above:

    WpsHostPort=13000

  17. Save your changes.

  18. Start WebSphere Portal:

    startServer WebSphere_Portal

  19. Verify that you can access WebSphere Portal by requesting the following URL from a browser:
    http://<www.setgetweb.com>:<new_port_number>/wps/portal

    For example,...

    http://www.setgetweb.com:13000/wps/portal

 

Install the next copy of WAS and WebSphere Portal

To install another copy of WAS and WebSphere Portal, you can use the WebSphere Portal installation program.

The WebSphere Portal installation program automatically detects existing installations of WAS. The program can then launch the WAS native installation program to install additional copies of WAS that can coexist with existing installations. To enable coexistence between WAS installations, the WAS installation program provides a means of reconfiguring the ports used by the new installation to prevent port conflicts with other WAS installations and applications.

To install another copy of WAS and WebSphere Portal, do the following:

  1. If you are running WebSphere Portal V4.x and WAS V4.x in a production environment, continue to the next step. Otherwise, stop all copies of WAS and WebSphere Portal running on the machine.

  2. Start the WebSphere Portal installation program, and proceed through the installation panels until you reach the installation type panel.

  3. Select Full, and click Next. The installation program detects the existing installation of WAS and displays information explaining that the WAS installation program will be launched to install another copy of WAS. Click Next to continue.

  4. Proceed through the installation panels, and enter the following information when requested:

    • The directory where the additional copy of WAS is installed, for example,...

      C:\Program Files\WebSphere\AppServer2

    • The directory where the additional copy of WebSphere Portal is installed, for example,...

      C:\Program Files\WebSphere\PortalServer2

    • The administrator ID and password for the additional copy of WebSphere Portal.

  5. On the summary panel listing the components to be installed, click Next. The WebSphere Portal installation program will automatically launch the WAS installation program. Proceed through the installation panels.

  6. When the WAS installation program detects an existing copy of WAS, select Install in a new directory and enter the directory where you want to install the copy. Note that this directory must match the directory you entered for WAS in the WebSphere Portal installation program, for example,...

    C:\Program Files\WebSphere\AppServer2

    Screen capture: Install a new copy of WAS

     

  7. Click Next.

  8. On the coexistence panel, select Reconfigure the product to coexist with other versions of itself. A list of ports is displayed.

    Screen capture: Panel to configure ports for new WAS copy

     

  9. Modify the port numbers with values that are not likely to be used by other copies of WAS or other programs. In the example above, the ports are numbered beginning with 11000 for the second installation of WAS. When modifying these ports for a third installation of WAS, we would start numbering at 11100, and continue at similar increments for additional installations. Note that the port numbers used with the HTTP server are not changed.

  10. Click Next.

  11. Select the Custom installation type, and ensure that the WAS Base features required for WebSphere Portal are selected. Refer to Plan for WebSphere Portal for the list of WAS Base features.

  12. Continue through the panels, and complete the WAS installation. When the WAS installation is finished, the WebSphere Portal installation program will resume automatically and install any required WAS fix packs and interim fixes. The installation program will then install the additional copy of WebSphere Portal.

  13. Configure the ports for the new WebSphere Portal installation to avoid port conflicts with the first WAS installation. Refer to the instructions in Configure the WebSphere Portal ports for coexistence, and increment the port values for the new WebSphere Portal appropriately.

  14. Start all previously installed copies of WAS and WebSphere Portal, and ensure that you can access them.

  15. Verify that the new installation of WAS is running...

    cd $PORTAL_HOME/bin
    startServer server1

  16. Verify that you can access the new WAS by requesting the following URL from a browser:

    http://<www.setgetweb.com>:<new_admin_port>/admin/

    ...where hostname.setgetweb.com is the fully-qualified host.name of the machine where WAS is running and new_admin_port is the port you specified for the administration console during installation.

    For example...

    http://www.setgetweb.com:11002/admin/

  17. Verify that you can access the new WebSphere Portal by requesting the following URL from a browser:

    http://<hostname>:<new_port_number>/wps/portal

    ...where hostname.setgetweb.com is the fully-qualified where WebSphere Portal is running and new_port_number is the transport port specified in the server.xml file. Specify the appropriate port value based on how you configured the new WebSphere Portal. For example, if you incremented the ports so that 13010 is the port for the new WebSphere Portal, you might enter a URL like

    http://www.setgetweb.com:13010/wps/portal

 

Install additional copies of WAS and WebSphere Portal

To install additional copies of WAS and WebSphere Portal, complete the following steps:

  1. If you are running WebSphere Portal V4.x and WAS V4.x in a production environment, continue to the next step. Otherwise, stop all copies of WAS and WebSphere Portal running on the machine.

  2. Install WAS and WebSphere Portal by completing the steps in Install the next copy of WAS and WebSphere Portal.

 

See also

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.