BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
JAM Documentation | JAM Workflow Processing Guide | Previous Topic | Next Topic | Contents | Index

Workflow Processing with Java Adapter for Mainframe

Many customers need an advanced e-business infrastructure that incorporates process rules, workflow, and application components. BEA designed WebLogic Java Adapter for Mainframe (JAM) to seamlessly plug in to BEA WebLogic Process Integrator, a powerful process integration and workflow engine. This software combination allows you to create business processes, process rules, and workflows that access mainframe applications.

Workflow Processing with WebLogic Process Integrator

WebLogic Process Integrator provides an intuitive flowchart model for defining business processes that work across the enterprise and in support of business-to-business interactions with minimal human interaction. The powerful workflow engine executes those processes, automatically invoking the resources required at each step. Online process monitoring provides real-time data about how the processes are working and any necessary changes can be made dynamically.

Fully J2EE compliant, WebLogic Process Integrator provides an intuitive graphical user interface that enables businesses to design, monitor, and modify workflow and e-business processes without scripting or programming. Its run-time engine automates and manages the activities of applications and such technologies as fax, WAP-enabled telephones, and other devices, with exception-based human intervention.

WebLogic Process Integrator uses XML as its standard data format. To access data from a legacy system in WebLogic Process Integrator, the data must be converted to XML first. WebLogic Process Integrator uses WebLogic XML/Non-XML Translator to translate data from binary to XML or from XML to binary.

Data Translation with WebLogic XML/Non-XML Translator

XML is quickly becoming the standard for exchanging information between applications and is invaluable in integrating disparate applications. WebLogic XML/Non-XML Translator provides for an exchange of information between applications by supporting data translations between binary formats from legacy systems and XML. WebLogic XML/Non-XML Translator normalizes legacy data into XML so it may be directly consumed by XML applications such as WebLogic Process Integrator.

Accessing Mainframe Applications Using Java Adapter for Mainframe

WebLogic Java Adapter for Mainframe seamlessly plugs in to WebLogic Process Integrator, allowing business analysts to include mainframe applications in business processes. Within the WebLogic Process Integrator framework, JAM uses WebLogic XML/Non-XML translator to translate mainframe data to and from XML. JAM can be used with WebLogic Process Integrator in the following two ways:

- WebLogic Process Integrator workflows can invoke applications on the mainframe. Data from the workflow is passed to the invoked application and any resulting data is returned to the workflow.

- Mainframe applications initiate a workflow in WebLogic Process Integrator using an XML event interface.

Understanding WebLogic Process Integrator Interaction with the Mainframe

Figure 1-1 illustrates the flow of data when a WebLogic Process Integrator workflow accesses mainframe applications through JAM. When WebLogic Process Integrator sends data to the mainframe application, the JAM gateway converts the XML data received from WebLogic Process Integrator to the binary format expected by the mainframe application. The JAM gateway invokes WebLogic XML/Non-XML Translator to perform this conversion. It then invokes the mainframe program and receives a response. This response is sent to WebLogic XML/Non-XML Translator to convert the data from mainframe format to XML. Then the converted response is sent to WebLogic Process Integrator.

Figure 1-1 Workflows Accessing Mainframe Applications

JAM also allows a workflow to be initiated by an event triggered by a mainframe application. When JAM receives a request from the mainframe, it looks within its configuration to find the destination application within WebLogic Server. If the specified destination is WebLogic Process Integrator, then JAM puts the mainframe data on a WebLogic Process Integrator queue. WebLogic XML/Non-XML Translator pulls the data off the Event Queue and recognizes that translation is required. The translation is performed and the data is returned to the queue. WebLogic Process Integrator workflow that uses this XML is then initiated. This flow of data is illustrated in Figure 1-2.

Figure 1-2 Mainframe Application Initiating a Workflow

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.