Docker-based Installation


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 to try 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 Myst Software Docker Registry.

If you are unable to use Docker, there are details on non-Docker installation here (ignore this note if you came from the non-Docker installation for the purpose of obtaining the docker image).

Network Requirements

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. The below table provides a set of recommended firewall rules for the Myst Studio server itself in a case where the Myst Build Server and Myst Artifact Repository are all residing on the same host.

Source Destination Protocol Note
Any myst-studio:443 HTTPS Access to Myst Studio Console
Any myst-studio:8081 HTTP Access to Myst Build Server
Any myst-studio:8083 HTTP Access to Myst Artifact Repository
myst-studio OFMW Admin Server Host(s) SSH Myst Studio will connect over ssh to the Admin Server of each environment for management operations.
OFMW Admin Server Host(s) OFMW Managed Server Hosts SSH Myst Agent will ssh from admin to managed server hosts if needed for installation and patching.
OFMW Admin Server Host(s) myst-studio:8083 HTTP Myst Agent will retrieve built artifacts for deployment from the Myst Artifact Repository

Optionally, the Myst Build Server and Myst Artifact Repository can be frontend by a HTTP Server similar to Myst Studio allowing for HTTPS traffic only. If you are not using the Myst Build Server and Artifact Repository and instead integrating with a different Build (CI) Server or Maven-based Artifact Repository, similar firewalling rules should be in place although the ports may be different.

Downloading the Myst Installer

The installation wizard (or installer) can be found at ()[].

Installation using the Wizard

The installation wizard can be kicked off by executing the jar installer using Java as follows:

java -jar <installer file>

If you need to run Myst Studio installer from the console (non-graphical), you can execute the following:

java -jar <installer file> -console

In the first step, you will be provided with an overview of the prerequisites.

In the next step, you will be asked to enter a path for the Myst Studio utilities. The standard convention is to installer under /opt/myst-studio however any path can be used.

In the next step, we can choose which packs we wish to install. At a minimum Myst Studio will be selected.

Optionally, you can choose:

  • Myst Build Server: Pre-configured Build Server for use with Myst for if you don't already have one.
  • Myst Artifact Repository: Pre-configured Maven Artifact Repository for if you don't already have one.
  • Build Extension for Oracle Middleware: Enables automated build for applications build on SOA, BPM, OSB, ADF and other products related to Oracle Middleware. When you choose this, it will automatically select Myst Build Server if it is not already selected. The Build Extensions are currently supported for:

Click Next.

In the next step, you will be prompted to import the Myst license key. The file is provided when you sign up for Myst and is in a format similar to Myst-*.lic.tar.gz

Prior to April 2017, Myst users were provided with a separate api.key and Myst.lic file. In installers prior to, these had to be imported separately. If you do not have a tar.gz file but have api.key and Myst.lic you can compress them to a new tar.gz and use that for that installer.

You will be prompted to confirm installation. Click Next.

The installation should take only a second or two.

After the installation is successful, you will be prompted with the next steps to be performed.

If desired, you can generate a silent installation script which can be used to perform an installation silently.

Silent Installation

To run a silent installation you can execute the following:

java -jar <installer file> <response file>

Providing Certificates for SSL

By default, Myst Studio will boot up with demo SSL certificates, this may be ok for a development or sandbox environment but should not be used for production.

If you do not replace the demo certificates, you will get security warnings from your browser when you access the Myst Studio console.

To update the certificates, replace the demo certificates at the following locations with your real certificates:

  • conf/data/nginx/ssl/cert.crt
  • conf/data/nginx/ssl/cert.key


If you have already started the Myst Studio stack, you must force a rebuild of the data container when you restart the stack, this can be done with the following command. ./bin/ -u If you are yet to start the stack, please continue on to the next steps. Myst will automatically build the data container on the first start.

Configuring Build Extensions

If you choose the Build Extensions for Oracle Middleware then you will need to download Oracle installers and a JDK. Place them in the Myst home at the following locations depending on the versions you chose:

Build Extensions in docker data containers are deprecated. Myst 5.8.6 uses docker volume mounts.

Docker volume mounts allow Oracle installers to be installed on the filesystem then volume mounted to the Myst Build Server docker container.

Version File conf/fmw/context/jdk/jdk-8u121-linux-x64.tar.gz
conf/fmw/context/12211/installers/fmw_12. conf/fmw/context/jdk/jdk-8u121-linux-x64.tar.gz
conf/fmw/context/12212/installers/fmw_12. conf/fmw/context/jdk/jdk-8u131-linux-x64.tar.gz

Once the Oracle installers are placed in the desired locations, you will need to install FMW by executing the following:

cd /opt/myst-studio/fmw

For version the script will also fix Oracle Maven Plugin dependency errors.

Starting the Myst Studio Stack

After the successful installation navigate to the Myst Studio home (in our example, /opt/myst-studio) and execute the following:

cd /opt/myst-studio/bin

Once the has completed you should be able to access the Myst Studio console at https://<your host>/console.

You can see the details of your running instances by executing docker ps from the command line.

Configuring Maven for Automated Build of Oracle Middleware

If you choose Build Extensions for Oracle Middleware when installing Myst, Maven must be configured on the build server, before you can build applications to run on products such as SOA, BPM, OSB and ADF. This can be done by simply executing the following from the Myst Studio home where SHORT_VERSION could be 122130 if you installed OFMW

cd /opt/myst-studio/bin

If you skipped the post-installation steps documented in the section on Configuring the Build Extensions the above command will not succeed.

Offline Installation

It is highly recommended that proxied internet access be available for the Myst server. This allows for easy upgrade of Myst by simply specifying a version number to download (e.g. ./ In an event that Myst Studio does not have internet access, you will need to download the required Myst Studio Docker Images from a host with internet access and then copy them to the Myst Server before executing the or Depending on whether you choose "Myst Build Server" and "Myst Artifact Repository", there may be multiple Docker images that need to be downloaded and copied to the server.

Myst Studio (Offline)

The Myst Studio Docker Image can be downloaded from the Myst website.

After downloading the Myst Studio installer from the website, copy it to the Myst host and execute the following

gunzip myst-studio-docker-image-
sudo docker load -i myst-studio-docker-image-
docker tag myst-studio

Make sure that you replace the above version details to correspond to that version of Myst that was downloaded.

Myst Build Server (Offline)

If you are planning to use Myst Build Server on a host without internet access, from a host with internet access and Docker installed run the following:

docker pull jenkins
docker save jenkins > myst-build-base.tar

Then copy the myst-build-base.tar to the Myst host and execute the following:

docker load -i myst-build-base.tar

Myst Artifact Repository (Offline)

If you are planning to use Myst Artifact Repository on a host without internet access, from a host with internet access and Docker + Myst installed run the following:

docker save maven-repository > maven-repository.tar

Then copy the maven-repository.tar to the Myst host and execute the following:

docker load -i maven-repository.tar

Build Extensions for Oracle Middleware (Offline)

If you are planning to use Myst Artifact Repository on a host without internet access, from a host with internet access and Docker + Myst installed run the following:

docker pull oraclelinux:7
docker save oraclelinux:7 > oracle-linux.tar

Then copy the oracle-linux.tar to the Myst host and execute the following:

docker load -i oracle-linux.tar

results matching ""

    No results matching ""