Updating the environment information for WebSphere Application Server

Using NexJ Studio, update the information about WebSphere Application Server (WAS) servers and connections for your deployment.

Before you can update the environment information for WAS, ensure that there is a server or environment file for your deployment. To create a new environment file using NexJ Studio, see Creating environment files.

Ensure that you have the following information about your WAS installation, which is specified during the WAS installation and configuration process:
  • adminUser
  • adminPassword
  • The file name of the JDBC driver, which is located in the WAS_ROOT\nexj\lib directory.
To configure WAS servers and connections in NexJ Studio:
  1. On the Deployment layer, in the Environment tab, open the environment file or the connection and server files for this deployment.
  2. In the environment or server file, on the Overview tab, ensure that Type is set to WebSphere.
  3. In the Deployment Location field, specify the locations for your deployment.

    • If you are deploying a server cluster, specify the location in the following format: protocol://host:port/cell/cluster.

      For example: soap://washost.nexjsystems.local/nexjCell/nexj.

    • If you are deploying a standalone server, specify the location in the following format: protocol://host:port/cell/node/server.

      For example: soap://washost.nexjsystems.local/nexjCell/Node1/server1.

    If you have deployed a plugin for a webserver, append the name of the webserver to the location. For example: soap://washost.nexjsystems.local/nexjCell/nexj;webserver1.

    For multiple webservers, the format is: protocol://host:port/cell/cluster;webserver1[&webserver2...&webserverN].

    In the format examples above, profile, cell, node, server, and webserver values are directory names. They are based on the following directory paths:
    • WAS_ROOT\profiles\profile\config\cells\cell\clusters\cluster
    • WAS_ROOT\profiles\profile\config\cells\cell\nodes\node\servers\server
    • WAS_ROOT\profiles\profile\config\cells\cell\nodes\node\servers\webserver

    The port is optional. The default protocol is SOAP; the default adminPort value for SOAP is 8880 (8879 with a cluster). For Java Remote Method Invocation, the default adminPort value is 2809 (9809 with a cluster).

    In an environment where there are separate servers for the deployment manager and the node agents, the host is the deployment manager server.

  4. In the Deployment User field, specify a user name.
    This can be the WAS administrative user defined when WAS was installed or another user included in the user registry, as long as that user has the deployer and configurator administrative roles defined.
  5. In the Password field, specify a password.
    This can be the WAS administrative password defined when WAS was installed or a password for another user included in the user registry.
  6. In the Overview tab, click the Clustering/Session subtab.
    • If you are deploying a server cluster, select the Distributed (Enable Clustering) option.
    • If you are deploying a standalone server, clear the Distributed (Enable Clustering) option.
  7. In the environment or connections file, select the Data Source Connections tab.
  8. For each data source connection, specify the name of your JDBC driver in the Path field. For example, jtds-1.2.2-7.jar.
  9. Save the updated environment file or server and connections files.
  10. Deploy the updated model.
After these steps are completed, your NexJ application has been deployed on WAS with correct environment information.
Note: If you want to modify the existing administrative user or add any additional administrative users, such as the MessageQueueConnection user, the WAS server process user, or the WAS administrative user, do the following:
  1. Use the NexJ Admin Console to add the users to the user registry.
  2. Using NexJ Studio, update the environment file to include the new or changed users.
  3. Redeploy your application.