Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Building Better Bridges

Building Better Bridges

Enterprise Application Integration (EAI) is a very popular topic these days. Businesses, as well as government entities at the local, state, and federal level, are all struggling to integrate their critical yet disparate information systems.

Some of the most challenging integration efforts involve integrating enterprise resource planning (ERP) or customer relationship management (CRM) systems with new and existing custom applications. These enterprise software applications often have proprietary architectures and complex APIs, and typically use proprietary programming languages unfamiliar to the mainstream developer community. However, some enterprise software vendors are attempting to make the integration effort more approachable. Using widely accepted standards such as XML and Web services, these vendors are attempting to build better bridges between their respective products and the world around them.

PeopleSoft, Inc., is one of the dominant vendors in the enterprise software market. The PeopleSoft product family spans such critical business functions as human resource management, financial management, supply chain management, and customer relationship management. These products, along with competitive offerings from vendors such as Siebel, SAP, and Oracle, often manage the most important business logic and data in the enterprise. As such, they represent important assets to be leveraged whenever possible and appropriate.

This article is the first in a two-part series describing integration methods and illustrating the use of integration technology to enable mutual reusability between PeopleSoft and J2EE applications. This article will describe how the Java Messaging Service (JMS) and PeopleSoft's Integration Broker technology can be used to integrate PeopleSoft and J2EE applications seamlessly. The second article will describe how to accomplish the same goal using Web services technology.

PeopleSoft Architecture and Integration Technology
Starting with version 8, PeopleSoft products leveraged the PeopleSoft Internet Architecture (PIA), allowing the full functionality of these applications to be accessed from within a Web browser. By eliminating the need for client software, PIA's comprehensive Internet accessibility enables customers to realize substantially lower deployment costs than were previously possible under traditional client/server architectures. In addition to these benefits, PIA transitions the PeopleSoft product suite to a standard, J2EE-based operating platform built on BEA technology. PeopleSoft 8.4, the latest version (and the focus of this article), uses WebLogic Server 6.1 and Tuxedo for its Web and application servers, respectively.

As illustrated in Figure 1, PeopleSoft's Web tier components are deployed as J2EE Web applications under WLS 6.1, while its back-end components fall under Tuxedo control and are accessible via Tuxedo's Java-based Jolt API. These servers can be colocated or distributed, allowing additional flexibility in establishing environments that are optimized for scalability and redundancy. PeopleSoft Web applications handle a number of critical functions, from serving standard application pages and managing the distribution of batch-generated report output, to retrieving and aggregating user-requested content through the PeopleSoft Portal product. One Web application, the PeopleSoft Integration Gateway, plays a key role in integrating PeopleSoft products with each other and with third-party systems, including J2EE- and Microsoft .NET-based applications.

The Integration Gateway is a component of PeopleSoft's Integration Broker (IB) technology, introduced in PeopleSoft 8.4 (see Figure 2). The Integration Broker is an XML-based messaging hub that supports both synchronous and asynchronous messaging between PeopleSoft and external applications. IB is composed of several components and services spanning the Web and application server environments. The Integration Gateway resides on the Web server, providing inbound and outbound pathways for PeopleSoft applications. Other components, such as the internal publication and subscription agents that actually move information across the application server boundary, compose the Integration Engine, and reside on the application server under Tuxedo control. Ultimately, one should be familiar with both environments to successfully develop and administer an IB integration solution. Due to the constraints of this article, I'll focus on the Web tier and the Integration Gateway, where the bulk of the developer-relevant configuration tasks lie.

The gateway provides the interface to the broker, managing the actual receipt and transmission of messages between integrated systems. The gateway consists of several listening and target connectors that support inbound and outbound communications between external systems and the integration engine. The connectors support a range of communication protocols, including HTTP, JMS, POP3, SMTP, and FTP. Additional PeopleSoft and PeopleSoft 8.1 connectors enable gateways to communicate with other PeopleSoft 8.4 and older 8.1 systems, respectively. Some of these protocols are supported for both inbound and outbound communications, while others are supported in only one direction (see Figure 2).

The Gateway Manager processes every message that enters through the Integration Gateway, invoking gateway services such as XML parsing, message validation, and logging. The Gateway Manager uses the content of the message object to determine the intended message recipient, and then uses the appropriate target connector to transmit the message. After receiving a response from the target connector, it forwards the response to the calling listening connector. During all of this processing, the contents of incoming messages are logged to a disk file, along with any errors encountered during processing.

A number of different physical architectures are possible, depending on the nature of the desired integration effort. For example, a simple integration, behind a company's firewall, may require a single local Integration Gateway. More elaborate integrations across firewall boundaries, LANs, and WANs could very well involve multiple remote Integration Gateway instances and several different listening and target connectors. As such, real-world PeopleSoft integration can get very complex, very quickly. This article presents some of the basics but will not delve into all of the possible integration scenarios, optimizations, and consequences.

Integration Broker Definitions and Configurations
Every IB integration requires some degree of definition. The integration may involve several different systems communicating via multiple protocols and varying semantics. Hence, a number of conceptual definitions must be created and configured to appropriately model and implement the desired integration. The major IB definitions include gateways, nodes, transactions, relationships, messages, and message channels.

  • Gateway: Gateways handle incoming and outgoing messages through the broker. Each gateway has an address, which is the URL for that gateway's PeopleSoft listening connector, http://<gatewayservername>/PSIGW/PeopleSoftListeningConnector. Gateways use their PeopleSoft connectors to communicate with Integration Engines and other (remote) gateways. Additional connectors can be used to exchange messages with external systems using a wide range of protocols. Gateways can be remote or local. However, only one local gateway may be defined for any given PeopleSoft instance.

  • Node: Nodes represent connection points in IB integrations, for example, other PeopleSoft applications or external systems. Nodes can be remote or local. However, for IB, all nodes are considered remote, except for the Default Local node representing the PeopleSoft instance being configured. A node's definition can reference a target connector, indicating the protocol (ex: JMS, HTTP, SMTP) the broker must use in order to reach that node.

  • Transaction: Transactions are the most basic unit of work in an integration. They are associated with nodes, and designate which messages the node receives (inbound) and transmits outbound), and what semantics (i.e., synchronous, asynchronous) are used during the process. Every integration requires at least one transaction at each IB node either to send or to receive a message at the node.

  • Relationship: Relationships reconcile transactional differences between the source and destination nodes of a given integration. For example, a given integration may define an inbound, asynchronous (inAsync) transaction of Message X at Node A, and an outbound, synchronous (outSync) transaction of Message Y, at Node B. In addition, Message Y may be a transformed, translated, or filtered version of Message X. Since, in this example, the semantics change from inAsync to outSync and the message formats differ, a relationship must be defined in order to resolve the differences and support the integration.

  • Message: Messages represent the application data to be sent and received through the Integration Broker. Messages can be rowset-based or nonrowset-based. The former conveys hierarchical database information, based on native PeopleSoft structures called records. The latter can be used to convey practically any other message content or structure, including XML and Simple Object Access Protocol (SOAP) messages.

  • Message Channel: Message channels are logical groupings of messages. Each message must belong to one and only one message channel. Message channel definitions are essential for sequenced processing, improved throughput, and message archival.

    All of the IB definitions must be defined and configured using PeopleSoft's powerful PeopleTools Development Environment. Portions of PeopleTools are accessible via the PeopleSoft Internet screens (dubbed "PIA screens"), while other portions can only be accessed via the separate Application Designer client program. Gateway, node, transaction, and relationship definitions must be defined and configured via the PIA screens, while messages, message channels, and any custom PeopleSoft programs (written in a language called PeopleCode) must be created and maintained via the Application Designer.

    An Example: Integration via JMS
    The following example will reinforce the concepts presented above. In this example, an integration scenario between WebLogic Server 7.0 hosted components and a single local PeopleSoft 8.4 instance using JMS will be explored.

    One of the first steps in implementing an IB integration is to define the messages that will be exchanged between the participating systems. Two messages will be defined: one for messages emanating from WLS 7.0 to PeopleSoft, and another for messages traveling back. For the sake of simplicity, this example will use nonrowset messages with XML content.

    Since any given message must belong to an existing message channel, the channel must be created first. After the message channel has been created, its configuration properties can be browsed. Figure 3 is an example of a message channel configuration dialog displayed in the Application Designer.

    The JKK_TX_MESSAGE_CHANNEL channel dialog displays the list of messages associated with the channel. In this example, the JKK_TX_REQUEST_MESSAGE and JKK_TX_RESPONSE_MESSAGE definitions represent the application data messages exchanged between WLS 7.0 and PeopleSoft. Typically, structured rowset messages will be defined in the Application Designer, along with a record-based content schema. However, for this simplified example, the message definitions are simply monikers acting as proxies for the unstructured content they represent.

    In this example, synchronous messaging will be used for both inbound and outbound traffic. Once messages arrive in PeopleSoft, they will be written to a disk file before an empty response message is created and then returned to the WLS-hosted caller. After this, the original message will be routed back to WLS (over JMS) via a feedback loop.

    In order to accomplish this, you must first write a PeopleCode request handler and attach it to the JKK_TX_REQUEST_MESSAGE definition in the Application Designer. As in other development environments, such as Visual Basic, PeopleCode message objects can respond to various events. A message's OnRequest event can specify a custom PeopleCode routine to handle the synchronous arrival of the message. The PeopleCode routine can perform the appropriate actions before creating and returning a status message.

    The PeopleCode request handler for the inbound JKK_TX_REQUEST_MESSAGE is shown in Listing 1(listings for this article can be found at www.sys.con.com/weblogic/sourcec. cfm). As illustrated, the first programmatic instruction uses the special IB function, getMessageXmlDoc(), to retrieve the incoming XML message. After this, the message contents are converted into an XML string before being appended to a file named IncomingRequests.log. Finally, CreateMessage and ReturnToServer are special functions used to generate and then return an empty status message through IB back to the caller.

    The next major step is to define and configure the necessary integration nodes, transactions, and relationships using the PeopleTools PIA screens.

    Two nodes, JKK_SOURCENODE and JKK_TARGETNODE, will be created to represent the WLS instance participating in the integration. This instance will be the ultimate receiver of the messages it originally transmitted. The JKK_SOURCENODE definition is fairly straightforward. However, the JKK_TARGETNODE node definition is more involved because it must ultimately transmit messages to an external destination (the WLS instance) via JMS. Figure 4 provides a look at the target connector information attached to JKK_TARGETNODE. Although there are several properties associated with the connector, we will focus on only the most important ones: JMSUserName, JMSPassword, JMSUrl, JMSTopic, and JMSFactory.

    JMSUrl specifies the host and listening port of the target JMS server. In this case, the server is WLS 7.0-based and resides at http://wls01:7001. JMSUserName and JMSPassword are valid user ID/password combinations on the target WLS 7.0 instance. JMSFactory and JMSTopic reference the factory and topic defined within the target JMS server's config.xml file. A JMS listener or message-driven bean (MDB) listening to the same combination of JMSFactory, JMSTopic, and JMSServer will rendezvous with the IB and receive any messages transmitted by the broker via JKK_TARGETNODE.

    The next step is to define the necessary inbound and outbound transactions and associated relationships. IB transaction mappings must be made from the perspective of the PeopleSoft instance's default local node. Hence, an inSync transaction conveying JKK_TX_REQUEST_MESSAGE and returning JKK_TX_RESPONSE_MESSAGE must be defined at JKK_SOURCENODE, while an outSync transaction with identical message characteristics must be defined at JKK_TARGETNODE.

    In addition, a relationship, shown in Figure 5, will be created to tether the two nodes together so inbound message traffic is routed to the target node and ultimately back to the WLS instance via the JMS target connector. Relationships, like many PeopleSoft objects, can be activated or deactivated, and can even become applicable upon a given effective date. All of this provides considerable flexibility, as multiple relationships can be defined across a set of node and date combinations.

    In addition, relationships can be used to reconcile differences in the data formats exchanged between a combination of source and target nodes. For example, the data emanating from JKK_SOURCENODE may need to be transformed, translated, or even filtered en route to JKK_TARGETODE. A relationship can perform these data manipulations using PeopleSoft batch programs called application engine programs. These programs can use a combination of PeopleCode, Extensible Stylesheet Language Transforms (XSLT), or SQL actions to perform the required data manipulations between a given combination of nodes. Such programs would be specified in the Transformations section of Figure 5.

    The next step is to configure the Integration Gateway to use the appropriate inbound JMS topics and queues. This configuration information is stored in the integrationGateway.properties text file, which is located under the Integration Gateway subdirectory of the installation tree. The gateway can listen to any combination of JMS topics and queues, and can use different JMS providers. For this example, the WebLogic JMS provider will be used, along with a single inbound JMS topic and a special gateway error topic. The gateway will publish processing errors to this topic, in addition to writing the errors to a cumulative error log file. This design would accommodate a custom error topic subscriber that could handle gateway errors programmatically.

    Listing 2 shows the portions of an integrationGateway.properties file relevant to the integration example. The ig.isc.serverURL, ig.isc.userid, ig.isc.password, and ig.isc.toolsRel properties specify the Jolt address, along with a valid user ID/password combination for the target application server. These properties effectively connect the gateway, which resides on the Web server, to the appropriate application server. Messages that enter the gateway will, under normal conditions, be routed to the target application server for processing by PeopleCode message subscriptions and OnRequest handler programs.

    The ig.jms.JMSProvider.JNDIFactory.WebLogic property setting instructs the gateway to use WebLogic as the JMS provider. Next, the ig.jms.Topics, and ig.jms.Topic1 lines define the total number of JMS listening topics and specific topic connection information, respectively. The subsequent ig.jms.ErrorTopic lines specify the JMS error topic to which gateway errors should be published. The JMS connection properties shown in Listing 2 will cause the gateway to rendezvous with topic publishers and subscribers on the WLS instance server.

    The final step of this example is to create the actual JMS topic publishers and subscribers that will rendezvous with the gateway via the topics defined in the integrationGateway.properties file. Specifically, a JMS subscriber will be needed to cover both the error topic and the PostingStatusMessage topic specified in the JMS target connector. These JMS subscribers can be standard JMS message listeners or even MDBs. A standard JMS topic publisher can be used to send JMS TextMessage instances into the gateway.

    Listing 3 shows three message properties that must be set prior to publishing JMS TextMessage instances to the gateway. The first property, MessageName, specifies the message associated with the textual message being published. The DestinationNodes property specifies the default local node for the target PeopleSoft system. Finally, the RequestingNode indicates the IB node sending the published messages. Since the MessageName and RequestingNode shown in the listing match the inSync transaction previously defined at JKK_SOURCENODE, the broker will accept and route the published messages to the JKK_TARGETNODE node.

    The concepts, definitions, and procedures outlined in this article enable J2EE and PeopleSoft 8.4 applications to be seamlessly integrated using JMS. The benefits of taking this approach are clear: standards-based protocols and data (e.g., JMS and XML), transactional integrity, assured message delivery (both within PeopleSoft IB and WebLogic JMS), and high scalability using a combination of mechanisms such as message channels and pools of MBDs. Another benefit is that it can be used to integrate J2EE with any PeopleSoft 8.4-based product, including Financials, HRMS, SCM, and CRM.

    It's important to remember that this article provides an outline, not an exhaustive treatment of this topic. Important issues such as security have not been discussed. Others, such as transaction management, are only implied by virtue of using JMS, but have not been covered. Both J2EE and PeopleSoft's Integration Broker are vast, complex technologies that cannot be covered in any appreciable detail within the constraints of this article. However, this outline can become the first step in the journey toward mastery of these technologies. The next article in this series will explore the integration of J2EE and PeopleSoft 8.4 applications using Web services.

  • More Stories By Joseph K. Krozak

    An expert systems architect with over fifteen years of full lifecycle software engineering experience in various applications including banking, supply chain management / manufacturing, law, insurance, and telecommunications. I have spent years mentoring management and development teams on the architecture, design, implementation, and planning of large-scale, distributed, enterprise applications.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

    @ThingsExpo Stories
    In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
    In his session at 21st Cloud Expo, Raju Shreewastava, founder of Big Data Trunk, provided a fun and simple way to introduce Machine Leaning to anyone and everyone. He solved a machine learning problem and demonstrated an easy way to be able to do machine learning without even coding. Raju Shreewastava is the founder of Big Data Trunk (www.BigDataTrunk.com), a Big Data Training and consulting firm with offices in the United States. He previously led the data warehouse/business intelligence and B...
    Recently, REAN Cloud built a digital concierge for a North Carolina hospital that had observed that most patient call button questions were repetitive. In addition, the paper-based process used to measure patient health metrics was laborious, not in real-time and sometimes error-prone. In their session at 21st Cloud Expo, Sean Finnerty, Executive Director, Practice Lead, Health Care & Life Science at REAN Cloud, and Dr. S.P.T. Krishnan, Principal Architect at REAN Cloud, discussed how they built...
    With tough new regulations coming to Europe on data privacy in May 2018, Calligo will explain why in reality the effect is global and transforms how you consider critical data. EU GDPR fundamentally rewrites the rules for cloud, Big Data and IoT. In his session at 21st Cloud Expo, Adam Ryan, Vice President and General Manager EMEA at Calligo, examined the regulations and provided insight on how it affects technology, challenges the established rules and will usher in new levels of diligence arou...
    Nordstrom is transforming the way that they do business and the cloud is the key to enabling speed and hyper personalized customer experiences. In his session at 21st Cloud Expo, Ken Schow, VP of Engineering at Nordstrom, discussed some of the key learnings and common pitfalls of large enterprises moving to the cloud. This includes strategies around choosing a cloud provider(s), architecture, and lessons learned. In addition, he covered some of the best practices for structured team migration an...
    The 22nd International Cloud Expo | 1st DXWorld Expo has announced that its Call for Papers is open. Cloud Expo | DXWorld Expo, to be held June 5-7, 2018, at the Javits Center in New York, NY, brings together Cloud Computing, Digital Transformation, Big Data, Internet of Things, DevOps, Machine Learning and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding busin...
    No hype cycles or predictions of a gazillion things here. IoT is here. You get it. You know your business and have great ideas for a business transformation strategy. What comes next? Time to make it happen. In his session at @ThingsExpo, Jay Mason, an Associate Partner of Analytics, IoT & Cybersecurity at M&S Consulting, presented a step-by-step plan to develop your technology implementation strategy. He also discussed the evaluation of communication standards and IoT messaging protocols, data...
    Smart cities have the potential to change our lives at so many levels for citizens: less pollution, reduced parking obstacles, better health, education and more energy savings. Real-time data streaming and the Internet of Things (IoT) possess the power to turn this vision into a reality. However, most organizations today are building their data infrastructure to focus solely on addressing immediate business needs vs. a platform capable of quickly adapting emerging technologies to address future ...
    22nd International Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, and co-located with the 1st DXWorld Expo will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud ...
    22nd International Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, and co-located with the 1st DXWorld Expo will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud ...
    DevOps at Cloud Expo – being held June 5-7, 2018, at the Javits Center in New York, NY – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Among the proven benefits,...
    @DevOpsSummit at Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, is co-located with 22nd Cloud Expo | 1st DXWorld Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait...
    Cloud Expo | DXWorld Expo have announced the conference tracks for Cloud Expo 2018. Cloud Expo will be held June 5-7, 2018, at the Javits Center in New York City, and November 6-8, 2018, at the Santa Clara Convention Center, Santa Clara, CA. Digital Transformation (DX) is a major focus with the introduction of DX Expo within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive ov...
    SYS-CON Events announced today that T-Mobile exhibited at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. As America's Un-carrier, T-Mobile US, Inc., is redefining the way consumers and businesses buy wireless services through leading product and service innovation. The Company's advanced nationwide 4G LTE network delivers outstanding wireless experiences to 67.4 million customers who are unwilling to compromise on qua...
    SYS-CON Events announced today that Cedexis will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Cedexis is the leader in data-driven enterprise global traffic management. Whether optimizing traffic through datacenters, clouds, CDNs, or any combination, Cedexis solutions drive quality and cost-effectiveness. For more information, please visit https://www.cedexis.com.
    SYS-CON Events announced today that Google Cloud has been named “Keynote Sponsor” of SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Companies come to Google Cloud to transform their businesses. Google Cloud’s comprehensive portfolio – from infrastructure to apps to devices – helps enterprises innovate faster, scale smarter, stay secure, and do more with data than ever before.
    SYS-CON Events announced today that Vivint to exhibit at SYS-CON's 21st Cloud Expo, which will take place on October 31 through November 2nd 2017 at the Santa Clara Convention Center in Santa Clara, California. As a leading smart home technology provider, Vivint offers home security, energy management, home automation, local cloud storage, and high-speed Internet solutions to more than one million customers throughout the United States and Canada. The end result is a smart home solution that sav...
    SYS-CON Events announced today that Opsani will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Opsani is the leading provider of deployment automation systems for running and scaling traditional enterprise applications on container infrastructure.
    SYS-CON Events announced today that Nirmata will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Nirmata provides a comprehensive platform, for deploying, operating, and optimizing containerized applications across clouds, powered by Kubernetes. Nirmata empowers enterprise DevOps teams by fully automating the complex operations and management of application containers and its underlying ...
    SYS-CON Events announced today that Opsani to exhibit at SYS-CON's 21st Cloud Expo, which will take place on October 31 through November 2nd 2017 at the Santa Clara Convention Center in Santa Clara, California. Opsani is creating the next generation of automated continuous deployment tools designed specifically for containers. How is continuous deployment different from continuous integration and continuous delivery? CI/CD tools provide build and test. Continuous Deployment is the means by which...