The bundle loader is an OSGi bundle that, when started, locates a list of bundles and performs the action specified on each bundle in the list.
The bundle list is a script in which each line is a command to the bundle loader to perform an action on a specified bundle. The actions that can be performed include START and INSTALL. The START action installs and starts a bundle, while the INSTALL action only installs a bundle. After the action command is the path to the bundle on which to perform the action.
The bundle list can contain the PREFIX command as well. When this is used, the string that follows PREFIX will be prepended to the name of each bundle in the bundle list.
The bundle list also supports the INCLUDE command. The INCLUDE command points to another bundle list that will also be read by the bundle loader.
This is an example of the file format:
// The line below will look for this exact file name START org.eclipse.osgi.services_3.1.200.v20070605.jar // The line below will look for a file beginning with this // (assuming wildcarding is enabled on WebSphere Premises Server) START org.eclipse.osgi.services_
When the bundle loader starts, it looks in three locations for the bundle list URL:
After successfully receiving the bundle list, the bundle loader runs the commands in the list to install the bundles. This process is stored in the ConfigAdmin object as a result property (for example, value="working"). After this task is completed, the bundle loader saves the final result (as a success or a failure) in the result property. Then, when the bundle loader is restarted or when the configuration changes, the bundle loader looks in the result value to determine if it should download additional bundles.
Use these steps to install the bundle loader and a bundle list. For reference, see the tools/remoteDC.zip sample packaged with the IBM® Data Capture and Delivery Toolkit for WebSphere® Premises Server.