Common Elements for the ELM Full Sync Integration Guided Process
The following table defines some of the common terms associated with the ELM Full Sync Integration Guided Process.
Field or Control |
Description |
---|---|
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 |
This is an application server pub/sub service that must be active in order to facilitate Integration Broker messaging. |
Message Node |
A message node represents any organization, application, or system that will be part of an integration. For example, a node can represent a customer, a business unit, a supplier, another trading partner, or an external or third-party software system. 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. For example, suppose that the following definitions exist in the Node A database:
Then the following definitions must exist in the Node B database for it to integrate with Node A:
The only local node definition used by PeopleSoft Integration Broker is the one designated as the Default Local, which represents the database that the user is signed on to. |
Service Operation |
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 Point |
This is another name for a service operation. |
Handler |
This is associated with a service operation. A handler contains specific programming logic for sending or receiving a message or for manipulating message content. |
Routing |
This is associated with a service operation. A routing contains specific information that determines the direction of the integration, inbound or outbound. A routing may have additional parameters to transform a message when it is sent or received. |
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 PeopleTools feature that consolidates many of the integration setup tasks into one centralized workcenter. |
Guided Process |
This is a feature in PeopleSoft 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 is guided through the steps to complete the business process. |
Activity Guide |
This is a PeopleTools 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 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 processes. You define these rules with Enterprise Components. |
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. |