Java CAPS Documentation

Business is data-driven. Different business sectors and industries have created and refined a wide variety of data formats and standards, often tightly coupled with rules for parsing, validating, and transforming data.

Java CAPS provides adapters to read and write data in the native format of specific databases or business systems, such as Oracle, Sybase, HL7, SWIFT, HIPAA, SAP, PeopleSoft, and dozens of others. In addition to adapters for data modeling and representation, Java CAPS also provides collaborations and engines for data transformation, and an implementation of the Java Messaging Service (JMS) for data queuing.

The Enterprise Service Bus (ESB) handles the flow of data to and from adapters that model the data, into and out of queues that persist the data, and through the collaborations and engines that transform the data.

Back to top

A service-oriented architecture (SOA) defines a framework for creating, exposing, and invoking services that are loosely coupled and interoperable, and orchestrating them with business logic to achieve a particular objective. As with most SOAs, Java CAPS uses XML-based web services described by WSDL (standard web services definition language) and orchestrated by BPEL (business process execution language).

A WSDL file is an XML document that describes the interface to a web service. This provides for loose coupling: So long as the contract is honored and the client (service consumer) has access to the WSDL, the service provider can change implementation details without requiring changes to client modules that invoke it.

BPEL is an XML-based language for orchestrating business processes. Because it is a high-level language, it shields you from the fine details of methods, object implementations, and attributes. Instead, you can think in constructs such as receiving data, replying to messages, invoking a service, and interacting with a partner.

Back to top

Java CAPS helps you combine existing or new business applications to create composite applications. This approach leverages investment in other systems and legacy applications, reduces development time and cost, and leads to higher quality and maintainability. So long as the application honors its publicly defined interface, it can used as a self-contained subassembly (service unit) in an overall service assembly. Each such application can be separately created, tested, maintained, and updated.

Back to top

The Java Business Integration (JBI) standard defines a framework for connecting, validating, testing, and deploying applications on application servers. JBI employs terminology such as subassemblies, service assemblies, binding components, and service engines.

Back to top

New GUI for design work. Uses NetBeans 6 plug-ins for familiarity, maintainability, compatibility.

Tailored for Sun Java Application Server 9.1

Support for JBI components (as NetBeans plug-ins):

• BDRU = BiDirectional ReUse (JBI Bridge)
• Sun Java Message Server
• Service Engines (SEs) for: Java EE, BPEL
• Binding Components (BCs) for: HTTP/SOAP
• CASA Editor (Composite Application Service Assemblies)
• eView / Mural

Back to top

• Transactionality: Start / propagate / commit / rollback / XA
• Management
• Monitoring (MBeans, and JMX notifications)
• Alerts (Via WSDL porttype, and JMX notification)
• Packaging / Deployment

Back to top

Application Server (See AS 9.1 above)

JBI Bus, also known as Normalized Message Router (NMR)

• Service Engines (SEs): Java EE SE
• Binding Components (BCs): HTTP BC
• Messaging Components: Sun Java Message Server

Global service collaboration is composed of:

• Collaboration description
• Services that fulfill one or more collaboration roles

Configuration

• Installation-time configuration
• Design-time configuration
• Run-time configuration (via MBeans)

Back to top