Converting an enterprise application to an OSGi application

You can automatically convert an enterprise archive (EAR) file that contains web application archive (WAR) files to an enterprise bundle archive (EBA) file.

Before you begin

Ensure that the enterprise application is suitable for conversion to an OSGi application. Check whether any manual conversion steps are required first. See Conversion of an enterprise application to an OSGi application.

About this task

You can automatically convert a web application to an OSGi application, that is, you can convert an EAR file that contains only WAR files. For other enterprise applications, you might require manual migration steps before you use the following procedure.

Procedure

  1. Rename the EAR file (.ear) to an EBA file (.eba).
  2. In WebSphere® Application Server, import the EBA file as an asset.
  3. Optional: Modify any converted Java™ 2 security settings.

    When you convert an application from Java EE to OSGi, any existing was.policy file is converted into a permissions.perm file to be used with the OSGi permissions framework, and all permissions are promoted to the application level. If you need finer granularity, you can modify the file after conversion. For more information, see Java 2 security and OSGi Applications.

Results

The WAR files are automatically converted to web application bundles (WABs). Any Java 2 security was.policy file is converted into a permissions.perm file. Any Utility JAR or EJB JAR files are not converted and the EJB function is not directly accessible in the EJB container.

Icon that indicates the type of topic Task topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Tuesday, 19 June 2012
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=ta_mig_ejb
File name: ta_mig_ejb.html