Version 10.7 Installable (Oct 2016)

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 platform lets you create and manage a private cloud behind your corporate firewall. It can also be used to set up a public cloud that serves multiple clients--generally with a shared application and global data. This page highlights changes to the installation process, along with features of the new release.

Platform Functionality

New Platform Features

In addition to bug fixes, this release contains features that have been added to the cloud platform, as described in the Release Notes.

New Installations

These instructions apply to new installations. To upgrade and existing installation, see the notes that follow.

• Quick Install Guide (development, testing, proof-of-concept)
• Platform Installation Guide (production installation)

Upgrade Notes

Important: Before upgrading, it is necessary to follow the preparation steps below.

Upgraded software support

The following software versions are supported:

• MySQL 5.7
• JDK 8

Note: While the installation and operation of the platform requires Java 8, custom code in a Java Class continues to be validated against Java 6 syntax -- in part because the instrumentation engine responsible for monitoring resource utilization only works on version 6 byte codes.

Upgrading to 10.7

This process utilizes an upgrade program to migrate a version 10.5 or 10.6 application server to version 10.7. Before the program runs, a new 10.7 application server is installed alongside the existing 10.5 or 10.6 server. The upgrade program then migrates custom JARs to the new server and modifies the server databases for use with 10.7 (the main database and each of the tenant databases).

To upgrade to 10.7:

1. Ensure that the 10.7 Hardware Requirements are met.
2. Ensure that the 10.7 Software Requirements#Required for Installation are met.

3. Stop the 10.5 or 10.6 server
4. For safety, perform Standard Database Backup.

5. Use the standard SoftwareAG installer to install the 10.7 platform, but do not start it, as yet. (It won't run, at this point.)
   Learn more: In webMethods documentation page see the 9.9 Installation document.
6. In the 10.7 {install_dir}, create the aal-update/ folder.
7. Locate update.zip in the AgileApps installation folder.
8. Unzip it to the 10.7 {install_dir}/aal-update
   Several JARs, the update program, and a wrapper script are created.

9. Run the update script:

   {install_dir}/aal-update/update.sh

   Parameters:

   • --aal-path {path} - Required.

   Provide the path to the 10.5 or 10.6 installation

   • move-reportdb-cfg=yes|no - Default: no.

   If there is a redundant database that is used for reporting, enable this option to replicate the configuration in the 10.5 or 10.6 server.

   • move-quartz=yes|no - Default: yes.

   Replicate the quartz configuration. Disable this option if you are planning a different configuration.

   • move-tomcat-ports=yes|no - Default: yes.

   Replicate the 10.5 or 10.6 configuration of tomcat ports (80 and 443) in the 10.7 server.
   Disable this option to use the default configuration (8284 and 8283).

10. Add the below servlet mappings to the web.xml available @ "$INSTALL_DIR/profiles/LJP/workspace/webapps/networking/WEB-INF/ after the closing tag of <servlet-mapping>(</servlet-mapping>) after <url-pattern>/SDAjaxFormSubmit</url-pattern>and attached is the sample for reference

    <servlet>

    <servlet-name>delegateeLogin</servlet-name>

    <servlet-class>com.es.relationals.DelegateeLogin</servlet-class>

    </servlet>

    <servlet-mapping>

    <servlet-name>delegateeLogin</servlet-name>

    <url-pattern>/delegateeLogin</url-pattern>

    </servlet-mapping>

11. When the script finishes, start the 10.7 server:

    {install_dir|/profiles/LJP/bin/startup.sh

12. In the event of an error, check:
    • {install_dir|/profiles/LJP/logs/wrapper.log
    • {install_dir|/profiles/LJP/logs/relationals.log
13. Proceed to Configuring the Application Server.