Removing SPIRepository agent type for database cartridges 6.0.0.10 or higher (4295971)

After completing the upgrade of database cartridges to versions 6.0.1.10 or higher including fixes for Log4j vulnerabilities, files for version 1.2.17 remain under the {fglam}\agents\SPIRepository\{version}\lib directory of the Foglight Agent Manager host.

After upgrading the database cartridges to version 6.0.0.10 or higher, the SPIRepository agents and associated cartridges are no longer required, but may still remain in the environment.

Complete the steps in the following sections in order to remove remaining agents and cartridge folders:

Deactivate and delete SPIRepository type agents

1. From the Agent Status dashboard, search for "SPIRepository".
2. Verify the Type column and select agents of type SPIRepository.
3. Take note of the agent managers hosting the SPIRepository agents.
4. Deactivate and delete the selected agents.

Please note that domain specific agents such as DB_SQL_Server_SPI_Repository, SSAS_SPI_Repository, DB_Azure_SPI_Repository, DB_Oracle_SPI_Repository or DB_MySQL_PI should not be deleted.

Undeploy the SPIRepository agent package from the Agent Managers

1. From the Agent Managers dashboard, select the agent managers that were previously hosting SPIRepository agents.
2. Click on Undeploy Agent Package.
3. Search for "SPIRepository" and select the agent package.
4. Click Next, verify the packages being undeployed and then Finish to proceed.

Disable the SPIRepository_{OS} cartridges

1. From the Cartridge Inventory dashboard, search for "SPIRepository_".
2. Select and Disable the following cartridges:
   • SPIRepository_Windows64
   • SPIRepository_Linux64_suse
   • SPIRepository_Linux64_rhel_centos

    

Please note that the SPIRepository cartridge (non-OS specific) should not be disabled.

Remove leftover cartridge folders

Undeploy of the agent packages should remove files under {fglam}\agents\SPIRepository, but if any remaining directories from SPIRepository agent types are still present in the agent manager host it should be safe to remove. The FglAM process may need to be stopped first.

• {fglam}\agents\SPIRepository

Please contact Support for assistance or clarification regarding this Knowledge Base article.