How to Federate the application server profile and custom profile with the Deployment Manager profiles

Here we learn how to federate the profile.
So before doing this activity we have to identify some required parameter are full fill or not.

1. There should be one Dmgr  profile has to be created.
2. At least one application server profile or at least one custom profile should be there
3. Dmgr profile manager should be up
4. know about the soap port number and hostname of the dmgr profile.

Syntax of profile Federation:-

was_home/bin> ./addNode.sh -profilename name of profile hostname_of_dmgr soap_port_dmgr

Example:-

Note:- Notice in red mark line for better understanding.

D:\IBM\WebSphere\AppServer\bin>./addNode.sh -profileName appSrv03 172.22.7.24  8879

ADMU0116I: Tool information is being logged in file
           D:\IBM\WebSphere\AppServer\profiles\AppSrv03\logs\addNode.log
ADMU0128I: Starting tool with the AppSrv03 profile
CWPKI0308I: Adding signer alias "CN=C17548.intellectdesign.com, " to local
           keystore "ClientDefaultTrustStore" with the following SHA digest:
           D1:90:84:FA:AF:F8:6D:58:9A:B1:BD:F3:0E:CA:5E:F8:BE:B7:2F:63
CWPKI0308I: Adding signer alias "default" to local keystore
           "ClientDefaultTrustStore" with the following SHA digest:
           0D:9A:91:0D:7A:24:AF:FD:D6:26:7A:4E:8B:56:06:D4:54:A7:9A:08
CWPKI0308I: Adding signer alias "datapower" to local keystore
           "ClientDefaultTrustStore" with the following SHA digest:
           A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17
ADMU0001I: Begin federation of node C17548Node02 with Deployment Manager at
           172.22.7.24:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: --------1
           172.22.7.24:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1 ------2
ADMU2010I: Stopping all server processes for node C17548Node02  ---------3
ADMU0510I: Server server1 is now STOPPED  ---4 
ADMU0024I: Deleting the old backup directory.  ---5 
ADMU0015I: Backing up the original cell repository. ---6
ADMU0012I: Creating Node Agent configuration for node: C17548Node02  ---7
ADMU0014I: Adding node C17548Node02 configuration to cell: C17548Cell01 ---8
ADMU0016I: Synchronizing configuration between node and cell. --9
ADMU0018I: Launching Node Agent process for node: C17548Node02
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:
           1452  ------------10 
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent  --------11
ADMU0506I: Server name: server1      ------------12


ADMU0300I: The node C17548Node02 was successfully added to the C17548Cell01
           cell.


ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone C17548Cell01
           configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the C17548Cell01 Deployment Manager with
           values from the old cell-level documents.


ADMU0306I: Note:
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 C17548Cell01 cell using wsadmin
           $AdminApp or the Administrative Console.


ADMU0003I: Node C17548Node02 has been successfully federated.


Note:- When any profile is federate with any profile in dmgr then a nodeagent will create.
later i will disscuss about the node agent.