Connecting to Instance

1. Start the instance.

2. Click Connect to view details required for accessing your instance.

   The Connect To Your Instance pop-up window opens.

3. Copy the public DNS address.

4. Execute the following command:

   ~]$ ssh ec2-user@PUBLIC_DNS_ADDRESS

5. Enter yes to confirm that you want to connect to your instance.

Installing Red Hat JBoss BPM Suite on VM Instance

1. Connect to the instance on which you want to install Red Hat JBoss BPM Suite.

2. Update your instance in order to get the latest version of Red Hat JBoss EAP 6.x by executing the following command:

   ~]$ sudo yum -y update

3. Switch to root:

   ~]$ sudo su

4. Copy the following configuration files to /etc/jbossas/standalone/ and /etc/jbossas/domain/:

   • standalone.xml
   • standalone-full.xml
   • standalone-full-ha.xml
   • standalone-ha.xml
   • standalone-osgi.xml

   Follow the instructions:

   1. Download Red Hat JBoss BPM Suite 6.3.0 Deployable for EAP 6 from Customer Portal.
   2. Change directory to the location of the downloaded zip file.

   3. Copy the zip file into the /tmp/ directory of your virtual machine instance:

      ~]$ scp jboss-bpmsuite-6.3.0.GA-deployable-eap6.x.zip ec2-user@PUBLIC_DNS_ADDRESS:/tmp

   4. Go to the /tmp/ directory of your VM instance and unzip the file:

      ~]# unzip jboss-bpmsuite-6.3.0.GA-deployable-eap6.x.zip

   5. Change directory to jboss-eap-6.4/standalone/configuration/ and copy all the configuration files listed above into /etc/jbossas/standalone/ and /etc/jbossas/domain/, for example:

      ~]# cp standalone.xml /etc/jbossas/standalone/

      Enter y to overwrite the file.

   6. Make sure that the files were overwritten: standalone.xml should contain the following:

      <system-properties>
        <property name="org.kie.example" value="true"/>
        <property name="org.jbpm.designer.perspective" value="full"/>
        <property name="designerdataobjects" value="false"/>
      </system-properties>

5. Copy the required applications (for example Business Central) to /usr/share/jbossas/standalone/deployments/:

   1. Change directory to /tmp/jboss-eap-6.4/standalone/deployments/.

   2. Copy Business Central:

      ~]# cp -r business-central.war /usr/share/jbossas/standalone/deployments/

      ~]# cp -r business-central.war.dodeploy /usr/share/jbossas/standalone/deployments/

6. Set the proper Red Hat JBoss EAP binding address.

   Each virtual machine has private and public IP addresses. The public IP address can be accessed outside the AWS, while the private IP address is accessible only inside the virtual network of your Amazon EC2 account.

   Important

   Every time you start the instance, the addresses change. Refer to the Red Hat JBoss Enterprise Application Platform 6.4 Administration and Configuration Guide for more information.

   One way to set the address is by doing the following:

   1. Run ifconfig and copy the inet addr address (for example 10.233.159.148).

   2. Open /etc/jbossas/standalone/standalone.xml and set the proper binding address:

      <interfaces>
        ...
        <interface name="public">
          <inet-address value="10.233.159.148"/>
        </interface>
        ...
      </interfaces>

7. Enable Git and SSH access to Business Central: add the following system properties (with your private IP address) into /etc/jbossas/standalone/standalone.xml.

   <property name="org.uberfire.nio.git.daemon.host" value="10.233.159.148"/>
   <property name="org.uberfire.nio.git.ssh.host" value="10.233.159.148"/>

Creating new AMI from Configured Instance

1. In the main menu, go to INSTANCES → Instances.

2. Locate your configured instance and click Actions → Image → Create Image.

   
3. In the Create Image dialog window, specify the image details and click Create Image.