Integrating Person Data

Owner-Subscriber

In an owner-subscriber integration model, one system is defined as the system of record and the other system subscribes to its person data messages. All EmplIDs exist and are in sync in both databases. For example, if CS is defined as the owner for adding and updating person data, the HCM system subscribes to the person messages; integration setup feeds person data additions and updates to HCM. The end-user experience can be managed via a portal or related content to navigate a combination of CS and HCM menus and pages.

This workflow depicts the process of adding an Admissions applicant in CS.

This workflow depicts the process of hiring an employee in HCM.

Subscriber Only

In a subscriber-only integration model, both systems are defined as system of record and integrations are configured to allow both systems to publish and subscribe to person data messages. All EmplIDs are populated to both systems and are kept in sync.

This workflow depicts the process of adding an Admissions applicant or employee in the Subscriber-only model.

Distinct Ownership

In a distinct ownership integration model, person data is added and updated in the appropriate CS or HCM system (as determined by the business processes of your institution; for example, employees are added and maintained in HCM). External Search/Match then becomes the method used in each system to ensure that users do not create duplicate records on campus. For example, as an employee is added to HCM, External Search/Match determines whether that new employee is already a student in CS with an EmplID and other bio-demo data housed in the CS system. If so, a "fetch" process can pull that EmplID and person data to HCM, ensuring that the individual retains a single unique ID on campus. Thereafter, each system must be manually updated, with no further integration between them.

This workflow depicts the process of adding an employee in HCM using External Search/Match to CS.

Incremental Synchronization

Data in the supporting tables in your system of record may change over time after the initial loading of setup, transactional data, and security data. Use incremental sync (Sync) services to send this information from your system of record to your subscribing target system to maintain data integrity.

An incremental sync captures data that was created, added, changed, or deleted in the system of record since the last synchronization. It uses the captured data to overwrite the same data in the subscribing system, thereby refreshing the subscribing system so that both systems have the same data.

After the initial fullsync data loads have completed in your subscribing target system, you may inactivate the associated fullsync services, and then activate the appropriate incremental Sync services to keep your systems updated.

Manual Entry Data Load

You can, if necessary, enter data manually into your CS and HCM systems. However, it would be tedious, time consuming, and possibly introduce typographical errors. Oracle does not recommend this method for most data elements unless required to load a small amount of data.

Transactional Data Loading Sequence

For all owner/subscriber configurations, person transactional information must be available and loaded from your system of record to your subscribing system for implementation. Oracle recommends that CS be the system of record for Person data. Your HCM system should remain the system of record for all HCM Workforce and other HR related transactional data.

The following table lists the required integration, indicates the type of service recommended, and the order in which you must load transactional table data into your HCM system.

Person Transaction Data Campus Solutions to HCM

*Existing CS functionality does not populate these tables. Depending on your use of HCM functionality, the records marked with an asterisk may not have data present at the time the fullsync is published.

Configuring the Integration Broker Gateway and Nodes

To configure the Integration Broker Gateways and Nodes in your CS and HCM databases:

1. Set the Service Configuration in the HCM database.

2. Configure the Gateway in the HCM database.

3. Configure the default local node in the HCM database.

4. Configure the HCM Gateway in the CS database.

5. Configure the CS node in the HCM database.

6. Configure the default LOCAL node in the CS database.

7. Configure the HCM node in the CS database.

8. Update the HCM Gateway nodes in the HCM database.

9. Update the HCM Gateway nodes in the CS database.

10. Update the Single Sign-on nodes.

11. Test Nodes.

1. Setting the Service Configuration in the HCM database.

   Navigate toPeopleTools > Integration Broker > Configuration > Service Configuration,and set up the following:

   Field or Control	Description
   Service Namespace	http://xmlns.oracle.com/Enterprise/HCM/services
   Schema Namespace	http://xmlns.oracle.com/Enterprise/Tools/schemas
   Target Location	http://machinename:port/PSIGW/PeopleSoftServiceListeningConnector
   Service System Status	Production

2. Configuring the Gateway in the HCM database.

   1. Navigate: PeopleTools > Integration Broker > Configuration > Gateways.

   2. Select Integration Gateway ID = LOCAL.

   3. Set URL = http://machinename:port/PSIGW/PeopleSoftServiceListeningConnector/databasename.

   4. Click the Load Gateway Connectors button. Save after it loads 9 connectors

   5. Click the Ping Gateway button. If successful, it displays an Active status.

3. Configuring the default local node in the HCM database.

   1. Navigate toPeopleTools > Integration Broker > Integration Setup > Nodes.

   2. Select the default local node and set up the following:

      Field or Control	Description
      Set Descr	HCM Instance
      Authentication Option	Password
      Node Password	PS
      Default User ID	PS

   3. Click the Connectors tab and set the following:

      Field or Control	Description
      Gateway ID	LOCAL
      Connector ID	PSFTTARGET

   4. Click the Portal tab and set up the following:

      Field or Control	Description
      Tools Release	8.54.xx
      Set Application Release	HCM
      Content URI Text	http://machinename:port/psc/databasename
      Portal URI Text	http://machinename:port/psp/databasename

      Note: Use <CTRL>+J keys to see the tools release string.

   5. Click the WS Security tab and set the following:

      Field or Control	Description
      Authentication Token Type	None
      Encrypted	Disable the check box.

   6. Save.

4. Configuring the HCM Gateway in the CS database.

   1. Navigate to PeopleTools > Integration Broker > Configuration > Gateways, and select .Add a New Value.

   2. Set the following:

      Field or Control	Description
      Integration Gateway ID	<Gateway Name for HCM>
      URL	http://machinename:port/PSIGW/PeopleSoftListeningConnector/databasename

   3. Click the Load Gateway Connectors button. It should load 9 connectors. Save.

   4. Click the Ping Gateway button.

      If successful, it displays an Active status.

5. Configuring the CS node in the HCM database.

   1. Navigate toPeopleTools > Integration Broker > Integration Setup > Nodes, and set up the following:

      Field or Control	Description
      Add Node	Name of CS Node
      Set Descr	CS Instance
      Set Authentication Option	Password
      Node Password	PS
      Default User ID	PS

   2. Click the Connectors tab and set up the following:

      Field or Control	Description
      Gateway ID	LOCAL
      Connector ID	PSFTTARGET

   3. Click the Portal tab and set up the following:

      Field or Control	Description
      Tools Release	8.54.xx
      Set Application Release	CS release version
      Content URI Text	http://machinename:port/psc/databasename
      Portal URI Text	http://machinename:port/psp/databasename

   4. Click the WS Security tab and set the following:

      Field or Control	Description
      Authentication Token Type	None
      Encrypted	Disable the check box.

   5. Click Save.

6. Configuring the default LOCAL node in the CS database.

   Note: The gateway used by this node is the HCM gateway. Node passwords must be consistent between the CS and the HCM databases.

   1. Navigate: PeopleTools > Integration Broker > Integration Setup > Nodes.

   2. Select the default local node and set up the following:

      Field or Control	Description
      Description	Set Descr = CS Instance
      Authentication Option	Password
      Node Password	PS
      Default User ID	PS

   3. Click the Connectors tab and set up the following:

      Field or Control	Description
      Gateway ID	Gateway Name for HCM instance Note: This is not the local gateway.
      Set Connector Id	PSFTTARGET

   4. Click the Portal tab and set up the following:

      Field or Control	Description
      Tools Release	8.54.xx
      Set Application Release	CS release version
      Content URI Text	http://machinename:port/psc/databasename
      Portal URI Text	http://machinename:port/psp/databasename

   5. Click the WS Security tab and set the following:

      Field or Control	Description
      Authentication Token Type	None
      Encrypted	Disable the check box.

   6. Click Save.

7. Configuring the HCM node in the CS database.

   Note: Each node is defined twice – once in each database. They should each use the same gateway.

   1. Navigate to PeopleTools > Integration Broker > Integration Setup > Nodes, and set up the following:

      Field or Control	Description
      Add Node	Name of HCM Node
      Set Descr	HCM Instance
      Set Authentication Option	Password
      Node Password	PS
      Default User ID	PS

   2. Click the Connectors tab and set up the following:

      Field or Control	Description
      Gateway ID	Gateway Name for HCM instance Note: This is not the local gateway.
      Set Connector Id	PSFTTARGET

   3. Click the Portal tab and set the following:

      Field or Control	Description
      Tools Release	8.54.xx
      Set Application Release	HCM release version
      Content URI Text	http://machinename:port/psc/databasename
      Portal URI Text	http://machinename:port/psp/databasename

   4. Click the WS Security tab and set the following:

      Field or Control	Description
      Authentication Token Type	None
      Encrypted	Disable the check box.

   5. Click Save. A Node Saved message box appears. Click OK.

8. Updating the HCM Gateway nodes in the HCM database.

   Both CS and HCM database nodes should point to the same Gateway. The specific Gateway should also have both nodes listed in the Gateway Advanced Properties.

   1. Navigate: PeopleTools > Integration Broker > Configuration > Gateways.

   2. Select gateway LOCAL.

   3. Click the Gateway Setup Properties link and set the following:

      Field or Control	Description
      User ID	administrator
      Password	Enter a password.

      Click OK.

   4. In the Gateway Default App. Server frame, set the App Server URL to ' //machinename:port.

      Note: Your port must match the one specified in your HCM application server.

   5. Enter the appropriate User ID and password.

   6. Set the tools release to 8.54.xx.

   7. Make sure both the HCM and CS nodes are in the PeopleSoft Nodes tab. Ping the HCM node. It should be successful.

   8. Click Return.

9. Updating HCM Gateway nodes in the CS database.

   Follow the process outlined in Step 8 to update the HCM Gateway node in the CS database.

10. Updating the Single Sign-on nodes in both CS and HCM databases.

    Single Sign-on is used in this recommended configuration.

    1. Navigate: PeopleTools > Security > Security Objects > Single Signon.

    2. Ensure that both the default local node and the other node you are using are listed.

11. Testing Nodes.

    Both nodes must be 'pingable' from each database. On each database,

    1. Navigate: PeopleTools > Integration Broker > Service Operations Monitor > Administration > Node Status.

    2. Enter the node name and click the Ping Node button. It should respond successfully.

Configuring the PERSON_BASIC_SYNC Service

The PERSON_BASIC_SYNC service is the primary integration point for syncing core personal data between your CS and HCM systems. The following tasks detail how to configure the PERSON_BASIC_SYNC service to publish from your CS system and subscribe in the target HCM system.

• Owner/Subscriber: If you implement the owner/subscriber model, you can configure your PERSON_BASIC_SYNC service to publish from your primary CS system to your target HCM system.

• Subscriber Only: If you implement the subscriber–only model, you can configure the PERSON_BASIC_SYNC service in both your CS and HCM systems to publish and subscribe.

  Note: The source and target database configuration tasks described are for CS 9.2 (source) and HCM 9.1/9.2 (target) databases on PeopleTools 8.54.xx.

Configuring Campus Solutions as the Source Database

1. Update security by adding the Service Operation(s) to your primary permission list.

   1. Navigate to PeopleTools > Security > Permissions & Roles > Permission Lists.

   2. Select the relevant permission list from the search dialog box.

   3. Select the Web Services tab.

   4. Enter the corresponding Service(s) for the Service Operation(s) you want to use.

   5. Click the Edit link and select Full Access to provide access to the relevant Service Operation(s) listed on the Web Service Permissions secondary page.

   This graphic provides an example of the Web Service Access page for the PERSON_BASIC_SYNC operation.

   

2. Activate Service Operations and Create Routings in CS.

   1. Navigate to PeopleTools > Integration Broker > Integration Setup > Service Operations.

   2. Select PERSON_BASIC_SYNC from the search dialog box.

      This example illustrates the fields and controls on the PERSON_BASIC_SYNC service operation page. You can find definitions for the fields and controls later on this page.

      

   3. Check the Active check box on the General tab.

   4. Make note of the Queue Name field, as you need to verify that the PERSON_DATA Queue is in Running status later.

   5. Click the Handlers tab. Set the SCC_HR_PERSON handler to Active.

      This example illustrates the fields and controls on the PERSON_BASIC_SYNC Handlers page.

      

   6. Click the Routings tab and add a new routing for the Service Operation by entering a value in the Routing Name field and clicking the Add button.

      This example illustrates the fields and controls on the Routings page for PERSON_BASIC_SYNC.

      

   7. Define a Sender Node and a Receiver Node on the Routings Definition page of the Routings component.

      This example illustrates the fields and controls on the PERSON_BASIC_SYNC routing definition page. You can find definitions for the fields and controls later on this page.

      

   8. Verify that the Active check box is checked.

   9. Click the Parameters tab and set up the following:

      This example illustrates the fields and controls on the PERSON_BASIC_SYNC Routing Parameters page. You can find definitions for the fields and controls later on this page.

      

      Field or Control	Description
      External Alias	Enter the external alias; for example, PERSON_BASIC_SYNC.VERSION_4.
      Message.Ver into Transform 1	For example, PERSON_BASIC_SYNC.INTERNAL.
      Transform Program	For example, HCM_MSG_XFRM.
      Message.Ver out of Transforms	For example, PERSON_BASIC_SYNC.VERSION_4.

   10. Click Save at the bottom of the Parameters page to save the routing.

   11. Click Return at the bottom of the Parameters page to return to the Service Operation setup page.

   12. Click Save at the bottom of any page in the Service Operations component to save the Service Operation.

3. Activate Message Queue.

   1. Navigate to PeopleTools > Integration Broker > Service Operations Monitor, > Administration > Queue Status.

   2. Scroll down the page until you find the relevant PERSON_DATA Queue Name.

   3. Review the queue Status and activate the queue by clicking Run, if needed. The queue status should be set to Running before leaving this page.

      This example illustrates queue status for PERSON_DATA.

      

Configuring HCM as the Target Database

1. Update security by adding the service operation to the required user’s permission list.

   This example illustrates the fields and controls on the Web Service Permissions page for the PERSON_BASIC_SYNC service.

   

   1. Navigate to PeopleTools > Security > Permissions & Roles > Permission Lists.

   2. Select the relevant permission list from the search dialog box (primary permission list for the user).

   3. Click the Web Services tab.

   4. Enter the corresponding Service(s) for the Service Operation(s) you want to leverage.

   5. Click the Edit link and add access to the relevant Service Operation(s) listed on the Web Service Permissions secondary page.

   6. Click OK to return to the Web Services page.

   7. Click Save to save the updated Permission List.

2. Activate Service Operation(s) and Create Routing(s) and Subscription Handler in HCM:

   1. Navigate to PeopleTools > Integration Broker > Integration Setup > Service Operations.

   2. Select PERSON_BASIC_SYNC from the search dialog box.

   3. Check the Active check box on the General tab.

   4. Make note of the Queue Name field, as you need to verify that the PERSON_DATA Queue is in Running status later.

      This example illustrates the fields and controls on the General page for the PERSON_BASIC_SYNC service operation in HCM.

      

   5. Click the Handlers tab. Set the SCC_HR_PERSON handler to Active.

      This example illustrates the fields and controls on the Handlers page for the PERSON_BASIC_SYNC service operation in HCM.

      

      This example illustrates the fields and controls on the Handler Details page for the SCC_HR_PERSON handler in HCM.

      

   6. Select the Routings tab and add a new routing for the Service Operation by entering a value in the Routing Name field and clicking the Add button.

      This example illustrates the fields and controls on the Routings page for the PERSON_BASIC_SYNC service operation in HCM.

      

   7. Enter the CS Sender Node and an HCM Receiver Node on the Routings Definition page of the Routings component.

   8. Verify that the Active check box is checked.

      This example illustrates the fields and controls on the Routing Definitions page for the PERSON_BASIC_SYNC service operation in HCM.

      

   9. Select the Parameters tab and set the following:

      This example illustrates the fields and controls on the routing Parameters page for the PERSON_BASIC_SYNC service operation in HCM.

      

      Field or Control	Description
      External Alias	Enter the external alias; for example, PERSON_BASIC_SYNC.VERSION_4.
      Message.Ver into Transform 1	For example, PERSON_BASIC_SYNC.INTERNAL.
      Transform Program	For example, HCM_MSG_XFRM.
      Message.Ver out of Transforms	For example, PERSON_BASIC_SYNC.VERSION_4.

   10. Click Save at the bottom of the Parameters page to save the routing.

   11. Click Return at the bottom of the Parameters page to return to the Service Operation setup page.

   12. Click Save at the bottom of any page in the Service Operations component to save the Service Operation.

   This example illustrates Integration Broker inbound request routing for PERSON_BASIC_SYNC.

   

CS/SFP Integration: When PERSON_BASIC_SYNC is subscribed (local-to-local routing), it runs a subscription handler that invokes a POST FasStudentUpdateEvent to SFP. The Notification Handler SCC_SFP must be set to Active.

Notification handler for biographic or demographic updates