ELM Full Sync Integration Guided Process

7/21/2019 ELM Full Sync Integration Guided Process

1/62

An Oracle Red Paper

August 2013

ELM Full Sync Integration Guided Process


2/62


Introduction ......................................................................................... 1

Disclaimer ....................................................................................... 1

Structure of This Red Paper ............................................................ 2

Related Materials ............................................................................ 2

Chapter 1 Overview ......................................................................... 4

Who Should Read This Paper? ....................................................... 5

Before You Begin ............................................................................ 5

Common Terms .............................................................................. 5

Chapter 2 Basic Integration Broker Setup in HCM ........................... 8

Configure Local and Remote Message Nodes ............................... 8

Configure Single Sign-On ............................................................. 10

Configure Gateway ....................................................................... 10

Activate Domain ............................................................................ 15

Activate Queues ............................................................................ 16

Chapter 3 - Basic Integration Broker Setup in ELM .......................... 18

Configure Local and Remote Message Nodes ............................. 18

Configure Single Sign-On ............................................................. 20

Configure Gateway ....................................................................... 20

Activate Domain ............................................................................ 25

Activate Queues ............................................................................ 26

Chapter 4 - Activate Full Sync Integration ......................................... 28

Chapter 5 - Activate Learning Management Sync Integration........... 35

Chapter 6 - Setup Security ................................................................ 39

Chapter 7 - Define Remote System .................................................. 41

Chapter 8 - Using the ELM Full Sync Integration Guided Process ... 42

Navigation Subpage Area ............................................................. 43

Pagelet Area ................................................................................. 45

Target Content Area ...................................................................... 46

Example: Initiating and Monitoring Process Foundation Data ...... 46

Chapter 9 - Activate Incremental Sync Integration ............................ 52


3/62


Validation and Feedback ................................................................... 58

Customer Validation ...................................................................... 58

Field Validation .............................................................................. 58

Authors .............................................................................................. 58

Revision History ................................................................................ 58


4/62


Introduction

This red paper is a practical guide for technical users, installers, system administrators, and

programmers who implement, maintain, or develop applications for your PeopleSoft system.

This red paper discusses the Enterprise Learning Management (ELM) Full Sync Integration

Guided Process delivered in Human Capital Management (HCM) 9.2.

Much of the information in this document originated within Oracle PeopleSoft HCM/ELM

Development and is meant, therefore, to provide an informative overview of this new

functionality delivered in PeopleSoft HCM 9.2.

Disclaimer

This material has not been submitted to any formal Oracle test and is published as is.It has

not been the subject of rigorous review. Oracle assumes no responsibility for its accuracy or

completeness. The use of this information or the implementation of any of these techniques is

a customer responsibility and depends on the customer's ability to evaluate and integrate them

into the customer's operational environment. While each item may have been reviewed by

Oracle for accuracy in a specific situation, there is no guarantee that the same or similar

results will be obtained elsewhere. Customers attempting to adapt these techniques to their

own environments do so at their own risk.

Information in this red paper was developed in conjunction with use of the products specified

and is limited in application to those specific hardware and software products and levels.

Oracle may have patents or pending patent applications covering subject matter in this

document. The furnishing of this document does not give you any license to these patents.

1


5/62


Structure of This Red Paper

This red paper provides guidance implementing the ELM Full Sync Integration Guided

Process.

Oracle updates this document as needed so that it reflects the most current feedback from the

field. Therefore, the structure, headings, content, and length of this document may vary with

each posted version. To see if the document has been updated since you last downloaded it,compare the date of your version to the date of the version that is posted on My Oracle

Support.

Related Materials

This paper is not a general introduction to PeopleSoft Integration Broker and is written for

experienced IT professionals with a good understanding of the PeopleSoft Internet

Architecture. To take full advantage of the information in this document, you should have a

basic understanding of system administration, basic Internet architecture, integration

technologies, relational database concepts and SQL, and how to use PeopleSoft applications.

This document does not replace the PeopleTools 8.4x or 8.5x documentation. Before you read

this document, you should become familiar with the PeopleSoft Internet Architecture

information in the PeopleTools documentation to ensure that you have a well-rounded

understanding of the technology.

Note.Much of the information in this document may eventually be incorporated into

subsequent versions of the documentation.

2


6/62


3

The following documentation discusses many of the fundamental concepts that are related to

the PeopleSoft Internet Architecture:

PeopleTools: Getting Started with PeopleTools

PeopleTools: System and Server Administration

PeopleTools: PeopleSoft Application Designer Developers Guide

PeopleTools: PeopleSoft Integration Broker

PeopleTools: PeopleSoft Integration Broker Administration

PeopleTools: PeopleCode API Reference

PeopleTools Installation for your database platform

PeopleTools Hardware and Software Requirements

Additionally, you should be familiar with the documentation that is delivered with Oracle

Tuxedo, Jolt, and WebLogic.


7/62


8/62


COMPANY_FULLSYNC

POI_TYPE_TBL_FULLSYNC

BUS_UNIT_HR_FULLSYNC

JOBCODE_FULLSYNC

Position Data

POSITION_FULLSYNC

Person Data

PERSON_BASIC_FULLSYNC

WORKFORCE_FULLSYNC

To process this integration, users will need to configure Integration Broker on their HCM and ELM

environments so that they can communicate. This red paper provides a general overview of this

configuration using the new Integration Network Workcenter delivered in PeopleTools 8.53.

This section includes these topics:

Who Should Read This Paper?

Before You Begin

Common Terms

Who Should Read This Paper?

The audience for this red paper is technical and functional resources.

A technical resource with a solid understanding of configuring Integration Broker between PeopleSoft

environments will be interested in the integration configuration that supports the ELM Full Sync

Integration Guided Process.

A functional resource that has a good understanding of the full sync integration that needs to be

processed between HCM and ELM will be interested in how to use the ELM Full Sync Integration

Guided Process to initiate and monitor the full sync integration between HCM and ELM.

Before You Begin

The topics covered in this red paper require a general understanding of required integration setup

between HCM and ELM and of the HCM data that is required to implement PeopleSoft 9.2 ELM.

Common Terms

The following table defines some of the common terms that are used in this guide.

TABLE 1. COMMON TERMS

5


9/62


TERM DEFINITION

Integration Broker PeopleSoft Integration Broker is a middleware technology that performs asynchronous and

synchronous messaging among internal systems and third-party systems.

Gateway The Gateway manages different types of messages that flow into and out of your PeopleSoft

application. The Gateway has specific connectors and properties that manage different types of

internal and third-party messages.

Domain These Application Server pub/sub services must be active in order to facilitate Integration Broker

messaging.

Message Nodes Nodes represent any organization, application, or system that will be part of an integration.

For example, nodes can represent customers, business units, suppliers, other trading partners,

external or third-party software systems, and so on.

Node definitions define the locations to or from which messages can be routed.

Default Local and Remote

Nodes

Each PeopleSoft Integration Broker database involved in an integration point must contain a default

local node definition for itself and a remote node definition for each of the other nodes involved.

Local and remote nodes are concepts relative to the database in which the nodes are defined.

If a user is signed on to Database A, which has Node A defined, then Node A is local.

If a user is signed on to Database B, then Node A is defined as remote.

If the following definitions exist in the Node A database

NODE_A (default local)

NODE_B (remote)

Then the following definitions must exist in the Node B database for it to integrate with Node A:

NODE_A (remote)

NODE_B (default local)

The only local node definition used by PeopleSoft Integration Broker is the one designated as the

Default Local, which represents the database on to which the user is signed on.

Service Operations A service operation represents integration between one or more applications or systems. It has a

specific configuration that determines how the operation will be processed, synchronously or

asynchronously. In addition, it contains routings that determine the direction, inbound or outbound, of

the service operation. A service operation has one or more handlers that contain and run the

programming logic for sending or receiving the message, manipulating message content, and so on.

Queues These queue service operations for processing.

Integration Points This is another name for a service operation.

Handlers These are associated with a service operation. A handler contains specific programming logic for

sending or receiving a message or for manipulating message content.

Routings These are associated with a service operation. A routing contains specific information that determines

the direction of the integration, inbound or outbound. Routings may have additional parameters to

transform a message when is it sent or received.

6


10/62


TABLE 1. COMMON TERMS

TERM DEFINITION

Integration Groups Integration groups provide a way of grouping like services that are associated with service operations.

Full Synchronization This type of synchronization synchronizes alldata between a Source and Target application.

Incremental Synchronization This type of synchronization synchronizes incremental changes between a Source and Target

application.

Introspection and

Deployment

This is the process of identifying integration setup that needs to be activated or created to deploy

service operations (integration points) between two PeopleSoft applications.

Integration Network

Workcenter

This is a new workcenter in PeopleTools 8.53 that consolidates many of the integration setup tasks into

one centralized workcenter.

Guided Process This is a new feature in HCM that enables users to define actions that must be completed within a

specific business process. Optionally, this feature can prompt users with up-front questions as to what

actions they want to perform within the business process. It then generates a PeopleTools Activity

Guide instance and transfers the user into a Workcenter page, where the user will be guided through

the steps to complete the business process.

Activity Guide This is a new PeopleTools 8.53 feature that generates a specific user instance of a pagelet area in a

workcenter that contains actions a user can complete within a specific workcenter. The activity guide

pagelet area tracks and monitors the status of the completed actions.

Integration Process Request This is a new feature that automates and streamlines the initiation of one or more full sync integrations

from PeopleSoft HCM. This feature also includes the ability to monitor and track the status of an

Integration Process Request.

Full Data Publish Rules Full Data Publish Rules control how a full-sync integration will process. Enterprise Components owns

these rules.

Full Data Publish Process This process initiates and publishes full-sync integrations.

Process FullSync Data This is an ELM process that retrieves data loaded into an ELM staging table and loads that data into

the final ELM table.

7


11/62


12/62


13/62


Again, the Authentication Option is defined as Password; therefore, you must specify a password for

the ELM node. The password for this node should be same as the node password defined in ELM for

the default local node.

Define the Connectors for this node as follows:

Figure 4. Connector page in ELM

Configure Single Sign-On

Because the two message nodes created for HCM and ELM represent PeopleSoft applications, the

trusted nodes for the Single Sign-on setup need to be updated to reflect these new nodes.

Navigate to PeopleTools, Security, Security Objects, Single Signon and insert the message nodes for

HCM and ELM.

Figure 5. Single Signon page in HCM

Configure Gateway

The Integration Gateway platform manages the actual receipt and delivery of messages passed among

systems through the Integration Broker. Messages are received through listening connectors and are

delivered from target connectors. The Gateway Manager is a dispatcher for messages that flow through

the Integration Gateway.

A gateway must be configured within the HCM and ELM databases so that they are able to

communicate with each other.

10


14/62


Local and remote integration gateways must be at the same or higher version as the application servers

with which they communicate. For the ELM Full Sync Integration Guided Process, the version should

be PeopleTools 8.53 or higher.

Navigate to PeopleTools, Integration Broker, Integration Network Workcenter, Gateway.

Search and access the Gateway ID LOCAL.

Figure 6. Gateways page in HCM

The steps to configure the Gateway are:

1. Specify the Gateway URL.

2. Load Gateway Connectors.

3. Update Gateway Setup properties.

Specify the Gateway URL

Specify the URL with the format:

http://machinename:port/PSIGW/PeopleSoftListeningConnector

The machinename:port is the machine name and port, host name, or IP address of the web server

hosting the gateway.

11


15/62


16/62


17/62


Figure 10. Gateway Properties sign-on in HCM

Enter the User ID, Password, and click OK to access the Gateway Properties.

The PeopleSoft Node Configuration page appears:

Figure 11.Screenshot of PeopleSoft Node Configuration page in HCM

The PeopleSoft Node Configuration page enables you to specify a Gateway Default App Server and

the local target nodes.

When the integration gateway receives an inbound message, it will receive the name of the message andthe target node for the message. If the message does not have a target node, then the Gateway Default

App Server settings will be used.

However, if the target node is specified for the message, then it will search the PeopleSoft Nodes

specified for the gateway so that it can direct the message properly.

14


18/62


For the integration between PeopleSoft HCM and ELM, you do not have to specify a Gateway Default

App Server. However, you do have to enter the HCM and ELM nodes that you created in the

PeopleSoft node grids.

Figure 12. PeopleSoft Nodes in HCM

The App Server URL consists of the machine name and the Oracle Jolt port number. The Jolt port

number can be found in the JOLTListener section in the psappsrv.cfg file or by using psadmin.exe to

review the JSL port setting for the application server configuration.

The User ID and Password are the User ID and Password specified when you created the application

server domain. PeopleSoft Integration Broker will automatically encrypt this password entry.

The Tools Release is the version number installed on the application server. Limit the number you

enter to two decimal places, for example, 8.53.

Click the Save button.

When you click the Ping Node button, it should return success for the HCM node. However, because

the integration setup is not complete in the ELM database, you will receive an authentication error.

Activate Domain

For integration between HCM and ELM to process, you must verify that the Integration Broker

domain is active.

Navigate to PeopleTools, Integration Broker, Integration Network Workcenter, Domain.

Figure 13.Screenshot of the Domain Status page in HCM

15


19/62


20/62


21/62


22/62


The Authentication Option is defined as Password; therefore, you will need to specify a password for

this node. Because this node will also be defined in HCM, it is important that the password specified in

HCM is the same, otherwise you will encounter an integration error.


Figure 16. Connectors page in ELM

You also need to create a node that represents the remote HCM database. The node name should

match the default local node name defined in HCM.

Figure 17. Node Definitions page in ELM

19


23/62


Again, the Authentication Option is defined as Password; therefore, you will need to specify a

password for the HCM node. The password for this node should be same as the node password

defined in HCM for the default local node.


Figure 18. Connectors page in ELM

Configure Single Sign-On

The two message nodes created for HCM and ELM represent PeopleSoft applications, so the trusted

nodes on the Single Sign-On setup need to be updated to reflect these new nodes:

Navigate to PeopleTools, Security, Security Objects, Single Signon and insert the message nodes for

HCM and ELM.

Figure 19. Single Signon page in ELM

Configure Gateway

The Integration Gateway platform manages the actual receipt and delivery of messages passed among

systems through the Integration Broker. Messages are received through listening connectors and aredelivered from target connectors. The Gateway Manager is a dispatcher for messages that flow through

the Integration Gateway.

A gateway must be configured within the HCM and ELM databases so that they are able to

communicate with each other.

20


24/62


Local and remote integration gateways must be at the same or higher version as the application servers

with which they communicate. For the ELM Full Sync Integration Guided Process, the version should

be PeopleTools 8.53 or higher.

Navigate to PeopleTools, Integration Broker, Integration Network Workcenter, Gateway.

Search and access the Gateway ID LOCAL:

Figure 20. Gateways page in ELM

The steps to configure the Gateway are:

Specify the Gateway URL.

Load Gateway Connectors.

Update Gateway Setup properties.

Specify the Gateway URL

Specify the URL with the format:

http://machinename:port/PSIGW/PeopleSoftListeningConnector

The machinename:port is the machine name and port, host name, or IP address of the web server

hosting the gateway.

21


25/62


For HTTPS, the URL should start with https. The integration gateway URL is case sensitive.

Figure 21. Gateways page in ELM showing URL

After you specify the URL, ping the Gateway to see if it is active.

When you click the Ping Gateway button, a new web browser window will open, indicating the status

of the integration gateway:

Figure 22. Example of the PeopleSoft Integration Gateway status in ELM

Load Gateway Connectors

The Connectors grid on the Gateways page lists the target connectors registered with the currentgateway. Initially, none of the delivered connectors is loaded and the grid is empty. You can load target

connectors automatically by clicking the Load Gateway Connectors button or you can manually enter

information in the grid.

22


26/62


Figure 23. Gateway Connectors grid in ELM

Click the Load Gateway Connectors button to have PeopleSoft Integration Broker examine the

properties of all installed target connectors and then load those properties into the gateway definition.

All the connectors appear in the Connectors grid, and the properties of each connector are updated to

reflect its current state.

Note.The Load Gateway Connectors button never overrides existing information. It only adds

missing information, so manually edited values are not affected. If you modified a connector, new and

modified properties are loaded and do not interfere with existing properties.

We are communicating between PeopleSoft applications, so it is important that Connector ID forPSFTTARGET is listed as a connector.

Update Gateway Setup Properties

The Gateway Setup properties allow you to configure the PeopleSoft Node Configuration, which

consists of the Oracle Jolt connections for unknown (default) and known message nodes.

Click the Gateway Setup Properties link and log into the Gateway properties page.

23


27/62


Figure 24. Gateway Properties sign-on page in ELM

Enter the User ID, Password, and click OK to access the Gateway Properties.

The PeopleSoft Node Configuration page appears:

Figure 25. PeopleSoft Node Configuration page in ELM

The PeopleSoft Node Configuration page enables you to specify a Gateway Default App Server and

the local target nodes.

When the integration gateway receives an inbound message, it will receive the name of the message andthe target node for the message. If the message does not have a target node, then the Gateway Default

App Server settings will be used.

However, if the target node is specified for the message, then it will search the PeopleSoft Nodes

specified for the gateway so that it can direct the message properly.

24


28/62


For the integration between PeopleSoft HCM and ELM, you do not have to specify a Gateway Default

App Server. However, you do have to enter the HCM and ELM nodes that you created in the

PeopleSoft node grids.

Figure 26. PeopleSoft Nodes grid in ELM

The App Server URL consists of the machine name and the Oracle Jolt port number. The Jolt port

number can be found in the JOLTListener section in the psappsrv.cfg file or by using psadmin.exe to

review the JSL port setting for the application server configuration.

The User ID and Password are the User ID and Password specified when you created the application

server domain. PeopleSoft Integration Broker will encrypt this password entry automatically.

The Tools Release is the version number installed on the application server. Limit the number you

enter to two decimal places, for example, 8.53.

Click the Save button.

Click the Ping Node button, and it should return success for the HCM and ELM node.

Activate Domain

For integration between HCM and ELM to process, you need to verify that the Integration Broker

domain is active.

Navigate to PeopleTools, Integration Broker, Integration Network Workcenter, Domain.

Figure 27. Domain Status page in ELM

25


29/62


30/62


Update the Queue Status to Run and then click Save. Repeat these steps for each queue that needs to

be activated.

27


31/62


32/62



WORKFORCE_FULLSYNC

In the HCM database, navigate to PeopleTools, Integration Broker, Integration Network WorkCenter,

Introspection/Deployment.

Figure 30. Search for Items - Introspection/Deployment page in HCM

To activate full sync integration, set the Integration Group Name to LEARNING MANAGEMENT

and select the Filter by Subgroup to FULL SYNC INTEGRATIONS as shown here:

Figure 31. Level group box

Click Search.

By clicking Search, all full sync integration for Learning Management will appear in the Select Items to

Process grid:

29


33/62


Figure 32. Select Items to Process grid

To view all rows, click the View All option for the Select Items to Process grid and select the following

12 full sync services:

COUNTRY_FULLSYNC

CURRENCY_FULLSYNC STATE_FULLSYNC

SETID_INITIALIZE

DEPT_FULLSYNC

COMPANY_FULLSYNC

POI_TYPE_TBL_FULLSYNC

BUS_UNIT_HR_FULLSYNC

JOBCODE_FULLSYNC

POSITION_FULLSYNC


WORKFORCE_FULLSYNC

30


34/62


35/62


36/62


37/62


38/62


Chapter 5 - Activate Learning Management Sync Integration

The ELM Full Sync Integration Guided Process is dependent on two sync integrations that must be

activated in order to communicate with the ELM application to:

Initiate the Process Full Sync Data

This process loads data populated in ELM Staging tables to the final ELM table.

Retrieve the process scheduler status of Process Full Sync Data

The process scheduler status is used to determine if Process Full Sync Data successfully completed.

To activate this sync integration, you will use the Introspection and Deployment task in the Integration

Network Workcenter. This task enables you to activate and deploy one or more integrations between

the default local node (HCM) and a target node (ELM).

In the HCM database, navigate to PeopleTools, Integration Broker, Integration Network WorkCenter,

Introspection/Deployment.

Figure 38. Search for Items Introspection/Deployment page


and select the Filter by Subgroup option and enter SYNC REQUEST INTEGRATIONS as shown

below:

35


39/62


Figure 39. Example of the values entered for Integration Group Name and Subgroup

Click Search.

By clicking Search, all full sync integration for Learning Management will appear in the Select Items to

Process grid:

Figure 40. Select Items to Process grid showing values

If you deselect HMCR_FRAMEWORK and click Continue, the Target page will appear:

Figure 41. Target page

36


40/62


The Target page enables you to identify the Remote Node you want to activate the full sync integration

against. Since you are logged into the HCM database, select the node that represents ELM, LM92T214,

as the node to process.

Click Continue and the Introspection/Deployment page will appear:

Figure 42. Introspection/Deployment page

This page displays the Node that you are introspecting against to activate the full sync integration

points listed in the Operation List grid.

By clicking the Introspect button, the system will generate a list of the integration broker setups that

must be deployed. It will identify if service operations, handlers, and routings need to be activated.

Here are the Introspection Results generated by Introspection for the sync integrations beingprocessed:

Figure 43. Example of the Introspection Results page

37


41/62


At the bottom of this page, you can select all Deployment actions and click the Deploy button to

deploy and activate the integration:

Figure 44. Example of the Introspection controls

Click Select All and Deploy to activate full sync integration between HCM and ELM.

The Introspection Results will be updated with the status of the deployment action taken:

Figure 45. Introspection Results page after clicking Deploy

38


42/62


43/62


44/62


Chapter 7 - Define Remote System

The ELM Full Sync Integration Guided Process uses two new components to initiate and monitor an

integration request containing one or more full sync integrations. These new components are part of a

new HCM framework called Integration Process Request.

The Integration Process Request framework has a setup table that contains specific information about

how integrations need to be processed when included in an integration process request.

For example, when initiating certain integrations between HCM and ELM, the data goes to a staging

table and another process in ELM is required to be executed. The setup table in the Integration

Process Request framework has information about this additional step that must be executed in the

ELM application to complete the processing of the integration.

To ensure that these additional steps are loaded into an integration process request, the Integration

Process Request Remote System table must be configured. This table stores a mapping between aRemote System ID and the Message Node that represents that remote system.

Note.To access this setup table, the user needs to be assigned the Integration Process Admin role.

In HCM, navigate to Set Up HCM, Common Definitions, Integration Process, Define Remote System.

Access Remote System LM for Learning Management:

Figure 48. Define Remote System page

Enter the Message Node that represents ELM and click Save.

41


45/62


Chapter 8 - Using the ELM Full Sync Integration Guided Process

After the HCM and ELM environments have been configured for Integration Broker, full sync

integration activated, user security assigned to appropriate User IDs in HCM and ELM, and the

Remote System configured, you are now ready to use the ELM Full Sync Integration Guided Process.

To initiate and access the ELM Full Sync Integration Guided Process, navigate to Set Up HCM,

Common Definitions, Guided Process, Select Guided Process.

Figure 49. Select Guided Process page

Using the Guided Process drop-down list, select Learning Management Full Sync Integration Process

and a guided process questionnaire will appear:

Figure 50. Select Guided Process page with a Guided Process selected

The guided process questionnaire enables you to personalize the process of running full sync

integration by allowing you to indicate what full sync integration you want to process. Each question

42


46/62


you answered with a Yes will include the steps in the guided process to initiate that full sync

integration.

If the user is unsure about the effect of answering the questions, he can click the More Information

icon in the row to view a pop-up page that provides details.

After the user has responded to the questions, she clicks the Start My Guided Process button. This

action transfers the user into the Guided Process Workcenter and provides an Activity Guide pagelet

that displays the steps the user needs to complete to process full sync integration between HCM and

ELM.

Based on the users responses to the questionnaire, different steps will be included in the Learning

Management Full Sync Integration Process.

For example, if the user answers Yes to all the questions, then the following steps will appear in the

Guided Process Workcenter:

Figure 51. Guided Process Workcenter Welcome page

The Guided Process Workcenter is broken down into the following three areas:

Navigation subpage area

Pagelet area

Target Content area

Navigation Subpage Area

In the Navigation subpage area, users can access these navigational buttons:

Figure 52. Navigational buttons in the Guided Process Workcenter

43


47/62


Previous

The Previous button enables you to move to the previous step in the guided process.

Next

The Next button enables you to move to the next step in the guided process.

Mark Complete

The Mark Complete button enables you to mark the step completed manually. This button is only

needed for pages that contain nothing to save.

For example, the Overview page. Once you finish reading the text on the page, users can click the

Mark Complete button to proceed.

Cancel

This button will delete the current instance of the Learning Management Full Sync Integration

Process and return you to the Select Guided Process page.

The deletion of the current instance of the Learning Management Full Sync Integration will notaffect the full sync integration processed or in process.

It is not recommended that the current instance be deleted while full sync integration is

processing. Once the current instance is deleted, the user will not have access to review the status

of the full sync integration that is processing.

Exit

This button enables you to exit the current instance of the Learning Management Full Sync

Integration Process and returns you to the Select Guided Process page.

The user is able to return to the current instance of the Learning Management Full Sync

Integration by selecting the guided process again.

44


48/62


Pagelet Area

Figure 53. Pagelet area of the Workcenter

The Pagelet area displays a high-level section associated to each guided process question you

answered Yes to.

For the Learning Management Full Sync Integration Process, we deliver four sections that enable the

user to initiate and monitor full sync integration for:

Foundation Data

Organization Data

Position Data

Person Data

To view all the steps in a high-level section, the user can expand the section by clicking the Expand

Link icon:

Figure 54. Expand Link icon

45


49/62


50/62


Monitor Integration Request

For the Overview, this information will appear in the Target area:

Figure 56. Guided Process Workcenter showing each section expanded

Because there is nothing to be saved on this page, you can click the Mark Complete button to update

the status of this step. This action will update the status of the section to In Progress, and the number

of tasks completed will be reflected in the Task Progress bar.

Figure 57. Guided Process Workcenter after clicking Mark Complete

To move to the next step, you can click the Next button in the upper right-hand corner of the

Workcenter or click the Create Integration Request step.

When you navigate to Create Integration Request, the following page will appear in the Target area:

47


51/62


52/62


Figure 60. Create Integration Process Request page after clicking Execute Integration Process

To move to the next step, you can click the Next button in the upper right-hand corner of the

Workcenter or click the Monitor Integration Request step.

The Monitor Integration Request will display the status of the Integration Process Request you just

generated. On this page, you will be able to view the processing status of Foundation Data integration:

Figure 61. Review Integration Process Request page

The Refresh button enables you to refresh the page as the integration is processing.

The following Service Statuses appear on this page:

NewThe service operation has not been processed.

Processing

The service operation is processing.

49


53/62


Done

All the steps for the service operation are complete.

Cancelled

The service operation was canceled due to an error.

If one of the service operations was canceled, then all subsequent service operations will be

canceled and the status of the integration request will be set to Cancelled.

You are able to click the Process Details link to review details about the full sync integration being

processed:

Figure 62. Process Details page

Depending on the full sync integration, more than one step may be involved in processing the

integration.

For example, if the full sync integration updated a staging table in ELM, then Process Full Sync Datawill be another step that is executed to complete the full sync integration.

These Step Statuses appear on this page:

New

The step for the service operation has not been processed.

Processing

The step for the service operation is processing.

Done

The step for the service operation is done.

Cancelled

The step for the service operation is cancelled due to an error.

If one of the service operations steps was canceled, then all subsequent service operations and

steps will be canceled, and the status of the integration request will be set to Cancelled.

50


54/62


You are able to click the Message Log Details link to review messages generated for processing the

step:

Figure 62. Message Log Details page

When all the full sync integration is completed, click the Mark Complete button and the Monitor

Integration Request will be marked as completed and the whole section will be marked as complete.

Figure 63. Pagelet area after Monitor Integration Request is marked as complete

Processing the full sync integration for Organization Data, Position Data, and Person Data works the

same way.

51


55/62


56/62


Figure 64. Search for items - Introspection/Deployment page in HCM


and select the Filter by Subgroup to INCREMENTAL SYNC INTEGRATIONS as shown below:

Figure 65. Integration Group and Subgroup

Click Search

By clicking Search, all incremental sync integration for Learning Management will appear in the Select

Items to Process grid:

53


57/62


Figure 66. Select Items to Process grid in HCM

To view all rows, click the View All option for the Select Items to Process grid and select the following

11 incremental sync services:

COUNTRY_SYNC

CURRENCY_SYNC

STATE_SYNC

DEPT_SYNC

COMPANY_SYNC

POI_TYPE_TBL_SYNC

BUS_UNIT_HR_SYNC

JOBCODE_SYNC

POSITION_SYNC

PERSON_BASIC_SYNC

WORKFORCE_SYNC

Click Continue and the Target page will appear:

54


58/62


Figure 67.Screenshot of the Target page in HCM

The Target page enables you to identify the Remote Node you want to activate the full sync integration

against. You are logged into the HCM database, so select the node that represents ELM, LM92T214,

as the node to process.

Click Continue and the Introspection/Deployment page will appear:

Figure 68. Introspection/Deployment page in HCM

55


59/62


This page displays the Node that you are introspecting against to activate the full sync integration

points listed in the Operation List grid.

By clicking the Introspect button, the system will generate a list the integration broker setup that needs

to be deployed. It will identify if service operations, handlers, and routings need to be activated.

To ensure that routings are created with the appropriate transformation settings required for HCM and

ELM integration, the system uses a new Deployment Configuration table in PeopleTools 8.53 that

contains information about how the integration routings must be created and activated.

Here are the Introspection Results generated by Introspection against the 12 integrations selected:

Figure 69. Introspection Results page

At the bottom of this page, additional controls are available to select all Deployment Actions and to

deploy and activate the integration:

Figure 70. Additional controls to Select All and Deploy

Click Select All and Deploy to activate full sync integration between HCM and ELM.

The Introspection Results will be updated with the status of the deployment action taken:

56


60/62


Figure 71. Introspection Results page after clicking the Deploy button

57


61/62


62/62

ELM Full Syc Integration Guided Process

August 2013

Author: PeopleSoft HCM Development

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U S A

Copyright 2013, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the

contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other

warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or

fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are

formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective

owners

Documents

ELM Full Sync Integration Guided Process