} Link

Deploy BuildVu on Oracle Cloud Infrastructure

Table of contents

  1. Download the WAR file
  2. Set up your VCN
  3. Upload BuildVu WAR file
  4. Install Docker
  5. Pull and run idrsolutions/buildvu
  6. HTTPS Integration [Optional]
  7. Environment variables
  8. Running BuildVu from different language clients

One of the easiest ways to deploy BuildVu on Oracle Cloud Infrastructure is to run a single compute instance and installing docker on it.

Download the WAR file

Before getting started, you first want to download the WAR file. This is required for the image to work.

For trial users:

  1. If you haven’t already, sign up for BuildVu trial.

  2. Open the email you recieve when you signed up.

  3. Follow the download link found in the Docker section.

For customers:

  1. Visit the Customer download page.

  2. Click on ‘Download Latest Customer WAR’.

  3. Submit your username and password.

Set up your VCN

Start by navigating to Virtual Cloud Networks (VCN).

1

Create a VCN (use the wizard if uncertain).

2

Once complete, open your VCN.

3

Select “Security Lists”.

4

Open the default list for your VCN.

5

Click on “Add Ingress Rules” and copy the settings below.

6

7

Click “Add Ingress Rules” and navigate to compute/Instances.

8

Click “Create Instance” and follow the network settings below.

9

Make sure to add the SSH key you will need to connect to the instance to continue, click create and open our preferred method for SSH connections. (I will be using bash.)

Enter "ssh -i key opc@" where key is the directory of the private key followed by your instance’s public IP e.g. ssh -i instance.key opc@123.123.123.123

Once connected, type the following commands waiting in turn for each to complete.

Upload BuildVu WAR file

In a seperate terminal, you will need to upload the WAR file with scp.

Using the same ssh details, the command will look like:

scp -i <key> <path/to/buildvu-microservice.war> opc@<instance public IP>:/home/opc

e.g.

scp -i instance.key buildvu-microservice.war opc@123.123.123.123:/home/opc

This will upload to the opc home directory; ready for use with docker.

Install Docker

sudo yum install docker-engine

Pull and run idrsolutions/buildvu

sudo docker pull idrsolutions/buildvu

If you get the following message then you will need to run another command to start the docker deamon:

10

sudo service docker start

Now launch the docker image.

sudo docker run -p 80:80 --mount "source=/home/opc/buildvu_microservice.war,target=/usr/local/tomcat/webapps/ROOT.war,type=bind" idrsolutions/buildvu

Now go to a web browser and enter the public IP of your instance followed by “:80” to connect e.g. 123.123.123.123:80. You should be shown a page displaying the name of the service being used, in this case “BuildVu Microservice Example”.

HTTPS Integration [Optional]

If you intend to use HTTPS encryption, you will need to update your VNS security list.

Navigate back to VNS and create a new ingress rule with the following settings: 11

Re-connect to your instance and add your certificate, key, and ca_bundle. They should have these names: certificate.crt private.key ca_bundle.crt

Now run the following command to start the service:

docker run -p 80:80 -p 433:433 --mount "source=/home/opc/buildvu_microservice.war,target=/usr/local/tomcat/webapps/ROOT.war,type=bind" idrsolutions\buildvu

If you encounter an error then you may need to run the following command instead. Please take caution in doing this - more information can be found in the docker docs.

docker run -p 80:80 -p 443:443 --mount "source=/home/opc/buildvu_microservice.war,target=/usr/local/tomcat/webapps/ROOT.war,type=bind" --volume "/path/to/ssl"/target:"/opt/ssl"/app:z,ro idrsolutions/buildvu

Environment variables

There are a few useful environment variables that you can use.

These are used to set a username and password to access the microservice:

  • ACCESS_USERNAME: used to set a username for the microservice.
  • ACCESS_PASSWORD: used to set a password for the microservice.

Running BuildVu from different language clients

Now that you have the docker server running you can follow the tutorials for using the API to begin your conversions.