Deploy a RHEL 7.4 VM on Azure with IBM WebSphere Application Server ND Traditional V9.0.5 pre-installed

Prerequisites

• Register an Azure subscription
• The virtual machine offer which includes the image of RHEL7.4, IBM WebSphere & JDK is used as image reference to deploy virtual machine on Azure. Before the offer goes live in Azure Marketplace, your Azure subscription needs to be added into white list to successfully deploy VM using ARM template of this repo.
• Install Azure CLI
• Install PowerShell Core
• Install Maven
• Install jq

Steps of deployment

1. Checkout azure-javaee-iaas
   • change to directory hosting the repo project & run mvn clean install
2. Checkout arm-ttk under the specified parent directory
3. Checkout this repo under the same parent directory and change to directory hosting the repo project
4. Build the project by replacing all placeholder ${<place_holder>} with valid values
   • connect to DB2 Server & Elastic Stack

     mvn -Dgit.repo=<repo_user> -Dgit.tag=<repo_tag> -DadminUser=<adminUser> -DadminPwd=<adminPwd> -DvmAdminId=<vmAdminId> -DvmAdminPwd=<vmAdminPwd> -DdnsLabelPrefix=<dnsLabelPrefix> -DconnectToDB2Server=true -Ddb2ServerName=<db2ServerName> -Ddb2ServerPortNumber=<db2ServerPortNumber> -Ddb2DBName=<db2DBName> -Ddb2DBUserName=<db2DBUserName> -Ddb2DBUserPwd=<db2DBUserPwd> -Ddb2DSJndiName=<db2DSJndiName> -DconnectToELK=true -DcloudId=<cloudId> -DcloudAuthUser=<cloudAuthUser> -DcloudAuthPwd=<cloudAuthPwd> -Dtest.args="-Test All" -Ptemplate-validation-tests clean install
     

   • connect to DB2 Server only

     mvn -Dgit.repo=<repo_user> -Dgit.tag=<repo_tag> -DadminUser=<adminUser> -DadminPwd=<adminPwd> -DvmAdminId=<vmAdminId> -DvmAdminPwd=<vmAdminPwd> -DdnsLabelPrefix=<dnsLabelPrefix> -DconnectToDB2Server=true -Ddb2ServerName=<db2ServerName> -Ddb2ServerPortNumber=<db2ServerPortNumber> -Ddb2DBName=<db2DBName> -Ddb2DBUserName=<db2DBUserName> -Ddb2DBUserPwd=<db2DBUserPwd> -Ddb2DSJndiName=<db2DSJndiName> -DconnectToELK=false -Dtest.args="-Test All" -Ptemplate-validation-tests clean install
     

   • connect to Elastic Stack only

     mvn -Dgit.repo=<repo_user> -Dgit.tag=<repo_tag> -DadminUser=<adminUser> -DadminPwd=<adminPwd> -DvmAdminId=<vmAdminId> -DvmAdminPwd=<vmAdminPwd> -DdnsLabelPrefix=<dnsLabelPrefix> -DconnectToDB2Server=false -DconnectToELK=true -DcloudId=<cloudId> -DcloudAuthUser=<cloudAuthUser> -DcloudAuthPwd=<cloudAuthPwd> -Dtest.args="-Test All" -Ptemplate-validation-tests clean install
     

   • connect to neither DB2 Server nor Elastic Stack

     mvn -Dgit.repo=<repo_user> -Dgit.tag=<repo_tag> -DadminUser=<adminUser> -DadminPwd=<adminPwd> -DvmAdminId=<vmAdminId> -DvmAdminPwd=<vmAdminPwd> -DdnsLabelPrefix=<dnsLabelPrefix> -DconnectToDB2Server=false -DconnectToELK=false -Dtest.args="-Test All" -Ptemplate-validation-tests clean install
     

5. Change to ./target/arm directory
6. Using deploy.azcli to deploy

   ./deploy.azcli -n <deploymentName> -i <subscriptionId> -g <resourceGroupName> -l <resourceGroupLocation>
   

After deployment

• If you check the resource group in azure portal, you will see related resources created
• To open IBM WebSphere Integrated Solutions Console in browser for further administration:
  • Login to Azure Portal
  • Open the resource group you specified to deploy WebSphere Cluster
  • Navigate to "Deployments > specified_deployment_name > Outputs"
  • Copy value of property adminSecuredConsole and browse it with credentials you specified in cluster creation
• The WebSphere server will be automatically started whenever the virtual machine is rebooted. In case you want to mannually stop/start/restart the server, using the following commands:

  systemctl stop websphere    # stop WebSphere server
  systemctl start websphere   # start WebSphere server
  systemctl restart websphere # restart WebSphere server