Add a Process Execution Engine

Process execution engines run the processes associated with projects and the engine databases keep track of the data for these processes.

To add a process execution engine to the Process Administrator:

  1. In the left pane of the Process Administrator, click Engines.

  2. In the right pane, on the Engines page, click Add.

  3. On the Engines | Choose Engine Type page, enter an Engine Name, set the Engine Type to WebLogic, and select an Engine Database Type.

  4. Click Next.

  5. On the Engines | Choose Engine Type | Edit Engine engine-name Database Configuration page, configure the engine database properties and click Next.

The SQL Server engine database properties include:

 
Host The name of the host computer or server on which Microsoft SQL resides and on which the database will be created.
Port

The port on the host the database will use.

Database The name of the engine database that will be created.
User A user name that will be created when the database is created. Once this user name has been defined in Process Administrator, the name cannot be changed. If a new user name is necessary, create a new process execution engine with the new user name.
Password A password that will be created for the user when the database is created.

The Oracle engine database properties include:

 
Host The name of the host computer or server on which Oracle resides and on which the database will be created.
Port The port on the host the database will use.
SID System identification for the database; also used to connect to the database. Sometimes called Oracle ID.
User A user name that will be created when the database is created. Once this user name has been defined in Process Administrator, the name cannot be changed. If a new user name is necessary, create a new process execution engine with the new user name.
Password A password that will be created for the user when the database is created.
Schema This is an optional property. If the name of a schema is entered, the configuration and introspection will only work on tables of that schema. If a schema name is not entered, the schema can be changed at runtime. For example, if a table named devel.invoice is referenced in a development environment and in production a different schema name is used, production references to devel.invoice will work only if the  schema name was not entered in this field.
Database String When this option is selected, the database connection information can be entered in the form of a URL. In the Database String Field, enter the URL in the format jdbc:datadirect://host:port;SID. Enter and confirm a password for the user that will be created when the database is created.
Tablespace
 		 Some database administrators divide databases into tablespaces to control and maintain table sizes. Enter the appropriate tablespace name here. Leave the field blank if there are no tablespaces and a default tablespace will be created. When the user name is created, the user creation statement references the tablespace.
Temporary Tablespace The name of the temporary tablespace used by the engine's database to perform temporary indexing for some access: TEMP of type TEMPORARY.
Profile
 		 A profile is a set of limits on database resources. If you assign the profile to the user being created, that user cannot exceed the established limits in the profile. This allows the administrator to limit the actions of a particular Oracle user. The Oracle administrator may have different profiles set for different groups of users so that there is control over what each group is authorized to use and over which resources from the database a particular group will have.
Maximum Pool Size The maximum number of connections that the pool can allocate. The pool will never create more connections than this limit imposes. The default is 10.
Connection Idle Time (Mins) The amount of time the database connection can remain idle before the connection will be dropped. The default is 5 minutes.
Maximum Opened Cursors Enter the maximum number of opened cursors allowed on the database. The default is 50. This value is related to the maximum pool size. The number of cursors is divided in between the number of maximum pool size and each connection will manage that number of cursors. For example, if you have 500 maximum opened cursors and the maximum pool size is 50, each connection can have a maximum of 10 opened cursors.
 

Related Topics: