Search Engine: Elastic

Article ID: 133172, created on Sep 13, 2018, last review on Sep 13, 2018


APS 2.0 Application subscriptions have been created in OA, then Cloud service has been stopped manually on the Cloud side (Subscriptions were suspended etc). Why subscriptions and corresponding APS 2.0 services are still running in OA? How to fix current inconsistency (completely remove APS 2.0 services of these subscriptions from OA).


Actions made on cloud service side do not assume sending of any requests to OA, it is normal situation. APS application can implement periodic synchronization with the cloud, however this rare functionality always means user/licenses synchronization but not service status itself. We cannot expect that APS application checks cloud service state and creates Cancellation Order if the one is turned off.


So, to stop APS 2.0 service and subscription on the OA side you should turn ON suspended subscriptions in the Cloud and place cancellation Orders. If subscriptions cannot be turned ON on the cloud side Unprovisioning tasks would fail on the OA side. To complete them successfully it will be necessary to created separate ticket to CloudBlue support asking to switch impacted APS 2.0 application to dummy Endpoint server temporary. Note that we recommended you to achieve this goal by means of standard OA functionality, without OA DB intervention that is necessary in case of switching to dummy APS endpoint.

Email subscription for changes to this article
Save as PDF