Red Hat JBoss Web Server 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 Red Hat JBoss Web Server 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 Web Server page on the AWS Marketplace
Launch from AWS

2. Launching an instance

In order to launch JBoss Web 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

The Red Hat JBoss Web Server products are shipped with a base binary installation. On the first login to the instance – after logging onto the instance via SSH as the ‘ec2-user’ user you will see basic information about JBoss installation. The following is an overview of the steps you will be guided through to create the required profiles on the instance:

Once the instance has started up (you can see it by having ” 2/2 checks passed ” in EC2 console).

  1. Log onto the instance from the EC2 console or via SSH as the ‘ec2-user’ user, using the key you selected above.  For example:
    • From the EC2 console by clicking  the “Connect to your instance” button with username “ec2-user“, using the previously (instance launch-time) selected .pem keyfile.
    • Via SSH from your desktop, for example
      ssh -i ./MidVisionUSMC.pem ec2-user@ec2-52-87-198-23.compute-1.amazonaws.com
  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
        * Support: http://support.midvision.com/redmine/projects/devtestcloud
        * Forum:   https://www.midvisioncloud.com/community

Welcome, this is MidVisionCloud JBOSS Web Server image.
You can find JBOSS installation under /opt/jws-5.3 (use sudo su to access as a root user) 
Follow the instruction from https://www.midvisioncloud.com/ibm-websphere-on-amazon-web-services/jboss-web-server-linux-aws/ to configure your default web server.

4. Accessing the web consoles

4.1 Access the Red Hat JBoss Web Server

In order to access the JBoss Web Server admin console you will need to configure your environment as it is described in Red Hat JBoss Web Server documentation: https://access.redhat.com/documentation/en-us/red_hat_jboss_web_server/5.3/html/installation_guide/installing_jboss_web_server_on_red_hat_enterprise_linux#rhel_zip
  1. Create a new file in /opt/jws-5.6/tomcat/bin 
    [root@ip-172-30-0-32 jws-5.6]# vi /opt/jws-5.6/tomcat/bin/setenv.sh
    Insert the JAVA_HOME definition, for example: 
    export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.262.b10-0.el7_8.x86_64
    You can find the path to java using 
    alternatives --config java
  2. Make this file executable 
    [root@ip-172-30-0-32 bin]# chmod ugo+rwx ​/opt/jws-5.6/tomcat/bin/setenv.sh
  3. Run post install script and make tomcat user an owner: 
    [root@ip-172-30-0-32 bin]# cd /opt/jws-5.6/tomcat/
[root@ip-172-30-0-32 tomcat]# ./.postinstall.systemd
[root@ip-172-30-0-32 tomcat]# cd ..
[root@ip-172-30-0-32 jws-5.6]# chown -R tomcat:tomcat tomcat/
  4. Enable and start jboss web server service: 
    systemctl enable jws5-tomcat.service 
systemctl start jws5-tomcat.service
  5. Then you should be able to access JBoss Web Server console on 
    http://[publicip]:8080

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 ec2-user“
  • tomcat: This user is used by JBoss Web Server systemd service (if you followed the steps from section 4.1) to run the default server. You cannot login as tomcat user. 
  • 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.
You can find JBoss Web Server installation under : 
/opt/jws-5.0
If you decided to run JBoss Web Server as a systemd service then you could start and stop the service using: 
systemctl start jws5-tomcat.service
systemctl stop jws5-tomcat.service

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

Please visit our support website.