Docker-based Installation

• Prerequisites
• Network Requirements
• Installation using the Wizard
• Providing Certificates for SSL
• Configuring Build Extensions
• Starting the Myst Studio Stack
• Configuring Maven for Automated Build of Oracle Middleware
• Offline Installation
  • Myst Studio (Offline)
  • Myst Build Server (Offline)
  • Myst Artifact Repository (Offline)
  • Build Extensions for Oracle Middleware (Offline)

Prerequisites

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.

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.

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.

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:
  • 12.2.1.3.0
  • 12.2.1.2.0
  • 12.2.1.1.0

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

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.

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.

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/start.sh -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:

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
./install-fmw.sh

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
./start.sh

Once the start.sh 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 12.2.1.3.0.

cd /opt/myst-studio/bin
./configure-maven.sh <SHORT_VERSION>

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. ./upgrade.sh 5.5.0.0). 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 start.sh or upgrade.sh. 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-5.5.0.0.tar.gz
sudo docker load -i myst-studio-docker-image-5.5.0.0.tar
docker tag  docker-registry.rubiconred.aws:5000/myst-studio:5.5.0.0 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:

/opt/myst-studio/bin/pull.sh
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