New Catalog Items
1. Create the locator service as follows
1.1. Define it as follows
1.2. Set properties as follows
1.3. Add INSTALL script as shown below
#!/bin/sh # Import global conf . $global_conf set -e #To support ubuntu java bins export PATH=$PATH:/usr/java/jre-vmware/bin mkdir -p $install_path java -Dsqlfire.installer.directory="$install_path" -jar `basename "$SQLFire102_Installer"` cd $install_path/*SQLFire* mkdir locator ./bin/sqlf locator start -peer-discovery-address=$locator_ip -peer-discovery-port=$locator_port -client-bind-address=$locator_ip -client-port=$client_port -dir=locator
2. Create a SQLFire server service
2.1. Define it as follows
2.2. Set properties as follows
2.3 Add install script as shown below
#!/bin/sh # Import global conf . $global_conf set -e #To support ubuntu java bins export PATH=$PATH:/usr/java/jre-vmware/bin mkdir -p $install_path java -Dsqlfire.installer.directory="$install_path" -jar `basename "$SQLFire102_Installer"` cd $install_path/*SQLFire* mkdir server1 ./bin/sqlf server start -dir=server1 -client-port=$client_port -client-bind-address=$server_ip -locators=$locator_ip[$locator_port]
Blueprint using the Catalog Items above
The catalog items are simply added to the templates as needed. From the image below we have one locator VM and a cluster of SQLFire server node VM's as well. This enables us to create as many SQLFire member nodes as needed.
From the screen shot below it shows how we determine the locator IP address as well as the SQLFire server node IP address at runtime as we need that to be injected in for us before the lifecycle INSTALL phase is started.
