Example profile creation commands to help you create 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 |
---|---|
-create | N/A |
-templatePath | "install_root\profileTemplates\default.esbserver" (must be fully qualified) |
-profileName | "my_WESBSA_profile" |
-enableAdminSecurity | "true" |
-adminPassword | "admin_pwd" |
-adminUserName | "admin_id" |
![]() |
"manual" |
-dbServerPort | "50000" |
-ceiDbName | "event" |
-dbDelayConfig | "false" |
-dbHostName | "localhost" |
-ceiDbAlreadyConfigured | "false" |
-dbType | "DB2_Universal" |
-dbName | "WPRCSDB" |
-dbCreateNew | "false" |
-dbDelayConfig | "true" |
-dbUserId | "db_id" |
-dbPassword | "db_pwd" |
-dbDriverType | "4" |
-dbHostName | "localhost" |
-dbServerPort | "50000" |
-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.
Parameter | Default values |
---|---|
-profilePath | "install_root\profiles\my_WESBSA_profile" |
-hostName | "host_name" |
-nodeName | "host_nameNodenode_number" |
-cellName | "host_nameNodenode_numbercell_numberCell" |
![]() |
"true" |
![]() |
"localsystem" |
![]() |
"Administrator" |
-dbOutputscriptDir | "install_root\profiles\my_WESBSA_profile\dbscripts\CEI_event" |
-dbJDBCClasspath | "install_root\universalDriver_wbi\lib" |
-dbJDBCClasspath | "install_root\universalDriver_wbi\lib" |
-dbOutputScriptDir | "install_root\profiles\my_WESBSA_profile\dbscripts\CommonDB\DB2\WPRCSDB" |
The following command example creates a deployment manager profile called my_WESBDMGR_profile on a Windows server.
Table 3 shows manageprofiles command parameters with example values used to create a deployment manager profile.
Parameter | Value |
---|---|
-create | N/A |
-templatePath | "install_root\profileTemplates\dmgr.esbserver" (must be fully qualified) |
-profileName | "my_WESBDMGR_profile" |
-enableAdminSecurity | "true" |
-adminPassword | "admin_pwd" |
-adminUserName | "admin_id" |
![]() |
"manual" |
-ndtopology | "false" |
-dbType | "DERBY_NETWORKSERVER" |
-dbName | "WPRCSDB" |
-dbCreateNew | "true" |
-dbDelayConfig | "false" |
-dbUserId | "db_id" |
-dbPassword | "db_pwd" |
-dbHostName | "localhost" |
-dbServerPort | "1528" |
Table 4 shows manageprofiles command parameters with default values that do not normally have to be changed.
Parameter | Default values |
---|---|
-profilePath | "install_root\profiles\my_WESBDMGR_profile" |
-hostName | "host_name" |
-nodeName | "host_nameCellManagernode_number" |
-cellName | "host_nameCellcell_number" |
![]() |
"true" |
![]() |
"localsystem" |
![]() |
"Administrator" |
-dbOutputScriptDir | "install_root\profiles\my_WESBDMGR_profile\dbscripts\CommonDB\Derby\WPRCSDB" |
The following command example creates a custom profile called my_WESBCUSTOM_profile on a Windows server.
This example is set to operate with the deployment manager profile created above.
Table 5 shows manageprofiles command parameters with example values used to create a custom profile.
Parameter | Value |
---|---|
-create | N/A |
-templatePath | "install_root\profileTemplates\managed.esbserver" (must be fully qualified) |
-profileName | "my_WESBCUSTOM_profile" |
-dmgrHost | "remote_host" |
-dmgrPort | "8885" (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" |
Table 6 shows manageprofiles command parameters with default values that do not normally have to be changed.
The following command example creates a deployment manager profile called my_WESBDMGR_DE_profile on a Windows server.
Table 7 shows manageprofiles command parameters with example values used to create a deployment manager profile.
Parameter | Value |
---|---|
-create | N/A |
-templatePath | "install_root\profileTemplates\dmgr.esbserver" (must be fully qualified) |
-profileName | "my_WESBDMGR_DE_profile" |
-enableAdminSecurity | "true" |
-adminPassword | "admin_pwd" |
-adminUserName | "admin_id" |
-ndtopology | "true" |
-topologyPattern | "Reference" |
-dbType | "DERBY_NETWORKSERVER" |
-dbName | "WPRCSDB" |
-dbCreateNew | "true" |
-dbDelayConfig | "false" |
-dbUserId | "db_id" |
-dbPassword | "db_pwd" |
-dbHostName | "localhost" |
-dbServerPort | "1530" |
Table 8 shows manageprofiles command parameters with default values that do not normally have to be changed.
Parameter | Default values |
---|---|
-profilePath | "install_root\profiles\my_WESBDMGR_DE_profile" |
-hostName | "host_name" |
-nodeName | "host_nameCellManagernode_number" |
-cellName | "host_nameCellcell_number" |
![]() |
"true" |
![]() |
"localsystem" |
![]() |
"manual" |
![]() |
"Administrator" |
-dbOutputScriptDir | "install_root\profiles\my_WESBDMGR_DE_profile\dbscripts\CommonDB\Derby\WPRCSDB" |
The following command example creates a custom profile called my_WESBCUSTOM_DE_profile on a Windows server. This example is set to operate with the deployment manager profile for a deployment environment created above.
See manageprofiles parameters for a listing of all valid manageprofiles parameters.
Table 9 shows manageprofiles command parameters with example values used to create a custom profile.
Parameter | Value |
---|---|
-create | N/A |
-templatePath | "install_root\profileTemplates\managed.esbserver" (must be fully qualified) |
-profileName | "my_WESBCUSTOM__DE_profile" |
-dmgrHost | "remote_host" |
-dmgrPort | "8897" (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 | "true" |
-topologyRole | "ADT Support Messaging" |
-dbType | "DERBY_NETWORKSERVER" |
-dbJDBCClasspath | "install_root\derby\lib" |
Table 10 shows manageprofiles command parameters with default values that do not normally have to be changed.