You can automatically convert an enterprise archive (EAR)
file that contains web application archive (WAR) files to an enterprise
bundle archive (EBA) file.
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
- Rename the EAR file (.ear) to an EBA
file (.eba).
- In WebSphere® Application
Server, import the EBA file as an asset.
- Optional: Modify any migrated Java™ 2 security settings.
When you migrate 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.