Welcome!

Microservices Expo Authors: Pat Romanski, Dalibor Siroky, Stackify Blog, Elizabeth White, Liz McMillan

Related Topics: Microservices Expo, Java IoT

Microservices Expo: Article

BPEL & B2B Synergies Reduce Supplier Enablement Costs

Helena Chemical Company Deploys New Technology & Techniques

(SYS-CON Media) - Although organizations use multiple technologies to solve myriad business problems, integrating two or more of these technologies to derive new business benefits presents additional challenges. This is especially true when the collaboration extends beyond an organization's own systems to include those of its business partners.

This article describes one such customer scenario in which Helena Chemical Company, a leading U.S. agricultural products specialist, used BPEL (Business Process Execution Language) and B2B technologies together to automate better and more productive supplier/distributor relationships. Put together, these technologies enabled a process-centric hub that provided significant business cost savings, faster supplier ramp-up, more responsive customer relations, and better process visibility both inside and outside the enterprise.

Traditionally, the alignment of information and processes has proven challenging for Helena because of the vast differences in its partners' systems and the content they produce and consume. The challenge for Helena (see Figure 1) was to meet its XML and electronic data interchange (EDI) needs by balancing the right enterprise components across diverse supplier systems and to remove the administrative overhead of manual approvals, support, and data entry to streamline its seasonal order process, which processes tens of thousands of supplier interactions per partner in a four-month period. Helena also needed fault-tolerant exception handling and controlled manual intervention to resolve business decisions and needs.

Faced with the need to manage supply partners and handle ordering and production details ahead of farmers' seasonal crop-planting cycles, Helena chose a process-based approach in which its internal order processing seamlessly integrated with partner B2B processes. The end result was an integrated solution that smoothly bridged the disparities between the diverse supplier systems by using standards-based information exchanges in tandem with process alignment techniques.

Solving the Business Needs
Although Helena's existing EDI systems provided some measure of automation, it had an extended support infrastructure of paper, fax, and telephone-based coordination that needed to be replaced with the modern business process capabilities provided by BPEL and B2B solutions. These modern tools provide exceptionally greater levels of information agility, process control, and exception handling than traditional EDI-based systems.

When companies integrate with partners and suppliers, the initial focus is on automating the exchange of XML documents. This exchange can be handled by modern B2B protocols such as ebXML, RosettaNet, and EDI over the Internet (AS/2). But once the XML business documents are exchanged, they are often processed internally using traditional techniques such as batch-oriented transfer, human data entry into multiple systems, and traditional manual approval processes - leaving the information fragmented across multiple systems. This mismatch between slow manual internal processes and automated external processing can wipe out the gains achieved from supplier partner automation. Staff resources and time continue to be needed to manage customer relationships and resolve delivery and order tracking and coordination issues. The reverse scenario can also occur: internal processes are streamlined, but are saddled with archaic external B2B transactions that use FTP, fax, e-mail, and human interaction.

The ebXML standard solution stack provides a B2B toolkit that allows implementers to resolve these partner integration issues. This toolkit includes formal XML-enabled mechanisms that capture collaboration protocol agreements (CPAs) between participants - which define their actions, roles, and the transactions that will be carried out between them - and couple them into discrete send/receive binary collaborations. These XML mechanisms also provide end-point addressing to server messaging systems, as well as secure and reliable message delivery. Each partner then uses its own ebXML message envelopes to convey its partner ID, business actions, and the transaction data needed for each step of the business process. A rule- and event-driven business process engine - such as BPEL provides - can then key off these XML exchanges and control the state transitions and exceptions, along with the integration into back-end enterprise resource planning (ERP) systems.

The Helena case study shows how traditional B2B interchanges can be rapidly upgraded and fully automated with modern business process management (BPM) technology using open standards-based software with graphical and visual configuration tools that set up each partner and control the exchanges needed. These tools allow fine-grained control using standards-based XML formats for everything from partner profiles to collaborative message mappings to process flow details and rules, thus allowing delivery of a complete event-driven solution (Figure 2) that doesn't require custom low-level coding.

Developing Process-Centric B2B Hubs
To move from traditional B2B hubs that integrate data with internal systems, to process-centric hubs, organizations are integrating B2B with internal processes using XML-aware BPEL scripting technology. These internal processes are not simple data-handling receive/respond integration processes, but the actual end-to-end, event-driven business processes that run the organization.

For example, in the past, a purchase order (PO) received over RosettaNet would typically be input into an ERP or customer relationship management (CRM) system and any further processing would reside in the ERP or CRM system. With BPEL, processes - such as "Order to Cash" and "Procure to Pay" - are executed in the business process engine, with subsequent orchestrations into ERP, CRM, and other internal applications. Thus, B2B business interactions can be integrated into the larger BPEL processes and become reusable and extensible as BPEL process components rather than static low-level coding done at various downstream points in traditional legacy systems. This approach - which leverages XML transactions, Xpath, and BPEL rules - creates a more agile solution that can deal with a wider range of disparity in the XML transaction formatting and data point details received from the external partners' systems. It also brings together data, rules, and process decisions into one coherent solution rather than dispersing them across systems.

This approach presents significant benefits (see Figure 3). First, the direct integration leads to fewer conflicts of rules and triggers across software components. Second, monitoring and management at the process level provide a view of not only the status of the process but also the status of the B2B engine, allowing for an integrated view of the overall process. Third, BPM technologies such as BPEL allow for the inclusion of human-directed workflow components, which are the critical elements of any true B2B integration, thus allowing for complete process integration.

Figure 3 shows a summary of the handoff and process flow between the B2B and BPEL components in the solution architecture. Each component performs a discrete role, such as steps five, six, and seven, which are responsible for correctly routing each message to the partner based on the collaboration protocol agreement (CPA) and the transaction type, and securely and reliably delivering the message. Similarly, in the BPEL processing section, steps three and 14 ensure that the message content is correctly transformed based on business rules, partner, and transaction type. Most importantly, BPEL provides the correlation and state management between inbound and outbound transactions (steps four and 13) based on the unique partner IDs and transaction IDs contained in the message envelopes. Steps one and 15 provide the integration to the back-end applications through standard APIs.

To deliver the full production environment at Helena, the IT consulting team implemented the new technology using an incremental approach. Building on the existing database foundation at Helena, the team added the Oracle XML gateway, along with ebXML messaging support for the partners' chemical industry transaction exchanges. Then the team prototyped integration into the back-end processing systems via BPEL and schema transformations and refined the workflow.

This incremental approach let Helena step from a simple EDI-based legacy environment to a sophisticated workflow process with B2B XML exchanges, ERP integration, and alerting. Particularly impressive was Helena's own design approach, which uses BPEL/human workflow processes in its B2B interactions and BPEL for IT task automation. By using BPEL for error analysis during the IT task mode, and then quickly switching to BPEL/human workflow orchestration to pass the error details to the appropriate e-commerce support specialist for resolution, Helena was able to rapidly evolve and adapt its business solution.

The Solution - The Technology Details
The seamless integration of the ebXML message service (ebMS), message transformation and BPEL tools inside the Oracle XML gateway was the key to rapidly configuring the business solution that Helena Chemical Company required (see Figure 3). Helena's own staff was involved in every step of the development process and was able to immediately assimilate the new technologies due to the transparency of the tools and the XML-enabled mechanisms. Stress testing was also done before going live to simulate seasonal peak production volumes and ensure that the supporting hardware configuration was sufficient.

Helena chose not to add complex lookup and transformation capabilities using the optional Oracle XML Publisher data transformation toolset and instead achieved better control in BPEL itself by combining mapping as an external e-commerce function and customizing it by extending BPEL's own XML-handling capabilities. This approach will allow Helena to support future enhancements such as business activity monitoring (BAM) by creating triggers and rules based around the XML content and transaction flows, and Helena is actively investigating such future options.

Helena chose to use the Oracle solution set after carefully evaluating its existing tools and available options. (Although Helena's choice of solution gave it significant advantages, it's important to realize that comparable standards-based solution stacks can deliver equivalent levels of integration between the B2B ebXML standards approach and the BPEL approach.) The ebXML editor used to create each partner's collaboration protocol profile (CPP) is integrated with the Oracle messaging and partner registry and the BPEL workflow manager. This visual editing tool allows partner templates to be quickly created and then used to add new partners. The template ensures that the CPA generated for each partner can be validated against the transactions received, and also against the actions in the BPEL business process definitions. Similarly, the ebXML message envelopes link to the partner CPAs via the unique partner IDs and the business actions assigned to the XML message handling and the BPEL processing scripts. Each partner therefore has its own private, secure CPA definition between it and Helena that controls the B2B actions its system can perform and how Helena handles those exchanges internally.

Next, we consider the messaging transaction standards and the handling logic. While Helena's process was inherently more complex and involved a number of collaborating processes and human worklist interactions, let us look at the components and interactions of a generic process flow. The main control logic is typically implemented using the BPEL process definition editor as a series of BPEL actions, conditions, rules, and workflow steps. The B2B/XML interactions used by the agricultural chemical industry are a result of collaboration between the Chemical Industry Data Exchange (CIDX), Petroleum Industry Data Exchange (PIDX), and a nonprofit trade association representing the agricultural industry.

CIDX previously built the XML-based Chem standards that defined 52 business messages required by chemical companies to carry out highly secure transactions with suppliers and customers over the Internet. This work was enhanced and extended in collaboration with PIDX, and then the ebXML messaging standards were selected as the preferred secure transport mechanisms via the Internet.

Between the B2B interactions, the BPEL processes, and the back-end ERP system, the XML content acts as the integration glue. To achieve this result, the BPEL - along with the Oracle XML handling tools - retains the values of the content as variables in memory, along with the state of the particular process handling. This means that content does not need to be unmarshaled from the XML into traditional tables and columns in the SQL database. Delaying that handling to a point as late in the process as possible adds agility and greatly reduces the overhead of continually repackaging information and maintaining the associated programming of code logic.

Once the information is committed into the back-end ERP system, the Oracle AQ adapter in conjunction with XML Gateway, an eBusiness Suite component, handles the manipulation of the XML content into the appropriate ERP formats and data. Again, this reduces the amount of custom coding required.

Open Standards, Open Solutions
The Helena case study shows that combining open standards and leveraging the flexibility inherent in XML can allow organizations to produce an innovative solution that elegantly solves a complex set of business needs. The ability of BPEL (in combination with B2B) to support this blend of technologies in an open way-quickly and easily-is crucial. For Helena, having these robust capabilities supported by graphical and visual development tools dramatically reduced the learning curve and setup times for its staff and delivered speed to market. These were critical business success criteria for Helena, because its cyclical business required quick delivery of the new system prior to its peak business period.

The technology combination used by Helena shows great flexibility to meet a wide range of operational needs, and the successful working model implemented at the company can clearly be duplicated by other companies with similar industry B2B and enterprise application integration (EAI) needs. By providing direct support for event management, the BPEL component also makes it possible to support additional enterprise-level process management solutions - such as BAM and ERP management reporting - that are designed to give greater visibility into processes, milestones, and intervals in delivery of services and products to the customers.

Summary of the Benefits and Lessons Learned
In bringing together the power of traditional B2B processing and the RAPID messaging standards defined for the chemical industry, along with the business process management tools developed in the BPEL specifications, the Helena Chemical project demonstrates the future pathway for Web Services and the business solutions built around them.

The B2B approach leverages years of solid formal business experience, while the Web Service approach and BPEL provide agile adoption strategies and technologies. Clearly these tools can be combined into a solution that offers customers effective business tools that don't require extended programming and development efforts to implement, and can therefore be implemented and deployed in weeks rather than months.

This scenario illustrates that the future of B2B is based on the formal business process and transaction models that have always been its strengths, and their adoption across a whole industry. Rather than diminishing the importance of B2B, the continued and accelerating adoption of Web Service technologies is likely to create more need for formal B2B-based business processes to reduce the cost of adoption and implementation across industry groups.

Resources

More Stories By David Webber

David Webber is an industry consultant for applications of XML and ebXML. Previously vice president of business development for XML Global Technologies, Inc., and cofounder of the XML/edi Group, he is now working with OASIS XML standards committees. David’s current project team just received a special recognition award for its leading SOA work from the SOA/CoP Second Conference in Washington, D.C. David holds two U.S. patents on advanced information transformation with EDI and holds a degree in physics with computing from Kent University, England.

More Stories By Nishit Rao

Nishit Rao is director of product management for Oracle Fusion Middleware. He is focusing on enhancing and evangelizing the middleware platform to meet the demanding needs of Oracle customers. He has more than 15 years experience in engineering and product management for messaging, Common Object Requesting Broker Architecture, J2EE, integration, and SOA products. He also has experience rolling out middleware solutions as an architect for a large global logistics company. He holds an MBA from the University of California, Berkeley, and a BS in electrical engineering.

Comments (1) View Comments

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.


Most Recent Comments
SOA Web Services Journal News 01/04/07 12:12:50 PM EST

Although organizations use multiple technologies to solve myriad business problems, integrating two or more of these technologies to derive new business benefits presents additional challenges. This is especially true when the collaboration extends beyond an organization's own systems to include those of its business partners.

@MicroservicesExpo Stories
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...