|Applies To||RSA Product Set: RSA Via Lifecycle and Governance, Identity Management and Governance (formerly Aveksa)|
RSA Version/Condition: 6.8.1 P17, P18, P19, and P20; 6.9.1 P04, P05, P06, and P07
|Issue||The installation of patches, starting with 6.8.1 P17 and 6.9.1 P04, might require additional time to apply due to a change that was made in the persistence of workflow metadata.|
This additional time, which may be significant, is required to verify that the appropriate configuration data is stored in the workflow to ensure consistency during the import/export process. The amount of time needed for this process is dependent on the complexity of the workflows.
|Cause||Starting with 6.8.1 P21 and 6.9.1 P08, a table modification has been provided which helps improve the workflow migration significantly, however, the application of the patch will still be longer based on the number of workflows. |
This code change is needed to verify that the appropriate configuration data is stored in the workflow to ensure consistency during the import/export process.
|Resolution||The time to apply the patch could be significant in the following situation:|
The amount of time it takes to fix the workflow data will vary on the number of workflows (complexity), specifically how many sub-workflows are involved.
To determine the number of workflows involved, run the query below.
In 6.8.1 P21 and higher and 6.9.1 P08 and higher, let the patch application run, which is a one-time performance hit. Once the migration has occurred it will not have to run again.
While applying the patch.sh script (or running the deployed ear), the patch will apply SQL. This is outputted to a file called Run-once.log.
(On jboss this is found here: ./jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log/run-once.log ).
It is in the same directory as aveksaServer.log if the environment is a WAS/WLS system.
The following will be executing at the tail of the run-once.log file while the migration is running:
Start time [Tue Oct 27 10:39:31 EDT 2015]
This is the loop to look for. This will help confirm if the migration is still running and if that is what is taking the time to apply the patch.
|Notes||This article applies ONLY the the versions below.|