IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JDBC > Configure the module for deployment

Setting connection properties for the external service wizard

Specify the connection properties that the external service wizard uses to connect to the database instance to discover database objects.

Before you can configure the connection properties, you must have started the external service wizard.

If you plan on discovering stored procedures in a Sybase database, be aware that the transaction mode setting on the stored procedure might potentially impact your decision on whether to use the Set Auto Commit on database connection property. For more information about how the transaction mode setting for stored procedures impacts your decision on whether to check Set Auto Commit on database connection see, Solutions to common problems in the Troubleshooting and support information topic.

The external service wizard requires these properties to connect to the database for discovery and for creating the service description. For more information about the properties, see Connection properties for the wizard.


Procedure

  1. In the Select the Processing Direction window, select Outbound or Inbound, and then click Next.

  2. In the Specify the Discovery Properties window, specify the connection properties for the wizard to use to connect to the database. The connection properties vary depending on the database to which your adapter connects. The properties that apply to the supported databases are described in the following steps.

    1. In the list of database software, select your product and version. The Properties area displays fields where you specify database-specific connection properties.

      For IBM DB2 Version 9.1 for z/OS , select V8 (New-Function Mode).

      For Derby and Sybase, select Generic JDBC.

    2. In the JDBC driver type field, select the type of JDBC driver you want to use.

      For IBM DB2 for IBM i, select AS/400 Toolbox for Java or IBM DB2 Universal to discover database objects. You can configure the module later to use the native driver for local access on the server at run time.

      If you are using a Derby database and you selected Generic JDBC as your database software, the JDBC driver type field pre-fills with a value of Other.

    3. In the Database field, specify the database name. For Oracle databases, this is the System ID (SID).

    4. In the Host name field, specify the host name or IP address of the database server. If you specify the IP address in IPv6 format, enclose the address in square brackets ([]).

    5. In the Port number field, specify the port number for connecting to the database.

    6. For DB2, Oracle, Microsoft SQL Server and Informix databases, if you select a named driver in JDBC driver type, the wizard provides a default value for the JDBC driver class name field and builds the value for the Database URL field from other connection fields. Additionally, for some of the named JDBC driver types, the wizard provides a default value for Port number. If you select the driver Other for any database software (for example, Derby) and for certain other drivers, you must specify the driver class name and database URL (although part of the database URL might be entered for you). See Database URL and JDBC driver class name.
    7. For Informix database only: In the Server name field, specify the name of the Informix database server to which the adapter connects.

    8. In the Additional JDBC driver connection properties field, specify additional properties to be set when connecting to the database. Specify one or more name: value pairs, separated by the semicolon character (;).

      For example: 

      loginTimeout:20;readOnly:true;
securityMechanism:USER_ONLY_SECURITY

    The connection information is used only for the discovery process. Later in the wizard, you can specify different connection information to use at run time.

  3. In the User name and Password fields, type the user name and password to use to connect to the database from the wizard. This user name is used only during the discovery process and is not saved. Later in the wizard, you can specify a different user name and password or a different authentication method to use at run time.

  4. Optional: In the Prefix for business object names field, type a string to be placed at the beginning of business object names.

  5. To enable bidirectional support for the adapter at run time:

    1. Click Advanced.

    2. In the Bidi properties area, select Bidi transformation.
    3. Set the ordering schema, text direction, symmetric swapping, character shaping, and numeric shaping properties to control how bidirectional transformation is performed.

  6. If you are performing discovery on a Sybase database using the jConnect driver, there may be a scenario where the transaction mode setting for the stored procedure prevents the adapter from discovering result sets from the stored procedure. If the transaction mode property for the stored procedure is set to the default value of "unchained mode" or "Transact-SQL mode", select the Set Auto Commit on database connection check box in the Advanced properties area. By selecting the Set Auto Commit on database connection check box you bypass the "unchained mode" configuration for the stored procedure, allowing the adapter to discover result sets from the stored procedure.

    If you fail to select the Set Auto Commit on database connection check box and the transaction mode property for the stored procedure is set to "unchained mode", the adapter returns the Cannot add object to selection error. For more information about how the transaction mode setting for stored procedures in Sybase impact adapter processing at discovery time, see Solutions to common problems in the Troubleshooting and support information topic.

    If the transaction mode property for the stored procedure is set to "chained mode", you do not need to select the Set Auto Commit on database connection check box. For a detailed property description of Set Auto Commit on database connection, see Set Auto Commit on database connection.

  7. To change the location of the wizard's log files or the amount of information included in the logs, select the Change the logging properties for the wizard check box, and then provide the following information:

    • In the Log file output location field, specify the location of the log file for the wizard.

    • In the Logging level field, specify the severity of errors that you want logged.

    This log information is for the wizard only; at run time, the adapter writes messages and trace information into the standard log and trace files for the server.

  8. Click Next.

    If the wizard displays the window showing the exception, eccom.ibm.adapter.framework.BaseException, it cannot connect to the database server. The message contains additional information about a possible cause for the problem. In addition, you can check the logs, which are in the directory specified in Log file output location. Verify that the connection information is correct.


Results

The external service wizard connects to the database and displays the Find Objects in the Enterprise System window.


What to do next

Continue working in the wizard. The next step is to examine the database to locate the objects for which you want the wizard to create business objects.

Configure the module for deployment


Previous topic: Adding external software dependencies


Next topic: Configure the module for outbound processing


Related concepts:

Globalization and bidirectional transformation


Related reference:

Connection properties for the wizard