Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS

---

 

Configure external WebSphere application servers

After creating a middleware server representation of an external WebSphere^® application server in the administrative console, update a few configuration settings so that they are defined specifically for your WebSphere Application Server installation.

 

Before you begin

• If you have a large topology of WebSphere application servers, you can use the migration toolkit to create the representations of these servers in the environment. See Migrate large topologies of external WebSphere application servers for more information.

• Federate the node that is running the WebSphere application server and create a representation of the server in the administrative console.

 

About this task

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 from the administrative console, configure the server operations for the WebSphere Application Server middleware server representation.

 

Procedure

1. Update the WebSphere variables so that they match the settings on the node that is running the WebSphere Application Server. In the administrative console, click Environment > WebSphere Variables. Edit the following variables:

   WAS51_HOME

   Specifies the location of the WebSphere Application Server Version 5.1 installation.

   Default values are set at the cell scope level:

   c:\Program Files\IBM\WebSphere\AppServer

   /opt/IBM/WebSphere/AppServer

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

   WAS6_HOME

   Specifies the location of the WebSphere Application Server Version 6 install location.

   Default values are set at the cell scope level:

   c:\Program Files\IBM\WebSphere\profiles\AppServer

   opt/IBM/WebSphere/profiles/AppServer

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

2. Update server operations for the WebSphere Application Server to include the user name and password.

   1. In the administrative console, click Servers > Other middleware servers >External WebSphere Application Server > WebSphere_Application_Server > Server operations.

   2. Edit the start and stop server operations to include the user name and password that is required to run these commands.

 

What to do next

• To configure your remaining WebSphere Application Servers, create a server template of your current WebSphere Application Server.

• To view the log files for your WebSphere Application Server in the administrative console, use the external log viewing service. This service is enabled by default. The following directories are configured by default:

  • ${INSTALL_ROOT}/logs/${WAS_SERVER_NAME}

• To edit configuration files for your WebSphere Application Server, use the external configuration service. The following files are included by default:

  • {$WAS_SERVER_HOME}/var/conf/server.xml

• After creating representations of all the WebSphere Application Servers, you can add the representations to a dynamic cluster.

• WAS6_PROFILE_NAME - Default values set at the APPSERVER01 should be set at the server level.

---

Previous topic
Federating middleware nodes

Next topic

Creating middleware server templates

Next topic

View middleware server configuration files

Next topic

Configure the external log viewing service

Next topic

Creating dynamic clusters

 

Related concepts

Migration toolkit

 

Related tasks

Migrate large topologies of external WebSphere application servers
Configure middleware server operations
Configure WebSphere variables Adding middleware servers to configurationsAdding assisted life-cycle middleware servers

 

Related reference

Middleware server creation administrative tasks