Troubleshooting archiving of CI associations

In the Mid Tier interface, when you archive tickets, the application archives only the ticket data and not any ticket CI associations. Therefore, you might encounter performance issues when you access an existing ticket that relates to one or more CIs. Use this information to troubleshoot and resolve the problem. 

You must have administrator access to the application.

Issue symptom

You encounter performance issues when you access an existing ticket.

Issue scope

You try to access an existing ticket that relates to one or more CIs.

Resolution

1. Launch the browser and enter the URL: http://<hostName:portNumber>/arsys/forms/<serverName>/MSM:MigrationTasks
   where hostName is the name of the webserver on which Mid Tier is running, and serverName is the name of the server on which AR System server is running.
   
2. In Task Tag Group, enter ITSM-CMDB Trigger Related Archive, and click Search.
3. From the search results, select the application that has a lot of CI associations. 
4. From Migration Status, select Executing.
5. Click Save.
6. From the menu, click Home.
   
7. In the navigation pane, click Applications, and then select AR System Administration > AR System Archive Manager Console.
8. From Archive Policies, select Archive Legacy Unarchived CMDB Relationship to ITSM tickets.
   
   
9. Click Enable Policy.
10. Enter the number of days in the Age in Days box, and then click Apply.
    Age in Days indicates the number of days after which data is archived.
11. Select the ticket for which you want to enable the archiving policy.
    For more information, see Archiving data.
    When archive runs, the application also archives the CI associations of the archived tickets.