25.2.3.12. Clustered Managed Domains

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