Revision as of 05:58, May 20, 2020 by Xavier (talk | contribs) (Update with the copy of version: Draft)
Jump to: navigation, search

Architecture

This section contains some examples of deployments of Intelligent Automation framework and validated Database Management System (DBMS) architecture in a high-availability (HA) architecture.

Important

If you wish to install a standalone Messaging Server or a standalone Load Balancer server, then you should delete the existing load balancer component from TomcatMessaging/webapps after installation. For example, if you want a standalone Load Balancer server, then delete the fish-messaging file from TomcatMessaging/webapps.


Important

To ensure a better performance,

  • The database environment should present itself as a single endpoint for each DB. IA does not support connecting to multiple config or reporting databases.
  • The databases are in sync with each other.
  • The database switchover process must be independent and there is no action required from IA for the database switching.


Microsoft SQL Server

This diagram shows a sample deployment of Intelligent Automation framework and validated Microsoft SQL Server in a high-availability (HA) architecture.

GAAP350 Dep Architecture.png

Oracle

This diagram shows a sample deployment of Intelligent Automation framework and validated Oracle in a high-availability (HA) architecture.

GAAP350 Dep HA-Oracle.png
Comments or questions about this documentation? Contact us for support!