Deleting Profile:

wasprofile - The available modes are:

1. create,

2. augment,

3. delete,

4. unaugment,

5. deleteAll,

6. listProfiles,

7. getName,

8. getPath,

9. validateRegistry,

10.validateAndUpdateRegistry,

11.help

For detailed help on each mode enter: -<mode> -help. For example, -create -help.

3. Delete
When profile server is not running.

C:\Program Files\IBM\WebSphere\AppServer\bin>wasprofile -delete -profileName

AppSrv01

INSTCONFSUCCESS: Success: The profile no longer exists.

ONLY LOG Folder will remain … all other Directory will be deleted.

When profile server is running.

C:\Program Files\IBM\WebSphere\AppServer\bin>wasprofile -delete -profileName

Dmg

r01

INSTCONFPARTIALSUCCESS: The profile no longer exists, but errors occurred.

Bin folder is cleared , but Some Folder Remains.

Verify After deleting.

C:\Program Files\IBM\WebSphere\AppServer\bin>wasprofile -listProfiles

[]

U can delete all Profiles in one shot.

C:\Program Files\IBM\WebSphere\AppServer\bin>wasprofile -deleteAll

INSTCONFSUCCESS: Success: All profiles were deleted.

CREATING Profile
wasprofile -create
-profileName profile_name
[-profilePath fully_qualified_profile_path]
[-templatePath template_path]
[-nodeName node_name]
[-cellName cell_name]
[-hostName host_name]
[-serverName server_name]
[-dmgrHost host_name]
[-dmgrPort SOAP port]
[-startingPort starting_port | -portsFile filepath]
[-isDefault]
[-exthttp http_server_port]
[-os400passwords]
[-validationlist os400_password_validation_list]
[-debug]

To Get Process ID:

SystemAdministrator>> Deployment Manager >> Runtime.

Creating Profile:
C:\Program
Files\IBM\WebSphere\AppServer\bin\ProfileCreator>>
pctWindows.exe
Adding Node:
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>addnode shreeji-66ce9feNode01
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0001I: Begin federation of node shreeji-66ce9feNode01 with Deployment
Manager at shreeji-66ce9feNode01:8879.
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to connect to
host shreeji-66ce9feNode01 at port 8879., resulting from:
java.lang.reflect.InvocationTargetException
ADMU4123E: Ensure that the Deployment Manager is running on the specified host
and port.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file: C:\Program
Files\IBM\WebSphere\AppServer/profiles/AppSrv01\logs\addNode.log
After restart of DMGR
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>addnode shreeji-6
6ce9fe
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0001I: Begin federation of node shreeji-66ce9feNode01 with Deployment
Manager at shreeji-66ce9fe:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
shreeji-66ce9fe:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node shreeji-66ce9feNode01
ADMU7702I: Because server1 is registered to run as a Windows Service, the
request to stop this server will be completed by stopping the
associated Windows Service.
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\stopServ
er.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server server1 stop completed.

ADMU0024I: Deleting the old backup directory.

ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: shreeji-66ce9feNode01
ADMU0014I: Adding node shreeji-66ce9feNode01 configuration to cell:
shreeji-66ce9feCell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: shreeji-66ce9feNode01
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:2424
ADMU9990I:
ADMU0300I: Congratulations! Your node shreeji-66ce9feNode01 has been
successfully incorporated into the shreeji-66ce9feCell01 cell.
ADMU9990I:
ADMU0306I: Be aware:
ADMU0302I: Any cell-level documents from the standalone
shreeji-66ce9feNode01Cell configuration have not been migrated to
the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the shreeji-66ce9feCell01 Deployment
Manager with values from the old cell-level documents.
ADMU9990I:
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 shreeji-66ce9feCell01 cell using
wsadmin $AdminApp or the Administrative Console.
ADMU9990I:
ADMU0003I: Node shreeji-66ce9feNode01 has been successfully federated.

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

Adding Application

Installing...

If there are enterprise beans in the application, the EJB deployment process can take several minutes. Please do not save
the configuration until the process completes.

Check the SystemOut.log on the Deployment Manager or server where the application is deployed for specific information about the
EJB deployment process as it occurs.

ADMA5016I: Installation of bank_war started.

ADMA5067I: Resource validation for application bank_war completed successfully.

ADMA5058I: Application and module versions validated with versions of deployment targets.

ADMA5005I: The application bank_war is configured in the WebSphere Application Server repository.

ADMA5053I: The library references for the installed optional package are created.

ADMA5005I: The application bank_war is configured in the WebSphere Application Server repository.

ADMA5001I: The application binaries are saved in C:\Program

Files\IBM\WebSphere\AppServer/profiles/Dmgr01\wstemp\103673538\workspace\cells\shreeji-
66ce9feCell01\applications\bank_war.ear\bank_war.ear

ADMA5005I: The application bank_war is configured in the WebSphere Application Server repository.

SECJ0400I: Successfuly updated the application bank_war with the appContextIDForSecurity information.

ADMA5011I: The cleanup of the temp directory for application bank_war is complete.

ADMA5013I: Application bank_war installed successfully.

Application bank_war installed successfully.

NOW Start Server that contains this war . and u r done

Adding new Profile and node to DMGR

1. Create DMGR
2. Create Profile appServer01
3. Start dmgr
4. Start appserver
5. Start app server’s consol
6. Goto Command prompt
7. Goto appserv01
8. Go to bin
9. addNode MachineName

10. Node will be federated Consol of app server will be un available.

O/p

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01>cd bin

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>addnode SHREEJI-

6CE9FE

ADMU0116I: Tool information is being logged in file C:\Program

Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\addNode.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU0001I: Begin federation of node localhostNode01 with Deployment Manager at

SHREEJI-66CE9FE:8879.

ADMU0009I: Successfully connected to Deployment Manager Server:

SHREEJI-66CE9FE:8879

ADMU0505I: Servers found in configuration:

ADMU0506I: Server name: server1

ADMU2010I: Stopping all server processes for node localhostNode01

ADMU7702I: Because server1 is registered to run as a Windows Service, the

request to stop this server will be completed by stopping the

 associated Windows Service.

ADMU0116I: Tool information is being logged in file C:\Program

Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\stopSer

er.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU3100I: Reading configuration for server: server1

ADMU3201I: Server stop request issued. Waiting for stop status.

ADMU4000I: Server server1 stop completed.

ADMU0024I: Deleting the old backup directory.

ADMU0015I: Backing up the original cell repository.

ADMU0012I: Creating Node Agent configuration for node: localhostNode01

ADMU0014I: Adding node localhostNode01 configuration to cell: localhostCell01

ADMU0016I: Synchronizing configuration between node and cell.

ADMU0018I: Launching Node Agent process for node: localhostNode01

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:

4040

ADMU9990I:

ADMU0300I: Congratulations! Your node localhostNode01 has been successfully

incorporated into the localhostCell01 cell.

ADMU9990I:

ADMU0306I: Be aware:

ADMU0302I: Any cell-level documents from the standalone localhostNode01Cell

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: 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 localhostCell01 cell using wsadmin

$AdminApp or the Administrative Console.

ADMU9990I:

ADMU0003I: Node localhostNode01 has been successfully federated.

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