Understanding PeopleSoft Product Configuration Data SynchronizationThis chapter provides an overview of Product Configuration data synchronization and discusses how to:
Migrate data using Data Mover.
Migrate data using application messaging.
Understanding PeopleSoft Product Configuration Data SynchronizationDuring a Product Configurator implementation the question of how to migrate data between different databases often arises. There are a couple of different approaches that can be used to synchronize Product Configuration data such as, configuration rules, and matrices between different databases. You can use PeopleSoft's Data Mover or the predefined application messages that Product Configuration provides. Product Configuration data can be replicated between different Financials and Supply Chain Management (FSCM) databases and or or a Customer Relationship Management databases.
Migrating Data Using PeopleSoft Data MoverProduct Configuration data can be replicated across databases using Data Mover. Complete Product Configuration data export and import scripts are provided on the PeopleSoft CD under the <PS_HOME>\scripts folder. Namely, the script that exports all of the Product Configuration data is cpdmsexport_all.dms and the script that loads the output from the export script into a database is cpdmsimport_all.dms.
See Also
Enterprise PeopleTools 8.46 PeopleBook: Data Management
Migrating Data Using Application MessagingProduct Configuration data can also be replicated across databases using Application Messaging. A batch, full publish and subscribe design pattern can be used to synchronize configuration setup records between databases. The following table provides a detailed list of all of the application messages that are provided for Product Configuration data synchronization:
|
Description |
Message (Publish/Subscribe) |
Associated Record(s) |
|
|
Batch, Full table synchronization of Product Configurator Constraint data. |
This message handles the publish and or or subscription of Product Configurator Constraint data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_CONSTRAINT_FULLSYNC |
CP_CONSTRT_HDR CP_CONSTRT_COND CP_CONSTRT_DETL |
|
Batch, Full table synchronization of Product Configurator Expression data. |
This message handles the publish and or or subscription of Product Configurator Expression data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_EXPRESSION_FULLSYNC |
CP_EXPR CP_EXPR_FORMAT |
|
Batch, Full table synchronization of Product Configurator Global Variable data. |
This message handles the publish and or or subscription of Product Configurator Global Variable data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_GLOBAL_FULLSYNC |
CP_GBL_VAR |
|
Batch, Full table synchronization of Product Configurator Internal Variable data. |
This message handles the publish and or or subscription of Product Configurator Internal Variable data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_INTRN_VAR_FULLSYNC |
CP_INTRN_VAR CP_INTRN_KEY |
|
Batch, Full table synchronization of Product Configurator Matrix data. |
This message handles the publish and or or subscription of Product Configurator Matrix data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_MATRIX_FULLSYNC |
CP_MATRIX_HDR CP_MATRIX_DETL |
|
Batch, Full table synchronization of Product Configurator Message data. |
This message handles the publish and or or subscription of Product Configurator Message data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_MESSAGE_FULLSYNC |
CP_MESSAGE CP_MESSAGE_LANG |
|
Batch, Full table synchronization of Product Configurator Multiple Option data. |
This message handles the publish and or or subscription of Product Configurator Multiple Option data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_MULTOP_FULLSYNC |
CP_MULTOP_HDR CP_MULTOP_DETL |
|
Batch, Full table synchronization of Product Configurator Option Variable data. |
This message handles the publish and or or subscription of Product Configurator Option Variable data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_OPTION_FULLSYNC |
CP_OPT_VAR |
|
Batch, Full table synchronization of Product Configurator Print Code data. |
This message handles the publish and or or subscription of Product Configurator Print Code data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_PRINTCD_FULLSYNC |
CP_PRINTCD |
|
Batch, Full table synchronization of Product Configurator Rule data. |
This message handles the publish and or or subscription of Product Configurator Rule data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_RULE_FULLSYNC |
CP_RULE_HDR CP_RULE_COMMENT CP_RULE_DETL CP_RULE_D_LANG CP_RULE_DETL_AD CP_RULE_DETL_CL CP_RULE_DETL_OS CP_RULE_HTML CP_RULE_HT_LANG CP_RULE_H_LANG |
|
Batch, Full table synchronization of Product Configurator Secondary Variable data. |
This message handles the publish and or or subscription of Product Configurator Secondary Variable data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_SECONDARY_FULLSYNC |
CP_SEC_VAR |
|
Batch, Full table synchronization of Product Configurator Template data. |
This message handles the publish and or or subscription of Product Configurator Template data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_TEMPLATE_FULLSYNC |
CP_TEMP_HDR CP_TEMP_DETL |
|
Batch, Full table synchronization of Product Configurator Constant data. |
This message handles the publish and or or subscription of Product Configurator Constant data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_CONSTANT_FULLSYNC |
CP_CONSTANT |
|
Batch, Full table synchronization of Product Configurator Model data. |
This message handles the publish and or or subscription of Product Configurator Model data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_TREE_FULLSYNC |
CP_TREE_HDR CP_TREE_DETL |
|
Batch, Full table synchronization of Product Configurator Value List data. |
This message handles the publish and or or subscription of Product Configurator Value List data. This message is designed to be used with the Enterprise Integration Full Batch Publish design pattern. |
CP_VALUE_LIST_FULLSYNC |
CP_USERCD_HDR CP_USERCD_DETL CP_USERCD_LANG |
PeopleSoft Product Configurator Message Channels
Message channels group together message publications and subscriptions. You must set up message channels before you conduct application messaging.
PeopleSoft delivers the CP_SETUP message channel for the Product Configuration data.
Message Publication Run Control Definitions
You use the Full Data Publish page (Enterprise Components menu) to create the run control parameters and initiate the Table Replication Push (EOP_PUBLISHT) application engine process.
Instead of creating a separate run control definition for each message, you can add multiple request IDs—a row for each message name—to a single-run control ID to publish all messages at once.
Performing a Full Data Publish of Current Effective Data
To perform a full data publish:
Create effective-dated messages.
Note. Product Configurator has already provided these for you.
Define the message node, message channel, and message definition.
Create a full message definition that contains the necessary records in the publishing system. You can also set up message routing by using OnRouteTo PeopleCode.
Note. Remember to insert the message version first, otherwise you can’t add the tables that compose the message.
Begin by setting up the node and the transaction and connector details by using the Integration Profile setup function of Integration Broker. To set up the node:
Create a node.
Set up the connector.
The default target is PSHTTP, but you can instead provide the HTTP address for another target.
Associate the transaction to the node.
Provide the message name.
Designate whether the message is synchronous or asynchronous.
Create the message definition for the effective-dated message.
Define chunking rules and ordering views using the Chunking Rule page.
Create publish rule definitions.
Create run controls for the Full Data Publish program using the Full Data Publish page.
(Optional) Define message routing.
See Also
Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Integration Testing Utilities and Tools