JavaTM Platform, Enterprise Edition (Java EE) 5 Technologies

Enabling JBI Runtime with BPEL Support
for the Java EE 5 SDK Update 1 and Update 2 Bundles

Copyright © 2006 Sun Microsystems, Inc. All rights reserved.

This document contains the instructions to enable the JBI runtime with BPEL support that is provided with the Java EE 5 SDK Update 1 and Update 2.


Enabling JBI Runtime in the Java EE 5 SDK Update 1 and Update 2


When you install the Java Platform, Enterprise Edition 5 (Java EE 5) SDK Update 1 or Update 2 , the installer also installs Project Open ESB Starter Kit. Open ESB Starter Kit includes JBI Runtime with BPEL Support, however this feature is disabled by default.

Before you can use JBI Runtime with BPEL Support, you must first enable this feature, as described in the following procedure. You can enable the JBI runtime using either the Administration Console or the command line.

To Enable JBI Runtime with BPEL Support:


Note: The following instructions assume you have configured the Application Server to store the admin user password in a password file. If you do not store the admin password in an admin file, you will be prompted for the password during the procedure.

  1. Make sure the application server is running:

    asadmin start-domain [domain-name]

  2. Enable the JBIFramework life cycle module using either the Admin Console or the command line:

    From the Admin Console:

    1. Log in to the Application Server Admin Console

      Typically, you access the Admin Console at:

      http://localhost:4848

      Your administration port number might differ from the default.

    2. Navigate to Applications | Lifecycle Modules.

    3. Under Lifecycle Modules, click the JBIFramework link.

    4. Select the Enabled toggle indicating the Status of the lifecycle module, and then click Save.

    5. Restart the Application Server.


    From the command line, issue the following command:

    asadmin enable --user <admin user> JBIFramework

    Note: Other options might be required depending on your Application Server configuration.

  3. Restart the application server:

    asadmin stop-domain [domain-name]
    asadmin start-domain [domain-name]