How the "Installer" Agent Works:1
. Existing Installer Agent:
• If an "Installer" agent for a specific database type (e.g., SQL Server or Oracle) already exists on any Agent Manager (fglam), the installation tasks will be handled by that existing agent. No new "Installer" agent will be created.
2.
No Existing Installer Agent:
• If there is no "Installer" agent present on an Agent Manager, or if the user has deleted an existing agent, the Database Cartridge will automatically create and activate a new "Installer" agent before any installation tasks begin.
3.
Task Limitation:
• The "Installer" agent can only perform tasks on the specific Agent Manager host where it was created and installed.
High Availability Setup and Design Behaviour:
In a High Availability setup, the design principle of the "Installer" agents of Database Cartridges is such that they are not marked for failover. Key details include:
- The "Installer" agent will only be created or recreated on an Agent Manager host when needed, and only on that specific Agent Manager host.
- This behavior is consistent across both primary and secondary Agent Managers. If needed, a new "Installer" agent will be created on a secondary Agent Manager, but it will only be active on that particular host.
Key Points to Remember:
- The "Installer" agent is created on-demand, per database type, and per Agent Manager host.
- The "Installer" agent does not failover to other Agent Manager hosts in a High Availability setup.
- Deleting the "Installer" agent prompts the system to recreate it as needed.
