Configuring Rule Execution Server on a new profile

To create a new stand-alone instance of Rule Execution Server environment, you must first create a Decision Server profile. You can create a profile by using the Profile Management Tool or by using the manageprofiles command.

Before you begin

During profile creation, you are asked to select the database manager that hosts the tables for the execution server run time. Unless you are using Apache Derby, create this database before you configure a new profile. See Creating a Rule Execution Server database.

About this task

Depending on your operating system, you can either use the Profile Management Tool or the manageprofiles command to create a new profile:
  • On a 32-bit operating system, you can use the Profile Management Tool. The Profile Management Tool is not supported on an HP-UX operating system, nor is it on z/OS®.
  • On a 32-bit operating system or any other operating system, you can use the manageprofiles command.

The procedure describes how to use the manageprofiles command to configure Rule Execution Server on a new profile.

Procedure

  1. Open a command prompt (Windows) or a terminal emulator (Linux and UNIX environments) and navigate to the <WAS_InstallDir>/bin directory.
  2. Run the manageprofiles command by using manageprofiles.bat for Windows or manageprofiles.sh for Linux and UNIX environments.
    1. Required: Provide the following parameters.
      -create
      To create the new profile.
      -templatePath <template_path>
      where <template_path> is the location of the profile template. Provide the path to <WAS_InstallDir>/profileTemplates/rules/default/ds.
    2. Optional: Specify the following optional parameters.
      -dsHome installation location
      where installation location is the fully qualified path of the Decision Server installation directory <InstallDir>. You must specify this parameter if you have installed Decision Server in a non-default location.
      -profileName profile_name
      where profile_name is the name of the profile.
      -cellName cell_name
      where cell_name is the name of the cell.
      -nodeName node_name
      where node_name is the name of the node.
      -hostName host_name
      where host_name is the host name of the computer that hosts the profile.
      -serverName server_name
      where server_name is the server name.
      -enableAdminSecurity true|false
      where true turns on WebSphere® Application Server administrative security. If you provide this parameter, you must also provide -adminUserName and -adminPassword. If you do not specify this parameter, the default is false.
      -adminUserName username
      where username is the user ID to access WebSphere Application Server. Required only if enableAdminSecurity is enabled.
      -adminPassword password
      where password is the password for the user ID to access WebSphere Application Server. Required only if enableAdminSecurity is enabled.
      -dbType database_type
      where database_type specifies the database product. Valid values:
      • Derby_Embedded: the default value
      • DB2_Universal
      • Derby_NetworkServer
      • Oracle
      • MS_SQL_Server
      -dbName database_name
      where database_name is the name of the database. Required unless -dbType is Derby_Embedded.
      -dbUserId database_user_name
      where database_user_name is the user ID to access the database server. Required unless -dbType is Derby_Embedded.
      -dbPassword password
      where password is the password for the user ID to access the database server. Required unless -dbType is Derby_Embedded.
      -dbJDBCClasspath database_jdbc_classpath
      where database_jdbc_classpath specifies the path to the JDBC class path files. Required unless -dbType is Derby_Embedded.
      -dbJDBCLicenseClasspath database_jdbc_license_classpath
      where database_jdbc_license_classpath specifies the path to the JDBC class path files. Required only if -dbType is DB2_Universal.
      -dbHostName host_name
      where host_name is the host name for the database server. Required unless -dbType is Derby_Embedded.
      -dbServerPort port_number
      where port_number is the port of the TCP/IP service, or the port on which the database is listening. Required unless -dbType is Derby_Embedded.

Results

After you run the manageprofiles command, the profile is created.

Examples

The following examples show how to configure Rule Execution Server with the default messaging provider on Windows and Linux.
The first example creates a new application server profile on Windows by using embedded Apache Derby as the database provider and WebSphere Application Server default messaging as the messaging provider. 
manageprofiles.bat -create -templatePath "C:\Program
Files\IBM\ODM851\WAS\profileTemplates\rules\default\ds" -dsHome  "C:\Program
Files\IBM\ODM851"
The second example creates a new application server profile on Linux and UNIX environments by using embedded Apache Derby as the database provider and WebSphere Application Server default messaging as the messaging provider. 
manageprofiles.sh -create -templatePath "/opt/ibm/ODM851/ODM/WAS/profileTemplates/rules/default/ds" -dsHome  "/opt/ibm/ODM851/ODM"
Parent topic: Configuring Rule Execution Server by using profile templates