AgileApps Support Wiki

Difference between revisions of "Version 10.0 Installable (Feb 2014)"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
(84 intermediate revisions by the same user not shown)
Line 1: Line 1:
Release Notes for the installable version of the {{EnterpriseBrand}}.
:{| border="1" align="right" cellpadding="5" cellspacing="1"
|
'''''See also:'''''
* [[All Release Notes]]
* [[Release calendar]]
|}
__TOC__
==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.
''See also:''
''See also:''
:* [[Release Notes|Platform Release Notes]] for current version
:* Platform [[Release Notes]]
:* [[All Platform Release Notes]] for prior versions
:* [[All Release Notes]]
:* [[All Installable Version Release Notes]] for current and prior versions
:* [[Quick Install Guide]] (development and testing)
:* [[Platform Installation Guide]] (production installation)
 
==Installation Notes==


==Preparing for a First Installation==
For either a [[Installing and Upgrading the Application Server#First-Time Installation|First-Time Installation]] or [[Installing and Upgrading the Application Server#Upgrades|platform upgrade]], ensure that dependent utilities are at the minimum levels specified in the [[Software Requirements]].
<blockquote>
For [[Installing and Upgrading the Application Server#First-Time Installation|First-Time Installation]] of the Application Server, ensure that dependent utilities are at the minimum levels specified in the [[Software Requirements]].
</blockquote>


==Starting an Upgrade==
===Special Upgrade Instructions===
<blockquote>
This version of the platform installs Tomcat 7.0.47.
====Configure MySQL for Quartz Cluster====
# Before upgrading, back up any custom entries added to <tt>tomcat/webapps/networking/WEB-INF/web.xml</tt>,<br>because that file will be overwritten during the upgrade process.
:If you are running a Quartz Cluster, you need to configure MySQL to set the transaction level to read-committed and the replication mode to row level.
# After the upgrade, add back your custom entries.
: ''Learn more:'' [[Configuring_the_Quartz_Scheduler#Setting_up_a_Quartz_Cluster|Setting up a Quartz Cluster]]
</blockquote>


==Finishing an Upgrade==
<blockquote>
<blockquote>
====Reallocate Application Resources and Republish Packages====
'''Important:'''<br>
In version 9.0, new application resources ([[Objects]], [[Web Tabs]], [[Classes]],  [[Pages]],  [[Static Resources]],  [[Sites]],  and [[Components]]) are always created as part of the current application, and are not automatically available to all applications running in the current tenancy. That arrangement achieves a desirable separation that simplifies application development.
The format of servlet entries that include several URL patterns has changed in Tomcat 7.0.47. With the new format, all of the url patterns are included in single servlet-mapping as shown here:
 
In order to assure backward compatibility, however, the upgrade process from version 8.2 to version 9.0 makes sure that all such resources are made available to every application in the tenancy. That allocation ensured that no applications were broken by the upgrade.
 
But as a side effect, applications published as packages now contain every resource in the tenancy--not just the resources that the application previously included in the package.


Eliminating the side effect is a two step process:
:'''Old:'''
# Reallocate application resources:
::<syntaxhighlight lang="xml" enclose="div">
#:a. Go to '''Settings > Global Resources > Resource Sharing'''
<servlet>
#:b. Click '''[Edit]'''
    <servlet-name>MultiUrlPatternServlet</servlet-name>
#:c. Select each application that will be published as a package
    <servlet-class>com.abc.MultiUrlPatternServlet</servlet-class>
#:d. For each application, go through the list of resources.
</servlet>
#:e. For each resource that is ''not'' supposed to be part of the application package, move the resource from the '''Selected''' list back to the '''Available''' list.
# Republish the package


{{Important|''All'' published packages that will be used for installations need to be re-published after the upgrade. (Older packages will not work with the new version of the platform.)}}
<servlet-mapping>
    <servlet-name>MultiUrlPatternServlet</servlet-name>
    <url-pattern>/a</url-pattern>
</servlet-mapping>


====Update Dependent Utilities====
<servlet-mapping>
:After an [[Installing and Upgrading the Application Server#Upgrades|Upgrade]], it is strongly recommended that you update the JDK and MySQL to these minimum levels:
    <servlet-name>MultiUrlPatternServlet</servlet-name>
::* JDK 7.0, release _06 or higher
    <url-pattern>/b</url-pattern>
::* MySQL 5.5
</servlet-mapping>
:(The platform can be upgraded without updating these utilities, but it has been fully tested with them, both for functionality and for optimum performance.)
</syntaxhighlight>


====Install Open Office====
:'''New:'''
: OpenOffice is now used to generate compound PDF documents from the new Word and PowerPoint [[Print Templates#Print Template Formats|Print Template Formats]].
::<syntaxhighlight lang="xml" enclose="div">
: Before users work with that feature, therefore, OpenOffice needs to be installed and launched at system startup.
<servlet-mapping>
: ''Learn more:'' [[Software Requirements]]
    <servlet-name>MultiUrlPatternServlet</servlet-name>
    <url-pattern>/a</url-pattern>
    <url-pattern>/b</url-pattern>
</servlet-mapping>
</syntaxhighlight>
</blockquote>
</blockquote>


==Notable Changes==
==Installable Version Functionality==
These features are of primary interest to installers.<br>
''See also:'' Platform [[Release Notes]]


===Functional Changes===
<blockquote>
<blockquote>
====Support for Report Subqueries====
====LDAP Integration====
:A new tenant-management capability has been added, to allow for [[Subquery Filters]] in Views and Reports.
:Configure the platform to automatically authenticate users against an LDAP Server when they log in.
:This functionality is resource-intensive, and should not be granted indiscriminately.
:''Learn more:'' [[LDAP Configuration]]


====Packaging Restrictions Removed====
====Global Data====
:Restrictions on the packaging process have been removed, in order to simplify development efforts:
:Data added to a global tenancy can be seen and used by all tenants, with a single point of control for additions, updates, and deletes.
::* Items in a subscribed package, as well as the package itself, can now be republished by any tenant who has package publishing privileges.
:''Learn more: [[Global Data]]
::* In addition, any tenant with the capability to create a package can include system objects, so [[Tenant Capabilities]] no longer includes the ''Package System-Generated Objects'' option.


===="Development Tenancy" Capability Replaced by Sandboxes====
====New Licensing Mechanism====
:The [[Service Provider Settings]] no longer contain a ''Development Tenancy'' option. Instead, [[Sandboxes]] should be used for development, now that packaging restrictions have been removed.
:Beta installers did the installation first and then requested a license. In this production-ready release, a license is obtained first. Supplying it is part of the installation process.
:''Learn more:'' [[Platform License]]
</blockquote>
</blockquote>


===API Changes===
==Platform Functionality==
These features are coming to the cloud soon. But they're in the installable version now.<br>
''See also:'' Platform [[Release Notes]]
<blockquote>
<blockquote>
====Tenant Capability Changes====
==== <font color="purple">''Web Services Production-Ready with these Enhancements!''</font> ====
:A new tag has been added: <tt><subquery_filter></tt>, with values <tt>true</tt> or <tt>false</tt>.
:* External Lookup fields allow users to select a record from an external database.
:''Learn more:'' [[REST API:tenantCapabilities Resource]]
:* Fault-handling paths for Web Services can be defined in a Process
{{:Version 9.0 API Changes}}
:''Learn more:'' [[Web Services]]
 
==== <font color="purple">''Language Packs''</font> ====
: The platform interface can be presented in a variety of different languages, including French, Italian, German, and Spanish, as well as English. The choices available to users are determined by your Company Settings.
:''Learn more:'' [[Company Information#Available Language Settings]]
 
====MIME Types====
: Additional MIME Types can be added to the Apache Web Server configuration, so that documents and [[Static Resources]] are processed properly, when delivered to the end user's browser.
:''Learn more:'' [[Adding MIME Types]]
</blockquote>
</blockquote>
<noinclude>
<noinclude>


[[Category:Installable Version]]
[[Category:ISV Release Notes]]
</noinclude>
</noinclude>

Latest revision as of 07:00, 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.

See also:

Installation Notes

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

Special Upgrade Instructions

This version of the platform installs Tomcat 7.0.47.

  1. Before upgrading, back up any custom entries added to tomcat/webapps/networking/WEB-INF/web.xml,
    because that file will be overwritten during the upgrade process.
  2. After the upgrade, add back your custom entries.

Important:
The format of servlet entries that include several URL patterns has changed in Tomcat 7.0.47. With the new format, all of the url patterns are included in single servlet-mapping as shown here:

Old: 
<servlet>
    <servlet-name>MultiUrlPatternServlet</servlet-name>
    <servlet-class>com.abc.MultiUrlPatternServlet</servlet-class>
</servlet>

<servlet-mapping>
    <servlet-name>MultiUrlPatternServlet</servlet-name>
    <url-pattern>/a</url-pattern>
</servlet-mapping>

<servlet-mapping>
    <servlet-name>MultiUrlPatternServlet</servlet-name>
    <url-pattern>/b</url-pattern>
</servlet-mapping>
New: 
<servlet-mapping>
    <servlet-name>MultiUrlPatternServlet</servlet-name>
    <url-pattern>/a</url-pattern>
    <url-pattern>/b</url-pattern>
</servlet-mapping>

Installable Version Functionality

These features are of primary interest to installers.
See also: Platform Release Notes

LDAP Integration

Configure the platform to automatically authenticate users against an LDAP Server when they log in.
Learn more: LDAP Configuration

Global Data

Data added to a global tenancy can be seen and used by all tenants, with a single point of control for additions, updates, and deletes.
Learn more: Global Data

New Licensing Mechanism

Beta installers did the installation first and then requested a license. In this production-ready release, a license is obtained first. Supplying it is part of the installation process.
Learn more: Platform License

Platform Functionality

These features are coming to the cloud soon. But they're in the installable version now.
See also: Platform Release Notes

Web Services Production-Ready with these Enhancements!

  • External Lookup fields allow users to select a record from an external database.
  • Fault-handling paths for Web Services can be defined in a Process
Learn more: Web Services

Language Packs

The platform interface can be presented in a variety of different languages, including French, Italian, German, and Spanish, as well as English. The choices available to users are determined by your Company Settings.
Learn more: Company Information#Available Language Settings

MIME Types

Additional MIME Types can be added to the Apache Web Server configuration, so that documents and Static Resources are processed properly, when delivered to the end user's browser.
Learn more: Adding MIME Types
Retrieved from "https://agileappscloud.info/aawiki-src/index.php?title=Version_10.0_Installable_(Feb_2014)&oldid=21979"