Example profile augmentation commands to help you augment stand-alone server, deployment manager, and custom profiles using the manageprofiles command on your installation.
Table 1 shows manageprofiles command parameters with example values used to create a stand-alone server profile.
Parameter | Value |
---|---|
-augment | N/A |
-templatePath | "install_root\profileTemplates\default.esbserver" (must be fully qualified) |
-profileName | "AppServ03" |
-adminPassword | "admin_pwd" |
-adminUserName | "admin_id" |
-dbType | "DERBY_EMBEDDED" |
-dbUserId | "cei_id" |
-dbPassword | "cei_pwd" |
-ceiDbName | "event" |
-dbDelayConfig | "true" |
-ceiDbAlreadyConfigured | "false" |
-dbType | "DERBY_EMBEDDED" |
-dbName | "WPRCSDB" |
-dbCreateNew | "true" |
-dbDelayConfig | "false" |
-dbCommonForME | "false" |
-fileStoreForME | "false" (cannot be true when -dbCommonForME is also true) |
-configureBSpace | "false" |
Table 2 shows manageprofiles command parameters with default values that do not normally have to be changed.
The following command example augments a WebSphere Application Server deployment manager profile called Dmgr04 with WebSphere Process Server functionality on a Windows server. The parameters in Table 3 and Table 4 specify the following:
Table 3 shows manageprofiles command parameters with example values used to create a deployment manager profile.
Parameter | Value |
---|---|
-augment | N/A |
-templatePath | "install_root\profileTemplates\dmgr.esbserver" (must be fully qualified) |
-profileName | "Dmgr04" |
-adminPassword | "admin_pwd" |
-adminUserName | "admin_id" |
-ndtopology | "false" (configuration of a deployment environment is not supported during profile augmentation) |
-dbType | "DERBY_NETWORKSERVER" |
-dbName | "WPRCSDB" |
-dbCreateNew | "true" |
-dbDelayConfig | "false" |
-dbHostName | "localhost" |
-dbUserId | "db_id" |
-dbPassword | "db_pwd" |
-dbServerPort | "1529" |
Table 4 shows a manageprofiles command parameter with a default value that does not normally have to be changed.
The following command example augments a WebSphere Application Server custom profile called Custom05 with WebSphere Process Server functionality on a Windows server. This example is set to operate with the deployment manager profile created above.
The parameters in Table 5 specify the following:
Table 5 shows manageprofiles command parameters with example values used to create a custom profile.
Parameter | Value |
---|---|
-augment | N/A |
-templatePath | "install_root\profileTemplates\managed.esbserver" (must be fully qualified) |
-profileName | "Custom05" |
-dmgrHost | "localhost" |
-dmgrPort | "8902" (To find the -dmgrPort value, go to the dmgr_profile_root\logs directory for the deployment manager associated with this custom profile. In this directory, open the AboutThisProfile.txt file and find the value for the entry "Deployment manager SOAP connector port:".) |
-dmgrAdminPassword | "admin_pwd" |
-dmgrAdminUserName | "admin_id" |
-ndtopology | "false" |
-dbType | "DERBY_NETWORKSERVER" |
-dbJDBCClasspath | "install_root\derby\lib" |