I'm trying to archive old instances from CA Service Catalog integration before upgrade to 4.2 SP2.
1 - Created a process to archive all instances, changing autoarchive value to 1 using ControlInstance Calls
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:itp="http://www.ca.com/itpam"> <soapenv:Header/> <soapenv:Body> <itp:controlInstance> <itp:auth> <itp:user>USERNAME</itp:user> <itp:password>PASSWORD</itp:password> </itp:auth> <itp:instanceId>INSTANCE</itp:instanceId> <itp:action>archive</itp:action> </itp:controlInstance> </soapenv:Body></soapenv:Envelope>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <controlInstanceResponse xmlns="http://www.ca.com/itpam"> <actionStatus>The archive action was successfully executed.</actionStatus> </controlInstanceResponse> </SOAP-ENV:Body></SOAP-ENV:Envelope>
2 - After that, I verify the policies to grant Archive configuration
3 - But the instances keep at c2oruntimeobjects table.
Did I making anything wrong?
It is difficult to determine what is wrong based on the information provided. I might recommend you open a support case to help investigate, but here are couple things to note:
1. Those Policy values for archiving and purging are set at runtime, so they retain the policy configuration that was set when each instance was initially started. Please see Knowledge document Discussion of Archive and Purge configuration for further details on the various archive and purge settings.
2. Prior to version 4.2 SP2 there were a number of code issues that prevented the archive and purge from working properly
Does archiving work if you go onto the Operations tab, select a process instance, Right Click and select Archive?
Thank you Michael,
Yes, archiving work if i use the button and tried to restart PAM to refresh the Archiving Policies, but nothing changed.
I will open a case about that. I'll post the answer here if I had some luck
Good, so it sounds like archiving is working to some extent.
The archive settings in the Policy only effect instances started after the change was saved, any and all instances run prior to a change to these policies retain the older original policy and may explain to some degree why you are not seeing them archived.
That being said, the best action I can recommend is to upgrade to 4.2 sp2, where we have reworked the archiving engine and resolved the issues within the orchestrator that impacted archiving. We still see archiving issues when an instance is launched from Catalog but that is due to Catalog setting autoarchive=false for all instances meaning that they will never be automatically archived and must be archived manually through the Operations tab.