A Sun technical white paper entitled \'Developing a Service Engine Component\' gives interested JavaTM developers a hands-on example of the construction and deployment of a JavaTM Business Integration (JBI) service engine component.

The JBI 1.0 specification was approved this summer as a final standard by the Java Community ProcessSM (JCPSM). Two key elements make up JBI: an open, pluggable and extensible platform architecture and a Service Assembly.

The open, pluggable and extensible JBI platform provides an easy way for integration technologies and web services to collaborate. Vendors will benefit by being able to deliver SOA and integration faster based on the open standards and the JBI partner ecosystem. IT users will benefit as more complete solutions from vendors are released. In addition, users will have the flexibility to extend those solutions using the JBI partner ecosystem if their vendor is unwilling or unable to provide new functionality.

The Service Assembly is a standard definition of a composite application. It defines in a single document the routing information and artifacts that make up an application in an SOA. The JBI Service Assembly also will enable a new generation of more powerful, SOA-oriented software development tools.

This technical white paper is written for readers with the following experience:

• A working knowledge of the JBI Specification
• Java programming experience
• An installed copy of the Sun JavaTM System Application Server, version 8.1 (PE)
• An installed copy of the JBI SDK

"A number of Java classes must be created to construct a component, each implementing one or more interfaces. This guide will show the absolute minimum amount of code required to build, install, and deploy a service engine component," explains the Sun technical team. "Where appropriate, it will also give pointers about adding further functionality."

Along with information on creating a service engine component, including classes, the Sun technical team also explains packaging service engine classes; installing a service engine component; defining services for a component; deploying services to a component; and finally, testing the new service engine component to prove that it has been properly installed and has service deployed for it. This 23-page PDF also offers diagrams and charts to assist readers' understanding through the process of developing the service engine component. [...read more...]

From the latest issue:

Recent Blog Entries as of July 4, 2009, 8:23 am
'Managing ZFS File Systems in Solaris Containers' Demonstrating Out-of-the-box Performance Gains with memcached-1.3.1 The Father of Java on His Progeny's Future Patch Checked Advanced (PCA) - Solaris OS Patch Management Utility VirtualBox 3.0 Released	Doing a Mobile Install of OpenSolaris and VirtualBox on a Laptop Latest Support and Key Features of Solaris Cluster for SAP NetWeaver Stack Solaris News Bites White Paper: Getting Ahead of The Trend in the Mobility Market Intel Xeon 5500 Processor Series on OpenSolaris, Solaris, and Linux
Blog RSS Feed