Quick Install Guide

Installation Requirements

Hardware Requirements

Application Server	CPU - 64-bit Quad-core AMD Opteron 2214 or better is recommended Memory - 8GB on a 64 bit system is recommended Hard disk capacity - 21GB
Document storage	50GB additional storage recommended for a typical configuration (actual value determined by need) The Hard drives should be in a RAID configuration to withstand hard drive failure. A SAN can be used if it is available.
Database Server	CPU - Quad-core AMD Opteron 880 / Intel 64-bit, or better Memory - 16GB recommended Hard disk capacity - 100GB is recommended for the database(s) and the transaction log. The Hard drives should be in a RAID configuration to withstand hard drive failure. A SAN can be used if it is available.
Database backup	500GB recommended for database and document backups, in a typical configuration (actual value determined by need)

Software Requirements

Installing MySQL Version 8.0.xx

Operating System	RedHat Enterprise Linux Server - Version 7, Version 8 (recommended), or Version 9 Note: For RedHat Enterprise Linux Server, ensure that you perform the steps mentioned in the Additional Step for RedHat article. SUSE Linux Enterprise Server - Version 11 or Version 12 (recommended) CentOS Linux - Release 7 Note: You must change the System Locale Language settings to English USA Windows Server 2016
MySQL Server	MySQL Version 8.0.xx (i.e 8.0.29) (Community Edition or Enterprise Edition) MySQL Commercial or Community Client MySQL Commercial or Community Server MySQL Commercial or Community libraries MySQL Commercial or Community compatibility libraries MySQL Commercial or Enterprise common files If you are a platform user, see Configure the MySQL Server. To know more about MySQL 8 removed functionality, please click here Note: The MySQL RDS version 8 certification with the AgileApps version 10.16 is still in progress. The primary difference between MySQL v8 on-premises and MySQL v8 RDS is the restricted access to the parameters on RDS, which requires certain additional configuration steps to complete the setup and data migration. The deprecated ASC or DESC qualifiers for GROUP BY clauses are removed. This impacts the custom SQL used in the application and results in a database syntax error. It is recommended that the application designer reviews the custom SQL used in the application to adopt MYSQL 8. Java execSQL API REST execSQL Resource SQL Browser SQL Browser
Libraries	Download the third-party libraries and save them in a folder. You may want to integrate them into the system during the installation. Download mysql-connector-java-8.0.29.jar here Note: If mysql j/connector 8 series is used then set below properties in jdbc connection url string scrollTolerantForwardOnly=true Example: Edit below files present in <Install-dir>/profiles/IS_default/configuration/com.softwareagplatform.config.propsloader folder and add scrollTolerantForwardOnly=true in jdbc connection url values in the below listed property files: com.softwareag.catalina.resource.pid-agileappsRN.properties com.softwareag.catalina.resource.pid-agileappsQuartz.properties

Installing MySQL Version 5.7.xx

Operating System	RedHat Enterprise Linux Server - Version 7, Version 8 (recommended), or Version 9 SUSE Linux Enterprise Server - Version 11 or Version 12 (recommended) CentOS Linux - Release 7 Note: You must change the System Locale Language settings to English USA Windows Server 2016 Rocky Linux
MySQL Server	MySQL Version 5.7.xx (Community Edition or Enterprise Edition) MySQL Commercial or Community Client MySQL Commercial or Community Server MySQL Commercial or Community libraries MySQL Commercial or Community compatibility libraries MySQL Commercial or Enterprise common files If you are a platform user, see Configure the MySQL Server.
Libraries	Download the third-party libraries and save it in a folder. You may want to integrate them into the system during the installation. Download mysql-connector-java-5.1.24-bin.jar here. Download jta.jar here

Required for Basic Platform Functionality

Mail Server	Mail Server Configuration Choose any postfix, sendmail or so on. Run the mail server on TCP Port 25 The mail server should always be up and running for the platform functionality to work as expected Test and verify the Mail Server MTA (Mail Transfer Agent) with the following command: echo "test mail" | mail -s "hello" admin-name@myserviceproviderdomain.com An email message should be received at the specified address. If the confirmation message does not arrive, check the mail log to discover the cause.
Cache	Memcached 1.4.10 for caching Downloaded Memcached from http://memcached.org/ Memcached requires installation of libevent library version 2.0.16 (An event notification library) for your Operating System. It can be downloaded from http://www.monkey.org/~provos/libevent/. For more information, see Configuring memcached. Ehcache for caching Ehcache is available in the Common Tomcat profile. For more information, see Configuring Ehcache.
Web Server	Apache HTTP server 2.2.21 (Optional, but recommended) The Apache web server can be placed in front of the Tomcat appserver to deliver static content more efficiently. It is recommended for systems with large numbers of Static Resources and Documents The following modules must be compiled into Apache during installation: mod_proxy mod_ssl mod_expires mod_headers For more information, see Installing and Configuring Apache for Use with the Platform.
Java	The installation and operation of the AgileApps Cloud platform requires Java 8. However, 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.
Browser Support	Application excluding Process Internet Explorer 11 Microsoft Edge Firefox 32 (Minimum requirement) Chrome 48.0.2564 (Minimum requirement) Process Model Does not support Internet Explorer Does not support Microsoft Edge Firefox 32 (Minimum requirement) Chrome 48.0.2564 (Minimum requirement) As part of the security processes, the Remember me on this computer option is removed from the browser's login page. Important: To edit a Process Model, use Firefox or Chrome. Other browsers may work poorly, or not all. Accessibility Mode requires Firefox

Required for Additional Functionality

OpenOffice (optional)	OpenOffice 3.2.0 or higher This utility is required when generating PDFs from MS Word Document Templates It also used to support one-click viewing of documents, when configured in networking.properties Install the appropriate version of OpenOffice for your system from http://www.openoffice.org/download/ Add the following command to your system startup process: soffice -headless -accept="socket,host=127.0.0.1,port=8100;urp;" -nofirststartwizard Note: If you have a problem with glibc library version incompatibility while installing OpenOffice 3.4.x (for RedHat with version 5.6 and lower), you should download and install OpenOffice 3.20
HornetQ (optional)	HornetQ 2.2.14 The Messaging Server is an optional platform component that: Handles the on-screen notifications to prevent editing collisions when users view the same Case. Get HornetQ from http://www.jboss.org/hornetq/downloads.html. For more information, see Installing the Messaging Server.
Charting Libraries (optional)	Additional libraries are needed to email a chart or a report. For more information, see Install the Chart Handling Libraries.

Application Server Administration

Server Restart Sequence

When an installation employs memcached or the Messaging Server, it is important to follow this sequence when restarting servers:

<syntaxhighlight lang="bash" enclose="div">

1. STOP THE MESSAGING SERVER, if one is running:

/etc/init.d/messaging stop {hornetq-folder}/bin/stop.sh

1. STOP ALL APPLICATION SERVERS
2. On each server:

{install-dir}/profiles/IS_default/bin/shutdown.sh

1. STOP ALL memcached SERVERS
2. On each server:

/bin/memcached -d stop

1. START ALL memcached SERVERS
2. On each server:

/bin/memcached -d start -p {port} -u {user} -m {MB_of_memory}

  # Typical values:
  #    Port: 11211,  User: root,  MB of memory: 25

1. START ALL APPLICATION SERVERS
2. On each server:

{install-dir}/profiles/IS_default/bin/startup.sh

1. START THE MESSAGING SERVER, if you're running one:

{hornetq-folder}/bin/start.sh /etc/init.d/messaging start </syntaxhighlight>

Considerations

• Stopping application servers ensures that they aren't adding entries to the cache.
• Stopping memcached makes sure that the cache is flushed.
• Those two steps can occur in either order. It is the next two for which order is critical:

• Restarting memcached first makes sure that a clean copy of the cache is available.
• When the application servers come up, they use the clean cache.

Start the Application Server

1. Login as root
2. {install-dir}/profiles/IS_default/bin/startup.sh

Restart the Application Server

1. Login as root
2. {install-dir}/profiles/IS_default/bin/restart.sh

Stop the Application Server

To stop the application server, you kill the Apache Tomcat container it's running in.

1. Login in as root
2. {install-dir}/profiles/IS_default/bin/shutdown.sh

Initial Access

Accessing the Application Server

After the application server has been started:

1. Access the Service Provider URL: http://{yourDomain}/networking/Service?t=1&targetpage=ViewPort.jsp:

Where:

• {yourDomain} is the platform domain. For example: yourcompany.com
• Default username and password: Use the credentials you typed into the Software AG installer.

Note: These credentials are only applicable to the on-premise fresh installations of AgileApps and not for AgileApps cloud.

The platform will request that you change your password after you login the first time.

2. Setup the Service Configuration with these required parameters:

Configure the Service Settings and specify Service and Domain names:

Parameter	Description	Typical Value
Service Name	Name of the service provider	Financiocorp Services
Prefix for Service Domain	Optional subdomain name	Allowed characters: a-z, A-Z, 0-9, - (alphanumeric, plus hyphen) Example: service
Service Domain	The Domain Name part of the URL	mydomain.com
Domain URL	Read Only Automatically populated as: Prefix + Service Domain	service.mydomain.com

Creating a Tenant

1. After Login, create a new tenant from a web browser using the URL as follows:
2. https://yourdomain.com/networking/Service?t=2308

   Where yourdomain.com is the name of your domain

You are now ready to begin application development or install an existing applicaton for testing.