Myst Installation Guide
- Understanding the Myst installation
- Myst Topology
- Alternative Myst Topologies
- System Requirements
- Network Requirements
- Installation in 3 simple steps
Understanding the Myst installation
A typical Myst installation consists of the following:
|Myst Studio||Web-based Management Console|
|Myst Repository||Storage layer for Myst platform and application state|
|Myst Build Server||Optional CI Server, if not using a third-party one such as Jenkins|
|Myst Maven Repository||Optional Maven Repository, if not using a third-party one such as Artifactory|
The Myst Studio console can be installed on a single server or across multiple tiers. Myst is supported on a container-based architecture (e.g.
docker) or on a virtual/physical server architecture. Rubicon Red recommend the use of the container-based architecture.
The Myst Server can be established on modern container runtimes such as
docker (CE / EE) and
containerd. An installer is provided to easily establish the stack on a single server instance. After completing the installation and starting the containers, the following containers will be running:
myststudio_https- Nginx exposing
myststudio_web- Tomcat instance accessed by
myststudio_db- MySQL instance accessed by
State for the stack is automatically stored in a container volume and accessed via
The following additional containers can be optionally installed:
myststudio_ci- Myst Build Server exposing
maven-repository- Myst Maven Repository exposing
Exposed ports can be configured by adjusting the port mappings in the
docker stack configuration
Alternative Myst Topologies
In an event that container-based topology is undesired, the stack can be rolled out on a non-container infrastructure. More details on this approach are documented in the Alternative Installations section.
The following prerequisites should be in place on the server that will host Myst Studio prior to running the Myst installer.
- Java 1.7+ is installed.
- Docker 1.10+ and Docker Compose is installed.
The Myst license tar.gz file must be available. This is provided when you sign up for Myst Studio.
After the installation, internet access is required for the latest version of Myst to be pulled down directly from the public Myst Docker Registry. If you are behind an internet proxy, please follow these steps to ensure all installation dependencies can be directly pulled from the Rubicon Red Docker Registry.
If you are unable to use Docker, there are details on non-Docker installation here
As Myst is a management tool, it is best suited in a management network so that it can access all of the environments that it needs to manage. Myst will connect to the instances that it manages via
ssh protocol and
tcp as needed. More details on network requirements are available here section.
Installation in 3 simple steps
Once the Myst installer has been download, it can be used to establish the Myst stack on
docker. Once the System Requirements are in place, the process of getting up and running is a 3 steps process.
- Run the Myst Installer
java -jar fc-installer-6.3.1.jar
- After running the installer, Myst can be started with
- By default, the Myst Studio console is accessible from