Installation - Installing as an NT Service

Veduta can be installed as an NT service. This permits Veduta to start automatically on server startup.

The Veduta NT service configuration files will only be installed if the Windows Service option was chosen during the installation.

We recommend understanding the basics of running and configuring Veduta before configuring Veduta as an NT service. The below assumes some basic knowledge of running Veduta.

Configuring Veduta as an NT Service

Normally Veduta is configured via command-line options. When running as an NT service, these configuration options are specified in a configuration file conf\wrapper.conf. This configuration specifies which Java virtual machine to run, the Veduta command-line configurations, and various Java-specific configurations. When run as a service, Veduta is pre-configured to run in client/server mode.

To configure Veduta command-line options, edit the below lines in conf\wrapper.conf:

wrapper.app.parameter.1=com.oopsconsultancy.veduta.main.Veduta
wrapper.app.parameter.2=-webserver
wrapper.app.parameter.3=-d
wrapper.app.parameter.4=examples\servlet

The first line must remain the same. Each following line represents a command line argument, and are numbered sequentially. The above is equivalent to running Veduta thus:

> java -jar veduta-complete.jar -webserver -d examples\servlet

Veduta can require a memory configuration on the server side. The configuration line:

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=512

is equivalent to running Veduta thus:

> java -Xmx512m ...

By default, the configured service will pick up whichever Java is on the PATH. To change the Java version being used, specify:

# Java Application
wrapper.java.command=%JAVA_HOME%\bin\java

to (for example) pick up the Java VM referenced by %JAVA_HOME%

Check your configuration changes by running Veduta as:

> bin\VedutaService.bat

This runs Veduta from the command line using the same configuration as it will use when run as a service. You should see output similar to:

C:\Program Files\OOPS Consultancy\Veduta>bin\VedutaService.bat
wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
jvm 1    | Wrapper (Version 3.2.1) http://wrapper.tanukisoftware.org
jvm 1    |
jvm 1    | Using standard logging (-Djava.util.logging.config.file={filename} to override)
jvm 1    | Veduta 1.0.4beta TRIAL VERSION EXPIRES Tue Nov 14 00:00:00 GMT 2006
jvm 1    | 14-Oct-2006 17:44:54 INFO: Enabled housekeeping. Deleting entries older than 14 day(s)
jvm 1    | 14-Oct-2006 17:44:55 INFO: Log db update : in-memory db started
jvm 1    | 14-Oct-2006 17:44:56 INFO: Running as a server : rmi://localhost:1098/VedutaServer

Installing and Running Veduta as an NT Service

Once configured as above, install as an NT service by running:

    > bin\InstallVedutaService.bat

Veduta will be visible in the Services browser:

Veduta will be configured to start automatically. This and other service attributes can be configured in the conf\wrapper.conf or via the Services browser. Veduta can be controlled via the Services browser or via the standard NT service command line controls:

    > net start Veduta
    > net stop Veduta

Service logs are available in the veduta-service.log file in the Veduta installation directory. This is configurable from the conf\wrapper.conf configuration.

For more service configuration options, or troubleshooting the service configuration, see the Java Service Wrapper home page.

Installation - Basic Installation Getting Started - Configuring