Sharding input properties file

The sharding input properties file is a file created that is passed in to the di-parallel-process utility when indexing shards.

The sharding input properties file contains the following sections and properties:


System properties

System properties are shared by other utilities. For example, passwords that are common among utilities.


Database properties

Database properties are used to establish database connections with the database server. All database properties start with the Database keyword, followed by the property name, which is separated by a period. The following list shows the database properties:


Global preprocessing and indexing properties

Global properties are used for preprocessing and indexing by all shards, if not otherwise overwritten by the shard itself. All global properties start with the Global keyword, followed by the property name, which is separated by a period.

Global properties can be grouped into the following categories: server properties, preprocessing properties, and indexing properties. The following list shows the global server properties:

The following list shows the global preprocessing properties:

The following list shows auto-sharding properties.

Note: Auto-sharding is compatible with vertical sharding and the combination is recommended.

The following list shows the global indexing properties:


Master search server properties

There is typically only one set of master properties. They start with the keyword Master, followed by either the common keyword or the locale name (for example, en_US), followed by the property name, which is separated by a period.

The master properties must include at least the master-specific properties. Only the global server properties can be overwritten in the master properties. Otherwise, if not redefined, the global properties are used.

Note: The following properties use the en_US locale with shards A and C as a sample. Configure your sharding input properties file according to the locale and shard types that we are using.


Horizontal Shard properties

There is typically a set of horizontal shard properties for each horizontal shard. The horizontal shard properties start with the Shard keyword, followed by the shard name, followed by either the common keyword or the locale name, followed by the property name, all separated by periods.

The horizontal shard properties must include at least the horizontal shard's specific properties. All global properties can be overwritten in the horizontal shard, except for auto-merge-index. If no properties are redefined, the global properties are used. The following list shows the horizontal shard-specific properties, using shard A as a sample:

Vertical Shard properties

There is typically a set of vertical shard properties for each vertical shard. The vertical shard properties start with the Shard keyword, followed the shard name, either the common keyword or the locale name, followed by the property name, all separated by periods.

The vertical shard properties must include at least the vertical shard-specific properties. Only the global preprocessing properties can be overwritten in the vertical shard. Otherwise, if not redefined, the global properties are used.

The following list shows the vertical shard-specific properties, using shard V as a sample:


Overriding properties

To override a shard or master global property, use the following convention to overwrite it at the common level:

To override a shard or master global property, use the following convention to overwrite it at the locale level:


Sample properties files

The Utility Docker image contains two sample properties files. The example di-parallel-process.properties file uses the en_US locale with shards A, B, and C. These shard definitions are commented-out in favor of auto-sharding, but have been kept as examples because manual sharding is still supported. We can find the sample files in the directory /opt/WebSphere/CommerceServer90/properties/parallelprocess/.