Determine the kind of profile you want to create, which in turn determines the template to use for your

new profile (using the -templatePath option). The following templates are available: default.wbiserver: for a WebSphere Process Server stand-alone server profile, which defines a stand-alone server. dmgr.wbiserver: for a WebSphere Process Server deployment manager profile, which defines a deployment manager. A deployment manager provides one administrative interface to a logical group of servers on one or more workstations. managed.wbiserver: for a WebSphere Process Server custom profile, which, when federated to a deployment manager, defines a managed node. If you have decided that your solution requires a deployment environment, your runtime environment requires one or more managed nodes. A custom profile contains an empty node that you must federate into a deployment manager cell to make operational. Federating the custom profile changes it into a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating. Also, WebSphere Process Server profiles cannot use a WebSphere Enterprise Service Bus deployment manager, but WebSphere Enterprise Service Bus profiles can use a WebSphere Process Server deployment manager. default.esbserver: for a WebSphere Enterprise Service Bus stand-alone server profile, which defines a stand-alone server. dmgr.esbserver: for a WebSphere Enterprise Service Bus deployment manager profile, which defines a deployment manager. managed.esbserver: for a WebSphere Enterprise Service Bus custom profile, which, when federated to a deployment manager, defines a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating. WebSphere Enterprise Service Bus profiles can use a WebSphere Enterprise Service Bus or WebSphere Process Server deployment manager.
Examples

You can use the manageprofiles commandto create a deployment manager profile. The deployment manager administers the application servers that are federated into the cell. Required parameters -create Creates the profile. (Required) -profileName Specifies the name of the profile. (Required) -templatePathtemplate_path Specifies the path to the template files in the

installation root directory. (Required)Use the following format:

-templatePath install_root/profileTemplates/wxdcg_augment /dmgr ./manageprofile.sh -create -profileName profile01 templatePath /usr/IBM/WebSphere/AppServer/profileTemplates/dmgr enableAdminSecurity true serverName mgmt_server -nodeName test_node -cellName test_cell adminUserName was7 adminPassword was7

Create a custom profile

./manageprofile.sh -create -profileName profile01 -templatePath install_root/profileTemplates/managed.wbiserver Fedrate the NODE to DMGR

Steps for this task Start the deployment manager. Start the deployment manager either by selecting Start the deployment manager from its First Steps console or by entering the following command (where profile_root represents the installation location of the deployment manager profile, by default
install_root/profiles/deployment_manager_profile_name. profile_root/bin/startManager.sh

Issue the addNode command. Issue one of following commands, depending on platform:
./addNode.sh

deployment_manager_host deployment_manager_SOAP_port