Implementing the Oracle Workforce Administration for PeopleSoft Human Resources Partial Process Integration Pack

This chapter provides an overview of the Oracle Workforce Administration Integration Pack for PeopleSoft Human Resources Application Integration Architecture (AIA), and discusses how to:

• Activate integrations.

• Publish the data.

• Launch the integration service.

• Populate the domain value maps.

Understanding the Workforce Administration for PeopleSoft Human Resources Integration

Oracle provides a partial Process Integration Pack (PIP) that publishes reference data information through the Application Integration Architecture (AIA) layer and sends PeopleSoft HR person, worker, and talent profile entries through AIA to a staging table in PeopleSoft. From there, your organization can build your own integrations to desired target systems.

As part of the Workforce Administration for PeopleSoft HR partial integration pack, PeopleSoft delivers the following:

• New services for synchronization and validation of reference data for use from PeopleSoft HR to the target system.

• Domain Value Maps (DVMs) within PeopleSoft Enterprise Components to define and transform common values for control data between PeopleSoft and the target system

These services are provided to publish data for load and synchronization for the process integration between PeopleSoft HR and the target system:

• Full synchronization for initial loading of person, worker, and talent profile data

• Incremental synchronization and update of person, worker, and talent profile data

Note. Changes that are delivered for the Oracle Workforce Administration Integration Pack for PeopleSoft Human Resources Application Integration Architecture (AIA) are posted on My Oracle Support website (http://metalink.oracle.com).

Prerequisites

To activate services and publish data for the integration between Workforce Administration for PeopleSoft HR and the target system:

• Confirm that all DVMs, both PeopleSoft and Application Integration Architecture (AIA) DVMs, are populated

• Read and become familiar with information in Oracle Workforce Administration Integration Pack for PeopleSoft Human Resources 3.1 Implementation Guide.

See Also

Enterprise PeopleTools PeopleBook, Integration Broker, "Using the Service Operations Monitor."

Enterprise PeopleTools PeopleBook: Integration Broker, "Managing Integration Gateways."

Activating Integrations

To activate the Workforce Administration for PeopleSoft HR process integration, you must complete specific setup tasks and activate the gateways and service operations that are specific to the Workforce Administration for PeopleSoft HR process integration.

The tables in this section list the setup tasks to accomplish and the gateways and service operations to activate.

Setup Tasks

This table lists tasks for activating integrations in your database. You should perform these setup tasks on both the publishing and subscribing databases, unless stated otherwise.

Sync Messages

This table lists the gateways and service operations to activate for sync messages:

Full Sync Messages

This table lists the gateways and service operations to activate for full sync messages:

Steps to Activate Integration Broker Gateways

To activate Integration Broker gateways, complete the following steps:

1. Ping the local gateway (PeopleTools, Integration Broker, Configuration, Gateways) to ensure it is running, the connectors are loaded, and that the status is Active.

2. Click the Gateway Setup Properties link on the Gateways page, and ensure that the default local node, usually the database name, has an entry on the PeopleSoft Node Configuration page.

3. Ensure that the default local node, usually the database name, is appended to the Target Location URL at the service configuration (PeopleTools, Integration Broker, Configuration, Service Configuration).

4. Verify that the Domain and its IB dispatchers are running (PeopleTools, Integration Broker, Service Operations Monitor, Administration, Domain Status).

5. Activate node definitions (PeopleTools, Integration Broker, Integration Setup, Nodes).

See Enterprise PeopleTools PeopleBook: Integration Broker, "Managing Integration Gateways."

Steps to Activate Service Operations

To activate service operations, complete the following steps:

1. Access the service operations that are listed for this integration (PeopleTools, Integration Broker, Integration Setup, Service Operations).

2. Review service operation security by clicking the Service Operation Security link and select Active for General, Handler Status and Routings.

Steps to Activate Delivered Outbound Routings

To activate delivered outbound routings (activate routings that include external alias and transform properties), complete these steps:

1. Access the Routings page (PeopleTools, Integration Broker, Integration Setup, Service Operations, Routings).

2. From the Routings tab, select the Selected check box for the outbound routing whose Receiver Node is PSFT_XOUTBND, and click the Activate Selected Routings button.

3. Click the routing name to access the Routing Definitions page. Confirm that the Sender Node on this page is the default local node name and the Receiver Node is the AIA node PSFT_XOUTBND.

4. Click the Connector Properties page and replace the <id:port> within the PRIMARYURL by the FMW server host name and port number.

5. After the PSFT resolutions are applied, recycle both the PSFT App Server and the PSFT Process Scheduler (Stop/Clear Cache/Start). Recycling these ensures that all of the new IB objects in the resolutions will work correctly.

See Enterprise PeopleTools PeopleBook, Integration Broker, "Using the Service Operations Monitor."

See Enterprise PeopleTools PeopleBook, Integration Broker, "Providing Services."

Publishing Data

After you initiate the integration, you must publish the data and launch the integration services. This section discusses how to:

• Publish initial setup (fullsync) data.

• Publish incremental setup (sync) data.

Publishing Initial Setup (FullSync) Data

Full sync set up is typically a one-time setup activity using service operations with the _FULLSYNC suffix.

Use the Full Table Publish utility to publish the entire setup table. The subscribing database erases its setup table and synchronizes itself by supplying and populating data from the service operation.

Make sure that you have activated the full publish rules before you run this process.

Publishing Incremental Setup (Sync) Data

Incremental sync changes use service operations with a _SYNC suffix, which are associated with setup pages. When you make changes to corresponding setup data, such as names and addresses, a service operation is published automatically when you save the page.

Launching the Integration Services

Making updates to the pages listed in this section or running their associated processes, triggers services for the integration with Workforce Administration for PeopleSoft HR.

Pages that Launch the Integration Services

Populating the Domain Value Maps

This section provides an overview of domain value maps (DMVs) and discusses how to populate the DVMs.:

Understanding the DVMs

A DVM is a standard feature of Oracle's Service Oriented Architecture (SOA) Suite. DVMs are XML files that contain the mapping between related information in the participating applications. The Application Integration Architecture (AIA) DVMs are maintained in the AIA layer and are used to transform the messages from one system to the expected format of the other system. PeopleSoft maintains DVMs in addition to the DVMs that are stored within AIA. The AIA DVMs and their corresponding PeopleSoft DVMs should be maintained in both systems.

The PeopleSoft ABCS does not reference the AIA domain value maps (DVMs) at runtime.

The transformation within PeopleSoft Integration Broker populates the EBM with AIA Common values using the PeopleSoft Application Integration Framework for DVMs domain value map (DVM) framework, and passes the common values in the Sync<data type>ListEBM.

PeopleSoft DVM values are provided in the AIA DVM to help the end user understand the context for populating DVM data for each participating system requiring DVM translation in their ABCS. The values in the AIA DVM for PeopleSoft are not used by the integration. The ABCS of each participating system requiring DVM translation can use the AIA DVM data to translate to values specific to that system.

Update the PeopleSoft DVMs prior to running any initial loads or initiating any incremental setup or transactional flows.

The PeopleSoft DVMs must be populated, maintained, and synchronized with their corresponding AIA DVM.

It is important to remember that any AIA DVM with a corresponding PeopleSoft DVM must be maintained in both PeopleSoft and in AIA. The AIA DVMs map the data in the third-party target system column to the COMMON column, and the PeopleSoft DVMs map the COMMON column to the PSFT_01 column. The PeopleSoft values within the AIA DVMs are provided as reference only for those DVMs with a corresponding PeopleSoft DVM.

Pages Used to Create and Maintain the DVMs

See Also

Enterprise Components: Application Integration Framework Documentation Update, Defining and Populating Value Maps.

Populating the DVMs

Access the Populate Domain Value Maps page (Enterprise Components, Integration Definitions, Transformation Framework, Populate Domain Value Maps):

Access all of the PeopleSoft DVMs that are used in the Workforce Administration for PeopleSoft HR integration. Populate or verify that all values are included and that the COMMON values are the same as those in the corresponding AIA DVMs.

To access and update the corresponding AIA DVMs, log into Oracle Enterprise Manager - ESB Control and click the Maps icon.

See For a list of the PeopleSoft DVMS and their AIA DVM counterparts that are delivered for use with each Workforce Administration for PeopleSoft HR integration scenario: Oracle Workforce Administration Integration Pack for PeopleSoft Human Resources 3.1 Implementation Guide, "Integration Scenarios"

See Oracle Workforce Administration Integration Pack for PeopleSoft Human Resources 3.1 Implementation Guide, "Populating the PeopleSoft Domain Value Map (DVMs)".