Known Issues › Automatic Touchpoint Recovery does not work for Non-Domain Orchestrators

Automatic Touchpoint Recovery does not work for Non-Domain Orchestrators

Symptom:

Auto recovery of operators does not work on the non-domain orchestrator for the following scenarios:

• If the non-domain orchestrator is configured as a touch point in an environment other than default environment.
• If all the touchpoints, host groups, and Touchpoint groups that are configured in an environment where non-domain orchestrator is configured as a touchpoint other than default environment.

Note: After you log in to the Domain URL, auto recovery of operators works on the domain and non-domain orchestrator, if the non-domain orchestrator is configured as a touchpoint in the default environment.

Solution:

To recover the operators for non-domain orchestrators manually, follow these steps:

1. Log in to CA Process Automation.
2. Navigate to the Configuration Browser and select the environment where the touchpoints are configured.
3. Right-click the Orchestrator and select Recover Operators.

Abort Process User Interface Issue

When you log in CA Process Automation and click the Operations tab, the Process Instances page displays the list of process running in an instance. You abort a number of processes. Now, upon opening the processes that you have aborted, you may find some operators of the aborted processes still in the running state.

Utility to Calculate Upgrade Downtime

The time to upgrade to a new PAM instance is directly proportional to the runtime database volume. Based on the runtime database volume you have within your PAM instance, upgrade may take considerable amount of time. In this release, you can calculate the estimated time to upgrade using the following utility:
\\< CA Process Automation Installation Folder>\<DVD1>\upgradeTimeCalculator.bat.