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 that you plan to use for bus-enabled Web services.
Before you begin
Determine the servers or clusters on which to install and configure an SDO repository as described in Planning your Bus-enabled Web services installation, then add each server or cluster as a member of a bus as described in Configuring the members of a bus.
An SDO repository can work with most database products. For specific information about choosing and configuring your preferred database, consult your database administrator or database product documentation, and read the notes in this topic on database usage.
About this task
To install and configure an SDO repository, complete the following steps:
- Install your preferred database product.
- Create a JDBC provider and a data source for your database.
- Run the installSdoRepository.jacl script one or more times, to install the SDO application on each server and to set the database type that the SDO repository is to use.
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:
- For a single server configuration, you can use either your preferred database or the embedded Cloudscape database that is supplied with WebSphere® Application Server .
- For a network deployment configuration you can use either your preferred database or the supplied Cloudscape database and associated Network Server application. However, be aware of the limitations of Cloudscape Network Server. For example, it does not support transactions.
- The SDO repository dictates the schema and table names that it uses, so different repositories must use different databases to ensure that they do not access the same data. Use one SDO repository for each cell, so that if you have multiple cells you use multiple databases, one for each cell.
- Create the database for your preferred database supplier using the Table.ddl file from the relevant app_server_root/util/SdoRepository/database_type directory. The Table.ddl file describes the database table that is needed by the SDO repository.
Note: If you use Microsoft® SQL Server 2005, the Table.ddl file might not be available. In this case, configure the SDO repository to use SQL Server 2000 then configure SQL Server 2005 to support it as an existing SQL Server 2000 application.
- The -editBackendId flag on the installSdoRepository.jacl script determines the database type that the repository is to use. The back end ID determines what database-specific rules the application follows when talking to the database. See the associated note on the installSdoRepository.jacl script.
- Some databases require a user ID that has been granted permissions to access the SDO repository database. Create a user ID for user name SDOREP before you create the tables for Oracle, Sybase, and Microsoft SQL Server databases. Because of the way these databases handle user names and table names, the user name must be SDOREP to enable the SDO repository to access its table with the fully qualified name SDOREP.BYTESTORE. Make sure that you grant permission for the SDOREP user to read from, and write to, the database in the []WAS_HOME[]/util/Sdo Repository/ directory.
- If you use an Informix® database, do not disable logging.
- The SDO repository does not require XA support. In most cases you can use either an XA or a non-XA data source. However, if your database is Oracle 8 or 9, you must use the Oracle JDBC driver (non-XA) for the SDO repository data source.
- You might also choose to perform other steps such as creating an index of the primary key to improve database performance. Do not change the schema, table and column names.
Notes on the installSdoRepository.jacl script: