Arguments

The following table lists the arguments supported for the Distribute Data method.

Argument	Description
Configuration Id	The load splitter uses the configuration ID to get the configuration for the servers, threshold, minimum batch size, list of servers to run on, and so on.
Mode	Determines whether the load splitter runs in write or read mode. Read mode is the default.
Object Types	A property set that identifies the types of objects in a run and a child property set that contains a WHERE clause and the table name of each object type. For example: Object Type = Contact WHERE Clause = Specialty LIKE Cardiology TableName = S_PARTY
Request Id	Identifies the rows in the S_ASGN_LB_DATA table for a specific assignment request.
Server Component	Identifies the server component that the load splitter uses to pass the object rows for subsequent processing. The component is either Assignment Manager (AsgnSrvr) or Batch Assignment (AsgnBatch). This parameter also contains a child property set that has the input arguments used by a particular server component. For example: AsgnSrvr can take in the following input arguments based on underlying component parameters: AsgnKey, CopyPersonSpecData, and so on.
Component Parameters	The property set that contains all the parameters for the specified server component. This property set must be added as a child of each (previous) Object Type property set. Note: It is not possible to pass parameters such as Assignment Key, Regular Assign, and Reporting Mode using the Load Splitter Service business service. If you specify any of these values to be passed by the load splitter as property name and value pairs, then they are ignored. For example, the Assignment Key is ignored and Batch Assignment chooses the default All AM Rule Set component parameter rather than the particular rule group that you want to execute.
Set Server Component Object Type Parameter	Indicates which parameter to populate with the object type.
Set Server Component SQL Parameter	Indicates which parameter to populate with the load-balanced SQL statement.