GlassFish ESB v2.1 AMI for EC2

June 23, 2009

Now GlassFish ESB v2.1 is available via Amazon Elastic Compute Cloud ( Amazon EC2 ). To help easily build and secure cloud applications, the GlassFish ESB v2.1 AMI is created on hardened opensolaris .

This AMI is installed only with runtime component of the GlassFish ESB v2.1 ie. GlassFish 2.1 server + jbi components, with default configurations, for details on port numbers & credentials check the /root/ec2sun/GFESBV21_README. The applications created using the designtime component of the GlassFish ESB v2.1 can be deployed in the EC2 instance using admin console. Port ‘4848’ has to be opened in EC2 instance to access the admin console.

AMI ID: ami-5347a13a

AMI Manifest: opensolaris-2008.11-gfesb-v2.1.img.manifest.xml


Sun includes GlassFish ESB in GlassFish Portfolio

February 10, 2009

Sun Microsystems announced the release of Sun GlassFish Portfolio, the open source Web platform based on GlassFish. Built on open source projects including Apache Tomcat, Ruby, PHP, Liferay Portal, OpenESB and GlassFish, the Sun GlassFish Portfolio packages these components into an open source platform with range of support and services options, from basic patch services to 24×7 mission critical support.

Why the announcement is significant for GlassFish ESB and OpenESB project?

With today’s announcement of the GlassFish Portfolio, Sun Microsystems has also announced the commercial support options for GlassFish ESB (or Sun GlassFish Enterprise Service Bus), including a pricelist. For many companies not withstanding the effort in the community, it’s a requirement to have commercial support before considering using an open source product. So with today’s announcement, we should see an acceleration in OpenESB adoption, and as a consequence, also in OpenESB development! Good news for OpenESB!!!

The GlassFish Portfolio includes the GlassFish Application Server along with other components. To view the entire list go here.

Using DataMashup with DataDirect driver

December 15, 2008

I elaborate here the steps on configuring the netbeans ( designtime ) and appserver ( runtime ) to use the datadirect driver which in turn can be utilized by the DataMashup Service Engine ( edmse ).

Note: For creating and running an end-to-end datamashup project, refer here.

Note: If you are using GlassFishESB, the DD drivers has to be purchased by you individually. If you are using JavaCAPS6, you can find the DD drivers for oracle at ‘<JavaCAPS6 home>\.netbeans\caps\modules\ext\oracleadapter’. Though please remember datamashupSE is not part of JavaCAPS6 and its new component shipped along with GlassFishESB and JavaCAPS6 update 1 releases.

Configuring Netbeans (Designtime):

Adding New Driver:

  1. Goto NB, Services -> Databases -> Drivers -> New Driver, click on ‘Add’ and navigate to the folder ‘<JavaCAPS6U1 home>\.netbeans\caps\modules\ext\oracleadapter’.
  2. Add all the files from the folder and click on ‘Find’
  3. Select ‘’ which appears in the drop down list
  4. Give a name ‘DD37’ and finish.

Adding New Connection:

  1. Click on the driver ‘DD37’ and select connect using.
  2. Provide the connection details as shown in the image below and close.

Configuring GlassFish ( Runtime ):

  1. Copy the driver files from ‘<JavaCAPSR6U1 home>\.netbeans\caps\modules\ext\oracleadapter’ to ‘<JavaCAPS6U1 home>\appserver\domains\domain1\lib\ext’. Restart the appserver.
  2. Logon to the appserver admin console.
  3. Goto Resource -> JDBC -> Connection Pools, create an new connection pool with following values,
    Name: oracledd37pool
    Resource type: javax.sql.DataSource
    Database Vendor: Oracle
    Datasource Classname:
  4. Add the following properties in Additional properties,
    SID : orcl11
    User: qajbi_shared
    password: < password for db >
    portNumber: 1522
    URL: jdbc:SeeBeyond:oracle://ieccaps10:1522;SID=orcl11
  5. Save the configuration and test the connection by clicking on ‘Ping’.
  6. Goto Resource -> JDBC -> JDBC Resources, and create a new jdbc resource with the following values,
    JNDI Name: jdbc/OracleDD37pool
    pool name: oracledd37pool  ## select the connection pool created in step 3

Configuring DataMashup SE and Project to use the datadirect connection pool in runtime:

  • Open the casa editor, and provide a application configuration name for edm interface as shown in the image below, ( any name can be used )
  • Save and build the Composite App.

    • Goto Services -> Servers -> GlassFish V2 -> JBI -> Service Engines -> sun-edm-engine and open the properties

    • Click on the button ‘…’ on the right end of Application configuration.

    • Provide the name of the application configuration as same as what is given in the casa editor. In this case it is ‘OraOraViewXmlJbi’,
    • And the resource name as created in the application server. In this case it is ‘jdbc/OracleDD37pool’, as shown below,

    • Deploy and run the project.

    GlassFish ESB

    September 14, 2008

    Its a milestone event for OpenESB and milestone 1 for GlassFish ESB.

    The Open Source ESB for Integration & SOA, with commercial support by Sun Microsystems

    GlassFish ESB is a binary distribution of OpenESB. It consists of subset of the components in OpenESB. Sun will provide commercial support for GlassFish ESB. With this, a big obstacle in the adoption of OpenESB has been removed! Click on the image to download GlassFish ESB. For more information, see

    Rise of CEP in OpenESB

    August 18, 2008

    Most people associate Open ESB with enabling SOA. While thats true, only a few people know that Open ESB also enables Event-Driven Architectures (EDA)! The Intelligent Event Processor, or IEP is the component that does this. IEP is an open source Complex Event Processing (CEP) and Event Stream Processing (ESP) engine. Go check it out"