Develop > Presentation layer > Customize IBM Sales Center > Deploy customizations to the IBM Sales Center > Post deployment provisioning mechanisms
Use IBM Tivoli Device Management Server
Workplace Managed Client includes an Enterprise Management Agent that can be used in conjunction with a Tivoli Device Management Server to install, upgrade, and configure applications running in the WED4WL client. The Agent and Server can also manage other aspects of the client machine, such as installing or upgrading native applications, or manipulating the contents of the Windows registry.
WED4WL documentation discusses an installation option Install as service. This installs a copy of WED4WL that runs as a Windows service, and does not expose a graphical user interface. It is useful when only the Enterprise Management Agent functionality manages the client system, but is not a suitable platform for supporting applications like Websphere Commerce Sales Center. Do not choose this installation option.
Tivoli Device Management Server is not supplied with Websphere Commerce, but is a component of several IBM products that may be separately acquired. The Enterprise Management Agent in WED4WL requires a Device Management Server version 1.8 or later. An appropriate DMS is available in the IBM products Websphere Everyplace Deployment v6 and Websphere Everyplace Device Manager v6.
For information about installing and configuring DMS, and on the full set of capabilities it provides, see the documentation supplied with the product that supplies it. Here we will assume the server is already configured and the objective is to use it to install or uninstall Eclipse features into a WED4WL runtime.
The Device Management Server is capable of executing a number of different types of management operations on a variety of different device types. In DMS terms, distribution of Websphere Commerce Sales Center or of customized Eclipse features to install on a WED4WL Windows XP client uses a native software distribution job targeting a Windows 32-bit device. Windows 32-bit devices are a subset of OSGi devices, which in turn are a type of BaseOMA DM device.
To distribute software to the client platform, we will use the NativeAppBundle tool provided as part of the Device Management Server distribution to wrap the Eclipse update site in an OSGi bundle. You will then create and schedule a Software Distribution job targeting the client. When the created bundle is received on the client by the Agent, it programmatically invokes the Eclipse Update Manager to install the features packaged in the update site.
Prerequisites
Procedure
- DMS installed and configured on a server whose port 80 is accessible from the client. Websphere Application Server security must be enabled on the DMS server. Although the Device Manager installation guide indicates that enabling security is optional, security is mandatory to correctly support Windows 32-bit devices.
- WED4WL is installed on the client, either using the WED4WL installer, or the Sales Center Quick Install. This post-deployment option is currently not supported for production install by client imaging.
Results
This example is broken into five tasks:
- Using IBM Tivoli Device Management Server: Enable Enterprise Management Agent
- Using IBM Tivoli Device Management Server: Create an Eclipse NativeAppBundle
- Using IBM Tivoli Device Management Server: Registering the NativeAppBundle with the Device Management Server
- Using IBM Tivoli Device Management Server: Scheduling a software distribution job
- Using IBM Tivoli Device Management Server: Uninstallation using a Bundle Control Job
- Using IBM Tivoli Device Management Server: Enable Enterprise Management Agent
- Using IBM Tivoli Device Management Server: Create an Eclipse NativeAppBundle
- Using IBM Tivoli Device Management Server: Registering the NativeAppBundle with the Device Management Server
- Using IBM Tivoli Device Management Server: Scheduling a software distribution job
- Using IBM Tivoli Device Management Server: Uninstallation using a Bundle Control Job
Related concepts
Deploy customizations to the IBM Sales Center
Post deployment provisioning mechanisms
Related tasks
Use IBM Tivoli Device Management Server: Enable Enterprise Management Agent
Use IBM Tivoli Device Management Server: Create an Eclipse NativeAppBundle
Use IBM Tivoli Device Management Server: Scheduling a software distribution job
Use IBM Tivoli Device Management Server: Uninstallation using a Bundle Control Job