Date Created: Sun 02-Mar-2008

Related Document Categories:

Get my WebSphere Application Server course here >>

Very basic overview of Installing Network Deployment Manager & Application Server for WebSphere 5.1 on Windows.

Installing Deployment Manager

start the deployment manager

Check the admin console is running


Login to check that we have a correctly running dmgr

What we need to do now is create a profile for a node and federate it.

We have to be on the application server (node)

Look for the soap port in serverindex.xml located: C:\ws51\profiles\dmgr\config\cells\cell01\nodes\dmgr

<specialEndpoints xmi:id="NamedEndPoint_4" endPointName="SOAP_CONNECTOR_ADDRESS">
<endPoint port="60879" host="SteveRT60" xmi:id="EndPoint_4"/>


Adding a node via the admin console

Adding node
ADMU0001I: Begin federation of node node01 with Deployment Manager at

ADMU0009I: Successfully connected to Deployment Manager Server:

ADMU0505I: Servers found in configuration:

ADMU0506I: Server name: server1

ADMU2010I: Stopping all server processes for node node01

ADMU0510I: Server server1 is now STOPPED

ADMU0024I: Deleting the old backup directory.

ADMU0015I: Backing up the original cell repository.

ADMU0012I: Creating Node Agent configuration for node: node01

ADMU0014I: Adding node node01 configuration to cell: cell01

ADMU0016I: Synchronizing configuration between node and cell.

ADMU0018I: Launching Node Agent process for node: node01

ADMU0020I: Reading configuration for Node Agent process: nodeagent

ADMU0022I: Node Agent launched. Waiting for initialization status.

ADMU0030I: Node Agent initialization completed successfully. Process id is: 6100

ADMU0523I: Creating Queue Manager for node node01 on server jmsserver

ADMU0525I: Details of Queue Manager creation may be seen in the file: createMQ.node01_jmsserver.log


ADMU0300I: Congratulations! Your node node01 has been successfully incorporated into the cell01 cell.


ADMU0306I: Be aware:

ADMU0302I: Any cell-level documents from the standalone node01 configuration have not been migrated to the new cell.

ADMU0307I: You might want to:

ADMU0303I: Update the configuration on the cell01 Deployment Manager with values from the old cell-level documents.


ADMU0306I: Be aware:

ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell.

ADMU0307I: You might want to:

ADMU0305I: Install applications onto the cell01 cell using wsadmin $AdminApp or the Administrative Console.


ADMU0003I: Node node01 has been successfully federated.

The new node will not be available in the console until you log in again. This is what you see when you log back in.

If we look at the application servers we will see the server1 that was automatically created by the application server (node install)

If you do not like the name server1, you could delete this server and create servers with new names.

Creating a cluster

First we have to create another server: server2

We now have a cluster for with two servers 2, server 3. Server 1 is not ins the cluster. As you can see it al depends on the way in which you want to add your servers/clusters etc. There is more than one way to skin a cat..

Get my WebSphere Application Server course here >>

Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many leading brands around the world. Steve specialises in JEE, DevOps and Thought Leadership.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.

  • Linked In
  • Twitter
  • About Me
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide


  • WebSphere Courses


WebSphere Categories

Other Categories