Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 3 - Methods of Execution Enterprise JavaBean Execution Model

Intelligent Business Integration Reference Guide

♦ Overriding input and output map cards and sending and returning data using

HTTP

♦ Enabling and overriding map runtime settings

♦ Generating and compiling servlets

The Servlet Integrator wizard provides you with step-by-step instructions on how

to create, set up, and execute a Java servlet.

Enterprise JavaBean Execution Model

Mercator provides an EJB API that enables maps to be executed by an Enterprise

JavaBean containing business logic and deployed to an application server.

Providing this capability enables maps to be tightly integrated into a Java

component infrastructure, thereby leveraging all of the business logic (middle-tier)

consolidation, flexibility, and load-balancing capabilities of EJB or J2EE application

servers. While some Java programming is required to create the necessary

Enterprise JavaBean (EJB) interfaces, Mercator provides packaged EJB API

components that are “ready-to-go”, enabling maps to be deployed and run as

EJBs.

The benefit of this approach is that all of the power of Mercator product’s

standardized transformation and connectivity capabilities can be fully leveraged by

anyone seeking to deploy an EJB-based architecture. Rather than needing to write

Java code to perform complex transformation, connectivity, and routing, maps can

be fully leveraged to perform these tasks. Again, as with other execution models,

the same inherent Mercator technology components are used—maps. This means

that a more unified skill set is applicable across all integration models, thereby

reducing to a minimum, the overhead in writing the Java code to perform

transformation, routing, and connectivity. This frees up more time to concentrate

efforts on developing the business logic in the application layer code, resulting in a

much quicker implementation. In addition, because the source components (type

trees, map source files, and so on) are not procedural code listings, but rather

visual, object-based components, the ongoing maintenance of these components

is more straightforward; utilizing the extensive capabilities provided by the

Mercator Design Studio.

EJB-wrapped maps can be invoked in a variety of ways. The most common

method is by using another piece of coded EJB logic (often referred to as an

“executive” EJB). It is also possible to invoke maps using servlets.

The EJB API consists of a stateful and stateless Session bean that wraps a map.

Note Refer to the Mercator Integration for Java Reference Guide for more information.