This section provides a technical overview of the way the runtime layer architecture is implemented for selected deployment platforms. The goal of this section is to help to answer questions such as How does SCORE Adaptive Bridges support J2EE and EJBs?

SCORE Adaptive Bridges supports a wide range of client technologies, middleware products and server platforms. Please see Supported Platforms for an overview of the current platforms.

If you do not immediately see your particular product or infrastructure mentioned then please Contact us via your local sales organization. We are constantly adding new platforms; it is also possible to add platforms based on specific projects requirements.

Java Application

In this scenario a new Java GUI might be developed for an existing legacy application. The adaptive proxy is generated as normal Java classes and can be used directly from the Java client. The Java GUI client developers can use the full functionality of their GUI toolset – all communication with the legacy application is performed via the generated adaptive proxy.

The technology adapter can use a variety of different middleware technologies to connect to the server, including the IBM CICS Transaction Gateway and Java JNI connecting through Oracle Tuxedo.

J2EE Application Server

In this scenario a remote application might be developed for use in the field by sales staff using their notebooks. A Java application might be developed for the client to perform the basic processing. This needs to connect into legacy applications and data stores to process orders, for example.

The architecture calls for a middle tier based on a standard J2EE application server with the “client” implemented with a combination of servlets, Java Server Pages (JSP), Java Beans and/or Enterprise Java Beans (EJBs).

In this scenario SCORE Adaptive Bridges can generate the adaptive proxy as an EJB that uses the J2EE Connector Architecture (JCA) to “escape” from the J2EE environment and connect to the client-side technology adapter. From here it then connects out via the selected middleware to the server.

Oracle WebLogic Server

In this scenario a new Web-based application is being developed using an HTML client. The majority of the processing is provided by an existing legacy application. Some additional data that is not easily available from the existing application must be obtained directly from one of the legacy data stores.

The architecture calls for a middle tier based on the Oracle WebLogic J2EE application server. The middle tier of the “client” is implemented with a combination of servlets, Java Server Pages (JSP), Java Beans and/or Enterprise Java Beans (EJBs).

In this scenario SCORE Adaptive Bridges can generate the adaptive proxy as an EJB that uses the special Oracle WebLogic Tuxedo Connector (WTC) to “escape” from the J2EE environment and connect to the client-side technology adapter. From here it then connects out via Oracle Tuxedo to the server. WTC is a special facility available with the BEA WebLogic application server to connect to servers using Oracle Tuxedo. This is a more optimized solution that using the standard J2EE Connector Architecture (JCA).

Web Services Platform

In this scenario a new mobile application is being developed to run disconnected on a Personal Digital Assistant (PDA). From time-to-time the PDA connects into the corporate network and needs to synchronize with a series of legacy applications. The synchronization with the PDA is being handled by a third party Web services platform that offers this functionality. Part of the synchronization requires passing updates to a legacy application. The connectivity to the legacy application is to be handled by SCORE Adaptive Bridges.

The Web services platform is acting as the client application to the adaptive services crated with SCORE Adaptive Bridges. The Web services platform has a standard interface that it expects to use to connect to external sources. This interface is defined as a standard WSDL document provided by the Web services platform vendor.

To support this scenario SCORE Adaptive Bridges can discover the expected interfaces from the WSDL document and use these to create the PIM in the composition model. The adaptive proxy is generated as Java classes that can be invoked directly from the Web services platform. The Web services developer sees a standard Web service that meets the expected interface specification. They have no need to be aware of how the information is being communicated to the legacy application.

Where to Go Next?

Now that you have seen examples of the runtime layer architecture you are invited to review some additional ways of learning about SCORE Adaptive Bridges. If you have not already done so then you might want to look at the business perspective in Business View. If you are more interested in methodologies then the Methodology View is a good place to start. Alternatively you might want to look at the Process View that looks at SCORE Adaptive Bridges from a process perspective – what do you actually do to build adaptive services.