Amazon EC2 Installation and Support 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 WebSphere MQ + MidVision RapidDeploy on AWS base image 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 required Queue Managers, Queues and Listeners etc.

Visit the IBM MQ Standard and Advanced Edition + MidVision RapidDeploy pages on the AWS Marketplace

2. Launching an instance

In order to launch IBM WebSphere MQ (referred as MQ or WMQ) + 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

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.medium type or larger is recommended when running IBM WebSphere MQ. Larger instances may be required based on the number of IBM WebSphere MQ queue managers etc required and the expected resource use of each; 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 1414 and 1415 to connect to WMQ, 
Port 9090 to reach RapidDeploy web console, 
Port 9443 to reach IBM MQ 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. Remember to open also ports that will be used by Queue Manager (usually you 1414 and 1415)
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 a base binary installation but without the necessary Queue Managers created. On the first login to the instance, you will be placed into a console wizard, which will guide you through the process of creating and starting IBM WebSphere MQ Queue Managers and other configuration steps. 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 ‘ubuntu’ user, using the key you selected above. For example:
- From the EC2 console by clicking the “Connect to your instance” button with username “ubuntu“, using the previously (instance launch-time) selected .pem keyfile.
- Via SSH from your desktop, for example
```
ssh -i ./MidVisionUSMC.pem ubuntu@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/ibm-websphere-on-amazon-web-services/
        * Support: http://support.midvision.com/redmine/projects/devtestcloud
        * Forum:   https://www.midvisioncloud.com/community      

Please run 'sudo su - mqm' to start using provided services.

Welcome, this is MidVisionCloud RapidDeploy and IBM WebSphere MQ  image first run configuration.

Configuration steps
- Create and Start a default IBM MQ web console
- Set RapidDeploy framework initial password

Create and Start default IBM MQ Web Console? [y/n]

On the first login to the instance, you will be placed into a console wizard, which will guide you through the process of creating and configuring IBM WebSphere MQ. After logging onto the instance via SSH as the ‘ubuntu’ user and switching to ‘mqm’ user you will be placed in a setup wizard. The following is an overview of the steps you will be guided through to create the required profiles on the instance:
1. Create and Start a default IBM MQ web console.
2. Set initial password for RapidDeploy user “mvadmin”.
All inputs asking for specific data can be left as blank just by hitting [return] , which will pick the default value displayed at the end of the question. Please refer to IBM documentation for WebSphere MQ configuration.

If you choose default options you should see this information:

Configuration finished, you may now start using RapidDeploy services and other software. Web user interfaces are available on:
IBM MQ Web Console: https://ec2-52-206-103-87.compute-1.amazonaws.com:9443/ibmmq/console (web console credentials: mqadmin/i-0e5b506ae1cfa1790)
RapidDeploy: ec2-52-206-103-87.compute-1.amazonaws.com:9090/MidVision

4. Accessing the web and command line consoles

4.1 Access the IBM MQ Web Console

If you choose to create and start IBM MQ Web Console then you can access it on:

https://[publicip]:9443/ibmmq/console

Note: make sure you have port 9443 open in your Security group when trying to access IBM MQ web console. Your password for the default username ‘ mqadmin ‘ is set to instance-id but you can change it by just editing a file

/var/mqm/web/installations/Installation1/servers/mqweb/mqwebuser.xml

and restarting web console:

[mqm] endmqweb
[mqm] strmqweb

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

mqm: 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 ubuntu“, “su mqm“
ubuntu: This user has SUDO rights. You use it to login by SSH to the instance.

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 mqm home directory. Those scripts are executed when logging into the instance controlled by .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.

Starting and stopping RapidDeploy manually

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:

[mqm@ ] sudo service rapiddeploystart start 
[mqm@ ] 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.2 Problem with the connection to Queue Manager

Common ERRORS and issues with obtaining connection:

MQRC_UNKNOWN_CHANNEL_NAME
– you need to make sure the QM is actually running and the channel you selected exists. Some of the MQ clients like WAS for example require capital letters in configuration, so for example even if your channel name is “defaultChannel” you need to put “DEFAULTCHANNEL” in your MQ Client
– check if your Listener port is correct and if the Listener has Running status
MQRC_NOT_AUTHORIZED
Usually it happens because of the following reasons:
– CHLAUTH parameter is enabled in your QM configuration. Disable this parameter if you don’t need it or read more about this attribute on IBM documentation pages
```
runmqsc QMGR1
  display QMGR
  ALTER QMGR CHLAUTH(DISABLED)
  end
```
– the MQ Client user is not permitted to connect to QM
```
[mqm@ip-172-30-0-167 ~]$ setmqaut -m QMGR1 -t qmgr -g root +all
```
– the MQ Client requires the user to have password. In our instance there is no password set for mqm user but you can easily change it
```
[mqm@ip-172-31-2-146 ~]$ sudo su
[root@ip-172-31-2-146 mqm]# passwd mqm
New password: 
Retype new password: 
passwd: all authentication tokens updated successfully.
```

6.3 gsk8capicmd_64 command not available

The easy way to be able to run the gsk8capicmd_64 command is to create the LD_LIBRARY_PATH variable with the gskit8 lib directory and execute the full path of the binary gsk8capicmd_64:

[mqm@ip-172-31-1-61 ~]$ export LD_LIBRARY_PATH+=":/opt/mqm/gskit8/lib:/opt/mqm/gskit8/lib64" 
[mqm@ip-172-31-1-61 ~]$ /opt/mqm/gskit8/bin/gsk8capicmd_64

Also, you can add the gskit8 bin directory to the PATH variable, then instead of the full path of the binary, you can just run the command gsk8capicmd_64:

[mqm@ip-172-31-1-61 ~]$ export PATH+=":/opt/mqm/gskit8/bin"
[mqm@ip-172-31-1-61 ~]$ gsk8capicmd_64

6.4 Contacting MidVision support

Please visit our support website.