Related Repositories

• Base image deployed by this Azure application
• WebSphere traditional cluster
• Liberty on ARO
• Liberty on AKS

Deploy RHEL 8.4 VM on Azure with IBM WebSphere Application Server traditional V9.0.5 single server

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.
7. Install Bicep version 0.7.4 or later.

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 -DvmSize=<vmSize> -DdnsLabelPrefix=<dnsLabelPrefix> -DadminUsername=<adminUsername> -DadminPasswordOrKey=<adminPassword|adminSSHPublicKey> -DauthenticationType=<password|sshPublicKey> -DwasUsername=<wasUsername> -DwasPassword=<wasPassword> -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 one VM and related resources 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
3. To visit servlets of DefaultApplication which is installed in the server by default
   1. Copy value of property snoopServletUrl and open it in your browser
   2. Copy value of property hitCountServletUrl and open it in your browser

Deployment Description

The offer provisions a traditional WebSphere Application Server Base and supporting Azure resources.

• Computing resources
  • A VM with the following configuration:
    • OS: RHEL 8.4
    • JDK: IBM Java JDK 8
    • WebSphere Traditional version: 9.0.5.x.
  • An OS disk and a data disk attached to the VM.
• Network resources
  • A virtual network and a subnet. User can also select to deploy into a pre-existing virtual network.
  • A network security group if user selects to create a new virtual network.
  • A network interface.
  • A public IP address assigned to the network interface if user selects to create a new virtual network.
• Key software components
  • A WebSphere Application Server Base 9.0.5.x installed on the VM with the followings configuration:
    • The WAS_INSTALL_ROOT is /datadrive/IBM/WebSphere/Base/V9.
    • Options to deploy with existing WebSphere entitlement or with evaluation licens.
    • WebSphere administrator credential.
    • Database data source connection if user selects to connect a database.
  • IBM Java JDK 8. The JAVA_HOME is ${WAS_INSTALL_ROOT}/java/8.0.