Installing and Running Foundation Services as a Windows Service

Configuring the Java Service Wrapper

When you install SAS Foundation Services, a master wrapper.conf file is created in your SASHOME directory. Additional application-specific wrapper.conf files are created for any programs that use the Java Service Wrapper.

In most cases, you can use the default wrapper.conf files without making any changes. Instead, you can use command-line arguments in the executable scripts to override the configuration settings. The wrapper.conf file contains the following configuration directives:

wrapper.java.command: specifies the fully qualified path to java.exe.
wrapper.java.mainclass: specifies the name of the class that will be instantiated by wrapper.exe. This class must contain a main method and must implement WrapperListener. In the sample configuration file wrapper.conf, this directive specifies a class called com.sas.services.deployment.servicewrapper.ServiceWrapperImpl, which is provided with SAS Foundation Services. When this class is instantiated by wrapper.exe, it registers itself as an event listener and takes action whenever the native wrapper signals an event. For more information, see the class documentation at http://support.sas.com/92api.
wrapper.java.classpath1: specifies the location of the java archives that you want to load.
wrapper.app.parameter.1: specifies the metadata source configuration file, which specifies the location of the deployment configuration for remote foundation services.
wrapper.java.library.path: specifies the location of the wrapper.dll or wrapper.so file.
wrapper.java.additional.1: specifies additional java parameters.

Setting a Dependency for the Metadata Server Service

If your deployment metadata is stored in a SAS Metadata Repository, and the SAS Metadata Server has been installed as a service on the same machine as the SAS Services application, then you need to specify a service dependency to ensure that the services start in the correct order. You can specify the service dependency by adding the following line to wrapper.conf :

wrapper.ntservice.dependency.1=Metadata-Service-Name

Changing Timeout Intervals

If the Java Service Wrapper is timing out while starting up or shutting down, it might be necessary to increase the timeout intervals from the default values. Add the following parameters to wrapper.conf as appropriate.

wrapper.startup.timeout: specifies the startup timeout interval in seconds. The default value is 30.
wrapper.shutdown.timeout: specifies the shutdown timeout interval in seconds. The default value is 30.

Top of Page