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 IBM Control Desk image + MidVision RapidDeploy at the selected version. In order to use this image, you need to launch it with your selected type, and log in via SSH to create and configure your installation

Visit the IBM Control Desk + MidVision RapidDeploy page on the AWS Marketplace

2. Launching an instance

In order to launch IBM Control Desk + MidVision RapidDeploy, 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.

From the AWS Marketplace

From the AWS EC2 Control Panel

From the AWS Marketplace

Select the Product based on your requirements in the AWS Marketplace;
Click on the link to go to that versions page in AWS Marketplace;
Check the ‘Other Versions ‘ link to see other versions available (you can select the actual version later).
Under ‘Pricing Details‘ panel select your Region and either Hourly or Yearly fees.
Click on the ‘Continue‘, button to go to the ‘1-Click Launch‘ tab on the configuration page;
On the ‘Software Pricing‘ panel choose your instance type and pricing type;
On the ‘Version‘ panel, select the fix pack version you require;
On the ‘Region‘ panel, select the Region you require;
On the ‘EC2 Instance Type‘ panel, choose the instance type. The m3.large type or larger is recommended when running IBM Control Desk;
On the ‘VPC Settings‘ panel Configure the VPC settings to your requirements or leave the defaults;
On the ‘Security Group‘ panel, specify the security group. The security group needs to permit to following ports [note that the internal firewall will be configured later to permit only ports used by WebSphere]:
```
Port 22 to connect via SSH (enabled by default), 
Port 9090 to reach RapidDeploy web console, 
Port 20000 and 20100 to open for RapidDeploy Remote Agent (optional)
```
- If you don’t already have a security group as above, go to your EC2 Control Panel and select ‘Security Groups‘ under ‘Network & Security‘
- Click ‘Create Security Group‘ button
- To open all ports, Click ‘Add Rule‘.
- In the ‘Type‘ dropdown, Specify ‘All TCP‘ or your preferred configuration.
- In the ‘Source‘ dropdown, Specify ‘Anywhere‘ or your preferred configuration.
On the ‘Key Pair‘ panel, select a key pair to use. You will need this key later to connect to the instance.
Scroll back to the top of the page and click ‘Accept Software Terms and Launch with 1-Click‘.
The Instance will be Launched.

From the AWS EC2 Control Panel

Select the AMI based on your requirements;
Right click on the AMI, or from the drop down menu, choose the ‘Launch’ option;
On the ‘Choose Instance Type‘ tab, choose the instance type. The M3.large type or larger is recommended when running IBM Control Desk; Click ‘Next: Configure Instance Details‘.
On the ‘Configure Instance‘ tab Configure the instance to your requirements or leave the defaults. Click ‘Next: Add Storage‘.
On the ‘Add Storage‘ tab, add additional storage as required or leave as default. Click ‘Next: Tag Instance‘.
On the ‘Tag Instance‘ tab, Tag your instance with a suitable name. Click ‘Next: Configure Security Group'.
On the ‘Configure Security Group‘ tab, specify the security group. The security group needs to permit to following ports:
```
Port 22 to connect via SSH (enabled by default), 
Port 9090 to reach RapidDeploy web console, 
Port 20000 and 20100 to open for RapidDeploy Remote Agent (optional)
```
- To open all ports, Click ‘Add Rule‘.
- In the ‘Type‘ dropdown, Specify ‘All TCP‘ or your preferred configuration.
- In the ‘Source‘ dropdown, Specify ‘Anywhere‘ or your preferred configuration.
Click ‘Review and Launch‘.
Review settings, then click ‘Launch‘.
Add your key pair, Check the ‘Acknowledge key file access’ checkbox and click ‘Launch Instance‘.

3. Initial login and setup

The products are shipped with IBM Control Desk + MidVision RapidDeploy. IBM Control Desk is a base binary installation but without the necessary profiles created. When it comes to RapidDeploy on the first login to the instance, you will be placed into a console wizard, which will guide you through the process of configuring your instance. The following is an overview of the steps you will be guided through to get started with the installed products on the instance. Once the instance has started up (you can see it by having ” 2/2 checks passed ” in EC2 console).

Log onto the instance from the EC2 console or via SSH as the ‘midvision’ user, using the key you selected above. For example:
- From the EC2 console by clicking the “Connect to your instance” button with username “midvision” , using the previously (instance launch-time) selected .pem keyfile.
- Via SSH from your desktop, for example
```
ssh -i ./MidVisionUSMC.pem midvision@ec2-52-87-198-23.compute-1.amazonaws.com
```

You should see the MidVision banner and then you are placed in a setup wizard.

Welcome to                                                                                                                                             

 __  __ _     ___     ___     _                    ____ _                 _
|  \/  (_) __| \ \   / (_)___(_) ___  _ __        / ___| | ___  _   _  __| |
| |\/| | |/ _` |\ \ / /| / __| |/ _ \| '_ \ _____| |   | |/ _ \| | | |/ _` |
| |  | | | (_| | \ V / | \__ \ | (_) | | | |_____| |___| | (_) | |_| | (_| |
|_|  |_|_|\__,_|  \_/  |_|___/_|\___/|_| |_|      \____|_|\___/ \__,_|\__,_|

                                                       A MidVision Service

        * WebSite: https://www.midvisioncloud.com/
        * Support: http://support.midvision.com/redmine/projects/devtestcloud
        * Forum:    https://www.midvisioncloud.com/community/


Welcome, this is MidVisionCloud RapidDeploy and  IBM Control Desk  image first run configuration

Configuration steps
- Set RapidDeploy framework initial password
- Open ports on RHEL firewall

Set initial password for RapidDeploy user “mvadmin“. Hit [return] to accept the default of the instance id.

Configuring password for RapidDeploy default user 'mvadmin'
Set password for user 'mvadmin'. Submit blank for default value of the instance id: i-090a826faa3b56f75

Open required firewall ports on Red Hat Linux firewall. Select ‘y‘ and hit [return].

Open firewall ports for RapidDeploy and  IBM Control Desk (default port 9090)  [y/n]?

You should see ports list of ports being opened. Type ‘exit‘ to leave this section and the wizard. The correct URLs to access the RapidDeploy and Control Desk installation path are displayed.

Configuration finished, you may now start using RapidDeploy services and other software. Web user interfaces are available on:

RapidDeploy: ec2-34-230-51-127.compute-1.amazonaws.com:9090/MidVision
You can find your IBM Control Desk installation under /opt/IBM/SMP
You can find your IBM WebSphere Application Server installation under /opt/IBM/WebSphere

4. Accessing the web consoles

4.1 Accessing the IBM Control Desk Installation

After the initial node creation upon first login, the installation can be accessed from

/opt/IBM/SMP

Please refer to the IBM Control Desk documentation for further usage information.

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:

http://[publicip]:9090/MidVision

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.

Instance Users

[midvision]: This is the default user for AMIs where both IBM Control Desk and RapidDeploy are installed, 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. Use this user to create Control Desk profiles. 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.

Opening Red Hat Entreprise Linux firewall with the open-firewall.sh script

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 9090
Open firewall port 9090 iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]

Files used for MidVision-Cloud services

There are a few scripts and other files in mqm 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.

Starting and stopping RapidDeploy manually

To restart RapidDeploy manually from the filesystem, use the rapiddeploy linux service. The RapidDeploy version is 5.1.0. 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.

Changing RapidDeploy initial password

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.3 Contacting MidVision support

Please visit our support website.