Page History

Registers services that each component within the bundle exposes if all required service dependencies are available. For each component, at the very least a component service is registered

Stops all services registered by the component.

Updates the plugin to a newer version. If a problem is encountered during the update, the plugin is automatically rolled back to the existing version. The following describes a typical plugin update scenario:

1. The plugin developer creates a 1.1 version of a plugin and gives it to a system administrator.
2. The system administrator copies the updated plugin to the machine running XperienCentral. If XperienCentral is running in a clustered environment, the updated plugin is copied to the machine running the read/write node XperienCentral instance.
3. The system administrator determines the ID of the plugin in the Apache Felix Gogo shell.
4. The system administrator executes the wmupdate method, specifying the ID of the plugin to update and the absolute path of the JAR file containing the updated plugin. For example:

wmupdate 59 file:/home/deploy/helloworld_1_1.jar


5. The plugin is updated to the new version and is set to the active state. In a clustered environment, the plugin is also automatically updated on all slave instancesread-only nodes.

Removes all content that was created during and after the installation of the component.