Related Repositories

• Base images deployed by this Azure application
  • twas-nd
  • ihs
• WebSphere traditional single server
• Liberty on ARO
• Liberty on AKS

Deploy RHEL 8.4 VMs on Azure with IBM WebSphere Application Server ND Traditional V9.0.5 cluster and IBM HTTP Server V9.0 pre-installed

Prerequisites

1. Register an Azure subscription.
2. The virtual machine offer which includes the image of RHEL 8.4 with IBM WebSphere and JDK pre-installed 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.
3. Install Azure CLI.
4. Install PowerShell Core.
5. Install Maven.
6. Install jq.

Local Build Setup and Requirements

This project utilizes GitHub Packages for hosting and retrieving some dependencies. To ensure you can smoothly run and build the project in your local environment, specific configuration settings are required.

GitHub Packages requires authentication to download or publish packages. Therefore, you need to configure your Maven settings.xml file to authenticate using your GitHub credentials. The primary reason for this is that GitHub Packages does not support anonymous access, even for public packages.

Please follow these steps:

1. Create a Personal Access Token (PAT)

   • Go to Personal access tokens.
   • Click on Generate new token.
   • Give your token a descriptive name, set the expiration as needed, and select the scopes (read:packages, write:packages).
   • Click Generate token and make sure to copy the token.

2. Configure Maven Settings

   • Locate or create the settings.xml file in your .m2 directory(~/.m2/settings.xml).
   • Add the GitHub Package Registry server configuration with your username and the PAT you just created. It should look something like this:

      <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 
                             https://maven.apache.org/xsd/settings-1.2.0.xsd">
       
     <!-- other settings
     ...
     -->
     
       <servers>
         <server>
           <id>github</id>
           <username>YOUR_GITHUB_USERNAME</username>
           <password>YOUR_PERSONAL_ACCESS_TOKEN</password>
         </server>
       </servers>
     
     <!-- other settings
     ...
     -->
     
      </settings>

Steps of deployment

1. Checkout azure-javaee-iaas

   1. Change to directory hosting the repo project & run mvn clean install

2. Checkout arm-ttk under the specified parent directory

   1. Run git checkout cf5c927eaf1f5652556e86a6b67816fc910d1b74 to checkout the verified version of arm-ttk

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

   mvn -Dgit.repo=<repo_user> -Dgit.tag=<repo_tag> -DuseTrial=true -DnumberOfNodes=<numberOfNodes> -DvmSize=<vmSize> -DdmgrVMPrefix=<dmgrVMPrefix> -DmanagedVMPrefix=<managedVMPrefix> -DdnsLabelPrefix=<dnsLabelPrefix> -DadminUsername=<adminUsername> -DadminPasswordOrKey=<adminPassword|adminSSHPublicKey> -DauthenticationType=<password|sshPublicKey> -DwasUsername=<wasUsername> -DwasPassword=<wasPassword> -DselectLoadBalancer=<appgw|ihs|none> -DenableCookieBasedAffinity=<true|false> -DihsVmSize=<ihsVmSize> -DihsVMPrefix=<ihsVMPrefix> -DihsDnsLabelPrefix=<ihsDnsLabelPrefix> -DihsUnixUsername=<ihsUnixUsername> -DihsUnixPasswordOrKey=<ihsUnixPassword|ihsUnixSSHPublicKey> -DihsAuthenticationType=<password|sshPublicKey> -DihsAdminUsername=<ihsAdminUsername> -DihsAdminPassword=<ihsAdminPassword> -DenableDB=<true|false> -DdatabaseType=<db2|oracle|sqlserver> -DjdbcDataSourceJNDIName=<jdbcDataSourceJNDIName> -DdsConnectionURL=<dsConnectionURL> -DdbUser=<dbUser> -DdbPassword=<dbPassword> -Dtest.args="-Test All" -Pbicep -Passembly -Ptemplate-validation-tests clean install

5. Change to ./target/cli directory

6. Using deploy.azcli to deploy

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

After deployment

1. If you check the resource group in azure portal, you will see multiple VMs and related resources specified for the cluster created
2. To open IBM WebSphere Integrated Solutions Console in browser for further administration:
   1. Login to Azure Portal
   2. Open the resource group you specified to deploy WebSphere Cluster
   3. Navigate to "Deployments > specified_deployment_name > Outputs"
   4. Copy value of property adminSecuredConsole and browse it with credentials you specified in cluster creation
   5. Copy value of property ihsConsole and open it in your browser if you selected to deploy IBM HTTP Server before

Deployment Description

The offer provisions a WebSphere Application Server (WAS) ND cluster and supporting Azure resources.

• Computing resources
  • VMs with the followings configurations:
    • OS: RHEL 8.4
    • JDK: IBM Java JDK 8
    • WebSphere Traditional version: 9.0.5.x.
  • Several VMs consisting of a WebSphere Application Server ND 9.0.5.x cluster with the following configurations:
    • A VM to run the WebSphere deployment manager and an arbitrary number of VMs to run the worker nodes of the cluster.
    • Choice of VM size.
    • An OS disk and a data disk is attached to the VM.
  • An IHS VM if user selects to deploy an IHS as load balancer, with the following configurations:
    • Choice of VM size.
    • An OS disk and a data disk is attached to the VM.
• Network resources
  • A virtual network and one or two subnets. User can also choose to deploy into an existing virtual network.
    • Two subnets are required if user selects to deploy an Azure Application Gateway.
    • A network security group if you select to create a new virtual network.
  • Several network interfaces:
    • One network interface for each VM.
    • One network interface created for private endpoint of the stroage account if user selects to deploy an IBM HTTP Server (IHS) as load balancer.
• Load Balancer
  • Choice of IBM HTTP Server (IHS) or Azure Application Gateway.
  • Several public IP addresses:
    • assigned to the network interface of WebSphere deployment manager VM if user selects to create a new virtual network.
    • assigned to the network interface of IHS VM if user selects to create a new virtual network and deploy an IHS as load balancer.
    • assigned to the Azure Application Gateway if user selects to deploy an Azure Application Gateway as load balancer.
  • A Private Endpoint for the storage account if user selects to deploy an IHS as load balancer.
• Storage resources
  • A storage account for VM boot diagnostics, and sharing files if user selects to deploy an IHS as load balancer.
• Key software components
  • A WebSphere Application Server ND 9.0.5.x installed on each VM of the cluster with the following configurations:
    • The WAS_INSTALL_ROOT is /datadrive/IBM/WebSphere/ND/V9.
    • WebSphere administrator credential.
    • Database data source connection if user selects to connect a database.
  • IBM HTTP Server installed on the IHS VM with the following configurations:
    • Options to deploy with existing WebSphere entitlement or with evaluation licens.
    • IHS administrator credential.
  • IBM Java JDK 8. The JAVA_HOME is ${WAS_INSTALL_ROOT}/java/8.0.