Network Deployment (Distributed operating systems), v8.0 > Reference > Troubleshoot tips > Troubleshoot OSGi applications


Migrate and coexisting for OSGi applications

No special steps are required to migrate from the OSGi Applications Feature Pack in WAS v7 to the current version. Enhancements made since Version 7 can affect how you configure your OSGi applications, particularly for working in mixed cells.

To migrate your OSGi applications and associated configuration from v7, follow the platform-specific instructions given in the "Migrating, coexisting, and interoperating" section of the information center. When you reach the point in the migration process when you run the WASPostUpgrade command (with the includeApps parameter set to TRUE), the following resources are migrated to the current version of the product:

After we have migrated the configuration, or if you want to run OSGi applications on v7 nodes in mixed cells, you will find it useful to understand the main enhancements made since Version 7, and the implication of those enhancements for using the applications with different versions of the application server:


Main enhancements made since Version 7


Current version enhanced support for Version 7 nodes

In a mixed cell, the current version provides the following enhancements to help support the v7 nodes:


Version-related considerations for composite bundles

A composite bundle cannot be used by an application running on a v7 server if any of the following conditions apply:


Version-related considerations for application types

The following types of OSGi application cannot run on a v7 server:


Other version-related considerations

OSGi applications that can run on v7 nodes are also supported on v8 nodes. When you import an application written for Version 7 into a cell that includes v7 nodes, the runtime environment automatically provides the extra support needed to host the application on all the nodes in the cell. However, if you import an application written for v7 into a cell that has no v7 nodes, the runtime environment assumes that you are importing a current version application and the application might not run.

To solve this problem, add a v7 node to the cell and then reimport the application.

If an application is running on a cluster, and the application cannot run on a v7 node, the system will not allow you to add a Version 7 node to the cluster.

If we have a WAS v7 node that is 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, 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. See An existing v7 application server augmented with the OSGi Applications feature cannot be federated into a v8 Deployment Manager.

sep2011

Related concepts:

About OSGi Applications

Related tasks:

Secure OSGi Applications

Related reference:

OSGi Applications: Troubleshooting tips
OSGi Applications: Known restrictions
Reference topic Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.

+

Search Tips   |   Advanced Search