AgileApps Support Wiki Pre Release

Difference between revisions of "Version 10.9 Installable (Oct 2017)"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 11: Line 11:
The installable version of the {{EnterpriseBrand}} allows you to create and manage a private cloud behind your firewall. {{EnterpriseBrand}} also helps you to set up a public cloud with a shared application and global data. Β 
The installable version of the {{EnterpriseBrand}} allows you to create and manage a private cloud behind your firewall. {{EnterpriseBrand}} also helps you to set up a public cloud with a shared application and global data. Β 


===10.9 platform features and fixes===
===10.9 Features and Fixes===
For more information on new features and fixes, see [[Release Notes]]. Β 
For information on fixes, see [[Version 10.9 Platform]]. The following new features are introduced for this release:
==== Certificates in your trustStore ====
:You must have these certificates in your trustStore if you are interacting with the AgileApps Cloud platform through any third party REST services.
:''For more information, see'' [[Certificates in your trustStore]].


===Software support===
==== Enable HTML Sanitization ==== Β 
:* MySQL 5.7
:When this option is selected, it prevents XSS attacks by allowing you to use only the HTML tags and attributes listed in the table. When this option is not selected, all the HTML tags and attributes are allowed and XSS attacks are not prevented.
:* JDK 8
:''For more information, see'' [[Widget Types]].
For more information, see [[Software Requirements]] and [[Hardware Requirements]]


==New Installation==
==== Installing AgileApps Live for Windows ====
For new installation, see [[Quick Install Guide]] and [[Platform Installation Guide]].
: AgileApps Live is now available for Windows. To install AgileApps Live on Windows operating system, see [[Installing AgileApps Live for Windows]]


{{Note|The installation and operation of the {{EnterpriseBrand}} requires Java 8. But, the custom code in Java Class continues to be validated against Java 6 syntax as the instrumentation engine responsible for monitoring resource utilization works only on Java 6 byte codes.}}
==== Create record with specific ID ====
:You can define your own record ID while creating a record through REST. For more information, see [http://agileappscloud.info/aadev/REST_API:record_Resource#Create_record_with_specific_ID Create record with specific ID].


==Upgrading an existing installation==
==== Update a record using filter ====
Upgrade options available:
:You can update a record using filter criteria. For more information, see [http://agileappscloud.info/aadev/REST_API:record_Resource#Update_a_record_using_filter Update a record using filter].
:* Version 10.5 to Version 10.9
:* Version 10.6 to Version 10.9
:* Version 10.7 to Version 10.9
:* Version 10.8 to Version 10.9


===Upgrade program===
==== SQL Parameterized query ==== Β 
AgileApps Cloud uses an upgrade program to update from an existing application server to the target application server.Β 
:To execute the SQL query, you have to provide the parameters in the prepared statement. This parameterized query avoids SQL injection issues. AgileApps Cloud supports parameterized SQL query as well as the plain SQL query. For more information, see [[SQL Parameterized query]]
{{Note|
:* 10.5, 10.6, 10.7, and 10.8 are the existing application servers.
:* 10.9 is the target application server. }}


====Highlights====
==== Capability to trigger business rules when user changes teams ====
:* The upgrade program migrates the configuration changes from an existing application server to the target application server. Changes include the files like '''networking.properties, custom_wrapper.conf, log4j.properties, quartz.properties''' and so on. After the upgrade is complete, a report of the upgrade program is available at '''{install_dir}/aal-upgrade/upgrade/SummaryReport.txt'''.
:webMethods AgileApps Cloud now supports business rule events whenever a user changes memberships to various teams that he or she could be part of. For more information, see [[Event Rules]].
:* The upgrade program takes a backup of the primary databases (db1000, db892085391, db766224774 & relationals) and tenant databases. These databases can be restored if an existing application server needs to be restarted.
:* The program upgrades the primary database and tenant’s database to the target installation by running the required SQL patches.
:* The upgrade program migrates the custom JARs from an existing application server to the target application server by reading the '''β€˜_custom_libs’''' property available at '''{install_dir}/aal-upgrade/upgrade/upgrade_supported_configurations.txt''' file.
{{Note|
* This upgrade utility program must be run on every application server and web server.
* This upgrade utility program does not support the Windows operating system version of the AgileApps Cloud.
}}


====Prerequisites:====
==== Support on Windows 2016 and Suse Linux 12 ====
:* Set a minimum value of 512 MB of RAM or more for '''max_allowed_packet''' property in '''my.cnf''' or '''my.cfg''' (MySQL configuration files) under '''[client]''', '''[mysqld]''' & '''[mysqldump]''' sections. If you are installing any package through [[Packages]] using AgileApps Cloud application, you must have at least 512 MB of RAM or ten times the size of package.
:webMethods AgileApps installation is now supported on Windows Server 2016 and SLES12 operating systems, thus improving both the developer and production environments. For more information, see [[Software Requirements]].
:* Verify the privileges to access the source database with the username, password, host-name and port as mentioned in the '''com.softwareag.catalina.resource.pid-agileappsRN.properties''' file under the target application server. Use the following command to ensure that you have the database access:
::;mysqldump -u<DB_USER_NAME> -p<DB_PASSWORD> -h<DB_SERVER_HOST_NAME> -P<DB_PORT> db<DB_NUMBER> > db<DB_NUMBER>.sql
::For example: mysqldump -uthomas -pthomas-hvmaalind05 -P3306 db1108948326 > db1108948326.sql
:* You must have read, write and execute permissions to the target installation directory {install_dir}.


====Upgrading to 10.9====
==== Refresh of applications in Marketplace ====
#Stop the existing application server.
:webMethods AgileApps Cloud has now refreshed all the existing application templates in the Marketplace and introduced new applications for customers to install in their tenants and customize it as per their requirements. All these applications now come with some sample data, a template external site, and customizable object models. These applications are contributed by the user community and hence not supported by Software AG. There is a new application sample called ComplaintDesk which has speech recognition capability added to the external site. For more information, see [[Community Marketplace]].
#Install the 10.9 application server using SoftwareAG installer. For more information, see '''webMethods 10.1''' Installation documents available on Empower.
{{Important|
*Do not run the 10.9 application server after installation.
*After the installation, the 10.9 application server exists in parallel with the existing application server.
*Do not initiate the upgrade program.}}
:3. Create a new folder '''aal-upgrade''' in the installed 10.9 root directory '''{install_dir}'''.
:4. Extract '''upgrade.tar.gz''' under '''{install_dir}/aal-upgrade''' directory. The '''upgrade.tar.gz''' is available at '''{install_dir}/AgileApps/upgrade'''. The extracted folder consists of three files '''upgrade.sh, upgrade.jar, upgrade_supported_configurations.txt,''' and one folder '''db-upgrade-patches'''.
:5. Provide executable permission to '''upgrade.sh''' file.
:6. Open the '''upgrade.sh''' file available at '''{install_dir}/aal-upgrade/upgrade'''.
:7. Replace the value for the '''libs''' property in '''upgrade.sh'''.
::Existing value:
:::libs="../../AgileApps/lib/commons-cli-1.2.jar:../../AgileApps/lib/commons-lang-2.4.jar:../../AgileApps/lib/log4j-1.2.15.jar:../../AgileApps/lib/pdfbox-1.6.0.jar:../../AgileApps/lib/dom4j-1.6.1.jar:../../AgileApps/lib/jaxen-1.1.1.jar:../../AgileApps/lib/commons-io-1.4.jar:../../profiles/LJP/dropins/mysql-connector-java-5.1.24-bin.jar"
::Replaced value:
:::libs="../../AgileApps/lib/commons-cli-1.2.jar:../../AgileApps/lib/commons-lang-2.4.jar:../../AgileApps/lib/log4j-1.2.15.jar:../../AgileApps/lib/pdfbox-1.6.0.jar:../../AgileApps/lib/dom4j-1.6.1.jar:../../AgileApps/lib/jaxen-1.1.1.jar:../../AgileApps/lib/commons-io-1.4.jar:../../profiles/LJP/dropins/*"
:8. Run the '''upgrade.sh''' file with mandatory parameters.


:: '''Mandatory parameters'''
==== Improvements in Job scheduling ====
:::A. '''--aal-path''' - provide the folder path of the existing application server. Β 
:webMethods AgileApps Cloud now improves the way jobs are scheduled and prioritized for execution on the platform. These architectural changes result in reducing the number of job failures and also consume lesser memory and CPU resources. For more information, see [[Job Scheduler]].
::::Example: '''--aal-path=/{install_dir}/aal-lab/AgileApps10.6'''
:::B. '''--aal-version''' - provide the version number of the target application server.
::::Example: '''--aal-version=10.9'''
:::{{Note|If the aal-version number and the target application server number given in step 2 are not same, errors can occur.}}


:: '''Non-mandatory parameters'''
==== Improvements in UI performance ====
:::A. '''--aal-db-backup-folder {-BDF}''' - provide a path for database backup of all relationals and tenants.
:webMethods AgileApps Cloud has considerably improved the performance of the end-user user interface thus improving the experience for the user. Β 
::::Example: '''--aal-db-backup-folder=/{install_dir}/aal-lab/AgileApps10.6_DB_Backup'''
:::B. '''--remote-source {-RS}''' - provide this option if the source is installed on a remote machine. If you provide the RS parameter, then the upgrade program ignores the '''--aal-path''' from the mandatory parameter and a new source path is set.
::::Example: '''--remote-source=no|yes''' or '''--remote-source (~ yes)'''


{{Note|
===Software support===
*If the upgrade program finds RS parameter in the command then the upgrade program copies the required and related configurations from the remote machine to the local machine and upgrades the server. Β 
:* MySQL 5.7
*The upgrade program uses Linux SCP command for connecting and transferring the source configurations. This requires you to provide the user credentials to access the remote machine.}}
:* JDK 8
::C. '''--enable-quartz {-Q}''' - This parameter enables quartz configuration in the target application server. This parameter includes the Import and Export configurations also. Do not provide this parameter, if you are using a different server or node for running the Quartz configuration.
For more information, see [[Software Requirements]] and [[Hardware Requirements]]
:::Example: '''--enable-quartz=no|yes''' or '''--enable-quartz (~ yes)'''
::D. '''--ignore-db-upgrade {-IDU}''' - This parameter is for the environment with multiple nodes or servers connected to a centralized database server. Disable the database upgrade for target application server.
:::Example: '''--ignore-db-upgrade=no|yes''' or '''--ignore-db-upgrade (~ yes)'''


:: '''Note:'''
==New Installation==
::*Provide the mandatory parameter’s value separated by equal (=) character. For example, '''--aal-version=10.8'''
For new installation, see [[Quick Install Guide]] and [[Platform Installation Guide]]. Β 
::*Provide the non-mandatory parameters with values β€˜yes’ or β€˜no’ separated by equal (=) character. This Note is not valid for '''--aal-db-backup-folderΒ  {-BDF}'''.
::*The values β€˜yes’ and β€˜no’ are not case sensitive.
::*Syntax: {install_dir}/aal-upgrade/upgrade.sh mandatory-param1=val1 mandatory-param2=val2 mandatory-param3=val3 non-mandatory-param4 non-mandatory-param5 non-mandatory-param6. For example:Β  '''upgrade.sh --aal-path=/home/aal-lab/AgileApps10.6Β  --aal-version=10.8Β  --aal-db-backup-folder=/home/aal-lab/AgileApps10.6_DB_Backup'''
::*In case of errors, look at the log messages available at '''upgrade.log''' file under '''aal-upgrade/upgrade/logs'''.


{{Important|
{{Note|The installation and operation of the {{EnterpriseBrand}} requires Java 8. But, the custom code in Java Class continues to be validated against Java 6 syntax as the instrumentation engine responsible for monitoring resource utilization works only on Java 6 byte codes.}}
::*The upgrade utility program does not change the docs directory and temp directory paths of the target application server and points to the paths of the existing application server.
::*To change the path of docs directory and temp directory to a different location, go to Configure Service Settings.}}
:9. Copy the '''keystoreFile''' file from the existing application server to the target application server. The '''keystoreFile''' property is available at '''<EXISTING_10.6_INSTALL_DIR>/profiles/LJP/configuration/com.softwareag.platform.config.propsloader/com.softwareag.catalina.connector.https.pid-8284.properties'''.
:10. Copy the '''@secure.keystorePass''' value from the existing application server to the target application server. The '''@secure.keystorePass''' value is available at '''<EXISTING_10.6_INSTALL _DIR>/profiles/LJP/configuration/com.softwareag.platform.config.propsloader/com.softwareag.catalina.connector.https.pid-8284.properties'''.
:11. Start the 10.9 application server available at '''{install_dir}/profiles/LJP/bin/startup.sh'''
:12. In case of errors, check:
::'''{install_dir}/profiles/LJP/logs/wrapper.log'''
::'''{install_dir}/profiles/LJP/logs/relationals.log'''
:13. For custom configuration, proceed to [[Configuring the Application Server]].
Β 
=====Considerations=====
::* This upgrade program reads the custom libraries like third-party JARs from the '''upgrade_supported_configurations.txt''' file available at '''{install_dir}/aal-upgrade/upgrade''' folder.
::* If you want to copy any custom library (jars) file from the existing application server to the target application server, then update '''_custom_libs''' property. If there are multiple jars, separate the jars with a comma. For example: '''_custom_libs=docx4j-3.3.0.jar,el-api.jar,ehcache-2.10.2.jar'''.
::* If '''--remote-source''' option is provided in the command, you must have theΒ  permission to copy the configuration files from the existing application server present on the remote machine.
::* This program is designed to upgrade a single AgileApps server or multiple AgileApps servers (web servers or application servers) in a cluster which are pointing to the single centralized database (MySQL) server. While running the upgrade program, ensure that you always point to the source database and do not point to any newly installed database.
::* This program assumes that there are no changes in the service domain during the upgrade. However, if there are any such requirements, then this is considered as a manual process. The below mentioned SQL scripts can be followed to change the service domain immediately after running the upgrade program but before starting the target application server.
:::(a)
::::<syntaxhighlight lang="java" enclose="div">
- Update db892085391.NETWORK_ISV_SETTINGS set service_domain_3 = '<NEW_DOMAIN_WITH_PREFIX>' ;
</syntaxhighlight>
:::(b) If you have any prefix in the domain name, like '''sag.agileappscloud.eu''' (here sag is a service domain prefix), this implies the subdomain is enabled. Otherwise, follow next point (point C).
::::<syntaxhighlight lang="java" enclose="div">
- UPDATE db892085391.NETWORK_ISV_SETTINGS set service_domain_prefix = '<DOMAIN_PREFIX>' ;
- UPDATE db892085391.NETWORK_ISV_SETTINGS set service_domain = '<DOMAIN_WITHOUT_PREFIX>' ;
- UPDATE relationals.NETWORK_CUSTOMER set service_domain = replace(service_domain,'<OLD_DOMAIN_WITHOUT_PREFIX>','<NEW_DOMAIN_WITHOUT_PREFIX>');
- UPDATE db892085391.NETWORK_8c5b349851c041a28d19277a12dee8f0 set portal_service_domain = replace(portal_service_domain , '<OLD_DOMAIN_WITHOUT_PREFIX>','<NEW_DOMAIN_WITHOUT_PREFIX>');
</syntaxhighlight>
:::(c) If you do not have any prefix in the domain name, this implies the subdomain is not enabled.
::::<syntaxhighlight lang="java" enclose="div">
- UPDATE db892085391.NETWORK_ISV_SETTINGS set service_domain = '<NEW_DOMAIN_WITH_PREFIX>' ;
</syntaxhighlight>
:::(d)
::::<syntaxhighlight lang="java" enclose="div">
- UPDATE relationals.NETWORK_GLOBAL_PROPERTIES set assets_domain = '<NEW_DOMAIN_WITH_PREFIX>';
</syntaxhighlight>
::* This program does not copy the SSL certificate, its username and password from the existing application server to the target application server and must be done manually, if required.


==Upgrading an existing installation==
For information on upgrading to version 10.9, see [[Upgrading to Version 10.9]].
<noinclude>
<noinclude>


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

Revision as of 08:23, 13 February 2018

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

See also:

About the Installable Version

The installable version of the AgileApps Cloud platform allows you to create and manage a private cloud behind your firewall. AgileApps Cloud platform also helps you to set up a public cloud with a shared application and global data.

10.9 Features and Fixes

For information on fixes, see Version 10.9 Platform. The following new features are introduced for this release:

Certificates in your trustStore

You must have these certificates in your trustStore if you are interacting with the AgileApps Cloud platform through any third party REST services.
For more information, see Certificates in your trustStore.

Enable HTML Sanitization

When this option is selected, it prevents XSS attacks by allowing you to use only the HTML tags and attributes listed in the table. When this option is not selected, all the HTML tags and attributes are allowed and XSS attacks are not prevented.
For more information, see Widget Types.

Installing AgileApps Live for Windows

AgileApps Live is now available for Windows. To install AgileApps Live on Windows operating system, see Installing AgileApps Live for Windows

Create record with specific ID

You can define your own record ID while creating a record through REST. For more information, see Create record with specific ID.

Update a record using filter

You can update a record using filter criteria. For more information, see Update a record using filter.

SQL Parameterized query

To execute the SQL query, you have to provide the parameters in the prepared statement. This parameterized query avoids SQL injection issues. AgileApps Cloud supports parameterized SQL query as well as the plain SQL query. For more information, see SQL Parameterized query

Capability to trigger business rules when user changes teams

webMethods AgileApps Cloud now supports business rule events whenever a user changes memberships to various teams that he or she could be part of. For more information, see Event Rules.

Support on Windows 2016 and Suse Linux 12

webMethods AgileApps installation is now supported on Windows Server 2016 and SLES12 operating systems, thus improving both the developer and production environments. For more information, see Software Requirements.

Refresh of applications in Marketplace

webMethods AgileApps Cloud has now refreshed all the existing application templates in the Marketplace and introduced new applications for customers to install in their tenants and customize it as per their requirements. All these applications now come with some sample data, a template external site, and customizable object models. These applications are contributed by the user community and hence not supported by Software AG. There is a new application sample called ComplaintDesk which has speech recognition capability added to the external site. For more information, see Community Marketplace.

Improvements in Job scheduling

webMethods AgileApps Cloud now improves the way jobs are scheduled and prioritized for execution on the platform. These architectural changes result in reducing the number of job failures and also consume lesser memory and CPU resources. For more information, see Job Scheduler.

Improvements in UI performance

webMethods AgileApps Cloud has considerably improved the performance of the end-user user interface thus improving the experience for the user.


Software support

  • MySQL 5.7
  • JDK 8

For more information, see Software Requirements and Hardware Requirements

New Installation

For new installation, see Quick Install Guide and Platform Installation Guide.

Notepad.png

Note: The installation and operation of the AgileApps Cloud platform requires Java 8. But, the custom code in Java Class continues to be validated against Java 6 syntax as the instrumentation engine responsible for monitoring resource utilization works only on Java 6 byte codes.

Upgrading an existing installation

For information on upgrading to version 10.9, see Upgrading to Version 10.9.