Deploying Custom Filters to Unwired Server

Before deploying mobile business objects that use custom filter classes, you must copy the filter classes to the Unwired Server.

Prerequisites

Design-time: The filter classes must exist and be installed in the Tooling API, for example, as a jar in the Tooling API's lib\filters folder.
Runtime: Before deploying mobile business objects that use custom filter classes, you must copy the filter classes to the Unwired Server.

If your Unwired Servers are running in a cluster, you must copy the filter classes to the "primary" server in the cluster. From Sybase Control Center, you can identify which server is the current primary on the left-hand panel that lists your Unwired Servers.

Choose the target location for the filter classes and their dependency/third-party .JARs on the Unwired Server:
- To avoid having to restart Unwired Server, copy the filter classes, either in a .JAR file or the tree of filter classes, to:
  <Unwired-Server-install>\lib\filters\<DeploymentPackageName>
  
  For example, if you have a FilterTest_1.0.0 package with a filter called com.acme.filters.TestFilter, you would create a <Unwired-Server-install>\lib\filters\FilterTest_1.0.0\com\acme\filters\TestFilter.class directory. Or, you can jar up the com.acme.filters.TestFilter class into a acmeFilters.jar file and copy it to <Unwired-Server-install>\lib\filters\FilterTest_1.0.0\acmeFilters.jar.
- To restart Unwired Server post-deployment, copy the filter classes to:
  <Unwired-Server-install>\lib\filters\
Deploy the mobile business object to the Unwired Server.
The custom classloader for FilterTest_1.0.0. is refreshed during deployment so there is no need to restart Unwired Server.