Configuring data source connection pooling for sharded installations

About this task

In a sharded database installation, you can have five types of shards: Metadata, Statistics, System Configuration, Transaction, and Master.

  • You must configure a datasource on your application server for each shard and colony you have. For example, you could have a datasource named metadata_ds for the Metadata shard, a datasource named config_ds for the System Configuration shard, and so on.
  • When multiple shards are defined, the shards must all use either datasource or direct JDBC calls: they cannot use both. Sterling Order Management System Software
  • Datasources for the Statistics, System Configuration, Transaction, and Master shard can be configured using either the System Management Administrator (SMA) or the manageDBpool API. To configure the datasource for a Metadata shard, you must use the manageDBpool API.
  • At least three data sources must be specified for sharded database installations.
  • If not set, the datasource name defaults to Pool ID.

To configure datasources for a sharded installation:

Procedure

  1. Create the connection pools and datasources for each shard on your application server. See your application server documentation for specific configuration and operating instructions.
  2. Install the application.
  3. In a text editor, open (or create) the customer_overrides.properties file in the INSTALL\properties folder.
  4. In customer_overrides, add the line for your database from the following list:
    • For Db2®, add jdbcService.db2Pool.datasource=datasourceName
    • For Oracle, add jdbcService.oraclePool.datasource=datasourceName

      where datasourceName is the logical name of the external datasource.

  5. Save the customer_overrides file and run setupfiles.sh/cmd.
  6. Use the System Management Administrator (SMA) or manageDBpool API to add the datasource attribute to the selected pools.
    Note: You cannot add the datasource attribute for the metadata pool in the SMA. You must use the manageDBpool API instead.
  7. Build and deploy the EAR.
  8. Update the application server configuration to use -Dvendor=<appserver>

    – where the value of <appserver> is weblogic or websphere.

  9. Start the application server.