Version 7.1 Installable Version Release Notes

From LongJump Support Wiki
Revision as of 22:38, 10 March 2011 by imported>Aeric (→‎Customizable Locations for External Files)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Preparing for an Upgrade

Before following the platform upgrade process, upgrade dependent utilities to the minimum levels specified in the Software Requirements.

In addition, these upgrades are highly recommended. Although they are not required, they improve performance and have been heavily tested, so they are certified for use with the platform:

  1. Upgrade of MySQL to version 5.1.47
  2. Upgrade memcached server to 1.4.5, if used

New Platform Functionality

Package Data
It is now possible for ISVs to include Package Data when creating a package. Typically, object records are included, but the mechanism allows for arbitrary kinds of data.
Custom Cron Triggers for Data Policies
ISV Users can now specify custom cron triggers for highly granular scheduling when specifying the Repeating Frequency for a data policy.
Global Tenant Data Sharing
In addition to the standard single-tenant policies, global Tenant Data Sharing Policies make it possible to share Object data with all tenants simultaneously, using Java APIs on the client side to access and manage that data. Learn more: Using the JAVA API to Access Shared Data.
Definable Themes
New GUI themes can be defined, made the default, and added to the selection list.
Learn more: Creating a Theme

Customizing the Wiki

A copy of the Wiki can be customized using these features.

Customizable Brand Name

Put your brand name in Template:Enterprisebrand. Wiki pages are coded using <tt>{{enterprisebrand}}</tt>, so brand-name references are easily customized.

Customizable Locations for External Files

The Wiki points to a variety of external documents. For example: configuration files and code samples. The ability to easily change such locations is highly desirable, both to allow for a local copy of the Wiki and to simplify platform upgrades.

For example, Template:DOCHOST contains a URL that points to the location of external documents. Changing the URL in the template then changes the location from which all such documents are accessed. To make it work, links to external files are coded in the Wiki like this: [{{DOCHOST}}/somefile the file name]. The result is a link like this: the file name.

These customizable locations are used in links:

See also: