Difference between revisions of "Version 10.5 Installable (Oct 2015)"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 49: Line 49:
# Upgrade the platform to [[Version 10.3 Installable|version 10.3]]. That is the only version that supports the upgrade script.
# Upgrade the platform to [[Version 10.3 Installable|version 10.3]]. That is the only version that supports the upgrade script.
# Run the upgrade script.
# Run the upgrade script.
:The <tt>{{TBD|}}</tt> script must be run to prepare for the upgrade. This script must be run before starting the [[Installing and Upgrading the Application Server#Upgrades|platform upgrade]].
:: The <tt>{{TBD|}}</tt> script must be run to prepare for the upgrade. This script must be run before starting the [[Installing and Upgrading the Application Server#Upgrades|platform upgrade]].
:{{TBD|What the upgrade script does}}
:{{TBD|What the upgrade script does}}
==== Upgrading the License ====
{{TBD|Part of preparation or after upgrading? (If after, put an Important| note at top of section.)}}
This release switches to use the standard Software AG licensing mechanism. As a result, old licenses do not carry forward to this version. After upgrading, get a new license from {{TBD|location}}.


==== Other Changes ====
==== Other Changes ====

Revision as of 01:52, 12 February 2015

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

See also:

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.

Installable Version Functionality

These new and changed features are of interest to those who maintain an instance of the platform's installable version:

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

Installing and Upgrading

Ensure that Software Requirements are Met

Before starting either a First-Time Installation or a platform upgrade, ensure that dependent utilities are at the minimum levels specified in the Software Requirements.

<--

Installation Notes

-->

Upgrade Notes

Software Requirements

These software requirements have been upgraded:
  • MySQL 5.6
  • JDK 8

Notepad.png

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.

Preparing for an Upgrade

  1. Upgrade the platform to version 10.3. That is the only version that supports the upgrade script.
  2. Run the upgrade script.
The __TBD__ script must be run to prepare for the upgrade. This script must be run before starting the platform upgrade.
__TBD: What the upgrade script does__

Upgrading the License

__TBD: Part of preparation or after upgrading? (If after, put an Important__ This release switches to use the standard Software AG licensing mechanism. As a result, old licenses do not carry forward to this version. After upgrading, get a new license from __TBD: location__.

Other Changes

  • Folder structure changes
    __TBD: Assess impact of these changes. Describe implications.__
  • Potential JAR Conflicts
    These JARs have been added. If your platform instance has been adding similar JARs, there resulting conflict could cause unpredictable behavior.
  • __TBD: List added JARs.__

Learn More