WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Creating profiles with manageprofiles command with Derby or DB2® databases – examples

Example profile creation commands to help you create stand-alone server, deployment manager, and custom profiles using the manageprofiles command on your installation.

Stand-alone server profile

The following command example creates a WebSphere® Process Server stand-alone server profile called my_WESBSA_profile on a Windows® server. The parameters in Table 1 and Table 2 specify the following:
  • The DB2 Universal database product will be used for both the Common and Common Event Infrastructure databases, which are both assumed to already exist on the localhost. Both databases are set to be configured later (the -dbDelayConfig "false" and -dbDelayConfig "true" command parameter values specify that configuration scripts be created but not run). For complete listings of database-related manageprofiles parameters, see the topics manageprofiles parameters for Common database configuration (per database product) and manageprofiles parameters for Common Event Infrastructure database configuration (per database product).
  • The Windows service will be set for manual startup.
  • Business Space powered by WebSphere will not be configured.
  • The profile creation process will set the port values automatically (except for database-related ports). The process will validate the new profile against other profiles to ensure there are no port conflicts.
    Tip: To override the port values that the manageprofiles command will specify, use the -portsFile parameter. See manageprofiles parameters for a listing of all valid manageprofiles parameters.
  • Administrative security will be enabled.

Table 1 shows manageprofiles command parameters with example values used to create a stand-alone server profile.

Table 1. Specified manageprofiles command parameters
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"
For Windows operating system -winserviceStartupType "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.

Table 2. Defaulted manageprofiles command parameters
Parameter Default values
-profilePath "install_root\profiles\my_WESBSA_profile"
-hostName "host_name"
-nodeName "host_nameNodenode_number"
-cellName "host_nameNodenode_numbercell_numberCell"
For Windows operating system -winserviceCheck "true"
For Windows operating system -winserviceAccountType "localsystem"
For Windows operating system -winserviceUserName "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"

Deployment manager profile (without deployment environment setup)

The following command example creates a deployment manager profile called my_WESBDMGR_profile on a Windows server.

The parameters in Table 3 and Table 4 specify the following:
  • The Derby Network Server database product will be used for the Common database, which is set to be created and configured on the localhost during the profile creation process.
  • The Windows service will be set for manual startup.
  • The profile creation process will set the port values automatically (except for database-related ports). The process will validate the new profile against other profiles to ensure there are no port conflicts.
    Tip: To override the port values that the manageprofiles command will specify, use the -portsFile parameter. See manageprofiles parameters for a listing of all valid manageprofiles parameters.
  • Administrative security will be enabled.

WebSphere Enterprise Service Bus example

Table 3 shows manageprofiles command parameters with example values used to create a deployment manager profile.

Table 3. Specified manageprofiles command parameters
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"
For Windows operating system -winserviceStartupType "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.

Table 4. Defaulted manageprofiles command parameters
Parameter Default values
-profilePath "install_root\profiles\my_WESBDMGR_profile"
-hostName "host_name"
-nodeName "host_nameCellManagernode_number"
-cellName "host_nameCellcell_number"
For Windows operating system -winserviceCheck "true"
For Windows operating system -winserviceAccountType "localsystem"
For Windows operating system -winserviceUserName "Administrator"
-dbOutputScriptDir "install_root\profiles\my_WESBDMGR_profile\dbscripts\CommonDB\Derby\WPRCSDB"

Custom profile (without deployment environment setup)

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.

The parameters in Table 5 and Table 6 specify the following:
  • The Derby Network Server database product will be used for the Common database, which is assumed to already exist. The custom profile creation simply needs to point to the database used by the deployment manager to which the custom profile will be federated.
  • Administrative security will be enabled on the deployment manager to which the custom profile will be federated.
See manageprofiles parameters for a listing of all valid manageprofiles parameters.

WebSphere Enterprise Service Bus example

Table 5 shows manageprofiles command parameters with example values used to create a custom profile.

Table 5. Specified manageprofiles command parameters
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.

Table 6. Defaulted manageprofiles command parameters
Parameter Default values
-profilePath "install_root\profiles\my_WESBCUSTOM_profile"
-hostName "host_name"
-nodeName "host_nameNodenode_number"

Deployment manager profile (with deployment environment setup)

The following command example creates a deployment manager profile called my_WESBDMGR_DE_profile on a Windows server.

The parameters in Table 7 and Table 8 specify the following:
  • The profile creation process will automatically configure a deployment environment (specified by the parameters -ndtopology "true" and -topologyPattern "Reference").
  • The Derby Network Server database product will be used for the Common database, which is set to be created and configured on the localhost during the profile creation process. For a complete listing of database-related manageprofiles parameters, see the topic manageprofiles parameters for Common database configuration (per database product).
  • The Windows service will be set for manual startup.
  • The profile creation process will set the port values automatically (except for database-related ports). The process will validate the new profile against other profiles to ensure there are no port conflicts.
    Tip: To override the port values that the manageprofiles command will specify, use the -portsFile parameter. See manageprofiles parameters for a listing of all valid manageprofiles parameters.
  • Administrative security will be enabled.

WebSphere Enterprise Service Bus example

Table 7 shows manageprofiles command parameters with example values used to create a deployment manager profile.

Table 7. Specified manageprofiles command parameters
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.

Table 8. Defaulted manageprofiles command parameters
Parameter Default values
-profilePath "install_root\profiles\my_WESBDMGR_DE_profile"
-hostName "host_name"
-nodeName "host_nameCellManagernode_number"
-cellName "host_nameCellcell_number"
For Windows operating system -winserviceCheck "true"
For Windows operating system -winserviceAccountType "localsystem"
For Windows operating system -winserviceStartupType "manual"
For Windows operating system -winserviceUserName "Administrator"
-dbOutputScriptDir "install_root\profiles\my_WESBDMGR_DE_profile\dbscripts\CommonDB\Derby\WPRCSDB"

Custom profile (with deployment environment setup)

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.

The parameters in Table 9 and Table 10 specify the following:
  • The profile creation process will automatically assign the profile to a deployment environment (specified by the parameters -ndtopology "true" and -topologyRole ADT Messaging Support).
  • The Derby Network Server database product will be used for the Common database, which is assumed to already exist. The custom profile creation simply needs to point to the database used by the deployment manager to which the custom profile will be federated. For a complete listing of database-related manageprofiles parameters, see the topic manageprofiles parameters for Common database configuration (per database product).
  • Administrative security will be enabled on the deployment manager to which the custom profile will be federated.

See manageprofiles parameters for a listing of all valid manageprofiles parameters.

WebSphere Enterprise Service Bus example

Table 9 shows manageprofiles command parameters with example values used to create a custom profile.

Table 9. Specified manageprofiles command parameters
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.

Table 10. Defaulted manageprofiles command parameters
Parameter Default values
-profilePath "install_root\profiles\my_WESBCUSTOM_DE_profile"
-hostName "host_name"
-nodeName "host_nameNodenode_number"

concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cins_profilecreateex.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).