Appendix: Migrating Data from the Content Provider Using PeopleSoft Integration Broker

Several steps are involved when you are migrating data for use in PeopleSoft Portal Resource Finder from PeopleSoft Integration Broker. This appendix provides examples of how this can be accomplished. The information provided in this documentation is used to convey basic example scenarios. Please consult respective PeopleBooks for PeopleSoft Integration Broker and PeopleSoft Human Capital Management for specific details.

This appendix provides prerequisites and additional considerations for migrating data from content providers to Resource Finder, and discusses how to:

• Set up incremental sync from the content provider to Resource Finder.

• Set up full sync from the content provider to Resource Finder.

Prerequisites and Additional Considerations

Before beginning this process, ensure that setup data exists for the delivered sample messages. For example, the data for the data sources, participant types, attributes, participant mappings, and so forth must exist for COMPANY_SYNC, LOCATION_SYNC, and so forth. If these data sources do not exist, you must run the epx_msg_setup_imp.dms script along with the epx_msg_setup_imp.dat file. This script imports Resource Finder setup data for the PeopleSoft Human Capital Management (HCM) data sources into the Portal Solutions system database.

Setting Up Incremental Sync from the Content Provider to Resource Finder

This section discusses how to:

• Set up messages for the PeopleSoft Enterprise Portal.

• Set up messages for the content provider.

• Test the migration process.

Setting Up Messages for the PeopleSoft Enterprise Portal

To set up a message, COMPANY_SYNC as in this example, for the PeopleSoft Enterprise Portal:

1. Set up PeopleSoft Integration Broker so that it can ping the portal node successfully.

   Ensure that the ping shown on the Node Status page for the content provider node (such as HCM) is successful.

2. Activate the COMPANY_SYNC message for the PeopleSoft Enterprise Portal in PeopleSoft Application Designer.

   To do this, select the Active option on the Use tab of the Message Properties dialog box.

3. Activate the message subscription.

   To do this, select the Active option on the Use tab of the Message Subscription Properties dialog box.

4. Ensure that the message channel is running.

   To do this, ensure that the Run option on the Use tab of the Message Channel Properties dialog box is selected.

5. Add the message to the node definition.

   To do this, select PeopleTools, Integration Broker, Integration Broker Setup, Node Definitions in the PeopleSoft Enterprise Portal database, open the content provider node, and select the Transactions tab. For example, if you are editing the COMPANY_SYNC message for the HCM node, edit the PSFT_HR node. On the Transactions tab, add the COMPANY_SYNC message with an InAsync transaction type to the transaction.

6. Add the message channel security to the permission lists needed.

Setting Up Messages for the Content Provider

To set up a message, COMPANY_SYNC as in this example, for the content provider:

1. Set up PeopleSoft Integration Broker so that it pings the portal node.

   Ensure that the ping shown on the Node Status page for the content provider node (such as HCM) is successful.

   See Enterprise PeopleTools 8.50 PeopleBook: Integration Broker, "Using the Service Operations Monitor," Pausing, Testing, and Pinging Nodes.

2. Activate the COMPANY_SYNC message for the content provider in PeopleSoft Application Designer.

   To do this, select the Active option on the Use tab of the Message Properties dialog box.

3. Ensure that the message channel is running.

   To do this, ensure that the Run option on the Use tab of the Message Channel Properties dialog box is selected. Ensure that the message channel name is the same for both the portal and the content provider.

4. Add the message to the node definition.

   To do this, select PeopleTools, Integration Broker, Integration Broker Setup, Node Definitions in the content provider database, open the PeopleSoft Enterprise Portal node, and select the Transactions tab. For example, if you are editing the COMPANY_SYNC message for the PeopleSoft Enterprise Portal node, edit the PSFT_PA node. On the Transactions tab, add the COMPANY_SYNC message with an OutAsync transaction type to the transaction.

5. Add the message channel security to the permission lists needed.

Testing the Migration Process

After performing setup, test the process. You can test this process in the HCM database where you maintain transactions. In this example, in which we used COMPANY_SYNC, navigate to the page used to define the Company table. The incremental sync is launched any time the page is accessed and updated or saved. Consult HCM PeopleBooks for navigation details.

To test the setup for regular incremental syncs from the application:

1. Add a row of data or update an existing row of data in the Company table, for example.

2. In the content provider database, such as HCM, navigate to the Monitor Message - Message Instances page to ensure that the publication status is set to Done.

3. In the portal database, navigate to the Monitor Message page to ensure that the subscription status is set to Done.

4. Perform a query for the PS_EPX_PARTICIPANT table to ensure that the new participant has been added.

Setting Up Full Sync from the Content Provider to Resource Finder

This section discusses how to:

• Set up a full sync.

• Run the full sync.

• Run the full data publish.

Setting Up a Full Sync

If a full sync of the application must be performed, follow these steps.

Note. Be aware that the FULLSYNC messages are used rather than the regular messages. This procedure uses COMPANY_FULLSYNC as an example, instead of COMPANY_SYNC.

In some cases, improved performance with FULLSYNC messages can be achieved by decreasing the message size to be within the range of 25,000–100,000 bytes.

To set up a full sync:

1. Activate the message definitions in PeopleSoft Application Designer for both the PeopleSoft Enterprise Portal and the content provider.

2. Activate the message subscriptions in the Message Subscription Properties dialog box in PeopleSoft Application Designer for the PeopleSoft Enterprise Portal.

3. Ensure that the message channel is running for both the PeopleSoft Enterprise portal and the content provider.

4. Edit the permission list to add security to the message channel in the PeopleSoft Enterprise Portal and the content provider.

5. Add the appropriate transactions to the nodes on the Node Definition page.

   • In the HCM database, add the message transaction with an OutAsync transaction type to the portal node.

   • In the PeopleSoft Enterprise Portal database, add the message transaction with an InAsync transaction type to the HCM node.

6. You are now ready to run a full sync.

Running the Full Sync

To run the full sync:

1. Access the Full Table Publish Rules page in the HCM database.

   Consult the HCM PeopleBooks documentation for the correct navigation path.

2. Select the full sync message name, activate the status, and save the transaction.

Running the Full Data Publish

To run the full data publish:

1. Access the Full Data Publish page in the HCM database.

   Consult the HCM PeopleBooks documentation for the correct navigation path.

2. Select a Process Frequency value of Once.

3. Select the full sync message name in the Message Name field.

4. Save the transaction.

5. Click the Run button.

6. On the Process Scheduler Request page, select to run the Table Replication Publish Application Engine process (EOP_PUBLISHT) to run the full sync.

7. Access the Monitor Message page in both the content provider database and the PeopleSoft Enterprise Portal database to ensure that the publication and subscription, respectively, are set to Done and do not show any errors.

8. Query the table with a select statement from PS_EPX_PARTICIPANT to ensure that the data synchronized successfully.