Integration Broker PeopleTools

Integration Broker Steps –Introduction & terminologies –Application Server PUB/SUB services (Application Server) –Integration Broker -Architecture –Gateway Setup (Integrationgateway.properties) (PIA) –Node Setup (PIA) –Create/Enable Message Channel (AD) –Create/Enable Message (AD) –Security (PIA) –Attach Message to Node (PIA) –Monitor Messages (PIA) –Jolt & Tuxedo –Write Peolpecode (AD) (Appendix - A) –Appendix – B (for reference)

Introduction & terminologies- Integration Broker Overview Introduction Integration Broker Elements o Integration Gateway o Integration Engine o Connectors o Gateway Manager o Transaction Integration Broker Architecture Integration Scenario Connector Usage

Introduction & terminologies- Introduction Middleware Technology that facilitates synchronous and asynchronous messaging among internal systems and trading partners Modular design – Elements developed for integration can be reused Comprises of two high level sub-systems, Integration Gateway and Integration Engine.

Introduction & terminologies- Integration Broker Elements Integration Gateway Integration Engine Connectors Gateway Manager Transaction

Introduction & terminologies- Integration Gateway Platform that manages the actual receipt and delivery of messages Provides the support for the leading TCP/IP protocols used Provides the extensible interfaces for the development of new connectors for communication with legacy, ERP and internet based systems Backward compatibility for XML links and Application Messaging Maintains basic logging information for message receipt, delivery and errors Capable of message format management.

Introduction & terminologies- Integration Engine Runs on the PeopleSoft Application Server. Produces and consumes messages for the application Receives the messages through one or more separately installed integration gateways Treats the gateways as “Black Box” and communicate with them using standard connectors Can adapt the elements of existing integration to produce new integration with minor changes Handles the messages containing the data in a variety of formats like PeopleSoft rowsets, XML documents, Simple Object Access Protocol (SOAP) and unstructured data Sends and receives the messages synchronously or asynchronously Applies message transmission type and routing based on specification defined in PIA component Transforms message structure and translate data content Handles the security features

Introduction & terminologies- Connectors Two basic type of connectors used in Integration Gateway Listening Connectors Target Connectors Supports asynchronous, synchronous and polling based message handling Connectors are configurable based on user-defined setting at integration gateway and node level

Introduction & terminologies- Gateway Manager Processes every message that flows through the integration gateway Maintains links among the other major integration gateway components Invoked by listening connectors on receiving the message request Uses handles on messaging objects, IBRequest and IBResponse to determine how to route each message Uses number of services during each stage of operations Invokes the appropriate target connector based on the contents of the message object and waits for the response from target connector. On receiving the response, it forwards the response to the calling listening connector.

Introduction & terminologies- Gateway Services Error Handling: Standard error handling interface that is exposed to each connector. Provides error handling and error logging for most connectors Messaging Objects: There are two objects service in the Integration gateway IBRequest IBResponse XML Parsing: Used to parse and traverse XML data stored in content section of message Message Validation: Used for basic validation such as making sure the message identifies requestor and message name etc. to ensure that integration engine and the target application can process them.

Introduction & terminologies- Gateway Services Connector Management: Comprises of several smaller services to Manage connectors in Integration Gateway.Processes each IBRequest To determine the appropriate connector to call in each situation. Also Processes the IBResponse returned by each connector. Error & Message Logging: Standard logging interface that most components in the system use. Enables the administrator to quickly drill-down on problems or review message logs. Sample URL for checking errors in development environment.

Introduction & terminologies- Transaction Basic unit of work in Integration Associated with a specific node Used to designate a message that the current node can send or receive Defines the message as inbound / outbound message Defines transmission type I.e. Synchronous / Asynchronous Four basic types of Transaction Outbound Asynchronous (OutAsync) Outbound Synchronous (OutSync) Inbound Asynchronous (InAsync) Inbound Synchronous (InSync)

Application Server - PUB/SUB services (Application Server) Resides on the Application Server as a Messaging Server Process Sends and receives messages for the application through the IB Gateway Consists of Publication Broker, Publication Contractor and Subscription Contractor

Integration Broker -Architecture Listening Connectors HTTP PeopleSoft 8.1 JMS Gateway Manager Target Connectors POP3 HTTPSMTPPeopleSoft Gateway Services Error Handling Message Validation Messaging Objects XML Parsing Connector Management Error & Msg. Logging PeopleSoft 8.1 FileJMS

Integration Broker –Architecture continued PeopleSoft 8.4 HR (USA) System Integration Engine For HR: Local Integration Gateway For CRM: Remote Integration Gateway PeopleSoft Listening Connector HTTP Target Connector PeopleSoft Target Connector PeopleSoft Listening Connector Gateway Manager JOLT MIME HTTP For CRM: Local Integration Gateway For HR: Remote Integration Gateway PeopleSoft Listening Connector PeopleSoft Target Connector HTTP Target Connector PeopleSoft Listening Connector Gateway Manager PeopleSoft 8.4 CRM (UK) System Integration Engine JOLT MIME HTTP MIME HTTP MIME HTTP MIME HTTP Firewall Application Server(s) + Database Application Server(s) + Database

Gateway Setup (Integrationgateway.properties) (PIA) IB

Gateway Setup (Integrationgateway.properties) (PIA) IB

Gateway Setup (Integrationgateway.properties) (PIA) IB

Gateway Setup (Integrationgateway.properties) (PIA) IB

Node Setup (PIA) IB

Node Setup (PIA) IB

Node Setup (PIA) [Attach Message to Node (PIA)] IB

Node Setup (PIA) IB

Node Setup (PIA) IB

Node Setup (PIA) IB

Node Setup (PIA)[Attach Message to Node (PIA)] IB

Node Setup (PIA) IB

Create/Enable Message Channel (AD) IB

Create/Enable Message Channel (AD) IB

Create/Enable Message (AD) IB

Create/Enable Message (AD) IB

Create/Enable Message (AD) IB

Create/Enable Message (AD) IB

Security (PIA) IB

Monitor Messages (PIA) IB

Monitor Messages (PIA) IB

Monitor Messages (PIA) IB

Jolt & Tuxedo

Jolt is an application-layer network protocol that runs over TCP. It is proprietary and owned by BEA and was developed as the means for allowing Java applications to communicate with Tuxedo (also a BEA product). Tuxedo is a C-based OLTP monitor that multiplexes user sessions and transactions into a RDBMS and controls transaction execution. In a PeopleSoft system, C++ logic that interprets and executes application business rules and functionality run as services within the Tuxedo domain(s), with Tuxedo managing DB transaction boundaries and queues of requests. The role of PIA web servers is to create and manage presentation only. At runtime, all business logic executes in Tuxedo.

Appendix-A for publish Pub code &MSG = CreateMessage(Message.IF_CUST_MSG); &MSG.CopyRowsetDelta(GetRowset()); &MSG.publish(); Pub code

Appendix-A for subscription sub code &msg = GetMessage(); &rec = CreateRecord(Record.IF_CUST_TBL); &rs = &msg.getrowset(); &rec.setid.value = &rs.getrow(1).IF_CUST_TBL.setid.value; &rec.cust_id.value = &rs.getrow(1).IF_CUST_TBL.cust_id.value; &rec.descr.value = &rs.getrow(1).IF_CUST_TBL.descr.value; If &rs.getrow(1).PsCAMA.audit_actn.value = "A" Then &rec.insert(); End-If; If &rs.getrow(1).PsCAMA.audit_actn.value = "C" Then &rec.update(); End-If; sub code

Appendix-B Reference document  IB/IB

QUESTIONS???