MidVision RapidDeploy for Operational Decision Manager on AWS

Amazon EC2 Installation guide

1. Overview

This guide will provide step by step instructions how to start using the installed products on your AWS EC2 instance.

This AMI contains a ready-to-run MidVision RapidDeploy for Decision server image at the selected version. In order to use this image, you need to launch it with your selected type. Once launched, the ODM consoles will then be ready to access.

Visit the MidVision RapidDeploy for Decision Server page on the AWS Marketplace

2. Launching an instance

In order to launch MidVision RapidDeploy for Decision Server, a few settings need to be configured on the AWS console as follows.

The instructions for launching an instance differ depending on where you launch from. Initially you will launch the instance from the AWS Marketplace.

 3. Initial login and setup

On Launching the MidVision RapidDeploy for Decision Server instance, a sample server is also started automatically. You can log in to the IBM ODM  consoles without any further configuration.

4. Accessing the web consoles

4.1 Access the ODM Console

To confirm installation, access the ODM Consoles at:

TeamServer: [publicip]:9190/teamserver (rtsAdmin/[instance-id])
Decision Center: [publicip]:9190/decisioncenter (rtsAdmin/[instance-id])
Rule Execution Server: [publicip]:9190/res (resAdmin/[instance-id])

Use credentials in brackets using your ‘[instance-id]‘ as password.

The password defaults to the instance-id of the AWS instance.

4.2 Access the RapidDeploy web console

RapidDeploy server and agent will start up automatically when you start your instance. You can access the web console on:


Note: make sure you have port 9090 open in your Security group when trying to access RapidDeploy web console. For the first time, you can set the password for the default username ” mvadmin “.

5. Maintaining the installation

The following sections cover some of the activities you might want to perform after the instance has been started.
  • midvision:  This is the default user, which you can log in as. It is permitted to use all SUDO rights. To switch to the root user, type “sudo su“.
  • root:              This is the superuser in linux systems. You can log in as any other user without using passwords. E.g: “su ec2-user“, “su midvision
  • ec2-user:     This user does not have SUDO rights. If you want to switch back to root user, type “exit“, this will take you back to the previous user session.

RHEL instances are shipped with a firewall by default to protect your machine. For security reasons, the instance is only accessible via SSH (port 22) at first, so further ports can be opened on the firewall as needed. You will need to open all the ports in this internal firewall, which you have open in your Security group. There is a script placed in the user home of midvision (/home/midvision), which is also the starting location when logged in. You will need to be the root user to run this script. Example usage:

[midvision@ ] sudo ./open-firewall.sh 9990
Open firewall port 9990 iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]

There are a few scripts and other files in midvision and root users home directory, which will need to remain unchanged in order to keep the provided scripts working. There are a set of scripts in midvision home directory. Those scripts are executed when logging into the instance controlled by  .bash_profile , but you can also execute them manually whenever they are needed. There are some hidden files used as well,  .firstrun  indicates that the setup wizard has already ran once,  .dontask  indicates that the user will not be prompted again for running the setuphost script (if chosen not to ask again), .host file is needed to determine the previously bound hostname to WebSphere service.

To restart RapidDeploy manually from the filesystem, use the rapiddeploy linux service. The RapidDeploy version is 5.0.5. RapidDeploy home is located at /var/rd/midvision Example usage:

[midvision@ ] sudo service rapiddeploystart start 
[midvision@ ] sudo service rapiddeploystart stop

The RapidDeploy server uses an in-memory database, so your RapidDeploy framework needs to be shut down properly to save your work. This happens when the instance is stopping or when calling the stop service manually from the command line. Note that on instance restart, unsaved data will be lost.

For security reasons, you will need to change the default password (default value is ‘[instance-id]‘) for user mvadmin. This will be requested the first time only when you log in to the RapidDeploy server.

6. Troubleshooting

6.1 Session loss during setup

If you lose your SSH connection to the target instance during the first run setup script execution (e.g. as a result of a network problem), we advise you to delete and recreate the EC2 instance and run the script again.

6.2 Cannot access the IBM Operational Decision Center Console

Check that the default server is running, and you have correctly opened all the required ports on the firewall, especially 9190, and that your instance was created using a security group definition that allows TCP access to the instance on the required ports.

Note that ODM sample server usually needs at least 5 minutes to initialize. 

6.3 Error logs after logging in

Configuring password for RapidDeploy default user 'mvadmin'
Set password for user 'mvadmin'. Submit blank for default value of the instance id: i-01e196fa4b22077dc
Setting RapidDeploy password for user 'mvadmin'...
log4j:WARN No appenders could be found for logger (com.midvision.rapiddeploy.utilities.config.PropertyCache).
log4j:WARN Please initialize the log4j system properly.
HTTP/1.1 406 
Content-Type: text/plain
Transfer-Encoding: chunked
Date: Wed, 30 Jan 2019 08:22:58 GMT

Failed to login for the following reason: BadCredentialsException: Bad credentialsRapidDeploy password successfully set

We have been notified that some of our customers experienced the error above. It happens when the user logged in just after the instance has started.
Please remember that RapidDeploy usually needs at least 5 minutes to initialize.

6.4 Contacting MidVision support

Please visit our support website.