Browse Prior Art Database

A Facade Plugin for a B2B Engine to Call Services Deployed in Websphere

IP.com Disclosure Number: IPCOM000020770D
Original Publication Date: 2003-Dec-12
Included in the Prior Art Database: 2003-Dec-12
Document File: 2 page(s) / 56K

Publishing Venue

IBM

Abstract

Disclosed is a simple facade plugin to enhance the Business-to-Business(B2B) engine to invoke a provided function, a defined session Enterprise Java Bean (EJB), which invokes the microflow deployed in the Websphere runtime or Websphere Studio Application Developer (WSAD).

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

A Facade Plugin for a B2B Engine to Call Services Deployed in Websphere

A new business to business application often involves a B2B engine which is based on a proprietary model. With new requirements and new technologies, a new user interface is designed and the B2B engine is not sufficient to provide all the server functionalities. The Websphere Studio Application Developer or Websphere Runtime provides more server support, like deployment of services or EJB. The B2B engine has to be redesigned to call these kinds of provided functions running on Websphere. This disclosure describes a simple facade plugin to enhance the B2B engine to invoke a provided function, a defined session EJB, which invokes the microflow deployed in the Websphere runtime or WSAD.

Assume the B2B engine models data in the proprietary XML format. With the new requirements, a facade plugin has to be added to the application to invoke any deployed EJBs running on Websphere runtime or WSAD. The whole end-to-end scenario is explained in Fig. 1.

Figure 1

A new user interface of the B2B tool is designed. The new UI tool can be a plugin of WSAD or any other application. Upon publishing, the new tool calls code generation which converts the model from the new format to the proprietary format understood by the legacy system. Then, the plugin code in the B2B engine is called to handle the generated xml file and the specified provided function or service running on Websphere runtime. In our example, the deployed service is a service proxy session bean for a Microflow.

In particular, the runtime Plugin has these functions:

1

[This page contains 1 picture or other non-text object]

Page 2 of 2


1.


2.


3.


4.


5.

Figure 2

Fig. 2 shows the basic design of the Facade Plugin. The Plugin is designed to call any EJB so the p...