Creating Deployment manager profile:

It contains admin console, node and dmgr process. By default it won’t contain any server
to deploy applications and run the applications.
Using dmgr we can create n no of servers under one profile.
Click profile creation wizard from first step console.

Click Next
Here we have to select create deployment manager profile.

Click Next
Click Next

Click Next
Click Next

Click Next
Uncheck Run the Application Server process as a Windows service
Click Next
Click Next
Click Finish
Launch first step console. There u will find only one difference among other installations.
That is start the Deployment manager.
----- For start/stop dmgr using start/stopmanager.bat

To stop the dmgr process

 Login in to Admin console of dmgr there we can see lot of changes when compared to base
package admin console.
Base package admin console (Application server profile)

 Log in to dmgr admin console and do some r&d on that

http://localhost:9062/ibm/console

Creating Custom Profile:

---- Using profile creation wizard

Click Next
Profile Type select Custom profile

Click Next

Click Next
Click Next

Click Next
Click Next

Click Next
Click Finish
Federation
It is a process of adding a node either from application server profile or custom profile to
deployment manager profile. Once the node of either application server profile or custom
profile is available with dmgr we can create n no of servers under that node and we can
manage from the same dmgr console.
------ We can add a node by using a command
./addnode.sh <host-name of dmgr> <soap connector of dmgr> -includeapps
–username <user name> -password <password> (If global security is enabled we have to
give the user name and password).
------ At the time of federation a process called node agent will be created to communicate
between dmgr profile and federated profile.
------ A node which is having a node agent will be called as managed node.
------ A node which doesn’t have node agent will be called as an unmanaged node.
------ After federation and configuration if the node agent is down there is no impact for the
federated server profiles and applications. But we can’t do the administration activities through
the dmgr console.
------ If the dmgr is down at that time also there is no impact for the federated server profiles
and applications. We can access those applications normally.
------ When we stop dmgr and node agent we can access server and applications.
 Go to application server under server tab on left side pane.

Click New

Then you will get a error message see the below screen shot

------ For the first time when we login to the dmgr console there are no nodes that support
servers in the configuration. For that we have to add a node either from Application server
profile or Custom profile to the Deployment manager profile. Once the node of either
application server profile or custom profile is available with dmgr we can create n no of servers
under that node and we can manage from the same dmgr console.
Federation Process
Federation(Adding Node from Appsrv01 to Dmgr01)
----Go to <profiles/AppSrv01/bin>
----go to CMD prompt and execute the command
<Appserver/bin>addnode.bat <hostname Dmgr> <SOAP CONNECTOR PORT_Dmgr> -includeapps.

After the successful federation we have to add the n no of servers under App_Node01
Adding servers in dmgr console.
Go to dmgr admin console. Go to servers and click Application servers

Click New

Type Server name

Click Next
Click Next

Click Next

Click Next
Click finish

Click save changes

Check synchronize changes with node.
Click save.
Go to Sever and Application servers on left pane.

You will see the server3

Select server3 and click start button.

Go to CMD prompt check the status of the servers

Go to profiles/Appsrv01/bin
To stop the dmgr process runs the following command in CMD prompt.

To start the dmgr process runs the following command in CMD prompt

Federate Custom Profile:

------ Before federating the custom profile we have to start the deployment manager
Jump to Custom01 profile path
Execute the command to add a node to dmgr
------ Login to the dmgr console

Go to server and application servers

Click on Application servers

Click New
From the drop down select Custom_Node01
Enter server name: server4

Click Next
Click Next

Click Next

Click Finish
Click save changes

Check Synchronize changes with Nodes.

Click save changes.
Select server4 and click start

Through command line we can start/stop server4

---- For start/stop node agent using

Start/stopnode.bat

---- Synchronization Problem (If proper synchronization hasn’t done) follow below command.

profiles/Appsrv01/bin>syncnode.bat <hostname of dmgr> <soap connector of dmgr>

Note: In this case we have to stop the node and synchronization has to do.

Uninstallation:

---- Go to WAS root and _uninst folder

C:\IBM_ND_6.0\WebSphere\AppServer\_uninst
Click uninstall.exe
---- If we un-install directly by deleting or removing from control panel it doesn’t un-install
properly. It will through errors while fresh installation.

C:\windows\”vpd.propertiesfile”---- This property file will update in the time of installation and
Uninstallation.

Uninstallation by using silent Mode

By using below command in CMD prompt.

Deleting Profiles using CMD prompt:

Deleting all Profiles at a time:

---- We can find port no’s in

C:\IBM_ND_6.0\WebSphere\AppServer\profiles\AppSrv01\config\cells\dmgr_cell01\nodes\Cus
tom_Node01\serverindex.xml

One more method to find ports

C:\IBM_ND_6.0\WebSphere\AppServer\profiles\Dmgr01\logs\portdef.props
--- In this case if do any changes in portdef.props it will not effect. We have to do modification
in serverindex.xml at that time only it will effect.