Maintaining an OSGi composition unit
Whenever an enterprise bundle archive (EBA) asset is updated, we can (optionally) update the associated composition unit. We might also update a composition unit to add or remove a composite bundle extension. If any updates need configuration changes, we can also modify the configuration information for the composition unit.
An OSGi composition unit consists of an EBA asset, (optionally) one or more composite bundle extensions, and configuration information for running the asset and composite bundle extensions in a business-level application. If a new OSGi application deployment is available, we can update the OSGi composition unit so that the business-level application uses the newer configuration.
If any updates need configuration changes, we can also modify the configuration information for the composition unit. The configuration information can include HTTP session management, context roots, virtual hosts, security roles, run-as roles, JNDI mappings for Session enterprise beans, JNDI mappings for EJB references, and web application or Blueprint resource reference bindings for our OSGi application.
Tasks
- Add or remove composite bundle extensions for an OSGi composition unit
Use either of the following methods:
- Add or remove composite bundle extensions .
- Add or remove composite bundle extensions using wsadmin commands.
- Update an OSGi composition unit.
Use either of the following methods:
When all bundle downloads are complete, we can update the OSGi composition unit so that the business-level application uses the newer configuration. If any of the updates contain configuration options, you update the configuration information. We can also take the opportunity to make additional, non-essential configuration changes.
- Modify the configuration of an OSGi composition unit.
We can modify the configuration information for an OSGi composition unit at any time using either of the following methods:
- Modify the configuration of an OSGi composition unit using the administrative console.
- Modify the configuration of an OSGi composition unit using wsadmin commands.
When we save the changes to the composition unit, the associated business-level application is updated to use the new configuration. If the business-level application is running, the bundle and configuration updates are applied immediately.
If possible (that is, depending on the nature of the updates) the system applies the updates without restarting the application. If we update a bundle that provides only OSGi services to the rest of the application, then only that bundle is restarted. If we update a bundle that provides one or more packages to other bundles, then those bundles and any bundles to which they provide packages are restarted. If, however, a new package or service dependency is added, or an existing package or service dependency is removed, then the application is restarted; a newly added package and service can come from a newly-provisioned bundle, or from a bundle that has already been provisioned.
Subtopics
- Update an OSGi composition unit
If a new OSGi application deployment is available, we can update the OSGi composition unit so that the business-level application uses the newer configuration. If any of the updates contain configuration options, a wizard prompts you to update the configuration information.- Add or removing extensions for an OSGi composition unit
Add composite bundle extensions to, or remove them from, a composition unit containing an enterprise OSGi application.- Modify the configuration of an OSGi composition unit
We can modify the configuration information for a composition unit containing an enterprise OSGi application. An OSGi composition unit consists of an EBA asset, (optionally) one or more composite bundle extensions, and configuration information for running the asset and composite bundle extensions in a business-level application. The configuration information can include HTTP session management, context roots, virtual hosts, security roles, run-as roles, JNDI mappings for Session enterprise beans, JNDI mappings for EJB references, and web application or Blueprint resource reference bindings for our OSGi application.
Update bundle versions for an EBA asset Checking the bundle download status of an EBA asset Checking the update status of an OSGi composition unit Administer bundle repositories Exporting and importing a deployment manifest file
File name: was2972.html
prettyPrint();