• Print  |
  • Feedback  |

FOCUS AREAS

Developer Resources

Products

Technologies

API Reference

SAS AppDev Studio 3.0 Developer's Site

Middleware Server: Client Deployment Issues

Projects that use MWS should define the location of any JAR or class files that need to be deployed to a client machine. Specifically, MWS searches for deployable JAR and class files in the following order:

  1. the \ext (extensions) directory of the JRE
  2. the CLASSPATH directories
  3. the default directory of the MWS Class Loader.

The MWS Class Loader loads application-specific JAR and class files into a run-time environment.

When you start MWS from AppDev Studio software, the default directory that the MWS Class Loader scans for JAR and class files is \install-directory\Java\SAS\MWS (where install-directory is the directory in which AppDev Studio was installed). To change the default location that the MWS Class Loader scans for JAR and class files, follow these steps:

  1. Open the MiddleWare.cfg configuration file. This file is typically available in \install-directory\Java\SAS (where install-directory is the directory in which AppDev Studio was installed).

  2. Add or edit the -Dmws.class.path=<directory name> parameter.

When you run MWS on a server, the MWS Class Loader directory must be created by the server administrator. If MWS is run as a service on the server, follow the steps above to specify the JAR and class file location. If MWS is run using the startmws script, edit the -Dmws.class.path=<directory name> parameter in the Java command. For more information on the startmws script, see Using Middleware Server.

If you have used specific webAF wizards (for example, the InformationBean Wizard or the Package Wizard) to create any JAR or class files that need to be deployed to a client machine, you must copy those JAR or class files to the current MWS Class Loader directory.