+

Search Tips   |   Advanced Search

Configure the SDO repository

Service Data Objects (SDO) is an open standard for enabling applications to handle data from different data sources in a uniform way, as data graphs. Service integration bus-enabled web services use an SDO repository for storing and serving WSDL definitions. Use this task to create and configure your preferred database to store SDO data, and to install and configure an SDO repository on each server to use for bus-enabled web services.

Determine the servers or clusters on which to install and configure an SDO repository as described in Plan the bus-enabled web services installation, then add each server or cluster as a member of a bus as described in Configure the members of a bus.

An SDO repository can work with most database products. For specific information about choosing and configuring the preferred database, consult the database administrator or database product documentation, and read the notes in this topic on database usage.

To install and configure an SDO repository...

For more information about how to do this, first read the following notes on database usage and on the installSdoRepository.jacl script, and then complete the steps for one of these configurations:

Notes on database usage:

Notes on the installSdoRepository.jacl script:


Subtopics


Configure the SDO repository for a single server, and to use the embedded Derby database

In a z/OS environment we cannot use the embedded Derby database, because this database can be accessed by only one process at a time and even a single server on z/OS can run in multiple processes.

For a single server configuration and to use embedded Derby, you run the installSdoRepository.jacl script with the -createDb switch. This action creates the Derby database and installs the SDO repository.

To configure the SDO repository for a single server and to use the embedded Derby database...

  1. Open a command prompt, then change to the app_server_root/bin directory.

  2. Enter the following command: (iseries)

      wsadmin -f installSdoRepository.jacl -createDb

    (dist)(zos)

      wsadmin.ext -f installSdoRepository.jacl -createDb

    The -createDb flag tells the command to create a default Derby database. If we omit this flag, the command still installs an SDO repository configured to use Derby, but the command does not also create the database.


Configure the SDO repository for a single server, and to use a database other than embedded Derby

For a single server configuration that uses a database other than embedded Derby, you install the preferred database product, then create a JDBC provider and a data source, then run the installSdoRepository.jacl script twice:

  1. One time to install the SDO application on the application server.

  2. One time to set the database type that the SDO repository is to use.

To configure the SDO repository for a single server and to use a database other than embedded Derby...

  1. Create the database for the preferred database supplier using the Table.ddl file from the relevant app_server_root/util/SdoRepository/database_type directory.

    For an illustration of the process for creating tables in DB2, see Recreating database tables from the exported table data definition language. For more information, see Deploy data access applications.

  2. Create a J2C authentication alias.

    This is for use with the data source that we create in the next step. Check that the authentication alias matches the login details for the database instance, otherwise a connection will not be made.

  3. Create and configure a JDBC provider and data source.

    Set the following data source properties:

    • Set the authentication property to use the authentication alias created in the previous step.

    • Select the Use this Data Source in container managed persistence (CMP) check box.

    • Set the Name property to a name of our own choosing. For example, SDO Repository DataSource.

    • Set the JNDI name property to the following exact value: jdbc/com.ibm.ws.sdo.config/SdoRepository.

    • Set any other properties that are required settings for the chosen database.

  4. Optional: Test the data source connection:

    This option does not work in all configurations. The availability of this option depends on the scope at which the data source is defined, and the scope of any WebSphere Application Server variables used in the JDBC provider and data source configurations. For more information about testing connections to data sources, see Test connection service.

    1. In the console, navigate to Resources -> JDBC -> Data sources.

    2. Select the SDO repository data source.

    3. Click Test connection.

  5. Configure the SDO repository:

    1. Open a command prompt, then change to the app_server_root/bin directory.

    2. Install the SDO repository application on the server: (iseries)

        wsadmin -f installSdoRepository.jacl

      (dist)(zos)

        wsadmin.ext -f installSdoRepository.jacl

    3. Set the database type that the SDO repository is to use:

      (iseries)

        wsadmin -f installSdoRepository.jacl -editBackendId database_type

      (dist)(zos)

        wsadmin.ext -f installSdoRepository.jacl -editBackendId database_type

      for example:
      (iseries)

        wsadmin -f installSdoRepository.jacl -editBackendId DB2UDB_V82


      (dist)(zos)

        wsadmin.ext -f installSdoRepository.jacl -editBackendId DB2UDB_V82


Configure the SDO repository for a network deployment cell

If we are working in a network deployment environment, you install the preferred database product, then create a JDBC provider and a data source, then run the installSdoRepository.jacl script several times for each cell:

  1. One time to install the SDO application on the deployment manager.

  2. One time to set the database type that the SDO repository is to use.

  3. Several times to install an instance of the SDO application on each server or cluster to use for one or more of the bus-enabled web services roles.

To configure the SDO repository for a network deployment cell...

  1. Create the database for the preferred database supplier using the Table.ddl file from the relevant app_server_root/util/SdoRepository/database_type directory.

    For an illustration of the process for creating tables in DB2, see Recreating database tables from the exported table data definition language. For more information, see Deploy data access applications.

  2. Create the following node-level WebSphere Application Server variables on all affected nodes, including the deployment manager node.

    We can set these variables at either node or cell scope, depending upon the configuration. However for multi-platform nodes we cannot usefully set WAS_INSTALL_ROOT at cell scope, because the nodes have different installation directories.

    1. In the console, navigate to Environment -> WebSphere variables then set the scope to node level.

    2. Check that the WAS_INSTALL_ROOT variable exists, with a value of the root directory for the installation of WAS.

    3. Create a new variable your_database_JDBC_DRIVER_PATH, with a value of the location under which the database JAR files will be stored (in a later step) on each of the host machines within the cell.

  3. Create a J2C authentication alias.

    This is for use with the data source that we create in the next step. Check that the authentication alias matches the login details for the database instance, otherwise a connection will not be made.

  4. Create and configure a JDBC provider and data source.

    Set the following data source properties:

    • Set the authentication property to use the authentication alias created in the previous step.

    • Select the Use this Data Source in container managed persistence (CMP) check box.

    • Set the Name property to a name of our own choosing. For example, SDO Repository DataSource.

    • Set the JNDI name property to the following exact value: jdbc/com.ibm.ws.sdo.config/SdoRepository.

    • Set any other properties that are required settings for the chosen database.

  5. Deploy the database client JAR files on each of the host machines within the cell.

    The JAR files must be deployed to the location given by the your_database_JDBC_DRIVER_PATH variable that you declared in a previous step, otherwise remote nodes will not be able to connect to the SDO repository.

  6. Configure the SDO repository:

    1. Open a command prompt, then change to the app_server_root/bin directory.

    2. Install the SDO repository application on the deployment manager for this cell: (iseries)

        wsadmin -f installSdoRepository.jacl deployment_manager_node deployment_manager_server_name

      (dist)(zos)

        wsadmin.ext -f installSdoRepository.jacl deployment_manager_node deployment_manager_server_name

      for example:
      (iseries)

        wsadmin -f installSdoRepository.jacl dmgrNode dmgr


      (dist)(zos)

        wsadmin.sh -f installSdoRepository.jacl dmgrNode dmgr

    3. Set the database type that the SDO repository is to use:

      (iseries)

        wsadmin -f installSdoRepository.jacl -editBackendId database_type

      (dist)(zos)

        wsadmin.ext -f installSdoRepository.jacl -editBackendId database_type

      for example:
      (iseries)

        wsadmin -f installSdoRepository.jacl -editBackendId DB2UDB_V82


      (dist)(zos)

        wsadmin.ext -f installSdoRepository.jacl -editBackendId DB2UDB_V82

    4. Install an instance of the SDO repository on each server or cluster to use for one or more of the bus-enabled web services roles:

      • For each server that is not part of a cluster, repeat the following command:
        (iseries)

          wsadmin -f installSdoRepository.jacl node server_name


        (dist)(zos)

          wsadmin.ext -f installSdoRepository.jacl node server_name

      • For each cluster, repeat the following command:
        (iseries)

          wsadmin -f installSdoRepository.jacl -cluster cluster_name


        (dist)(zos)

          wsadmin.ext -f installSdoRepository.jacl -cluster cluster_name


Subtopics


Related concepts

  • SDO data graphs


    Related tasks

  • Start the wsadmin scripting client
  • Create a new Version 6.1 WS-Notification service

  • Implement JAX-RPC handlers to access SDO messages


    Related information:

  • Service Data Objects (SDO)