Microservices Expo Authors: Pat Romanski, Elizabeth White, Zakia Bouachraoui, Liz McMillan, Yeshim Deniz

Related Topics: Microservices Expo

Microservices Expo: Article

CapeConnect Two for J2EEby Cape Clear

CapeConnect Two for J2EEby Cape Clear

Two distinct initiatives have come to the forefront as means
by which applications can be presented as Web-based services:
Microsoft's .NET and the J2EE platform. Application servers
and toolsets are beginning to tailor themselves to the Web
services paradigm as the concept matures. One such product
is Cape Clear's CapeConnect Two for J2EE.

CapeConnect provides an environment in which Java and
J2EE components may be presented as Web services
accessible via SOAP calls, defined by WSDL, and
cataloged by UDDI. Figure 1 illustrates
CapeConnect's architecture. SOAP clients access
the CapeConnect Web Services Platform, which
routes requests to the appropriate enterprise component.
This provides the capability to leverage the existing
investment in enterprise technologies with minimal
modifications to those systems.

Components of CapeConnect
CapeConnect consists of three major components:

The CapeConnect Gateway, essentially the message broker,
receives all SOAP client requests and forwards the messages
to the XML engine.

The XML engine converts the incoming SOAP requests
into Java method calls, routes them to the appropriate
enterprise components, and converts the results back into
SOAP messages.
Exceptions are handled through SOAP faults.

The J2EE engine is a fully-compliant Enterprise Java
container that may be used to serve EJBs. Alternatively, CapeConnect fully integrates with BEA's WebLogic 5.1 and 6.0 application servers, which may be used in place of the provided container. Future versions of CapeConnect will include integration with the iPlanet family of application servers and IBM's WebSphere.

Working With CapeConnect
Installation and Configuration

The installation process for CapeConnect is simple. I've installed it on a Windows 2000 Pentium III machine with 256Mb of RAM; versions are also available for Linux and Solaris. At install time, the choice between using the provided J2EE engine and integrating with WebLogic for serving EJBs is presented. Integrating with WebLogic requires a few simple steps to establish communication between the servers prior to creating services. Once installed, CapeConnect is ready for use with example applications and for deploying custom components. For this review, I've elected to use the WebLogic integration option.

Supporting Web Services
CapeConnect Two for J2EE exposes stateless session EJBs and standard Java classes as services available through SOAP calls. To do so, the developer deploys Java classes and Enterprise beans with CapeConnect either in lieu of a separate application server if the provided container is being used, or, if integrated with WebLogic, as a supplement to the normal deployment process. CapeConnect then generates the stubs and XML translations required to handle requests. Optionally, the developer may generate a WSDL profile for the object being deployed.

Two formats of SOAP action fields are supported by a proprietary format recommended for clients that exclusively access CapeConnect services, or a custom-defined format providing flexibility to clients communicating with multiple server environments. If the custom format is used, CapeConnect requires that WSDL be generated for the components deployed.

Creating Web Services
I've created a simple movie management system using EJBs deployed on WebLogic 6.1. It allows users to create and update a catalog of their personal collections of movies and videos. The system contains a single stateless session EJB to provide the external interface and a BMP entity bean to manage data persistence.

Once the beans are deployed on WebLogic, CapeConnect must be configured to route SOAP requests to and from the stateless session EJB acting as the interface mechanism. The first requirement is the location of the application server that hosts the components. An XML configuration file manages the mappings between services and their containers. During installation, if integration with WebLogic was specified the connection to the server is already established in the configuration file. Additional instances may be added by editing the file manually. Once the location of the EJB container is specified, the CapeConnect console may be used to add the individual application object. The information provided in the entry for each service includes the service name, the JNDI name for the associated object in its container, the server on which it resides, and whether the service requires a secure connection from the client. If no WSDL is required, clients may begin requesting the deployed Web service. Otherwise, WSDL may be generated for deployed objects through a wizard.

SOAP Clients with Cape Clear SOAPDirect API
Although it supports custom SOAP messages, CapeConnect provides a proprietary API called SOAPDirect. The API is intended to simplify the development of Web services clients that communicate exclusively with services exposed by CapeConnect. It isolates the details of SOAP messages from developers to reduce the learning curve and time needed to create service clients.

Creating a SOAP Client
Creating SOAP clients with SOAPDirect is very straightforward. The first step in the process is to create a request object and add any associated parameters. The developer is required to have the URI for the desired service available in order to construct the request object. The URI includes the application name specified in the configuration console and the JNDI name of the object being requested. There are three mechanisms to handle parameters for a request.

  • Simple parameters, such as Strings, Integers, etc., may be added to the request through overloaded add methods that support the various Java data types.
  • Array parameters may also be passed to the request from additional overloaded methods that receive an array value of the various Java data types.
  • Generic container classes handle more complex, custom structures. This container class holds field names and values for the custom object in the request, which is then mapped to the method signature of the called component.
For the movie example, the lookup method requires two parameters. The first is a primitive integer value that represents the unique number of the movie. This is set with the appropriate add method on the request. The second parameter is a custom user object specific to the movie manager system. In order to pass the user along in the request, an instance of SDComplexType is created. Each property of the user is added to the SDComplexType object, which in turn is appended to the request object.

When the request is invoked, the CapeConnect Gateway receives the request and sends it off to the XML engine where it's interpreted and sent to WebLogic 6.1 for processing. WebLogic's response is received, translated back into a SOAP reply, and sent through the gateway to the calling client as an SDReply object.

From the SDReply object, data values can be extracted via the accessor methods structured not unlike the accessor methods on a JDBC Resultset object. The reply object also provides an accessor to an SDComplexType object that maps any complex object returned from the EJB. In the case of the movie management system, a customized movie object was returned with all the properties of a movie. By providing the name of the desired property, the values may be retrieved and manipulated in subsequent processing.

CapeConnect Two for J2EE provides an effective solution for extending enterprise components including EJBs, CORBA objects, and standard Java classes to the outside world as Web services. It's a very simple package to install and administer. The provided SOAPDirect API has a reasonable learning curve that isolates developers from the intricacies of SOAP. It also provides the flexibility to work with any variant of SOAP and makes the creation of WSDL definitions extremely simple. With its integration into WebLogic, and future integrations with iPlanet and WebSphere, CapeConnect allows existing investments to be leveraged and extended with minimal impact.

More Stories By Brian Barbash

Brian R. Barbash is the product review editor for Web Services Journal. He is a senior consultant and technical architect for Envision Consulting, a unit of IMS Health, providing management consulting and systems integration that focuses on contracting, pricing, and account management in the pharmaceutical industry.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Microservices Articles
Lori MacVittie is a subject matter expert on emerging technology responsible for outbound evangelism across F5's entire product suite. MacVittie has extensive development and technical architecture experience in both high-tech and enterprise organizations, in addition to network and systems administration expertise. Prior to joining F5, MacVittie was an award-winning technology editor at Network Computing Magazine where she evaluated and tested application-focused technologies including app secu...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
When building large, cloud-based applications that operate at a high scale, it’s important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. “Fly two mistakes high” is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee A...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addresse...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...