Managing Servers › How to Deploy CMDBf Web Services

How to Deploy CMDBf Web Services

After you install CA SDM, you can deploy CMDBf web services.

Follow these steps:

1. Verify that the web server is up and running.
2. Navigate to the CMDBHOME\sdk\websvc\CMDBF directory.
3. Run deploy_cmdbws.bat.

   The CMDBf web services are deployed and started.

Note: For more information about CMDBf web services depolyment, see the CA CMDB Technical Reference Guide.

How to Restart the CA SDM Servers

Depending on your CA SDM configuration,

• Restart the CA SDM servers in conventional configuration.
• Restart the CA SDM servers in advanced availability configuration.

Restart the CA SDM Servers in Conventional Configuration

For the conventional configuration, you restart the servers in the following order:

Note: To restart a server click Start, Settings, Control Panel, Administrative Tools, Services. Right-click the CA SDM Server and select Start.

1. Restart the secondary server.
2. Restart the primary server.

Restart the CA SDM Servers in Advanced Availability Configuration

For the advanced availability configuration, we recommend that you restart the CA SDM servers in the following order:

Note: To restart a server click Start, Settings, Control Panel, Administrative Tools, Services. Right-click the CA SDM Server and select Start.

1. Restart all Standby Servers.
2. Promote the Standby Server as the New Background Server.
3. Start the Old Background Server.

   When you start the background server, it becomes a standby server.

4. Choose the Less Active Application Server.
5. Restart the Less Active Application Server.
6. Stop the Other Application Server.
7. Start the Application Server.
8. Perform the steps 6 and 7 for the other application servers.

Promote the Standby Server as the New Background Server

Before you stop the background server, promote the standby server (that you have upgraded) as the new background server. If Support Automation is installed with CA SDM, notify the active Support Automation users about the background server shutdown.

Follow these steps:

1. Execute the following command on the background server to notify all active users using Support Automation to save their work:

   sa_server_notifier [-h] | [-q seconds] | [-c]
   

   -h

   Displays the help page.

   -q seconds

   This option notifies a local server (background) to quiesce in a specified time interval. This interval is the number of seconds before the server goes offline. This option cannot be used for a standby server or application server.

   -c

   This option cancels a previously sent quiesce request.

   A pop-up message is displayed to all the active users using Support Automation. This message notifies the users about the server shutdown and the time that is left for the shutdown. The users must save their work and logout within that scheduled time.

2. Execute the following command on the standby server that you wish to promote as the new background server:

   pdm_server_control -b
   

   -b

   Notifies a local standby server to become the background server. The standby server must already be running. If the server is not running, it is started but no failover is performed; to start a failover, run the command again.

   The background server shuts down automatically and the standby server is promoted as the new background server. This change does not affect the end-user sessions. The in-progress updates (if any) are stored and delayed, until the new background server comes online.

Choose the Less Active Application Server

You choose an application server with the least user activity. Run the following command on each application server to choose the one with no or minimal active sessions.

pdm_webstat

Note: This command does not capture the SOAP or REST Web Service sessions.

Stop the Other Application Server

You inform all the active users on an application server to move to the less active application server before you stop it. Ensure that you have restarted the less active application server before moving all the users to it.

Follow these steps:

1. (Recommended) Inform all active Support Automation analysts on the application server which you want to stop, to create a ticket in CA SDM with their session information. This process ensures that the session information is not lost. For example, the Support Automation analyst is in a session with a customer to resolve a hardware issue. In such a case, the Support Automation analyst can create an issue in CA SDM with the session information before the application server shuts down.
2. Send a notification (for example, an email notification) to all the active users on the application server to move to the less active application server that you just restarted. This notification can include the details of the updated application server.
3. Execute the following command on the application server:

   pdm_server_control [-h] -q interval -s server_name
   

   -h

   Displays the help page.

   -q interval -s server_name

   Notifies a local or remote application server to quiesce in a specified time interval.  This interval is the number of seconds before the server goes offline. When using this option without a server_name, the local server is notified to quiesce. This option cannot be used for a background or a standby server.

   A pop-up message is displayed to all the active users on the application server to notify them about the server shutdown and the time left for the shutdown. The users must save their work and logout within that time. The application server stops after the specified time. The users log on to the other application server to resume their work. The Support Automation analyst can refer to the ticket and resume their work.

   The application server is stopped successfully.