Configuring
You can review the information on configuring sharded and nonsharded deployments.
- Configuring the api.colony.indexer property for sharding
Sharding can be enabled by configuring the api.colony.indexer property in the yfs.properties_ysc_ext file. - Set up your environment to enable sharding
You can shard by enterprise, by seller, or by custom attributes, and you can add shards to your environment. - Move from nonsharded mode to sharded mode
You can change from nonsharded to sharded mode by changing specific properties. - Add a colony in silent install mode
You can create colonies in silent install mode by creating an addColony.xml file that you can pass with the manageColony command. - Assigning a colony to enterprises and sellers
After deploying your application, you can assign a colony to enterprises and sellers. - Ignoring exceptions when a colony is disabled
You can specify to ignore exceptions for a colony if it is disabled. - Migrate data in a sharded deployment
During incremental configurations of IBM® Sterling Selling and Fulfillment Foundation, the Configuration Deployment Tool (CDT) migrates configuration data. The CDT contains sharding options for migrating colonies of enterprises. - Adding a new database vendor to your system
You can add a new database vendor to your system either during or after the installation of IBM Sterling Selling and Fulfillment Foundation by adding DB vendor jar files. - Custom sharding
You can extend the sharding capabilities that are provided out-of-the-box by IBM Sterling Selling and Fulfillment Foundation, and set up custom sharding according to a particular attribute to meet your business needs. - Using configuration organizations
In a sharded environment, if an organization wants to inherit Configuration data from another organization, the best practise is to create a third, configuration organization, which eases future data migration.
Parent topic: Sharded and nonsharded deployments