Difference between revisions of "Version 10.4 Installable (Apr 2015)"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (23 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
| | | | ||
'''''See also:''''' | '''''See also:''''' | ||
* [[All Release Notes]] | * [[All Release Notes]] | ||
* [[ | * [[Release calendar]] | ||
|} | |} | ||
==About the Installable Version== | ==About the Installable Version== | ||
| Line 13: | Line 12: | ||
===Platform Functionality=== | ===Platform Functionality=== | ||
<blockquote> | <blockquote> | ||
==== | ====Feature Enhancements==== | ||
: | :This page describes late-breaking features and bug fixes, as well as features of interest to installers. | ||
:See the [[Release Notes]] for other enhancements that have added to the cloud platform since the last major release. | |||
====Bug Fixes==== | |||
:{| border="1" cellpadding="5" cellspacing="1" | |||
| LJP-59 || Validation when field removed from a form is used in a layout rule | |||
|- | |||
| LJP-82 || Reinstalling a package with change to a field's type didn't reset the read-only property | |||
|- | |||
| LJP-89 || Correct sorting issue in Tasks view | |||
|- | |||
| LJP-98 || New dashboard was not visible to all | |||
|- | |||
| LJP-102 || Custom Access Criteria for list view was not applied in combination with other expressions | |||
|- | |||
| LJP-121 || Report presentation in dashboard did not match the actual report | |||
|- | |||
| LJP-126 || Layout rules could not be used to disable Radio buttons | |||
|} | |||
</blockquote> | </blockquote> | ||
<!-- | |||
===Installable Version Functionality === | ===Installable Version Functionality === | ||
These new and changed features are of interest to those who maintain an instance of the platform's installable version: | These new and changed features are of interest to those who maintain an instance of the platform's installable version: | ||
| Line 23: | Line 40: | ||
:descr. | :descr. | ||
:''Learn more:'' [[Feature]] | :''Learn more:'' [[Feature]] | ||
</blockquote> | |||
--> | |||
==Installing and Upgrading== | ==Installing and Upgrading== | ||
| Line 36: | Line 55: | ||
=== Upgrade Notes=== | === Upgrade Notes=== | ||
<blockquote> | <blockquote> | ||
==== Software Requirements ==== | ==== Changes to the Software Requirements ==== | ||
:These software requirements have been upgraded: | :These software requirements have been upgraded: | ||
::* JDK 8 | ::* JDK 8 | ||
::*: '''Note:''' | ::*: '''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. | ::*: 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. | ||
: | ==== Additional Installation Step for RedHat 6 ==== | ||
: | :Installations on RedHat version 6 need to ensure that the 32-bit version of the gcc library is found on the Java path. If the 64-bit version is found, and [[Java Code Governors]] are enabled, a <tt>StaticProbeInstrumenterException</tt> occurs when attempting to compile a Java class in the platform. To eliminate that problem: | ||
:# Login as a root | |||
: | :# Install the 32-bit instrumentation library: | ||
:#: <tt>yum install libstdc++.i686 libstdc++.x86_64</tt> | |||
:# Verify that it is working: | |||
:#* Go to ${TOMCAT_DIR}/bin/instrumentation/os/linux/x86 folder | |||
:#* Execute the binary: /probeinstrumenter <br>You should see usage instructions for the probeinstrumenter. | |||
</blockquote> | </blockquote> | ||
Latest revision as of 06:54, 21 February 2017
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
Feature Enhancements
- This page describes late-breaking features and bug fixes, as well as features of interest to installers.
- See the Release Notes for other enhancements that have added to the cloud platform since the last major release.
Bug Fixes
LJP-59 Validation when field removed from a form is used in a layout rule LJP-82 Reinstalling a package with change to a field's type didn't reset the read-only property LJP-89 Correct sorting issue in Tasks view LJP-98 New dashboard was not visible to all LJP-102 Custom Access Criteria for list view was not applied in combination with other expressions LJP-121 Report presentation in dashboard did not match the actual report LJP-126 Layout rules could not be used to disable Radio buttons
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.
Upgrade Notes
Changes to the Software Requirements
- These software requirements have been upgraded:
- 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.
Additional Installation Step for RedHat 6
- Installations on RedHat version 6 need to ensure that the 32-bit version of the gcc library is found on the Java path. If the 64-bit version is found, and Java Code Governors are enabled, a StaticProbeInstrumenterException occurs when attempting to compile a Java class in the platform. To eliminate that problem:
- Login as a root
- Install the 32-bit instrumentation library:
- yum install libstdc++.i686 libstdc++.x86_64
- Verify that it is working:
- Go to ${TOMCAT_DIR}/bin/instrumentation/os/linux/x86 folder
- Execute the binary: /probeinstrumenter
You should see usage instructions for the probeinstrumenter.
Learn More
- Quick Install Guide (development and testing)
- Platform Installation Guide (production installation)