Difference between revisions of "Version 10.5 Installable (Oct 2015)"
imported>Aeric |
imported>Aeric |
||
| Line 59: | Line 59: | ||
===Upgrading to 10.5=== | ===Upgrading to 10.5=== | ||
This process utilizes an upgrade program to migrate a version 10.4 application server to version 10.5. Before the program runs, a new 10.5 application server is installed, alongside the existing 10.4 server. When the upgrade program runs, it migrates | This process utilizes an upgrade program to migrate a version 10.4 application server to version 10.5. Before the program runs, a new 10.5 application server is installed, alongside the existing 10.4 server. When the upgrade program runs, it migrates custom JARs to the new server, and it modifies the server databases for use with 10.5 (the main database and each of the tenant databases). | ||
To upgrade to 10.5: | To upgrade to 10.5: | ||
Revision as of 20:58, 22 September 2015
Release Notes for the installable version of the AgileApps Cloud platform.
See also:
- Version 10.4 Installable (previous release)
- All Release Notes
- Upcoming Releases
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.
Bug Fixes
- LJP-291: Broken links to the chart-handling libraries in the support wiki were fixed.
- LJP-356: Display an error message when imports are disabled, and an import is attempted.
Installable Version Functionality
These new and changed features are of interest to those who maintain an instance of the platform's installable version:
Standard Installation Process
- An on-premise installation of the AgileApps Cloud platform is accomplished using the standard Software AG installation procedures.
Certificate-based Platform Access
- When the on-premise installation architecture is configured with a certificate-validation server, the platform can be accessed by browsers or by REST APIs without a login step, by supplying an identifying certificate.
- Learn more: Client Certificate Authentication in a private AgileApps Cloud (pdf)
Session Limits
- A new Tenant Capabilities option, Session Limits, enables the Session Management feature for selected tenants.
- Learn more: Session Management
Promotion Codes
- Platform administrators can create promotion codes for new tenants, "sweetening the pot" for a specified period of time to encourage new business.
- Learn more: Promo Code Configuration
Promotion Code APIs
- Along with the new promotion codes comes the ability to manage them using APIs. So it becomes possible to define a custom interface, rather than requiring the sales organization to use the platform admin interface.
- Learn more: REST API:promoCode Resource
Upgrade Notes
Important:
Before upgrading, it is necessary to follow the preparation steps below.
Upgraded Software Requirements
- These software requirements have been upgraded:
- MySQL 5.6
- 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.
Platform Changes to Be Aware Of
- Folder structure changes
- __TBD: Assess impact of these changes. Describe implications.__
- Potential JAR Conflicts
- These JARs have been added. If your platform instance has added similar JARs, there could be conflicts that cause unpredictable behavior.
- __TBD: List added JARs.__
Upgrading to 10.5
This process utilizes an upgrade program to migrate a version 10.4 application server to version 10.5. Before the program runs, a new 10.5 application server is installed, alongside the existing 10.4 server. When the upgrade program runs, it migrates custom JARs to the new server, and it modifies the server databases for use with 10.5 (the main database and each of the tenant databases).
To upgrade to 10.5:
- Upgrade the platform to version 10.4 (the version required to run the 10.5 upgrade script).
- Ensure that the 10.5 Hardware Requirements are met.
- Ensure that the 10.5 Software Requirements#Required for Installation are met.
- Stop the 10.4 server
- Backup the platform database.
- Configure the MySQL Server so it is ready for use.
- Use the standard SoftwareAG installer to install the 10.5 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. - In the 10.5 {install_dir}, create the aal-update/ folder.
- Download update.zip
- __TBD: upload update.zip__
- Unzip it to the 10.5 {install_dir}/aal-update
Several JARs, an application program, and a wrapper script are created. - Run the update script:
- {install_dir}/aal-update/update.sh
- When the script finishes, start the 10.5 server:
- {install_dir|/profiles/LJP/bin/startup.sh
- In the event of an error, check:
- {install_dir|/profiles/LJP/logs/wrapper.log
- {install_dir|/profiles/LJP/logs/relationals.log
- When done, proceed to Configuring the Application Server.
Learn More
- Quick Install Guide (development, testing, proof-of-concept)
- Platform Installation Guide (production installation)