24.8. Clustered Managed Domains

Procedure 24.14. Launch a Cluster Domain Contoller

1. Create an elastic IP for this instance.
2. Select an AMI.
3. Go to Security Group and allow all traffic (use Red Hat Enterprise Linux's built-in firewall capabilities to restrict access if desired).
4. Choose "running" in the public subnet of the VPC.
5. Choose a static IP (e.g. 10.0.0.5).
6. Put the following in the User Data: field:

   ## mod cluster proxy addresses
   MOD_CLUSTER_PROXY_LIST=10.0.0.4:7654
    
   ## password that will be used by slave host controllers to connect to the domain controller
   JBOSSAS_ADMIN_PASSWORD=<password for slave host controllers>
    
   ## subnet prefix this machine is connected to
   SUBNET=10.0.0.
   
   ## S3 domain controller discovery setup
   # JBOSS_DOMAIN_S3_SECRET_ACCESS_KEY=<your secret key>
   # JBOSS_DOMAIN_S3_ACCESS_KEY=<your access key>
   # JBOSS_DOMAIN_S3_BUCKET=<your bucket name>
    
   #### to run the example no modifications below should be needed ####
   JBOSS_DOMAIN_CONTROLLER=true
   PORTS_ALLOWED="9999 9990 9443"
   JBOSS_IP=`hostname | sed -e 's/ip-//' -e 'y/-/./'` #listen on public/private EC2 IP address
    
   cat > $USER_SCRIPT << "EOF"
   ## Get the application to be deployed from an Internet URL
   # mkdir -p /usr/share/java/jboss-ec2-eap-applications
   # wget https://<your secure storage hostname>/<path>/<app name>.war -O /usr/share/java/jboss-ec2-eap-applications/<app name>.war
    
   ## Install the JDBC driver as a core module
   yum -y install mysql-connector-java
   mkdir -p /usr/share/jbossas/modules/com/mysql/main
   cp -v /usr/share/java/mysql-connector-java-*.jar /usr/share/jbossas/modules/com/mysql/main/mysql-connector-java.jar
    
   cat > /usr/share/jbossas/modules/com/mysql/main/module.xml <<"EOM"
   <?xml version="1.0" encoding="UTF-8"?>
   <module xmlns="urn:jboss:module:1.0" name="com.mysql">
      <resources>
         <resource-root path="mysql-connector-java.jar"/>
      </resources>
      <dependencies>
         <module name="javax.api"/>
      </dependencies>
   </module>
   EOM
    
   cat > $USER_CLI_COMMANDS << "EOC" 
   ## Deploy the sample application from the local filesystem
   deploy /usr/share/java/jboss-ec2-eap-samples/cluster-demo.war --server-groups=other-server-group
    
   ## ExampleDS configuration for MySQL database
   data-source --profile=mod_cluster-ec2-ha remove --name=ExampleDS
   /profile=mod_cluster-ec2-ha/subsystem=datasources/jdbc-driver=mysql:add(driver-name="mysql",driver-module-name="com.mysql")
   data-source --profile=mod_cluster-ec2-ha add --name=ExampleDS --connection-url="jdbc:mysql://${db.host}:3306/${db.database}" --jndi-name=java:jboss/datasources/ExampleDS --driver-name=mysql --user-name="${db.user}" --password="${db.passwd}"
   /profile=mod_cluster-ec2-ha/subsystem=datasources/data-source=ExampleDS:enable
   EOC
    
   ## this will workaround the problem that in a VPC, instance hostnames are not resolvable
   echo -e "127.0.0.1\tlocalhost.localdomain localhost" > /etc/hosts
   echo -e "::1\tlocalhost6.localdomain6 localhost6" >> /etc/hosts
   for (( i=1 ; i<255 ; i++ )); do
      echo -e "$SUBNET$i\tip-${SUBNET//./-}$i" ;
   done >> /etc/hosts
    
   EOF

7. For Production Instances

   For a production instance, add the following line beneath the USER_SCRIPT line of the User Data field, to ensure security updates are applied on boot.

   yum -y update

   Note

   yum -y update should be run regularly, to apply security fixes and enhancements.
8. Launch the Red Hat AMI instance.

Procedure 24.15. Launch Host Controllers

1. Select an AMI.
2. Define the desired number of instances (the number of slave host controllers).
3. Select the VPC and instance type.
4. Click on Security Group.
5. Ensure that all traffic from the JBoss EAP 6 cluster subnet is allowed.
6. Define other restrictions as desired.
7. Add the following into the User Data field:

   ## mod cluster proxy addresses
   MOD_CLUSTER_PROXY_LIST=10.0.0.4:7654
    
   ## clustering setup
   JBOSS_JGROUPS_S3_PING_SECRET_ACCESS_KEY=<your secret key>
   JBOSS_JGROUPS_S3_PING_ACCESS_KEY=<your access key>
   JBOSS_JGROUPS_S3_PING_BUCKET=<your bucket name>
    
   ## host controller setup
   ### static domain controller discovery setup
   JBOSS_DOMAIN_MASTER_ADDRESS=10.0.0.5
   ### S3 domain controller discovery setup
   # JBOSS_DOMAIN_S3_SECRET_ACCESS_KEY=<your secret key>
   # JBOSS_DOMAIN_S3_ACCESS_KEY=<your access key>
   # JBOSS_DOMAIN_S3_BUCKET=<your bucket name>
   
   JBOSS_HOST_PASSWORD=<password for slave host controllers>
    
   ## database credentials configuration
   JAVA_OPTS="$JAVA_OPTS -Ddb.host=instancename.something.rds.amazonaws.com -Ddb.database=mydatabase -Ddb.user=<user> -Ddb.passwd=<pass>"
    
   ## subnet prefix this machine is connected to
   SUBNET=10.0.1.
    
   #### to run the example no modifications below should be needed ####
   JBOSS_HOST_USERNAME=admin
   PORTS_ALLOWED="1024:65535"
   JBOSS_IP=`hostname | sed -e 's/ip-//' -e 'y/-/./'` #listen on public/private EC2 IP address
    
   cat > $USER_SCRIPT << "EOF"
   ## Server instance configuration
   sed -i "s/main-server-group/other-server-group/" $JBOSS_CONFIG_DIR/$JBOSS_HOST_CONFIG
    
   ## install the JDBC driver as a core module
   yum -y install mysql-connector-java
   mkdir -p /usr/share/jbossas/modules/com/mysql/main
   cp -v /usr/share/java/mysql-connector-java-*.jar /usr/share/jbossas/modules/com/mysql/main/mysql-connector-java.jar
    
   cat > /usr/share/jbossas/modules/com/mysql/main/module.xml <<"EOM"
   <?xml version="1.0" encoding="UTF-8"?>
   <module xmlns="urn:jboss:module:1.0" name="com.mysql">
      <resources>
         <resource-root path="mysql-connector-java.jar"/>
      </resources>
      <dependencies>
         <module name="javax.api"/>
      </dependencies>
   </module>
   EOM
    
   ## this will workaround the problem that in a VPC, instance hostnames are not resolvable
   echo -e "127.0.0.1\tlocalhost.localdomain localhost" > /etc/hosts
   echo -e "::1\tlocalhost6.localdomain6 localhost6" >> /etc/hosts
   for (( i=1 ; i<255 ; i++ )); do
      echo -e "$SUBNET$i\tip-${SUBNET//./-}$i" ;
   done >> /etc/hosts
    
   EOF

8. For Production Instances

   For a production instance, add the following line beneath the USER_SCRIPT line of the User Data field, to ensure security updates are applied on boot.

   yum -y update

   Note

   yum -y update should be run regularly, to apply security fixes and enhancements.
9. Launch the Red Hat AMI instance.

Procedure 24.16. Test the Apache HTTP server instance

• Navigate to http://ELASTIC_IP_OF_APACHE_HTTP_SERVER in a browser to confirm the web server is running successfully.

Procedure 24.17. Test the Domain Controller

1. Navigate to http://ELASTIC_IP_OF_DOMAIN_CONTROLLER:9990/console
2. Log in using the username admin and the password specified in the User Data field for the domain controller. Once logged in, the administration console landing page for a managed domain should appear (http://ELASTIC_IP_OF_DOMAIN_CONTROLLER:9990/console/App.html#server-instances).
3. Click the Server label at the top right side of the screen. Select any of the host controllers in the Host dropdown menu at the top left side of the screen.
4. Verify that this host controller has two server configurations called server-one and server-two and verify that they both belong to the other-server-group.

Procedure 24.18. Test the Host Controllers

1. Navigate to http://ELASTIC_IP_OF_APACHE_HTTP_SERVER/cluster-demo/put.jsp in a browser.
2. Verify that one of the host controllers logs the following message: Putting date now.
3. Stop the server instance that logged the message in the previous step (see Stop a Server Using the Management Console).
4. Navigate to http://ELASTIC_IP_OF_APACHE_HTTP_SERVER/cluster-demo/get.jsp in a browser.
5. Verify that the time shown is the same as the time that was PUT using put.jsp in Step 2.
6. Verify that one of the running server instances logs the following message: Getting date now.
7. Restart the stopped server instance (see Section 2.3.2, “Start a Server Using the Management Console”)
8. Connect to the Apache HTTP server instance.

   $ ssh -L7654:localhost:7654 ELASTIC_IP_OF_APACHE_HTTP_SERVER

9. Navigate to http://localhost:7654/mod_cluster-manager to confirm all instances are running correctly.