Introduction to Workflows

WebLogic Integration makes a distinction between automated and manual workflows. Automated workflows, also known as Java Process Definitions (JPDs), are implemented as a Java class compiled into an Enterprise JavaBean (EJB). Workshop is used to create the JPD files, and their code is generated by using annotations.

A Web-based tool called the worklist client is provided for user interaction with the process definition. If a JPD requires user interaction, all pending tasks for a user are displayed through the worklist client, which the user can then complete.

Data transmission is achieved by using XML documents. Workshop provides a visual Data Transformation tool that uses the XQuery language to transform data from any other format to XML.

An internal message broker, an implementation of a Java Messaging Service (JMS) message server, is used for asynchronous communications. These messages are stored in a database to guarantee message delivery. The scope of the internal message broker is a single WebLogic Server instance. To process messages across server instances, you need to use JMS or Web services.

JPFS VERSUS JPDS

When you define application flow with Page Flows, JPF files are created. JPDs are files created for process definitions. Also, JPFs are synchronous, but JPDs can be asynchronous.

XQUERY

XQuery is a standard language that gives you flexibility when working with different data sources. When you issue an XQuery statement, an XML document is the output.

To support trading partner integration, WebLogic Integration supports the B2B standards, Electronic Business using Extensible Markup Language (ebXML), and RosettaNet. These standards outline the structure for interacting between trading partners. Web services can also provide an efficient way to communicate between trading partners .

ADAPTERS VERSUS WEB SERVICES

Knowing when to use adapters instead of Web services can cause some confusion. Adapters can be used with applications that you own and have control over. You need to write these adapters, which requires you to understand the technology behind the applications you control. Web services can be used when you have no control over the application you want to integrate with. You can simply use the services the application provides to get the required information without actually understanding the application itself.

Also, when working with Web services, both applications you want to communicate with need to support the Web service's standards. By using J2CA, you could integrate with any application by simply writing the adapter for that application.