Not logged in | Login
Open ES Bv 2 Release Info
In addition to these release notes, you might also want to consult the following release notes:
Open ESB supports pluggable service engines and communication protocol bindings, as well as dynamic, configurable message management and delivery.
Open ESB includes the JBI Runtime and the service engines and binding components listed below.
Developers can also create additional plug-in components to fit specific integration tasks.
All JBI components are initially installed in the shutdown state. When a service assembly is deployed to a component, the component automatically transitions to the started state.
|BPEL Service Engine||sun-bpel-engine||Provides services for executing Web Services Business Process Execution Language 2.0 (WS-BPEL, or BPEL) compliant business processes.|
|Java EE Service Engine||sun-javaee-engine||Connects Java EE web services to JBI components.|
|SQL Service Engine||sun-sql-engine||Provides SQL execution services to other JBI components.|
|XSLT Service Engine||sun-xslt-engine||Transforms XML documents using XSL style sheets.|
|File Binding Component||sun-file-binding||Provides a transport service to a file system and offers a comprehensive solution to interact with the file system from the JBI environment.|
|HTTP Binding Component||sun-http-binding||Provides external connectivity for SOAP over HTTP in a JBI 1.0 compliant environment.|
|JMS Binding Component||sun-jms-binding||Provides Java Message Service (JMS) transport for inbound and outbound messages.|
The JBI installation root directory is created by the installer. This directory contains static content that is shared across all instances in an application server installation. There is only one JBI installation root directory per application server installation.
<as_install_dir> /jbi /bin /components /doc /lib /schemas /shared-libraries
The JBI domain root directory is created by the application server at domain-creation time. This directory serves as a configuration and artifact repository for all instances in a domain.
<as_domain_dir> /jbi /autoinstall /components /config /service-assemblies /shared-libraries
The JBI instance root directory is created by the application server administration runtime at instance-creation time. This directory serves as a local repository for configuration and artifacts specific to an instance.
<as_instance_dir> /jbi /components /config /service-assemblies /shared-libraries
Open ESB provides several administration tools and utilities for administering composite applications.
JBI Ant tasks are integrated into the Sun Java System Application Server Ant client, asant. Note the following changes in Ant administration:
The following tasks have been added in this release:
These tasks are not included in the default task definitions in the asant environment. You need to load the JBI task definitions explicitly in the Ant script in the asant environment in order to use these tasks in the Ant script. To load the task definitions for these tasks, use the following in the Ant script before using these tasks:
<taskdef resource="com/sun/jbi/ui/ant/antlib.xml" />
For more information, see the JBI Ant Task Reference. You can find this reference in the following location in an Open ESB v2 installation: <App_Server_Install_Dir>/jbi/doc/antdoc/
The following targets have been added in this release:
For more information, see the JBI Ant Target Reference. You can find this reference in the following location in an Open ESB v2 installation: <App_Server_Install_Dir>/jbi/doc/antdoc/
Sun Java System Application Server's command-line administration utility, asadmin, includes JBI commands.
Detailed help for each JBI command is available in man-page format through the asadmin help command.
The following JBI commands have been added in this release:
The Sun Java System Application Server Admin Console provides JBI administration controls in the following areas:
NetBeans IDE 6.1 provides the following JBI administration tools:
We welcome your input on any issues that you find with Open ESB.
For issues with the core Open ESB runtime or with Open ESB components, go to:
To use the Open ESB issue tracker, you must be a member of the Open ESB project .
You can view issues that have been previously reported at https://open-esb.dev.java.net/issues/query.cgi .
For issues with the Java EE Service Engine, go to:
This section describes known issues and limitations with Open ESB v2.
You might also want to consult the following release notes for known issues:
The File Binding Component supports both Request-Response and One-Way message exchanges on the inbound side, but only supports One-Way operations on the outbound side.
The HTTP Binding Component cannot accept connections through a firewall. As a workaround, configure the Java properties proxyHost and proxyPort from the Administration Console of the application server. To do this, click the Application Server node in the tree, and the JVM Settings and JVM Options tabs in the right pane. Then add the following JVM options:
-Dhttp.proxyHost=myProxyServer.com -Dhttp.proxyPort=80</code>The proxy might also require authentication/authorization.
|ID||Description / Workaround|
|6522692|| Java EE Service Engine cannot act as both a service provider and service consumer to the same BPEL process.|
In a BPEL process, you cannot make a one-way invocation to the Java EE Service Engine and also have a correlated receive activity expecting an inbound message exchange from the same Java EE Service Engine to the same BPEL process.
Workaround: Model your scenario as an InOut Message exchange (request-response invocation from the BPEL Service Engine to the Java EE Service Engine).
|6504443|| SQL Service Engine requires third party driver to interoperate with Oracle's classes12.zip.|
Oracle does not implement the metadata calls that are used to generate the WSDL files, thus a third party driver such as that supplied by DataDirect must be used.
|96020|| WSDL files generated by the SQL Project module do not correctly identify parameter names.|
When using the SQL Project and generating Insert, Update, and Delete the parameter names are not generated correctly. For example, instead of generating parameter names matching the column names for the select statement, it creates parameters named param1, param2, param3, and so forth.
|6469537|| No warning is given when shutting down a component that has running service units. |
Workaround: Before shutting down a component, make sure all service assemblies with service units deployed to that component are stopped and shut down. This is to avoid other services attempting to access services that will no longer be available because of the component shutdown.