Migrate OSGi applications
This page provides a starting point for finding out how to migrate from the OSGi Applications Feature Pack in WAS v7, and how to use OSGi applications with different versions of the product.
For transitioning users: If we have a WAS v7
node that is augmented with the Feature Pack for OSGi Applications and JPA 2.0, and you federate the node into a WAS v8
cell, the addNode command does not succeed. This problem occurs only when you try to federate a v7 node that has already been augmented with either the OSGi applications feature or the JPA 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0 prior to Fix Pack 5. The solution is to augment your v7 node with Fix Pack 5, or later, of the Feature Pack for OSGi Applications and Java Persistence API 2.0. See the troubleshooting tip
An existing v7 application server augmented with the OSGi Applications feature cannot be federated into a v8
Deployment Manager.trns
For transitioning users:
- In the WAS v7 Feature Pack for OSGi Applications and Java Persistence API 2.0, when you add a composite bundle to the internal bundle repository, and that composite bundle directly contains bundles (in compressed files in the root directory of the composite bundle archive file), those bundles are added to the internal bundle repository both as part of the composite bundle and as individually-available bundles. If you subsequently delete the composite bundle from the repository, the individually-available copies of the bundles are not deleted. You might have used this mechanism as a convenient way to upload sets of bundles to the repository.
- In the current version, when you add to the repository a composite bundle that directly contains bundles, those bundles are not also added individually. To add sets of bundles to the repository, you package each set as a compressed archive file with a .zip file extension, then add the archive file to the repository. The system expands the file, and all the bundles in its root directory are added individually to the repository.
trns
Migrate and coexisting for OSGi applications