The Client Management Server has the ability to attempt to notify a client that it has an active task waiting.
Because of the many possible configurations of the Expeditor Client, there is only a proof of concept implementation included with the Expeditor Client and the Client Management server. This implementation uses the Web container on the client to host a servlet that the server uses to notify the client that it has work to do. For a more robust solution to client notification, you should consider creating an alternative notification method that supports your environment.
Notification tasks: XPD622
When you create a task, there is a Notify clients on task creation
check box. If this is selected, the task is considered when the notification process runs.
Automatic task expiration: XPD622
Normally, a task's status will become expired at the expiration time set in the task. For tasks that use notification it is possible for the server to modify the task status prior to the expiration time set in the task.
Replacing the default notification implementation: XPD622
The Expeditor Client and Client Management server include default proof-of-concept implementations for client notification. The notification implementations can be replaced by more robust implementations that better comply with your network and security requirements.
Enabling notification: XPD622
The server side client notification handler is enabled by default. The default client notification implementation is part for the Enterprise Management Agent Notification servlet. The Enterprise Management Agent Notification servlet provides an OSGi HTTP POST notification handler for supported Client Management server real-time notifications of OSGi device agents.
Parent topic: Managing with a Client Management server: XPD622