File Access Manager Services start/stop process

[#1]

Often File Access Manager servers hosting several FAM services need to be rebooted during applying an OS level patch (or) FAM services on those servers have to be restarted after patching the service, applying an efix and for any other unknown reason, the service/server has to be rebooted to address the issue.

Its imperative that these servers need to be shut down and restarted in a specific order to ensure proper connectivity between services after the restart.

Shutdown Sequence

These services may be running individually on their own dedicated File Access Manager servers, or may be on servers with shared services. These services or servers running these services must be shut down in the order shown below.

 Note: Disregard services that are not found in your environment, and proceed to the next service in the order shown here.

1. Activity Monitors

2. Permission Collectors and Data Classification Collectors

3. Central Permission Collection and Central Data Classification

4. RabbitMQ

5. EventManager and IIS

6. Core and UI Services

7. Elasticsearch

8. Agent Configuration Manager(ACM)

9. Scheduled Task Handler

10. Microsoft SQL Server database

Startup Sequence

Services or servers that were shut down in the order shown above must be restarted in this order.

 Note: Disregard services that are not found in your environment, and proceed to the next service in the order shown here.

1. Microsoft SQL Server database

2. Scheduled Task Handler

3. Agent Configuration Manager(ACM)

4. Elasticsearch

5. Core and UI Services

6. Event Manager and IIS

7. RabbitMQ

8. Central Permission Collection and Central Data Classification

9. Permission Collectors and Data Classification Collectors

10. Activity Monitors

Validation Steps

1. Open the File Access Manager Administrative Client (thick client) and click on the Health Center. The Health Center should show GREEN on all the tabs.

2. Refer to the appropriate application logs to ensure that the services were started without any errors.

3. If the logs show any errors related to connectivity, restart that service through the services.msc window.

4. If you still have difficulty in bringing any services up, contact SailPoint Support for further assistance.