WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Securing the JDBC provider configurable service

You secure the JDBC connection to a DB2® database by running the mqsisetdbparms command, and the mqsichangeproperties command.

About this task

A DB2 database requires a data source login name and password on all connections.

Procedure

You must secure the JDBC connection to the DB2 database by completing the following steps:

  1. Identify the user ID and password that you want to associate with the JDBC connection.

    In the scenario, db2admin is the user ID used. Request the user ID and password of your installation from your system administrator.

  2. Run the mqsisetdbparms command to associate the user ID and password with the security identity scenario that is associated with the database.

    mqsisetdbparms Server1 -n jdbc::SecurityIdentity -u userID -p password

    where:
    • -n is the security identity that is used to authenticate the JDBC connection. Set the value to jdbc::scenario.
      Note: In the scenario, you create a security identity whose value is scenario. However, you can use any name for the security identity. The security identity name that you define in this step must be used to configure the securityIdentity property of the JDBC configurable service in the following step.
    • userID is your user ID.
    • password is the password of the user ID.

    Run the following command:

    mqsisetdbparms Server1 -n jdbc::scenario -u db2admin -p password

    Note: The security identity that you define in this step is also used to configure the securityIdentity property of the JDBC configurable service.
  3. Update the securityIdentity property of the CLIENTS JDBC configurable service to associate the JDBC connection with the database security identity. Run the mqsichangeproperties command.

    mqsichangeproperties Server1 -c JDBCProviders -o CLIENTS -n securityIdentity -v scenario

    where:
    • Server1 is the name of the runtime broker.
    • -o defines the name of the JDBC configurable service. Set the value to CLIENTS.
    • -c defines the type of the configurable service. Set the value to JDBCProviders.
    • -n defines securityIdentity as the name of the property that you must set.
    • -v defines the value of the securityIdentity property. Set the value to scenario.

Results

You have secured the JDBC connection.

You have completed the scenario.