Before deploying SAP mobile business objects that use result checker classes, copy the compiled classes to <Unwired-Server-install>\lib\filters\<packageName> on the primary Unwired Server machine.
You can also place result checker classes into a directory structure; the root of which should start at packageName. During cluster synchronization, the SAP result checker classes are automatically distributed to other Unwired Servers in the cluster.
-
(Optional) To maintain and deploy a single file, create a Java archive of all your classes.
-
Choose the Unwired Server target location for the result checker classes, dependencies, and third-party JARs:
- To avoid restarting Unwired Server, copy either the JAR file or the individual class files to:
<Unwired-Server-install>\lib\filters\<DeploymentPackageName>.
For example, if you have a ResultChecker_1.0.0 package and a com.acme.filters.ResultChecker result checker class, create <Unwired-Server-install>\lib\filters\ResultChecker_1.0.0\com\acme\filters\ResultChecker.class. Or, create acmeFilters.jar from the com.acme.filters.ResultChecker classes, and copy it to <Unwired-Server-install>\lib\filters\ResultChecker_1.0.0\acmeFilters.jar.
- To restart Unwired Server after deployment, copy the classes to:
<Unwired-Server-install>\lib\filters\.
-
Deploy the SAP mobile business object to Unwired Server.