Version 10.9 Installable (Oct 2017)

Release Notes for the installable version of the AgileApps Cloud platform.

See also: All Release Notes Release calendar

About the Installable Version

The installable version of the AgileApps Cloud platform allows you to create and manage a private cloud behind your firewall. AgileApps Cloud platform also helps you to set up a public cloud with a shared application and global data.

10.9 platform features and fixes

For more information on new features and fixes, see Release Notes.

Software support

• MySQL 5.7
• JDK 8

For more information, see Software Requirements and Hardware Requirements

New Installation

For new installation, see Quick Install Guide and Platform Installation Guide.

Note: The installation and operation of the AgileApps Cloud platform requires Java 8. But, the custom code in Java Class continues to be validated against Java 6 syntax as the instrumentation engine responsible for monitoring resource utilization works only on Java 6 byte codes.

Upgrading an existing installation

Upgrade options available:

• Version 10.5 to Version 10.9
• Version 10.6 to Version 10.9
• Version 10.7 to Version 10.9
• Version 10.8 to Version 10.9

Upgrade program

AgileApps Cloud uses an upgrade program to update from an existing application server to the target application server. The upgrade program migrates the custom JARs from the existing application server to the target application server.

Note: 10.9 is the target application server.

Prerequisites:

• Set the value for max_allowed_packet property in my.cnf or my.cfg (MySQL configuration files) under [client], [mysqld] & [mysqldump] sections. If you are installing any package through Packages using AgileApps Cloud application, you must have at least 512 MB of RAM or ten times the size of package.
• Verify the privileges to access the database with the username, password, host-name and port as mentioned in the com.softwareag.catalina.resource.pid-agileappsRN.properties file under the target application server. Use the following command to ensure that you have the database access:

mysqldump -u<DB_USER_NAME> -p<DB_PASSWORD> -h<DB_SERVER_HOST_NAME> -P<DB_PORT> db<DB_NUMBER> > db<DB_NUMBER>.sql

For example: mysqldump -uthomas -pthomas-hvmaalind05 -P3306 db1108948326 > db1108948326.sql

Upgrading to 10.9

1. Stop the 10.5 or 10.6 or 10.7 or 10.8 application server.
2. Install the 10.9 application server using SoftwareAG installer. For more information, see webMethods 10.0 Installation documents available on Empower.

Important: Do not run the 10.9 application server after installation. After the installation, the 10.9 application server exists in parallel with the 10.5 or 10.6 or 10.7 or 10.8 application server. Do not initiate the upgrade program.

3. Create a new folder aal-upgrade in the installed 10.9 root directory.

4. Extract upgrade.tar.gz. The extracted folder upgrade is available at {install_dir}/AgileApps/upgrade. The extracted folder consists of three files upgrade.sh,upgrade.jar,upgrade_supported_configurations.txt, and one folder db-upgrade-patches.

5. Move the extracted Upgrade folder to aal-upgrade folder.

6. Provide executable permission to upgrade.sh file.

7. Run upgrade.sh file with mandatory parameters.

Mandatory parameters

1. --aal-path - provide the folder path of the existing application server.

   Example: --aal-path=/{install_dir}/aal-lab/AgileApps10.6

2. --aal-version - provide the version number of the target application server.

   Example: --aal-version=10.9

Non-mandatory parameters

1. --aal-db-backup-folder {-BDF} - provide a path for database backup of all relationals and tenants.

   Example: --aal-db-backup-folder=/{install_dir}/aal-lab/AgileApps10.6_DB_Backup

2. --remote-source {-RS} - provide this option if the source is installed on a remote machine. If you provide the RS parameter, then the upgrade program ignores the --aal-path from the mandatory parameter and a new source path is set.

   Example: --remote-source=no|yes OR --remote-source (~ yes)

Note: If the upgrade program finds RS parameter in the command then the upgrade program copies the required and related configurations from the remote machine to the local machine and upgrades the server. The upgrade program uses Linux SCP command for connecting and transferring the source configurations. This requires you to provide the user credentials to access the remote machine.

3. --enable-quartz {-Q} - This parameter enables quartz configuration in the target application server. This parameter includes the Import, Export and Reports configurations also. Disable this parameter if you are using a different server or node for running the Quartz configuration either by not providing this parameter or by providing the value as ‘no’ for this parameter.

Example: --enable-quartz=no|yes OR --enable-quartz (~ yes)

4. --ignore-db-upgrade {-IDU} - This parameter is for the environment with multiple nodes or servers connected to a centralized database server. Disable the database upgrade for target application server.

Example: --ignore-db-upgrade=no|yes OR --ignore-db-upgrade (~ yes)

Note

• Provide the mandatory parameter’s value separated by equal (=) character. For example, --aal-version=10.8
• Provide the non-mandatory parameters with values ‘yes’ or ‘no’ separated by equal (=) character. For example, --move-reportdb-cfg=yes and --move-reportdb-cfg=no
• You can also provide the non-mandatory parameters without the value ‘yes’. For example, --move-reportdb-cfg
• If you do not mention the non-mandatory parameter, the upgrade utility program does not consider the parameter.
• The values ‘yes’ and ‘no’ are not case sensitive.
• Syntax: {install_dir}/aal-upgrade/upgrade.sh mandatory-param1=val1 mandatory-param2=val2 mandatory-param3=val3 non-mandatory-param4 non-mandatory-param5 non-mandatory-param6. For example: upgrade.sh --aal-path=/home/aal-lab/AgileApps10.6 --aal-version=10.8 --aal-db-backup-folder=/home/aal-lab/AgileApps10.6_DB_Backup --move-reportdb-cfg --move-tomcat-ports --move-quartz
• In case of errors, look at the log messages available at upgrade.log file under aal-upgrade/upgrade/logs..
• After runnning the upgrade.sh file, SummaryReport.txt is generated at aal-upgrade/upgrade/SummaryReport.txt.