This chapter provides overviews of installation and configuration steps and the integration architecture and discusses how to:
Set up the integration environment in the PeopleSoft Enterprise system.
Set up the integration environment in the JD Edwards EnterpriseOne system.
This document does not describe in detail how to install and configure the integration. You should have installed the objects associated with the integration prior to using this document. However, this section provides an overview of the general steps involved for installing an integration and gives recommendations for improving the system performance. To review information about installation and configuration, review the installation and configuration steps.
Use this table to guide you through the installation and configuration process for JD Edwards EnterpriseOne application integrations with PeopleSoft Enterprise applications. To ensure proper integration, you must perform the steps in the order listed.
Note. References to the PeopleSoft Enterprise system in this table can refer to either PeopleSoft Enterprise 8.8 or 8.9. References to the JD Edwards EnterpriseOne system refer to JD Edwards EnterpriseOne 8.12. Refer to the Minimum Technical Requirements (MTRs) for your integration to determine the correct versions.
Step |
Instruction |
Notes |
1 |
Verify that you meet the minimum technical requirements to implement the JD Edwards EnterpriseOne application integrations with PeopleSoft Enterprise applications. |
See Minimum Technical Requirements (MTR) for each integration on the Customer Connect Integration Site. On Customer Connection, click Implement, Optimize, and Upgrade; Implementation Guide; Implementation Documentation and Software, Pre-Built Integrations for PeopleSoft Enterprise and JD Edwards EnterpriseOne Applications. Navigate from there to the page for your specific integration and then click the Minimum Technical Requirements document link. |
2 |
Install and configure the JD Edwards EnterpriseOne system. Apply the updates, service packs, or Electronic Software Updates (ESUs) specified in the MTR. |
|
3 |
Install and configure the PeopleSoft Enterprise system. Apply any maintenance pack and any ICEs specified in the MTR. |
|
4 |
Install and configure JD Edwards EnterpriseOne WSG Foundation 8.96 |
|
5 |
Install and configure the JD Edwards EnterpriseOne Adapter. |
|
6 |
Install and configure JDBC adapters. |
This step is required for ELM, HCM, SRM, and CRM integrations and for cross-referencing data. |
7 |
Install and configure PeopleSoft Enterprise Integration Broker nodes and channels. |
|
8 |
Install JD Edwards EnterpriseOne interface flows and Published Interface Documents (PIDs). Apply any downloads specified in the MTR. |
This step is required only for integrated solutions that support realtime updates. |
9 |
Install and import services to the Integration Server. |
See Minimum Technical Requirements |
10 |
Set up prerequisite data, activate realtime events, configure integration options, and run initial data loads. |
Individual users must be subscribed to appropriate realtime events. |
This diagram illustrates the high level architecture for integration between the PeopleSoft Enterprise system and the JD Edwards EnterpriseOne system:
Integration Architecture diagram
The PeopleSoft Enterprise system uses integration points and Integration Broker (IB). The JD Edwards EnterpriseOne system uses WSG Integration Server (IS), which includes z-file interfaces, interface flows, and other JD Edwards EnterpriseOne integration points.
Special services have been developed using WSG Integration Server technology that map, transform, and cross-reference data as it flows between the PeopleSoft Enterprise system and the JD Edwards EnterpriseOne system. These services are written using the WSG Developer Tool.
For a detailed insight into these technologies, refer to the relevant technical implementation guides.
This section lists a prerequisite and discusses how to:
Set up the local gateway.
Activate message channels.
Activate messages.
Activate message nodes.
Set up node definitions.
Set up integration transactions.
Add channels to permissions.
Activate message subscriptions.
Note. The tasks listed here refer to PeopleTools 8.45 and represent minimum guidelines for setting PeopleSoft Enterprise integrations. Please refer to the implementation guides for the PeopleSoft Enterprise products that you are integrating for complete information about setting up these products for integrations. Refer also to the setup chapter for your integration in this implementation guide for additional setup steps for your integration.
See Also
PeopleSoft Enterprise PeopleTools 8.46 Implementation Guide: Integration Broker, "Managing Integration Gateways," Administering Integration Gateways
PeopleSoft Enterprise Components for PeopleSoft Enterprise Financial Management Solutions, PeopleSoft Enterprise Service Automation, Asset Lifecycle Management, and Supply Chain Management 8.9 Implementation Guide, Enterprise Integration, “Activating Messaging Integration Points”
Configure the application server for your database to be with Pub/Sub Servers active.
Access these pages in the appropriate PeopleSoft Enterprise database for the integration you are using.
Page Name |
Object Name |
Navigation |
Usage |
IB_GATEWAY |
PeopleTools, Integration Broker, Configuration, Gateways |
Verify the setup of the local gateway. |
|
IB_NODE |
PeopleTools, Integration Broker, Integration Setup, Node Definitions |
Set up internal representation of the system with which to exchange messages. |
|
IB_NODECON |
PeopleTools, Integration Broker, Integration Setup, Node Definitions, Connectors |
Verify connector properties and provide a URL that points to the JD Edwards EnterpriseOne Integration Server. |
|
IB_NODETRXLIST |
PeopleTools, Integration Broker, Integration Setup, Node Definitions, Transactions |
Verify activation of the transactions used in this integration. |
|
ACL_MESSAGEMONITOR |
PeopleTools, Security, Permissions & Roles, Permission Lists |
Set up channel permissions to send and receive messages in the PeopleSoft Enterprise system. |
|
AMM_CHNL_STATUS |
PeopleTools, Integration Broker, Monitor Integrations, Monitor Message, Channel Status |
Verify the status of message channels. |
To set up the local gateway:
Search for the gateway ID for which you have selected the Local Gateway check box.
Specify the gateway URL as http://<web server name>:<port>/PSIGW/PeopleSoftListeningConnector
For example:
http://wsg27:81/PSIGW/PeopleSoftListeningConnector
Click Save to save the URL first.
Click Load Gateway Connectors to load the connectors, and then click Save.
Access the Channel Status page.
Select the Run button for each channel that you need to activate.
Note. The setup chapter for each integration in this implementation guide contains a list of required message channels for that integration.
Access Application Designer for the appropriate PeopleSoft Enterprise database.
For each message listed:
Select File, Open, Message to open the message.
Access the properties for the message object.
Ensure that you have selected the Active option in the Status box on the Use tab, and then click OK.
Save the message.
Note. The setup chapter for each integration in this implementation guide contains a list of required messages for that integration.
The system delivers message nodes as inactive. Ensure that you have activated the PSFT_E1 node or the node that you have set up to represent the JD Edwards EnterpriseOne system. If you have multiple JD Edwards EnterpriseOne systems, you need to complete these steps for each JD Edwards EnterpriseOne node that you use.
Access the Node Definitions page.
To activate message nodes:
Enter the appropriate node name, and click Search.
Ensure that you have selected the Active Node check box.
Save the node.
Note. Some integrations require additional nodes. For those integrations, the additional nodes are listed in the setup chapter for that integration in this implementation guide.
Select HTTPTARGET as the connector ID.
Identify the properties and provide a designated URL for the PSFT_E1 node or the node that you have set up to represent the JD Edwards EnterpriseOne system. If you have multiple JD Edwards EnterpriseOne systems, you need to complete these steps for each JD Edwards EnterpriseOne node that you use.
For the PRIMARYURL property, enter the URL of the Integration Server in the PRIMARYURL Value field.
The URL points to JD Edwards EnterpriseOne Integration Server and should have the format:
http://<WSG IS MachineName>:<IS port>/invoke/PSFT_Dispatcher.Inbound: InboundServiceDispatcher
Note. You must register each node in the properties file for the gateway. Search for the string ## JOLT connect string settings for Application Server(s) with known NODENAMEs and follow the instructions there.
See PeopleSoft Enterprise PeopleTools 8.46 Implementation Guide: Integration Broker, “Managing Integration Gateways,” Using the integrationGateway.properties File.
See PeopleSoft Enterprise PeopleTools 8.46 Implementation Guide: Integration Broker, “Appendix: Using the Integration Broker Connector SDK,” Developing Connectors, Developing Listening Connector Classes
You must activate nodes and their associated transactions for the integrations you are using.
Access the Transactions page.
To activate node transactions:
Click the Edit link.
Set the Status value to Active on the Transaction Detail tab, and click Save.
Click the Return to Transaction List link.
Note. The setup chapter for each integration in this implementation guide contains a list of required transactions for that integration.
To send and receive messages in the PeopleSoft Enterprise system, you must set the channel permissions.
Access the Permission Lists page.
To add channels to a permission list:
Select the permission list for a user ID that has access to the Message Monitor.
Select the Message Monitor tab, and insert a row for the required channel.
Set the access for the row, and then click Save.
Note. The setup chapter for each integration in this implementation guide contains a list of required channel permissions for that integration.
To activate message subscriptions:
Access Application Designer for the appropriate PeopleSoft Enterprise database.
For each message listed, open the message.
For each message subscription listed:
Right-click the message subscription and select Message Subscription Properties.
Ensure that you have selected the Active option in the Status box, and then click OK.
Save the message.
Note. The setup chapter for each integration in this implementation guide contains a list of required message subscriptions for that integration.
This section discusses how to:
Set up Unicode flat file encoding.
Set up the export folder for table conversions.
Activate realtime events.
See Also
JD Edwards EnterpriseOne Tools 8.96 System Administration Guide, "Working with Flat File Encoding"
The batch integration flows support UTF-8 encoding. Use the UTF-8 encoding for generating flat files in JD Edwards EnterpriseOne. If the default is not set to UTF-8, make sure that the user who generates the flat files has encoding set to UTF-8. Also, make sure that the correct environment is selected.
Use the Unicode Flat File Encoding Configuration program (P93081) to specify the encoding style for JD Edwards EnterpriseOne. The Unicode Flat File Encoding Configuration program enables you to specify a default encoding that applies to all users (*PUBLIC) and all environments (*ALL). You can overwrite the encoding style at the user level for a particular environment.
Verify that a folder called Export exists in the \B9\package name\ directory in which JD Edwards EnterpriseOne was installed.
Note. If the Integration Server resides on a different machine than the Export folder, you must set up the Export folder as a shared folder so that the Integration Server can access the flat file.
You must activate the realtime events that are used by the integrations that you are using. The section of this book for each integration lists the realtime events for that integration. You activate realtime events by changing the status of the event.
See JD Edwards EnterpriseOne Tools 8.96 Interoperability Guide, “Using Events – Guaranteed,” Defining Events.