This article describes federating or joining a base WebSphere Application Server node to a WebSphere Application Server Network Deployment cell.
Before you begin
There are two ways to federate a base WebSphere Application Server node into a deployment manager cell:
Always use the -includeapps parameter of the addNode command unless you included the applications during a previous federation of the base WebSphere Application Server node into the cell. See the description of the addNode command for more information about its parameters. The administrative console also provides an option for including applications on the base node into the cell.
Federating from the deployment manager administrative console requires a running base WebSphere Application Server.
Consider a scenario where you install both the base WebSphere Application Server product and the Network Deployment product on the same development machine. Installing a production Application Server on the same machine as the deployment manager is not recommended unless the machine has the capacity to handle both jobs. To let both products run at the same time, you must install the Network Deployment product using the coexistence panel, to select ports that do not conflict with the base WebSphere Application Server ports. After installation, stop the Application Server if it is running. Start the deployment manager server. Issue the addNode command from the bin directory of the base node. The deployment manager federates the base node and instantiates the nodeagent server process on the base Application Server node.
Why and when to perform this task
A coexistence environment might have multiple base WebSphere Application Server product installations on one machine. You can federate each installation into the same cell, or into different cells. Whenever the deployment manager federates a node into its cell, it configures the nodeagent server process for the node with a set of default ports. If the base node has the embedded messaging feature, the deployment manager also configures a JMS provider, jmsserver, which is a server process with another set of default ports.
Plan to configure the node agent and the JMS provider with port assignments that differ from the defaults, to verify that there is no conflict with coexisting installation instances that have similar configurations.
Mixed node cells
Ensure that the fix level of the Version 5 WebSphere Application Server product matches or is lower than the fix level of the Network Deployment product. For example, in a mixed node environment you can federate a Version 5.0.2 base node into a Version 5.1 deployment manager cell but you cannot federate a Version 5.1 base node into a V5.0.x deployment manager cell.
Steps for this task
Issue the command from the bin directory of the Application Server installation root.
For example, suppose you federate an installation instance that has a node name of MyNode.
What to do next
To continue, return to one of these topics: