AMS enables remote applications to access to database files on the computer on which it is running.
When distributing database files over many servers, there are a number of options:
- NFS (on Unix)
- Windows Share (Windows mapped drives/ network shares mapped to a drive letter are not supported)
- AMS (runs on all platforms)
AMS is recommended over NFS and Windows Share for performance and ease of use. Unlike NFS, there is little configuration required for AMS. The AMS is provided with InfiniteGraph and is easy to setup and start.
The AMS server listens to requests on port 6779. If you are using a firewall, please provide an exception so that port 6779 is open to ensure remote systems can communicate with the AMS.
Command Line Tools
There are three command line tools associated with the AMS. They are listed below. They can be used both on Windows and Unix operating systems:
To start the AMS service:
To stop the AMS service:
To check if the AMS is already running:
The last two command line tools (oocheckams and oostopams) can be run remotely as well. For example if you want to check to see if an AMS is running on a remote host called myserver.test.com, simply run it with a hostname as an argument:
Logging and Environment Variables
On Windows, the AMS logs messages to the Application Log which can be viewed with the Windows Event Viewer.
On Unix, the default location for the log is /usr/spool/obj. You can use the OO_SERVER_LOG_DIR environment variable to change this location. For example, to change the log directory to /var/log/infinitegraph in bash:
On Windows operating systems, the InfiniteGraph installer will add an AMS service, so that the AMS will start automatically at Windows startup. The name of the service is “ooams-3”.