With CA Service Desk Manager (CA SDM) Advanced Availability architecture, which server should be used for integrations (e.g. web services), Background Server or Application Server?
search cancel

With CA Service Desk Manager (CA SDM) Advanced Availability architecture, which server should be used for integrations (e.g. web services), Background Server or Application Server?

book

Article ID: 11424

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

With CA Service Desk Manager (CA SDM) Advanced Availability architecture, which server should be used for integrations (e.g. web services), Background Server or Application Server?

Environment

ServiceDesk 12.9, 14.x and 17.xAll Supported Operating Systems

Resolution

In an Advanced Availability architecture, integrations (e.g. web services) should be done with an Application server. This is because, during a failover, the Background server will not be available.  In addition, only the CA SDM Administrator will be able to login to the Background server. 

An integration which refers to the Application Registration table in an Advanced Availability architecture, will require an update to the ca_application_registration table to point to the application server URL to avoid unavailability of the Service Desk server during and after a failover. 

Integrations such as CA IT Asset Manager (CA ITAM), CA Service Catalog , and CA PAM refer to this table to get the CA SDM server name and it will be used during context launch from these products. By default, the table will be updated with the Background server for CA SDM. In case of a failover, this URL will not be valid and thus context launch from other products will not work. Therefore, the URL of the CA SDM product has to changed to the Application server URL or a load balancer URL to avoid unavailability of CA SDM server during and after a failover.

 

Additional Information

Considerations for Advanced Availability