how to federate the node to deployment manager in websphere?

>> by using addNode.bat command u can federate the node to the dmgr.
> please follow the below command for the node federation.

command:
---------
C:\Program Files\IBM\WebSphere\AppServer\bin>addNode.bat localhost 8879 -profileName AppSrv02 -username wasadmin -password wasadmin

>>after the command the below sripts is available.

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv02\logs\addNode.log
ADMU0128I: Starting tool with the AppSrv02 profile
CWPKI0308I: Adding signer alias "CN=localhost, O=IBM, C=US" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
BF:3F:09:3F:DD:2A:34:77:0E:50:0B:71:49:63:BB:A4:B2:CA:1B:3F
CWPKI0308I: Adding signer alias "dummyclientsigner" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
0B:3F:C9:E0:70:54:58:F7:FD:81:80:70:83:A6:D0:92:38:7A:54:CD
CWPKI0308I: Adding signer alias "dummyserversigner" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
FB:38:FE:E6:CF:89:BA:01:67:8F:C2:30:74:84:E2:40:2C:B4:B5:65
ADMU0001I: Begin federation of node vision2kNode01 with Deployment Manager at localhost:8879.
ADMU0001I: Begin federation of node vision2kNode01 with Deployment Manager at localhost:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: localhost:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node vision2kNode01
ADMU0512I: Server server1 cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: vision2kNode01
ADMU0014I: Adding node vision2kNode01 configuration to cell: localhostCell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: vision2kNode01
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:
4100
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: server1
ADMU9990I:
ADMU0300I: The node vision2kNode01 was successfully added to the localhostCell01 cell.
ADMU9990I:
ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone localhostCell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the localhostCell01 Deployment Manager
with values from the old cell-level documents.
ADMU9990I:
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 localhostCell01 cell using wsadmin $AdminApp or the Administrative Console.
ADMU9990I:
ADMU0003I: Node vision2kNode01 has been successfully federated.

C:\Program Files\IBM\WebSphere\AppServer\bin>