24.2.3.10. Instances clusterisées

Procédure 24.12. Lancer les AMI de JBoss EAP 6 clusterisée

1. Sélectionner une AMI.
2. Définir le nombre d'instances voulues (la taille du cluster).
3. Sélectionner le VPC et le type d'instance.
4. Cliquer sur le groupe Security Group.
5. Veillez à ce que tout le trafic en provenance du cluster JBoss EAP 6 soit autorisé.
6. Définir les autres restrictions suivant les besoins.
7. Ajouter ce qui suit dans le champ User Data :

   Exemple 24.7. Exemple de champ de données utilisateur

   ## 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>
   
   ## password to access admin console
   JBOSSAS_ADMIN_PASSWORD=<your password for opening admin console>
   
   ## 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 ####
   PORTS_ALLOWED="1024:65535"
   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 sample application from local filesystem
   deploy --force /usr/share/java/jboss-ec2-eap-samples/cluster-demo.war
   
   ## ExampleDS configuration for MySQL database
   data-source remove --name=ExampleDS
   /subsystem=datasources/jdbc-driver=mysql:add(driver-name="mysql",driver-module-name="com.mysql")
   data-source 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}"
   /subsystem=datasources/data-source=ExampleDS:enable
   /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool
   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