In Advanced Availability, can visualizer be configured on one application server with the remote SOAP web services on a different application server?
Article ID: 190838
CA Service Desk Manager
In a Conventional (primary, secondary) configuration, it is possible to configure Visualizer on the primary server to use the SDM SOAP web services deployment on a secondary server.
However, in an Advanced Availability configuration for Service Desk Manager (SDM) version 17.2 and below, it is not possible to configure Visualizer on an application server to use the SDM SOAP web services deployment of a different application server.
In fact, when configuring visualizer on an application server using pdm_configure, there is only a single value in the dropdown field that can be selected when specifying the location of the web services server; that value is automatically populated with the local server name.
For example, the first screenshot below shows that "Deploy SOAP Web Services" had not been selected when running pdm_configure on the local application server; the next screenshot shows that visualizer is to be configured and the location of the web services (there is only 1 host name in the Web Host dropdown list); and the last screenshot shows the popup message that is received which indicates that configuring visualizer will automatically deploy web services on the same server.
The limitation is part of the Advanced Availability design of Service Desk Manager (for applicable versions, please see the Environment section).
In an Advanced Availability environment, if Visualizer on a local application server could be set up to use the Service Desk Manager SOAP WebServices of a remote application server, the visualizer on the local server would attempt to use the boplogin session ID that was created on the remote server, which would fail because each server in an Advanced Availability environment has its own boplogin process that cannot be shared across servers.
In a Conventional configuration, the visualizer on the primary server can use a SOAP web services that is deployed on a secondary server because there is a single boplogin process across the servers.
In an Advanced Availability environment, is it not possible to prevent the deployment of SOAP web services if you choose to continue with the configuration of visualizer by pdm_configure by clicking OK on the popup message.
With the versions of the product mentioned, it is not possible to to configure Visualizer on an application server to use the SDM SOAP web services deployment of a different application server.
Although separation of Visualizer and SDM SOAP web services on different application servers is not possible, if there are performance concerns with visualizer on the current application server which is running other components, it may help to dedicate an application server to the Visualizer with its instance of SDM SOAP web services.
The section in the documentation under "How to Configure CMDB Visualizer" on the following page is relevant only to Conventional (primary, secondary) configuration in so far as pointing Visualizer to a remote web services server: 17.2 - How to Configure CMDB Visualizer