Configuring external WebSphere application servers

You can create middleware server representations of WebSphere® application servers that are in other cells.

Before you begin

About this task

External WebSphere application servers are application servers that reside outside of your Intelligent Management cell. For example, you might have two cells: one cell that is running WebSphere Application Server application servers, and another cell that is running Intelligent Management. In this scenario, you can install the node agent on the WebSphere nodes in the other cell, federate these nodes into your Intelligent Management cell, and create representations of your external WebSphere application servers. Using external WebSphere application servers can be useful in a migration scenario because you can continue to route traffic to servers that are running an older version with the ODR while you work on migrating your servers and applications to the latest version. However, external WebSphere application servers are assisted life-cycle servers and therefore do not receive the full life-cycle management that is provided when you create application servers directly in your Intelligent Management cell.

When you configure the external WebSphere application servers, if you installed WebSphere Application Server in a location other than the default directory, update the WebSphere variables so that the installation directory is correct. To perform server operations on your server, you must configure the server operations for the WebSphere Application Server middleware server representation.

Deprecated feature Deprecated feature: Intelligent Management support for using external WebSphere application servers is deprecated. Support for using the administrative console to configure these servers is removed. Use wsadmin scripting to manage these servers.depfeat

Procedure

  1. Update the WebSphere variables so that they match the settings on the node that is running the WebSphere Application Server. Follow the directions in the topic on modifying variables using wsadmin scripting to edit the following variables:
    WAS51_HOME
    Specifies the location of the WebSphere Application Server installation.
    Default values are set at the cell scope level:
    [Windows] c:\Program Files\IBM\WebSphere\AppServer
    [AIX HP-UX Solaris] /opt/IBM/WebSphere/AppServer

    If the home directory is different on different nodes in your configuration, create the WAS51_HOME variable for a specific node.

    WAS6_HOME
    Specifies the location of the WebSphere Application Server Version 6 installation location.
    Default values are set at the cell scope level:
    [Windows] c:\Program Files\IBM\WebSphere\profiles\AppServer
    [AIX HP-UX Solaris] opt/IBM/WebSphere/profiles/AppServer

    If the home directory is different on different nodes in your configuration, create the WAS6_HOME variable for a specific node.

    WAS6_PROFILE_NAME
    Specifies the name of the profile in which the external WebSphere Application Server server resides on its physical computer.
  2. Launch wsadmin scripting with a username and password so that you can start and stop server operations.

    Follow the directions in the topic on starting the wsadmin scripting client to enable security. The startMiddlewareServer command and the stopMiddlewareServer command require a user name and password to run.

What to do next

Task topic    

Terms and conditions for information centers | Feedback

Last updated: March 19, 2013 10:03 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twve_mwsexternal
File name: twve_mwsexternal.html