ELM Full Sync Integration Guided Process

An Oracle Red Paper
August 2013
ELM Full Sync Integration Guided Process


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 ............................................................... 21
Configure Gateway ......................................................................... 21
Activate Domain .............................................................................. 26
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

Validation and Feedback .................................................................... 58
Customer Validation ....................................................................... 58
Field Validation ............................................................................... 58
Authors ................................................................................................ 58
Revision History .................................................................................. 58

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

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

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, J olt, and WebLogic.
3

Chapter 1 Overview
Enterprise Learning Management (ELM) is designed to integrate with other applications to enable the
sharing of person and organization data. You can use the integration points that are delivered with
ELM to import data for internal learners and departments from PeopleSoft Human Capital
Management (HCM). PeopleSoft HCM will remain the system of record for all the imported data; this
data can be viewed, but not changed, in ELM.
The delivered integration points are designed to work with PeopleSoft HCM.
Note. You can import data from any XML-compliant HR application; however, modifications to the
integration points are necessary. This topic is not covered in this document.
Integration points are divided into two distinct categories: full sync and incremental sync. ELM uses
full sync integration points during system implementation to import all data for a given set of HCM
tables. After all full sync points are processed, Incremental Sync integration points are activated to
ensure that additions, modifications, and deletions of data in PeopleSoft HCM are imported into ELM.
To manage integration between PeopleSoft HCM and ELM, Integration Broker technology is used to
configure, activate, and monitor integration that synchronizes a given set of HCM tables. In addition to
this technology, Enterprise Components integration definitions and processes are used to configure
full sync data rules and to initiate the full sync integration points.
When you run a full or incremental integration point, the imported data is either loaded directly into
the ELM tables or sent to a staging table for validation before it is loaded. The process depends on the
type of data that is being imported. Because of data dependencies, some integration points must be run
in a specific order. Generally, data that is updated frequently or for which there is a high volume, such
as learner and workforce data, will go to a staging table first.
To improve and simplify the processing of full sync integration points between PeopleSoft HCM and
ELM, Oracle delivered a new feature, ELM Full Sync Integration Guided Process, in PeopleSoft 9.2.
This feature will enable users to initiate and monitor full sync integration points between HCM and
ELM, including the process that validates and loads ELM data from a staging table.
Users will be able to initiate and monitor the following full sync integration points:
Foundation Data
COUNTRY_FULLSYNC
CURRENCY_FULLSYNC
STATE_FULLSYNC
SETID_INITIALIZE
Organization Data
DEPT_FULLSYNC
4

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

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

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 all data 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

Chapter 2 Basic Integration Broker Setup in HCM
This chapter provides an overview of the required Integration Broker setup in HCM in order to use
the ELM Full Sync Integration Guided Process and discusses these topics:
Configure Local and Remote Message Nodes
Configure Single Sign-On
Configure Gateway
Activate Domain
Activate Queues
More detailed information about Integration Broker can be found in PeopleSoft PeopleTools 8.53
online documentation.
In the HCM environment, you must create a default local node for the HCM database.
Navigate to PeopleTools, Integration Broker, Integration Setup, Nodes to access this setup.

Figure 1. Node Definitions page in HCM
8

The Authentication Option is defined as Password; therefore, you must specify a password for this
node. Because this node will also be defined in ELM, the password specified in ELM must be the
same, otherwise you will encounter an integration error.
Define the Connectors for this node as follows:

Figure 2. Connectors page in HCM

You also need to create a node that represents the remote ELM database. The node name should
match the default local node name defined in ELM.

Figure 3. Node Definitions page in ELM
9

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.

Figure 4. Connector page in ELM
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

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

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

Figure 7. Gateway URL in HCM

After you specify the URL, ping the Gateway to see if it is active.
When you click the Ping Gateway button, it will open a new web browser window indicating the status
of the integration gateway:

Figure 8. PeopleSoft Integration Gateway status in HCM

Load Gateway Connectors
The Connectors grid on the Gateways page lists the target connectors registered with the current
gateway. 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 by manually entering
information in the grid.
12

Figure 9. Example of Gateway Connectors in HCM

Click the Load Gateway Connectors button to have PeopleSoft Integration Broker examine the
properties of all installed target connectors and 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 the 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.
Because communication is between PeopleSoft applications, it is important that the Connector ID for
PSFTTARGET is listed as a connector.
Update Gateway Setup Properties
The Gateway Setup properties enable 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.
13

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 and
the 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

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

The Domain Status page enables you to view the domains that have pub/sub servers on them that are
running against the application database. You also use this page to set domain grace periods manually,
allowing processing in a domain to finish before you pause the processing or take the domain offline.
To make a domain active, set the Domain Status to Active for the machine name listed in the Domains
grid, and then click the Update button. This action will activate the domain and, by clicking Refresh,
you will see the Dispatcher Status update the Status String to ACT for Active.
Activate Queues
For the full sync integration points in ELM Full Sync Integration Guided Process, you must activate
the following integration broker Queues:
ENTERPRISE_SETUP
TBLSET_CONTROL
PERSON_SETUP
HR_SETUP
PERSON_DATA
To activate the Queues, navigate to PeopleTools, Integration Broker, Integration Setup, Queues. Enter
the Queue name you want to activate and the following page will appear:

Figure 14. Queue Definitions page in HCM
16

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

Chapter 3 - Basic Integration Broker Setup in ELM
This chapter provides an overview of the required Integration Broker setup in ELM in order to use the
ELM Full Sync Integration Guided Process and discusses these topics:
Configure Single Sign On
Configure Gateway
Activate Domain
Activate Queues
More detailed information about Integration Broker can be found in PeopleSoft PeopleTools 8.53
documentation.
In the ELM environment, you need to create a default local node for the ELM database.
Navigate to PeopleTools, Integration Broker, Integration Setup, Nodes to access this setup.

18

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
Note. If your ELM node is used as a single signon node and it is referenced by any ELM components
that are displayed as part of a portal, you must define values for the Content URI Text and Portal URI
Text fields on the Portal page.
For more information on defining portal nodes, see Defining Portal Nodes.
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.
19


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

20

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 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.
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:
21

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.
For HTTPS, the URL should start with https. The integration gateway URL is case sensitive.

22

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 current
gateway. 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.

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.
23

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 for
PSFTTARGET 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.

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:
24

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 and
the 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.
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.
25

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
The Domain Status page enables you to view the domains that have pub/sub servers on them that are
running against the application database. You also can use this page to set domain grace periods
manually that allow processing in a domain to finish before you pause the processing or take the
domain offline.
To make a domain active, set the Domain Status to Active for the machine name listed in the Domains
grid, and then click the Update button. This action will activate the domain and, by clicking Refresh,
you will see the Dispatcher Status update the Status String to ACT for Active.
Activate Queues
For the full sync integration points in ELM Full Sync Integration Guided Process, the following
integration broker Queues need to be activated:
ENTERPRISE_SETUP
TBLSET_CONTROL
PERSON_SETUP
HR_SETUP
PERSON_DATA
To activate the Queues, navigate to PeopleTools, Integration Broker, Integration Setup, Queues. Enter
the Queue name you want to activate and the following page will appear:
26

Figure 28. Queue Definitions page in ELM
Update the Queue Status to Run and then click Save. Repeat these steps for each queue that needs to
be activated.
27

Chapter 4 - Activate Full Sync Integration
With the integration broker nodes, gateways, and domains active, you are now ready to activate the full
sync integration points between HCM and ELM.
To activate full 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).
You can activate the following integration broker setup:
Local and remote Service Operations
Local and remote handlers
Local and remote routings
Deployment Configuration will be used to set up any transformation parameters required between
HCM and ELM.
The Introspection and Deployment task will take you through the following:
Select the integration you want to activate and deploy.
Select the Target node you want to deploy against. The target node is ELM.
Perform Introspection to generate the Introspection Results.
Introspection Results detail the integration broker setup that needs to be deployed.
Select the Introspection Results you want to deploy.
Deploy integration.
For the ELM Full Sync Integration Guided Process, the following full sync integration needs to be
deployed:
COUNTRY_FULLSYNC
CURRENCY_FULLSYNC
STATE_FULLSYNC
SETID_INITIALIZE
DEPT_FULLSYNC
COMPANY_FULLSYNC
JOBCODE_FULLSYNC
POSITION_FULLSYNC
28

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

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
JOBCODE_FULLSYNC
POSITION_FULLSYNC
WORKFORCE_FULLSYNC

30

Click Continue and the Target page will appear:

Figure 33. Target page

The Target page lets you 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:
31

Figure 34. 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.
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 need to be created and activated.
Here are the Introspection Results generated by Introspection against the 12 integrations selected:
32

Figure 35. Introspection Results page

At the bottom of this page, you can select all Deployment actions and click the Deploy button to
activate the integration:
Figure 36. Introspection Controls at the bottom of the Introspection Results page

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:
33

Figure 37. Example of the Introspection Results after clicking the Deploy button

34

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).

Figure 38. Search for Items Introspection/Deployment page

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

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

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,

Figure 42. Introspection/Deployment page

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 being
processed:

Figure 43. Example of the Introspection Results page

37

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


Figure 45. Introspection Results page after clicking Deploy
38

Chapter 6 - Setup Security
For a user to access the ELM Full Sync Integration Guided Process and initiate full sync integration
between HCM and ELM, that user will need to be granted security access to certain components and
integrations in HCM and ELM.
Note. The security setup discussed in this chapter is an example for a user who has limited access for
processing the integration between HCM and ELM using the ELM Full Sync Integration Guided
Process.
In HCM, the user will need to be assigned a new role, LMLELM_Integration_Admin, which is
associated to the following permission lists:
HCSPSERVICE - Standard Service security
This permission list grants access to process all integration delivered in the PeopleSoft HCM
application.
LMLELM800 - LM Integration Administrator
This permission list grants access to ELM Full Sync Integration Guided process, including the pages
that allow the user to select the guided process and initiate the full sync integration.
PTPT4000 - PeopleSoft Integration Network
This permission list grants access to Integration Broker Network services that are used in the ELM
Full Sync Integration Guided Process.
In HCM, navigate to PeopleTools, Security, User Profiles and assign security access by assigning the
LMLELM_Integration_Admin Role:

Figure 46. Roles tab in User Profiles

In ELM, the user will need to be assigned to the following delivered Roles that grant access to process
integration and the ability to initiate the Process Full Sync Data process:
Integration Administrator
Associated to the PTPT4000 permission list for PeopleSoft Integration Network. This permission
39

list grants access to Integration Broker Network services that are used in the ELM Full Sync
Integration Guided Process.
LMLELM_Technical Administrator
Associated to two permission lists, HCSPSERVICE and LMLELM5400.
HCSPSERVICE - Standard Service security
This permission list grants access to process all integration delivered in the PeopleSoft HCM
application.
LMLELM540 - ELM Utilities
This permission lists grants access to standard utilities in ELM.
LMLELM_ELM_User
Associated to multiple permission lists that grant access to standard components, component
interfaces, and other objects required for an ELM user.
PeopleSoft User
Associated to multiple permission lists that grant access to specific PeopleSoft components for a
standard user.
In ELM, Navigate to PeopleTools, Security, User Profiles and assign security access by assigning these
Roles:

Figure 47. Roles tab in User Profiles

40

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 a
Remote 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

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

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

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 not
affect 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

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

After clicking the Expand Link icon for Process Foundation Data, the user sees this:

Figure 54. Results of expanding the Process Foundation Data option

Each section is comprised of the same steps. The user will have a step that provides an overview, a
step to initiate an Integration Request to process the full sync integration, and a step to monitor the
status of the full sync integration process.
Target Content Area

Figure 55. Target Content area page

The Target Content area is the primary area where users review information and where they initiate
and monitor the full sync integration.
When you first come into the Learning Management Full Sync Integration Process, you will be at the
main Welcome page (shown previously), which provides an overview of the guided process.
You can navigate in multiple ways within the Guided Process Workcenter. You can interact directly
with the steps in the Pagelet area by expanding sections and clicking directly on the steps or you can
use the Next and Previous buttons that appear in the upper right-hand corner of the Guided Process
Workcenter.
Example: Initiating and Monitoring Process Foundation Data
The Process Foundation Data section includes these three steps:
Overview
Create Integration Request
46

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

Figure 58. Create Integration Process Request page for Foundation Data

The status of the Create Integration Request step changes immediately to In Progress.
You can submit an Integration Process Request for the Integration Group Name LM FS Foundation
Data. Before the Integration Request can be generated, you must validate that all the integration
services are valid (that is, Service Operations must be active and configured).
If any of the service operations are not valid, you will have to contact a system administrator to review
the integration configuration.
When all the service operations are valid, the Execute Integration Process button will be enabled so
that the full sync integration can be initiated:

Figure 59. Create Integration Process Request page after clicking Validate Integration Services

When Execute Integration Process is clicked, you will receive the following confirmation displaying the
Integration Request ID, and the status of the Create Integration Request will be updated to Complete:
48

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:
New
The service operation has not been processed.
Processing
The service operation is processing.
49

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 Data
will 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

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

Chapter 9 - Activate Incremental Sync Integration
When all the full sync integrations have successfully processed between HCM and ELM, you are ready
to activate the incremental sync integration points between HCM and ELM.
Note. This chapter covers the activation of incremental sync integration for the full sync integrations
included in the ELM Full Sync Integration Guided Process. The same steps can be followed for
activating other incremental sync integrations between HCM and ELM.
To activate incremental 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).
The following incremental sync integrations must be deployed based on the full sync integration
executed between HCM and ELM:
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
52

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

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

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,

Figure 68. Introspection/Deployment page in HCM
55

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

56

Figure 71. Introspection Results page after clicking the Deploy button

57

Validation and Feedback
This section documents the real-world validation that this red paper has received.
Customer Validation
Oracle is working with PeopleSoft customers to get feedback and validation on this document.
Lessons that are learned from these customer experiences will be posted here.
Field Validation
Oracle Consulting Services has provided feedback and validation on this document. Additional lessons
that are learned from field experience will be posted here.
Authors
PeopleSoft HCM Development
Revision History
TABLE 2. REVISION HISTORY
DATE CHANGE
TBD Created document.
10/18/2013 Edited document

58

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.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
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 J ava are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open
Company, Ltd. 0410

ELM Full Sync Integration Guided Process

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ELM Full Sync Integration Guided Process

Загружено:

Авторское право:

Доступные форматы

An Oracle Red Paper

Вам также может понравиться