IBM App Connect Enterprise on Microsoft Azure

Microsoft Azure Installation and Support guide

1. Overview

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

This Virtual Machine image contains a ready-to-run IBM App Connect Enterprise 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 Integration Nodes, Message Flows and Listeners etc..

Visit the IBM App Connect Enterprise pages on the Microsoft Azure Marketplace

2. Launching an instance

In order to launch IBM App Connect Enterprise (referred as ACE), a few settings need to be configured on the Azure console as follows:

  1. Open new Azure Virtual Machine wizard;
  2. Select the IBM ACE Azure image based on your requirements from gallery;
  3. Choose VM name, size, Authentication user and credentials. The Standard DS2V2/General Purpose type or larger is recommended when running IBM App Connect Enterprise.  Basic DS1V2 is the minimal requirement, Larger instances may be required based on the number of IBM Integration Nodes etc required and the expected resource use of each;
  4. Define cloud service DNS name, Regions and open endpoint ports.
Port 22 to connect via SSH (enabled by default), 
Port 4445 to reach the ACE Web UI,
Port 5951 if using the remote toolkit,
Port 9090 to reach RapidDeploy web console (enabled by default), Port 20000 and 20100 to open for RapidDeploy Remote Agent (optional).

3. Initial login and setup

The IBM App Connect Enterprise products are shipped with a base binary installation but without the necessary Integration Nodes 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 Integration Nodes 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.
    1. Log onto the instance via SSH with your Azure user and credentials. Once the instance has started up (you can see it by having “Running” status in Azure console), you can connect to the instance via any SSH client. You can log in to your instance with provisioned Azure username  and the credentials which can be based on password or certificate file.
    2. 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/product-category/microsoft-azure-marketplace
              * 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 the MidVisionCloud IBM App Connect AMI first run configuration.
      
      Configuration steps:
      
      1. Create and start an IBM App Connect sample server.
      2. Set RapidDeploy framework initial password.
      3. Open ports on RHEL firewall.
      
      Create and start an IBM App Connect sample server? [y/n]
      
      
    3. Once the admin user is logged in, please log in as the  ‘mqm’ user via the command ‘sudo su – mqm’.
    4. You are placed in a setup wizard.
    5. Choose whether to create and start an IBM Integration Bus server.
    6. Set initial password for RapidDeploy user “mvadmin
    7. Choose which ports to open on Red Hat Linux firewall.
    Please refer to IBM documentation for IBM Integration Bus configuration

4. Accessing the web and command line consoles

4.1 Accessing the ACE Interface

After the initial node creation upon first login, the user interface can be accessed via

http://[publicip]:4445

You can log in to ACE console as “mqm” using  ‘mqm]‘ as password.

Please refer to the ACE documentation for further usage information.

4.2 ACE Licensing

The ACE node created as a part of the first login process will be created at your purchased licensing level. Each additional node MUST be created at your entitled level to comply with licensing restrictions. One can check their current license level per node from the command line. Where “integration_nodeName” is the name of the integration node to be queried. Please refer to the IBM ACE documentation for more specifics. 

[mqm@ ] mqsimode –o

4.3 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 “. 

You can prevent auto starting RapidDeploy on instance startup by removing it from the system chkconfig list.

systemctl disable rapiddeploystart.service 

5. Maintaining the installation

The following sections cover some of the activities you might want to perform after the instance has been started.
  • mqm: 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 mqm

To restart an ACE node from the command line, use the mqsi commands on the midvision users $PATH.
Example usage:

[mqm@ ] mqsistart
[mqm@ ] mqsistop

CentOS 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 the mqm user (/home/mqm), which is also the starting location when logged in. You will need to be the root user to run this script. Example usage:

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

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  .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.

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

If you don’t want to use RapidDeploy and free memory on your instance you can stop rapiddeploy service using command:

[mqm@ ] sudo service rapiddeploystart stop

Then in order to make sure it will not start when an instance starts again run this command:

[mqm@ ] sudo systemctl disable rapiddeploystart.service

For security reasons, you will need to change the default password (default value is ‘mvadmin‘) 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 Microsoft Azure instance and run the script again.

6.2 Cannot access the ACE admin console (ISC)

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

6.3 Contacting MidVision support

Please visit our support website.