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


Example: Creating profiles with manageprofiles command and Oracle database

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

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 features:

There are two configuration options available:
  • Optional: If you want all of the schema user IDs and tables to be created as part of the profile creation, you must provide a user ID that has SYSDBA privileges in the Oracle database. This ID is used to create the schemas and tables, but is not persisted anywhere in the configuration.
  • Optional: If you do not want to provide the SYSDBA user ID, you can export the scripts and execute them manually.

    For both of these options, you can select a specific schema user ID for each of the components.

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_WPSSA_profile"
-enableAdminSecurity "true"
-adminPassword "admin_pwd"
-adminUserName "admin_id"
-configureBPC "true"
-dbType "ORACLE10G" or "ORACLE11G"
-dbName "WPRCSDB"
-ceiDbName "EVENT"
-dbDelayConfig "true"
-fileStoreForME "false" (cannot be true when -dbCommonForME is also true)
-dbCommonForME "true"
-dbPassword "db_pwd"
-dbDriverType "oracle_thin"
-dbJDBCClasspath "oracle_library_directory"
-dbServerPort "1521"
-configureBSpace "true"
-configureBRM "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\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"
-ndtopology "false"
-dbType "ORACLE10G" or "ORACLE11G"
-dbName "WPRCSDB"
-dbDelayConfig "false"
-dbLocation "oracle_install_directory"
-dbPassword "db_pwd"
-dbDriverType "oracle_thin"
-dbHostName "localhost"
-dbJDBCClasspath "oracle_library_directory"
-dbServerPort "1521"
-dbSysUserId "sys_user_id"
-dbSysPassword "sys_pwd"

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 -winserviceStartupType "manual"
For Windows operating system -winserviceUserName "Administrator"
-dbOutputScriptDir "install_root\profiles\my_WESBDMGR_profile\dbscripts\"

Table 5 shows additional manageprofiles command parameters that are not displayed via the Profile Management Tool that can be specified to select your own user name and password combinations for Oracle.

Table 5. Additional manageprofiles command parameters for Oracle
Parameter Default values
-dbCommonUserId "common_db_userID" (used to create Common DB objects)
-dbCommonPassword "common_db_pwd"

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 6 and Table 7 specify the following:
  • The profile creation process will automatically configure a deployment environment (specified by the parameters -ndtopology "true" and -topologyPattern "Reference").
  • The Oracle 10g or Oracle 11g database product will be used for the Common database, which is assumed to exist on a remote host. The database is set to be configured as part of the deployment environment setup (the -dbDelayConfig "true" command parameter is not valid in a deployment environment setup). 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.
There are two configuration options available:
  • Optional: If you want all of the schema user IDs and tables to be created as part of the profile creation, you must provide a user ID that has SYSDBA privileges in the Oracle database. This ID is used to create the schemas and tables, but is not persisted anywhere in the configuration.
  • Optional: If you do not want to provide the SYSDBA user ID, you can export the scripts and execute them manually.

    For both of these options, you can select a specific schema user ID for each of the components.

WebSphere Enterprise Service Bus example

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

Table 6. 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 "ORACLE10G" or "ORACLE11G"
-dbName "WPRCSDB"
-dbUserId "sys_user_id" (Must be a SYSDBA user ID for deployment environments)
-dbPassword "sys_pwd"
-dbDriverType "oracle_thin"
-dbHostName "remote_host_name"
-dbJDBCClasspath "oracle_library_directory"
-dbServerPort "1521"

Table 7 shows manageprofiles command parameters with default values that do not normally have to be changed.

Table 7. 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"
-dbDelayConfig "false" (true is not valid for deployment environments)
-dbOutputScriptDir "install_root\profiles\my_WESBDMGR_DE_profile\dbscripts\"

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_ora_profilecreateex.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).