This page explains how to install the Artifact Management Server (AMS) software on all supported platforms.
TIBCO recommends installing AMS on a platform that meets or exceeds TIBCO StreamBase's requirements. Although you can install AMS on a platform that is below the StreamBase requirements, other platforms are not officially supported. For more information, see the Supported Configurations documentation page in the StreamBase Installation Guide, per the TIBCO Streaming® documentation.
Run the installer as supplied from your purchase. By default, AMS installs to:
C:\tibco\sb-cep\ (Windows)n.m\ams
/opt/tibco/sb-cep/ (macOS, Linux)n.m/ams/
Post-installation, configure AMS by editing its configuration file as needed for your deployment. See the Configuration Reference page for more information. For example, you may need to enable or change the contents of the local authentication realm to modify or remove existing users and roles that would otherwise get copied into the AMS persistence realm the next time the AMS starts. When the local authentication realm is enabled, the AMS persistence realm is automatically enabled as well. Any users that do not exist in the AMS persistence realm are copied from the local authentication realm.
Post-installation, also ensure the directory containing the AMS executable is on the PATH environment variable:
C:\tibco\sb-cep\ (Windows)n.m\bin
For Windows deployments, AMS provides a Command Prompt shortcut to set the appropriate environment, including the path, to run AMS.
/opt/tibco/sb-cep/ (macOS, Linux)n.m/bin
The file path to the database can be absolute or relative to the current working directory by setting the filePath property in the AMS.conf file.
The AMS web client is compatible with the following web browsers:
Google Chrome
Apple Safari
Other browsers may also work but are not officially supported.
If you encounter "stale data" issues in the Web Client such as pages that are not reloading new content, try:
closing your browser
clearing the browser cache and any cookies relating to the AMS URL
loading the client again