Red Hat JBoss Enterprise Application Platform on 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 Azure Virtual Machine contains a ready-to-run Red Hat JBoss Enterprise Application Platform 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 activate it.

Visit the Red Hat JBoss Enterprise Application Platform page on the Microsoft Azure Marketplace

2. Launching an instance

In order to launch JBoss EAP instance, a few settings need to be configured on the Azure console as follows:

  1. Open new Azure Virtual Machine wizard;
  2. Select the JBoss EAP 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 JBoss EAP.  Basic DS1V2 is the minimal requirement, which will be sufficient to run JBoss EAP. Larger instances may be required based on the number of JBoss EAP 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)

 3. Initial login and setup

The JBoss EAP product is shipped with a base binary installation. On the first login to the instance, you will be placed into a console wizard. The following is an overview of the steps you will be guided through to create the required profiles on the instance:

  1. Log onto the instance via SSH with your Azure user and credentials.
  2. Once the admin user is logged in, please log in as the  ‘amq-broker’ user via the command ‘sudo su – amq-broker’.
  3. You are ready to use Red Hat AMQ.

Once the VM instance has started up:

  1. Log onto the instance via SSH as the ‘azureuser’ user, using the key you selected above.  For example:
    • Via SSH from your desktop, for example
      ssh -i ./MidVisionUSMC.pem azureuser@[public-ip-address]
  2. Type sudo su - root
  3. You should see the MidVision banner and then you are placed in a setup wizard.
    Welcome to                                                                                                                                             
     __  __ _     ___     ___     _                    ____ _                 _
    |  \/  (_) __| \ \   / (_)___(_) ___  _ __        / ___| | ___  _   _  __| |
    | |\/| | |/ _` |\ \ / /| / __| |/ _ \| '_ \ _____| |   | |/ _ \| | | |/ _` |
    | |  | | | (_| | \ V / | \__ \ | (_) | | | |_____| |___| | (_) | |_| | (_| |
    |_|  |_|_|\__,_|  \_/  |_|___/_|\___/|_| |_|      \____|_|\___/ \__,_|\__,_|
                                                           A MidVision Service
            * WebSite:
            * Support:
            * Forum:      
    Please run 'sudo su - root' to start using provided services.

    Welcome, this is MidVisionCloud JBOSS EAP image.
    You can access JBOSS admin console on http://[public-ip]:9990. Log in with admin/mvadmin .
    Note that you can change your password as root user using /opt/jboss-eap-7.2/bin/ script.

4. Accessing the web consoles

4.1 Access the Red Hat JBoss Enterprise Application Platform

Confirm installation. The JBoss EAP admin console should be running on port 9990:


You can log in as a default admin user, use your [instanceId] as password.

5. Maintaining the installation

The following sections cover some of the activities you might want to perform after the instance has been started.
  • root: This is the superuser in linux systems. You can log in as any other user without using passwords. E.g: “su azureuser“, “su amq-broker
  • azureuser: The Azure default user.
You can find JBoss EAP installation under :
JBoss has been started as a standalone server (as root user) using
/opt/jboss-eap-7.2/bin/   -b -bmanagement &
You can stop the server as root user:
 /opt/jboss-eap-7.2/bin/ --connect --command=:shutdown

As mentioned above along with the JBoss EAP installation there is an admin console user created with password set to your [instanceId]. 



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 Azure instance and run the script again.

6.2 Contacting MidVision support

Please visit our support website.