Integration Broker-II

By Sravan Jammi
Contents

• Prerequisites for IB
• Setting up Asynchronous, Synchronous services. <Insert Picture Here>

• Check points
• Developing Transform programs
• Intro on tools JDeveloper, Liquid XML studio
• Overview on Async to Sync Service operation
• Data translation through codesets
• Creating codesets, codeset groups and codeset
values.
Prerequisites for IB

• Source/ Target Nodes should be configured

• Integration gateway must be configured <Insert Picture Here>

• In case of synchronous services the third party

system must be capable of responding back
• Target XML which is required for third party (
Incase of non-peoplesoft systems)
• Types of services legacy can handle
Setting up Messages

<Insert Picture Here>

Setting up Services

<Insert Picture Here>

Asynchronous Service Operation

<Insert Picture Here>

Synchronous Service Operation

<Insert Picture Here>

Defining Handlers

<Insert Picture Here>

Defining Routings

<Insert Picture Here>

 Check Points

 Ping source, Target nodes.

 Assign appropriate permission list in the service operation.
 Check the appropriate code sets assigned at the source/target
node levels.
 Check for message content before publishing the message.
 Developing Transform Programs
 Whenever there is a need to communicate with legacy(Non-
PeopleSoft system) we need to design a transformation program
to convert PeopleSoft specific XML in to legacy format.
 Define a transform program.
 Work with transform programs.
 OOTB Transformation tester
 Define a transform program

 In PeopleSoft Application Designer, select File, New, App

Engine Program to create a new program.
 Open the program properties and select the Advanced tab.
 Select a program type of Transform Only, click OK and save the
program.
 Insert sections, steps and actions as needed.
Transform Only
Working with transform programs

• JDeveloper
• Liquid XML studio
• XML spy
 Understanding Data Translation Through
Codesets
• It’s most appropriate when the sending and receiving systems
use different field values, or different combinations of fields and
their values, to represent the same information.
• One Integration Broker node can store in its Codesets repository
the equivalent fields and values used by another node.
 Configuring Codesets
 Define Codesets groups.
 Define Codesets.
 Define Codesets values.
 Import and export Codesets between databases.
 Delete Codesets.
 Use XSLT for data translation.
 Work with an XSLT translation example.
 Work with a PeopleCode translation example.
XSLT Translation Example

<psft_function name="codeset" codesetname="CAB_CRM_CST">

<parm name="STATUS_CODE">
<xsl:value-of
select="/CAB_ORDER_MSG/MsgData/Transaction/CAB_HDR_WRK/
RO_HEADER/STATUS_CODE"/>
</parm>
<value name="ORDERSTATUS" select="."/>
</psft_function>
 Peoplecode Translation Example

&xmlInput = %TransformData.XmlDoc;

&nodeRoot = &xmlInput.DocumentElement;

&arrOrder = &nodeRoot.FindNodes("MsgData/Transaction");

If &arrOrder.Len > 0 Then

For &i = 1 To &arrOrder.Len
&nodeOrderLine = &arrOrder [&i];
&arrDetailbase = &nodeOrderLine.FindNodes("CAB_HDR_WRK/RO_HEADER/RO_LINE");
If &arrDetailbase.Len > 0 Then
For &i = 1 To &arrDetailbase.Len
&nodeDetailbase = &arrDetailbase [&i];
&nodeStatus = &nodeDetailbase.FindNode("STATUS_CODE");
If All(&nodeStatus.NodeValue) Then
&strStatus = &nodeStatus.NodeValue;
&arrInputPairsAry = CreateArray(CreateArray("ORDERDETAILSTATUS", Substitute(&strStatus, " ", "_")));
&arrOutAry = CreateArrayRept(CreateArrayRept("", 0), 0);
&arrOutAry = FindCodeSetValues("CAB_LEGACY_CST", &arrInputPairsAry, "CAB_AS400", %LocalNode);
&nodeStatus.NodeValue = &arrOutAry [1][2];
End-If;
End-For;
End-If;
End-For;
End-If;
Assign Codeset to a Node
ORACLE IS A INFORMATION COMPANY