Deprecated. Do not use this pipelet. Replication tasks should be managed through the Business Manager.
This pipelet creates and starts a new replication process for the specified target system and configuration. The process is triggered asynchronously while the pipelet returns immediately. This pipelet can only be used on replication source systems (i.e. the 'Staging' instance). The parameter ReplicationConfiguration contains a mapping of a site name to a list of replication groups. Example: { 'Sites-SiteGenesis' : ['SITE_PROMOTION', 'SITE_PREFERENCE'], 'Sites-Site' : ['ORGANIZATION_CATALOG', 'ORGANIZATION_PRICE_BOOK'] } This parameter can be a Java object of type Map<String, Collection<String>> or a JavaScript String literal containing the needed information. Please refer to the documentation for a list of possible replication groups. The site ID can be provided with or without the prefix '-Site'. So 'Sites' and 'Sites-Site' is resolved correctly, as well as 'Sites-SiteGenesis' and 'Sites-SiteGenesis-Site'. The parameter TargetSystemID must be one of 'Production' or 'Development'. The pipelet will return an error status if the specified target system does not exist or is not yet initialized. If the process could be created and started successfully the returned status object is in state OK and contains the unique identifier of the created process. Additionally the id is provided as output parameter of type String for convenience in conjunction with the pipelet GetReplicationStatus. This identifier can be used for querying the state of the process. In case of an error, the returned status object will contain details about the problem.