1. Server Manager Guide
  2. Separate WAS Profiles

Separate WAS Profiles

It is recommended that you create separate WAS profiles when managing:

  • Multiple environments (such as production, test, and development)

  • Multiple instances of a web-based server (such as HTML Web Server, Transaction Server, and Business Services Server) in a Network Deployment (ND) WAS installation. Also in a ND WAS installation all the different WAS profiles can share one web server definition.

  • Multiple foundations of JD Edwards EnterpriseOne (such as Tools Release 9.0, 9.1 etc.)

  • Transaction Server

Note:

During profile creation, it is recommended that you specify your starting port number to a value that will give you a sufficient amount of port numbers (for example, 1000) between the last profile you created so as to not conflict with other currently assigned ports and ports that will be assigned in the future.

Note:

If you configure the WebSphere Application Server SOAP_CONNECTOR_ADDRESS port number outside of Server Manager (for example, from the WebSphere Administrative Console), you must restart the Management Agent that is managing that WebSphere Application Server instance. This is required because Server Manager uses that port to communicate with the WebSphere Application Server and only acquires the port value on start up of the Management Agent.

Note:

WAS Base/Standalone. The general recommendation is to use a single WAS profile to deploy and manage multiple instances of EnterpriseOne web-based servers (such as HTML Web Server, PIM Sync Server, and Business Services Server). This is because of the limitation of WAS Base/Standalone functionality and how the web server plug-ins are used and modified across profiles. The exception to the general recommendation is the Transaction Server. The recommendation is to deploy and manage the Transaction Server in a separate WAS profile. This is because of conflicts between HTML Server and Transaction Server within the same profile. In WAS standalone, when creating separate profiles you must create a separate web server definition and have a separate HTTP Server. See IBM WebSphere Administration documentation for more details on this requirement.