Difference between revisions of "Version 10.5 Installable (Oct 2015)"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (63 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 44: | Line 43: | ||
</blockquote> | </blockquote> | ||
== | ==New Installations== | ||
These instructions apply to new installations. To upgrade and existing installation, see the notes that follow. | |||
:* [[Quick Install Guide]] (development, testing, proof-of-concept) | |||
:* [[Platform Installation Guide]] (production installation) | |||
==Upgrade Notes== | |||
< | {{Important|<br>Before upgrading, it is necessary to follow the preparation steps below.}} | ||
=== Upgraded Software Requirements === | |||
:These software requirements have been upgraded: | :These software requirements have been upgraded: | ||
::* MySQL 5.6 | ::* MySQL 5.6 | ||
| Line 62: | Line 56: | ||
{{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.}} | {{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.}} | ||
=== | ===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. The upgrade program then migrates custom JARs to the new server and modifies the server databases for use with 10.5 (the main database and each of the tenant databases). | |||
=== | To upgrade to 10.5: | ||
# [http://agileappscloud.info/aa104/Upgrading_the_Application_Server 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. | |||
#: | |||
# [http://agileappscloud.info/aa104/Stop_the_Application_Server Stop the 10.4 server] | |||
# For safety, do a [[Database Backup and Recovery#Standard Database Backup|Standard Database Backup]]. | |||
#: | |||
# 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.)<br>''Learn more:'' In [http://documentation.softwareag.com/webmethods/wmsuites/wmsuites_vers.htm webMethods documentation page] see the {{wM Ver}} Installation document. | |||
# In the 10.5 <tt>{install_dir}</tt>, create the <tt>aal-update/</tt> folder. | |||
# Download [{{DOCHOST}}/files/update.zip update.zip] | |||
# Unzip it to the 10.5 <tt>{install_dir}/aal-update</tt><br>Several JARs, the update program, and a wrapper script are created. | |||
#: | |||
# Run the update script: | |||
#: <tt>{install_dir}/aal-update/update.sh</tt> | |||
#: Parameters: | |||
#::* <tt>--aal-path {path}</tt> - ''Required''. | |||
#::: Provide the path to the tomcat folder in the 10.4 installation | |||
#::* <tt>move-reportdb-cfg=yes|no</tt> - Default: ''no''. | |||
#::: If there is a redundant database that is used for reporting, enable this option to replicate the configuration in the 10.5 server. | |||
#::* <tt>move-quartz=yes|no</tt> - Default: ''yes''. | |||
#::: Replicate the quartz configuration. Disable this option if you are planning a different configuration. | |||
#::* <tt>move-tomcat-ports=yes|no</tt> - Default: ''yes''. | |||
#::: Replicate the 10.4 configuration of tomcat ports (80 and 443) in the 10.5 server.<br>Disable this option to use the default configuration (8284 and 8283). | |||
: | #: | ||
# When the script finishes, start the 10.5 server: | |||
#: <tt>{install_dir|/profiles/LJP/bin/startup.sh</tt> | |||
# In the event of an error, check: | |||
</ | #* <tt>{install_dir|/profiles/LJP/logs/wrapper.log</tt> | ||
#* <tt>{install_dir|/profiles/LJP/logs/relationals.log</tt> | |||
# When done, proceed to [[Configuring the Application Server]]. | |||
<noinclude> | <noinclude> | ||
[[Category:ISV Release Notes]] | [[Category:ISV Release Notes]] | ||
</noinclude> | </noinclude> | ||
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
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
New Installations
These instructions apply to new installations. To upgrade and existing installation, see the notes that follow.
- Quick Install Guide (development, testing, proof-of-concept)
- Platform Installation Guide (production installation)
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.
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. The upgrade program then migrates custom JARs to the new server and 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
- For safety, do a Standard Database Backup.
- 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
- Unzip it to the 10.5 {install_dir}/aal-update
Several JARs, the update program, and a wrapper script are created. - Run the update script:
- {install_dir}/aal-update/update.sh
- Parameters:
- --aal-path {path} - Required.
- Provide the path to the tomcat folder in the 10.4 installation
- move-reportdb-cfg=yes|no - Default: no.
- If there is a redundant database that is used for reporting, enable this option to replicate the configuration in the 10.5 server.
- move-quartz=yes|no - Default: yes.
- Replicate the quartz configuration. Disable this option if you are planning a different configuration.
- move-tomcat-ports=yes|no - Default: yes.
- Replicate the 10.4 configuration of tomcat ports (80 and 443) in the 10.5 server.
Disable this option to use the default configuration (8284 and 8283).
- 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.