Java Open Enterprise Service Bus Built with Java Business Integration (JBI) Technology
https://open-esb.dev.java.net
This early release of Open ESB is based on the JSR 208 Reference Implementation and adds ESB capabilities to all multiple JBI instances that participate in an Enterprise Service Bus (ESB). A Central Administration Server (CAS) is implemented as a JBI instance with special configuration parameters to set it up as the CAS for an ESB.
Note: This build is an experimental version of Open ESB. The Open ESB software is being provided to the community as part of the open-source community development effort. This software might not work and it could cause unanticipated problems. Users should not use this software for any purpose, other than experimentation, research, or other, non-production related uses.
Build060512_3 contains the experimental preview binary distribution only. If you want to work with the stable SDK source, you should refer to the existing kits available at Project Open ESB. These kits are available from the "Documents & Files" link after you log in.
CVS and the build tools are available from Project Open ESB for both the stable SDK and the experimental preview core runtime. For the experimental preview runtime, the CVS repository update might lag behind the distribution of the experimental binary and source-code archive copy. The SDK is available under the openesb_maint1 branch in CVS and the experimental preview is available in the main branch.
New features and updates of interest in this build include the following:
Enhanced support for distributed message exchanges using the Sun Proxy Binding.
Improved synchronization support for off-line management operations.
Administrative operations targeted at an instance that is unavailable are deferred until the instance comes on-line.
The ability to add ESB member instances that have not been created or started yet.
Once the instance is created and started, it automatically synchronizes with the CAS and joins the ESB.
ESB administration console now features online help.
Online help for the web console is still in early stages of development.
Standard ant targets that are defined in JSR 208 are now compatible with a multiple-instance ESB.
ESB console is still under development, but new features are available for preview:
| OS / Platform |
SolarisTM SPARC® 9*, 10
Solaris x86 9*, 10 Red Hat Linux AS 3.0 Red Hat Linux AS 4.0 JDS Release 3 (x86) JDS Release 3 32-bit (Opteron) Windows 2000 Server Windows 2003 Server Windows XP *For Solaris 9, you should install the appropriate Solaris Patch Cluster. |
| Application Server | Sun Java System Application Server 9.0 PE or equivalent application server available from Project GlassFish |
| Java 2 Platform, Standard Edition (J2SE) |
J2SE 5
If you are using the JAVA_HOME environment variable, it should point to a Java 2 Platform, Standard Edition 5 (J2SE 5) installation. If you are not using the JAVA_HOME environment variable, the PATH environment variable should contain the location of the Java Runtime Environment 5 (JRE 5). |
| Memory |
60 MB disk space
Recommend 512 MB or greater RAM Disk space includes space required to download, unzip, and install Open ESB. |
Open ESB contains the following sample components that are part of the JBI Reference Implementation:
File Binding (component name SunFileBinding)
Sequencing Engine (component name SunSequencingEngine)
Transformation Engine (component name SunTransformationEngine)
For Open ESB, the sample components have been updated to support both WSDL 1.1 and WSDL 2.0 deployments. In addition, this build includes these components:
JMS Binding (component name SunJMSBinding)
Proxy Binding (this is an internal ESB-only component)
ESB BPEL Engine (component name com.sun.bpelse-1.0-2)
This component requires the Java 2 Platform, Standard Edition 5.0 (J2SETM 5.0 platform)
A GUI-based installer is provided with Open ESB.
The ESB Central Administration Server (CAS) provides:
Ant-based administration tasks are provided. Using Ant you can:
The ESB Administration Console (web console) is in the early stages of development. Many of its features have not yet been implemented or are not fully functional. The console included in this build demonstrates what the console will look like and the type of functionality it will offer.
Some features are available on the Deployments, Components, and Instances tabs. Features accessed from the Overview tab (monitoring and alarms) are not yet available. Online help for the web console is also in the early stages of development.
The CLI-based administration tools are not yet complete even though it is provided in this release. They are not fully functional and should not be used.
This build contains two samples, with accompanying documentation: the JBI Demo sample and the BPEL service engine sample.
The JBI Demo sample is an updated version of the Quickstart sample that was provided with previous builds. The JBI Demo illustrates a basic single-instance JBI system.
The BPEL service engine example is the same example provided previously. The BPEL service engine example contains five BPEL sample projects that demonstrate basic use of the BPEL service engine with the HTTP SOAP binding component. The documentation for the BPEL service engine example is an updated version of the BPEL service engine Readme provided with a previous build.
The following issues have been identified for Build060512_3. If you discover any other issues with this release, please report them using the IssueTracker link, available after you log in to Project Open ESB. The IssueTracker might also contain other issues that have become known after the publication of these release notes.
| ID | Description / Workaround |
|---|---|
| – |
BPEL SE Sample Error Message: System cannot find specified files
Workaround: If you see error messages which include: "... The system cannot find the file specified," you might be able to avoid or correct this problem by first running the batch setup file asenv.bat.
|
| – |
Avoid trailing whitespace when specifying username in BPEL SE Sample.
Workaround: When setting the build and samples properties for jbi.username in jbi-install-root/samples/build.properties, whitespace after the username value is included in the username string. This may cause unanticipated results. If you experience difficulty, please check for any trailing whitespace following the username value and remove it if found.
|
| 6294216 |
Classloader memory leak causing java.lang.OutOfMemoryError: PermGen space errors
Workaround: Increase the Permanent Generation space to 128 MB (or more if necessary). To do this for the application server, use the create-jvm-options asadmin command. For example: asadmin create-jvm-options --user admin --port 12345 \
|
| 6362147 |
Installer fails if user incorrectly supplies the domain master password.
Workaround: If the application server domain was created without a master password, do not provide a master password during installation. Otherwise, make sure you supply the correct master password during installation. |
| 6384305 |
How to remove jbi from registry after manual delete of installed jbi bits is not documented.
Workaround: If an Open ESB installation was manually deleted without using the uninstaller, select a new location when reinstalling Open ESB. If you plan to use the same location, then edit the product registry file, removing all Open ESB related entries. The product registry file is located at: Windows: %SYSTEM_DIR%/system32
Linux: /var/tmp
Solaris Root: /var/sadm/install
|
| 6394860 |
HTTP SOAP binding component cannot accept connections through a firewall.
Workaround: Configure the proxyHost and proxyPort java properties using the application server Administration Console. Click on Application Server in the tree\JVM settings\JVM options. Select Add JVM Option to add two entries: -Dhttp.proxyHost=myProxyServer.com
The proxy might also require authentication/authorization. The HTTP SOAP BC does not have this feature (setting the HTTP property, Proxy-Authorization, with a base 64 encoded username:password) in this release. |
| 6404366 |
When deploying a service assembly containing multiple SUs targeted at a single component, the DeploymentService only processes one SU for that component.
Workaround: Limit service assembly archives to one service unit per targeted component. To deploy multiple service units to a given component, create a service assembly for each service unit targeted at that component. |
| 6408335 |
BPEL sample application files, build-test.bat and run-test.bat, are not in UNIX format.
Workaround: On UNIX platforms, run the commands as documented in the sample documentation:
|
| 6416176 |
Stopping a component when a non-CAS domain has previously been shutdown causes a lifecycle error
Workaround: This bug is only encountered when the component autostart feature is enabled. By default, the installer disables the framework autostart feature. To disable the autostart feature manually, set the framework autostart property as follows: <property name="com.sun.jbi.framework.ComponentStartup" value="NONE"/> |
| 6418234 |
When you start, stop, or shutdown components with a bad port number or bad hostname, the installation fails, throwing an exception
Workaround: Make sure you specify port numbers and hostnames correctly when administering JBI components. |
| 6418627 |
BPEL samples do not run if the application server install path or the path to J2SE installation contains spaces (Windows only)
Workaround: Make sure application server install path and the path to J2SE installation do not contain spaces. |
| 6419312 |
User modification required for build.properties. Before running the BPEL SE Demo, user must update build.properties file to update some settings and variables.
Workaround: User needs to change settings such as jdk.home and other variables so that they point to the correct location. A variable should not refer to another variable. For example, do NOT specify: jdk.home=${appserver.home}/jdk). Instead, specify the complete path. |
| 6420963 |
If you restart a component that has previously been started, list-binding-components is unreliable
Workaround: This bug is only encountered when the component autostart feature is enabled. By default, the installer disables the framework autostart feature. To disable the autostart feature manually, set the framework autostart property as follows: <property name="com.sun.jbi.framework.ComponentStartup" value="NONE"/> |
| 6424643 |
Unable to uninstall a JBI component from a CAS instance. When Open ESB is setup in multi-instance mode, there are issues with uninstalling components from CAS.
Workaround: This bug is only encountered when the component autostart feature is enabled. By default, the installer disables the framework autostart feature. To disable the autostart feature manually, set the framework autostart property as follows: <property name="com.sun.jbi.framework.ComponentStartup" value="NONE"/> |
Copyright 2006, Sun Microsystems, Inc.