Task 4.6 Configuring Startup Mode for the Standalone Execution Server

A Standalone execution server can be launched in two modes: Automated and Manual. In the automated mode, it's installed and running as a Windows service on Windows, or as a daemon on UNIX. In manual mode, a user starts the execution server as an application. This section includes details on configuring and launching execution server.

Task 4.6.1 Start/Stop File-AID/EX Execution Server as Windows Service

Windows services enable users to create long-running executable applications that run in their own Windows sessions. These services can be automatically started when the computer boots. They can also be paused and restarted. These features make services ideal for use on a server or whenever there is a need for long-running functionality that does not interfere with other users who are working on the same computer.

The execution server as a Service feature was intended to automatically start a remote execution server on a machine that is not being used as a workstation. Some users not only want this, but also additionally want to use the File-AID/EX tools on the same machine. This can be accomplished by performing the following steps:

1. Use the Execution Server Settings dialog box to add a new entry defining the system the service is installed on as a remote execution server. Select the new entry as the default execution server. Refer to the Homebase help for instructions.
2. Use the Shared Repository Connection dialog box to add a new shared repository using the repository on the system the service is installed on. Make this shared repository the default repository. Refer to the Repository Management Utility help for instructions.

Four batch files, located in the <FAEX_INSTALL_DIR>\dme folder, are supplied to support installing and running the File-AID/EX execution server as a Windows Service:

InstallExpressAsService — This batch file installs the File-AID/EX execution server service. After the service is installed, the File-AID/EX execution server starts. On subsequent reboots, the File-AID/EX execution server automatically starts. After this batch file is successfully run, the File-AID/EX execution server will be listed in the Windows Services dialog window and provides the ability to Start/Restart/Stop the File-AID/EX execution server.

UnInstallExpressAsService — This batch file stops the File-AID/EX execution server, then uninstall it as a Windows Service.

StartExpressAsService — If not running, this batch file starts the File-AID/EX execution server but does not perform an install.

StopExpressAsService — If running, this batch file stops the File-AID/EX execution server but does not perform an uninstall.

Task 4.6.2 Start/Stop File-AID/EX Execution Server as Windows Application

A standalone execution server can be launched in manual mode by using one of the following options.

• Open <File-AID/EX installation directory>\Dme folder in Windows Explorer and launch fa_exsrvr.exe.

  Warning

  Important

  To configure Java Virtual Machine for running the execution server, such as adjusting the memory limit, edit the file fa_exsrvr.vmoptions, located in the same directory.

• Launch goEngine.bat, located in the same directory. This mode provides a bit more flexibility for launching, as the batch file can be modified to point to a different JVM location, to include JDBC drivers from a custom location, and so on.

Task 4.6.3 Start/Stop the File-AID/EX Execution Server on Unix

The File-AID/EX execution server is installed automatically during the installation of File-AID/EX.

To start the execution server:

1. Navigate to the dme directory where File-AID/EX is installed and enter at the prompt ./go.sh
2. Press Enter. A message appears stating that the engine has compiled or the daemon is waiting for connection.

To stop the File-AID/EX execution server, perform (Ctrl+C) on the terminal session from which the execution server was started.