Understanding Creating and Implementing Integrations

This chapter provides a high-level overview of the steps to set up and create integrations and discusses:

Determining the messaging architecture.
Installing web servers.
Installing PeopleTools.
Installing application databases.
Installing and starting the PeopleSoft Pure Internet Architecture and integration gateways
Installing application servers.
Starting the PeopleSoft Pure Internet Architecture.
Configuring and starting messaging servers for asynchronous messaging.
Activating pub/sub server domains.
Defining integration gateways and loading connectors.
Configuring integration gateway properties.
Configuring PeopleSoft Integration Broker to handle services.
Creating integration metadata.
Granting security access to service operations

Determining the Messaging Architecture

A key step in creating and implementing integrations is to determine what systems to integrate and the architecture to use.

For example, your purpose might be to integrate with other PeopleSoft 8.4x systems where a firewall is involved, integration with third-party systems, or integrations with PeopleSoft 8.1x systems.

This PeopleBook features an appendix that provides overview information about messaging architecture scenarios. It discusses the architecture for integrating with:

PeopleSoft Integration Broker systems.
PeopleSoft Integration Broker systems through firewalls.
PeopleSoft Integration Broker systems by using hubs.
Third-party systems.
Third-party systems by using remote gateways.
PeopleSoft 8.1x systems.

See Also

Integration Scenarios

Installing Web Servers

To install and run PeopleTools, you must install a web server. PeopleTools currently supports BEA WebLogic 8.1, IBM WebSphere 5.1 and Oracle Application Server 10g.

See Also

Your web server documentation

Installing PeopleTools

PeopleSoft Integration Broker is installed as part of the PeopleTools installation process. The PeopleTools installation process also installs the executable file you need to install the PeopleSoft Pure Internet Architecture and the integration gateway.

See Also

PeopleTools 8.49 Install Guide for your database.

Installing Application Databases

After you install PeopleTools, install your application database.

See Also

PeopleTools 8.49 Install Guide for your database.

Starting the PeopleSoft Pure Internet Architecture

The next step is to install and start the PeopleSoft Pure Internet Architecture. The integration gateway is installed as part of the PeopleSoft Pure Internet Architecture installation.

Run the PeopleSoft Pure Internet Architecture setup program and start the application.

The location of the PeopleSoft Pure Internet Architecture setup file is <PS_HOME>\setup\PsMpPIAInstall\setup.exe.
Verify that the web server is running; it must be running to start the PeopleSoft Pure Internet Architecture.
Start the PeopleSoft Pure Internet Architecture by launching the startPIA.cmd file.

The location of the file is <PS_HOME>webserv\peoplesoft\startPIA.cmd.

Note. To stop the PeopleSoft Pure Internet Architecture, launch the stopPIA.cmd file. The location of the file is <PS_HOME>webserv\peoplesoft\stopPIA.cmd.
Verify that the PeopleSoft Pure Internet Architecture is installed correctly by launching it in a web browser.

See Also

PeopleTools 8.49 Install Guide for your database.

Configuring and Starting Messaging Servers for Asynchronous Messaging

Before using PeopleSoft Integration Broker for asynchronous integrations, you must configure and start the messaging server using PSADMIN.

Activating Pub/Sub Server Domains

You must activate the domain on which the pub/sub server resides before you can use the messaging server.

To activate pub/sub server domains, access the Quick Configuration page. In the Integration Broker Domains section of the page, locate your machine name and select Active from the dropdown list and click the Save button.

Defining Integration Gateways and Loading Connectors

PeopleSoft Integration Broker is delivered with one local gateway, LOCAL, defined. You can use this gateway as the default local gateway, or create a new gateway and designate that one as the default local gateway.

After you access the delivered local gateway or create your own, you must specify its URL and save the changes. The gateway URL is typically the following:

http://<local_host>/PSIGW/PeopleSoftListeningConnector

The integration gateway URL is case sensitive.

Next you must click the Load Gateway Connectors button to load the connectors delivered with PeopleSoft Integration Broker.

Managing Integration Gateways

Configuring Integration Gateway Properties

After you define the default local integration gateway, specify the integration gateway URL and load the delivered connectors, you must configure the integration gateway properties file.

To establish settings for the integration gateway and its delivered connectors, you use the integrationGateway.properties file. To access the properties file, in the Gateways component click the Properties link next to the integration gateway URL field.

At a minimum you must set the BEA Jolt connection string parameters in the DELIVERED CONNECTOR CONFIGURATION Section of the file. In most situations, you set the parameters under “JOLT connect string settings for Application Server(s) with known NODENAMEs.”

See Also

Defining Integration Gateways

Configuring PeopleSoft Integration Broker to Handle Services

To create services, service operations and generate WSDL documents, you must configure the system to handle services.

PeopleSoft Integration Broker features a Services Configuration page where you must specify the following items before you can create and work with services: services namespace, schema namespace and target location.

Creating Integration Metadata

This section provides a high-level overview of the integration metadata that you need to create to use PeopleSoft Integration Broker and a suggested order for creating it.

Understanding Integration Metadata

You use the following integration metadata to create and implement integrations.

Integration PeopleCode	You use integration PeopleCode to send and receive messages, route messages and manipulate message content.
Integration gateway definitions	This definition is an application’s internal representation of an installed integration gateway. An application requires at least the local gateway, through which it can send and receive messages. Multiple nodes can share the same local gateway, which might be the only gateway that you need for all of the integrations.
Message definitions	Message definitions provide the physical description of the data that is being sent, including fields, field types, and field lengths.
Node definitions	Nodes represent any organization, application or system that will play a part in integrations. 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. Because an application can send messages to itself, a default local node definition that represents the application is delivered as part of the integration engine. Each PeopleSoft installation must have one, and only one, default local node
Queue definitions	A queue isolates different groups of service operations from each other.
Routing definitions	Routing definitions determine the sender and receiver of an integration. Routing definitions allow you to specify inbound and outbound transformations that enable you to transform data structures into those that the sending or receiving systems can understand.
Service definitions	Service definitions group service operations into logical groups or categories.
Service operation definitions	Service operations define the processing logic of an integration. They specify the inbound, outbound and fault messages associated with an integration, the integration PeopleCode to invoke, and the routing to use.
Transformation programs	A transformation or transform program is a type of Application Engine program that you develop and specify as part of a routing definition. PeopleSoft Integration Broker supports the use of Extensible Stylesheet Language Transformation (XSLT) code and PeopleCode for developing transform programs. Transform programs can transform, filter and translate data.

Order of Precedence for Creating Integration Metadata

Create integration metadata in the following order:

Integration gateway definition.
Node definition.
Message definition.
Integration PeopleCode.
Transformation programs.
Queue definition.
Service definition.
Service operation definition.
Routing definition.

Granting Security Access Service Operations

When you create service operations, you must grant permission list access to them .

Moreover, granting security access to service operations is required to access and modify integration information in the Service Operations Monitor.

To grant security access to service operations, after you create and save a service operation a Service Operation Security link displays on the Service Operations-General page. Click the link to access the Web Service Access page and assign a permission list to the service operation.