was-nd-azure-iaas-single-node-v1.0.9

Release Note:

• Change value of message_key to ibm_datetime for Filebeat configuration;
• Include MIT license in source files;
• Update parent pom version and revise createUiDefinition.json to fix arm-ttk test failures;
• Update README.md;

was-nd-azure-iaas-single-node-v1.0.8

Release Note:

• Configure Filebeat so it can distribute WebSphere log to Elastic Service on Elastic Cloud, which is deployed on Azure Platform;
• Replace logStashServer related parameters with cloudId, cloudAuthUser & cloudAuthPwd in CreateUiDefinition.json, parameters.json, mainTemplate.json, install.sh, etc;
• Remove port 22 from network security group for security concern;

was-nd-azure-iaas-single-node-v1.0.5

Release Note:

• Refer virtual machine offer rhel74-was-jdk-preview from Azure Marketplace in imageReference to accelerate deployment of WebSphere application server single node;
• Remove parameters ibmUserId, ibmUserPwd & installKitUri from template solution to simplify user inputs;

was-nd-azure-iaas-single-node-v1.0.3

Release Note:

• Install Filebeat 7.x after WebSphere Application server is deployed to Azure VM
• Enable HPEL (High-Performance-Extensible-Logging) configuration for WebSphere application server
• Enable HPEL Log Viewer as systemd service so it can be automatically started after VM reboot
• Configure Filebeat so it can distribute WebSphere log to ELK Stack

was-nd-azure-iaas-single-node-v1.0.1

Release Note:

• Generate unique strings and append to name of various resources to make them unique
• Download all of script files at the beginning of custom extension deployment instead of the execution phase
• Add adminConsoleUrl to output of deployment
• Create container managed persistence (CMP) connection factory and associate it to the data source

was-nd-azure-iaas-single-node-v1.0.0

Release Note:

• Deploy a RHEL 7.4 VM on Azure with IBM WebSphere Application Server ND Traditional V9.0.5.1 pre-installed
• Setup a default server with default application using Application Server Profile
• Setup secured Admin Console
• Setup data access to the existing IBM DB2 Server if database connection info is provided