|
Oracle® Application Server Adapter for PeopleSoft User's Guide
10g Release 2 (10.1.2) Part No. B14060-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Adapter for PeopleSoft User's Guide
10g Release 2 (10.1.2) Part No. B14060-01 |
|
|
Previous |
Next |
Oracle Application Server connects to a PeopleSoft system through the Oracle Application Server Adapter for PeopleSoft (OracleAS Adapter for PeopleSoft). The OracleAS Adapter for PeopleSoft provides connectivity and executes interactions on a PeopleSoft system. This chapter discusses the following topics:
The OracleAS Adapter for PeopleSoft provides a means to exchange real-time business data between PeopleSoft systems and other applications, databases, and external business partner systems. The adapter enables inbound and outbound processing with PeopleSoft. The OracleAS Adapter for PeopleSoft can be deployed as a JCA 1.0 resource adapter. This deployment is referred to as the OracleAS Adapter JCA. It can also be deployed as a Web services servlet and as such is referred to as the Oracle Application Server Adapter Business Services Engine (BSE).
The adapter uses XML messages to enable non-PeopleSoft applications to communicate and exchange transactions with PeopleSoft using services and events.
Services: Applications use this capability to initiate a PeopleSoft business event.
Events: Applications use this capability to access PeopleSoft data only when a PeopleSoft business event occurs.
To support event functionality, two features are implemented:
Port
A port associates a particular business object exposed by an adapter with a particular disposition. A disposition defines the protocol and location of the event data. The port defines the end point of the event consumption.
The port is the Oracle adapter component that pushes the event received from the EIS to the adapter client. The only port supported in this release is Remote Method Invocation (RMI). It is used for integration with Oracle Application Server Integration InterConnect (OracleAS Integration InterConnect).
Channel
A channel represents configured connections to particular instances of back-end or other types of systems. A channel binds one or more event ports to a particular listener managed by an adapter.
The channel is the adapter component that receives events in real time from the enterprise information system (EIS) application. The channel component can be a File reader, an HTTP listener, a TCP/IP listener, or an FTP listener. A channel is always EIS specific. The adapter supports multiple channels for a particular EIS. This enables the user to choose the optimal channel component based on deployment requirements.
The OracleAS Adapter for PeopleSoft provides:
Synchronous and asynchronous, bidirectional message interactions for PeopleSoft component interfaces and PeopleSoft Application Messaging Manager.
Oracle Application Server Adapter Application Explorer (Application Explorer), a GUI tool that explores PeopleSoft metadata and builds XML schemas or Web services.
XML schemas for the JCA 1.0 resource adapter.
Web services for the OracleAS Adapter BSE.
The adapter connects to the PeopleSoft Application Server by accessing APIs for the component interfaces that correspond to its supported business objects. Every component interface contains data and business logic for the business component, thus alleviating a requirement for the adapter to duplicate the processes defined within the business component.
Oracle Application Server Adapter Business Services Engine Architecture
Figure 1-1 shows the generic architecture for the Oracle Web service adapter for packaged applications. The adapter works in conjunction with the Oracle Application Server Adapter Business Services Engine (BSE), as deployed to a Web container in a J2EE application server.
Oracle Application Server Adapter Application Explorer (Application Explorer), a design-time tool deployed along with BSE, is used to configure adapter connections, browse EIS objects, configure services, and configure listeners to listen for EIS events. Metadata created while you perform these operations are stored in the repository by BSE.
BSE uses SOAP as a protocol for consuming requests from clients, interacting with the EIS, and sending responses from the EIS back to clients.
Figure 1-1 Oracle Application Server Adapter Business Services Engine Architecture
Oracle Application Server Adapter Generic JCA Architecture
Figure 1-2 shows the generic architecture for the OracleAS Adapter JCA for packaged applications. The OracleAS Adapter JCA is deployed to a standard JCA Container and serves as host container to the adapters. The connector is configured with a repository. Application Explorer, a design-tool that works in conjunction with the connector, is used to configure adapter connections, browse EIS objects, configure services, and configure listeners to listen for EIS events. Metadata created while you perform these operations are stored in the repository by the connector.
Figure 1-2 Oracle Application Server Adapter Generic JCA Architecture
PeopleSoft provides for integration with other applications and systems through its component interface framework and its Integration Broker (in release 8.4) or Application Messaging (in release 8.1) facility. The OracleAS Adapter for PeopleSoft uses the PeopleSoft framework and leverages various integration access methods to provide the greatest amount of flexibility and functionality. Integration access methods supported by the OracleAS Adapter for PeopleSoft include:
In the PeopleSoft environment, a component interface is a container for distributing PeopleSoft application data among PeopleSoft logical systems and for exchanging PeopleSoft application data with non-PeopleSoft systems.
The component interface is based on an existing business process within PeopleSoft. An example is a purchase order entry, which can be a PeopleSoft-delivered process or a user-developed process. The component interface also inherits its methods (Add, Update, and so on) and its business logic from the underlying business process.
PeopleSoft delivers generic component interfaces with each of its applications. These are called Enterprise Integration Points (EIP). Customers also can develop their own custom component interfaces, or they can modify EIP as required.
The OracleAS Adapter for PeopleSoft enables you to:
Access a PeopleSoft component using a component interface. Component methods are also referred to as services.
Receive messages from a PeopleSoft application. Messages are also referred to as events.
When you access a PeopleSoft component from another application, you work with:
Component interfaces. If a component interface does not exist, create, secure, and test one. If the component interface exists, but you modified it, secure and test it. For more information, see your PeopleSoft documentation. Alternatively, you can secure and test the component interface and create the component interface API after you generate schemas or Web services.
Component interface APIs. Create an API for the component interface.
Schemas and Web services. Create schemas or Web services for the component methods.
See Chapter 2, "Adapter Configuration Using OracleAS Adapter Application Explorer" for more information.
To receive a message from PeopleSoft, you work with:
The Integration environment. Configure and test your PeopleSoft Integration Broker (release 8.4) or Application Messaging environment (release 8.1). To ensure that the environment is properly configured, see your PeopleSoft documentation.
Message routing. Configure TCP/IP Target Connector (release 8.4), HTTP Target Connector (release 8.4), or TCP/IP Handler (release 8.1). See Chapter 1, "Introduction to Oracle Application Server Adapter for PeopleSoft" for more information.
|
See Also:
|
