Oracle (DataDirect Connect for JDBC)

To create an Oracle database service endpoint for a DataDirect Connect for JDBC driver:

1. Access the Service Endpoints | Add Service Endpoint | Edit Service Endpoint endpoint_name page for the SQL Database type and Oracle (DataDirect Connect for JDBC) subtype.
   
   For access instructions, see Creating a Service Endpoint.

2. Enter the properties for the service endpoint:
   
   The basic properties are:

• Host - The host server where the Oracle database software resides.

• Port - Default port number for the Oracle database.

• SID - System identification for database; also used to connect to the database. Sometimes called the Oracle ID.

• User -  A user name that will be created when the database is created.
  
  Note: Once this user name has been defined in the Process Administrator, the name cannot be changed. If a new administrative user name is necessary, create a new service endpoint that uses the new user name.

• Password - The administrative password for the Oracle database.

• 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 could 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 would work only if the schema name was not entered in this field.

• Database String - If this option is selected, the database connection information can be entered in the form of a URL. Complete the host, port, SID, user, and schema (schema is optional) fields. Then select the database string checkbox. In the database string field, enter the URL in the format jdbc:datadirect://host name:port number;SID. Enter and confirm a password for the user that will be created when the database is created.

      The advanced properties are:

• 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 - Enter the appropriate temporary tablespace name here. This tablespace, which is a TEMP of type TEMPORARY, performs temporary operations for the Engine database, including temporary indexing for some access.

• Profile - A profile is a set of limits on database resources. If you assign the profile to a user, 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 each group's access to specific database resources.

3. Configure the following Runtime options for the service endpoint or accept the defaults:

• Maximum Pool Size - Enter 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) - Enter the amount of time the database connection can remain idle before the connection is 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.

4. Click Save.

Note: Default values may not be appropriate for your database.  You should review and override with values suitable for the database.