Network Deployment Setup
- If you are going to use stand-alone WebSphere MQ, install that first.
- Install the base WAS product on each machine that is to become a node in the cell. Later, when you are ready to create your cluster, there are several ways to federate a stand-alone appserver into the deployment manager cell.
To create multiple configuration instances on the machine, use wsinstance.sh.
- Install the WAS Network Deployment product on a machine. Only one system hosts the deployment manager.
As the deployment manager federates base WAS nodes, it expands the cell that it manages. Although you can install a base WAS on the same machine as the deployment manager, it is not usual in a production environment unless you have a machine with the capacity to host both products. Co-deploying WebSphere ND and Base on the same box can lead to complications and is discouraged.
The deployment manager is the central administrative manager. It does not install the base WAS product on other machines. The only functions supported in the Network Deployment installation are the deployment manager and its associated administrative programs.
- Start the deployment manager process using one of the following methods:
- As a monitored process, which restarts automatically if a failure occurs
- As an unmonitored process, which is what the startManager command does
Run the startmanager utility from the /bin directory of the deployment manager installation root.
For production systems, running the deployment manager as a monitored process is recommended.
- Run the addNode command on every node that you plan to federate into the cell.
The addNode command incorporates a base WAS product node into a deployment manager cell. You must run this tool on every system that you plan to make part of a Network Deployment cell. There are several parameters for the addNode command, but the most important are -includeapps , the host name of the deployment manager node, the JMX connector type, and the JMX port of the deployment manager node.
The deployment manager instantiates the node agent process, nodeagent , on the Application Server node. (It also instantiates the WebSphere JMS provider, jmsserver , if you installed the embedded messaging server feature on the base node.)
Alternatively, you can use the administrative console of the deployment manager to add running Application Server nodes to the cell.
- Enable the appropriate level of security after the installation is complete.
- Develop and unit test application components.
Load existing application components and modules into your development environment and debug them.
- Assemble code into a main application module or enterprise archive file.
- Start all servers in the test environment.
- Deploy your applications in the test environment.
- Test all applications thoroughly.
Follow normal test procedures as you move the test environment into production. Review the information in the Migrating topic to understand what look for. In particular, review the table at the end of the topic that links you to specific recommendations and practices.
You must configure your migrating applications to ensure that they migrate in the way you want.
- Prepare and monitor the environment into which you deploy applications.
- Adjust application code, configurations, and system settings to improve performance.
- Fix any known problems.
- Set up your production system by configuring all server processes for monitoring by their operating systems.
Results
One can create a working WAS cell.
What to do next
Use the administrative console or other administrative tools to observe and control the incorporated nodes, and the resources on these nodes. The console provides a central location for configuring, monitoring, and controlling all Application Servers on all nodes within the cell.
Setting up a multinode environment
Migrating and coexisting
Creating servers in coexistence or multiple instance environments
Changing HTTP transport ports
addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command
Port number settings in WAS versions
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.