Skip to content
CA Service Management - 14.1
Documentation powered by DocOps

Install/Uninstall Options Manager Options

Last update November 8, 2015

Contents

You can install Options when installing CA SDM or can install them later. Some Options are automatically installed when you install the application that uses them.

Install an Option

You install an option from CA SDM. If you are using advanced availability configuration, you can install an option only from the background server. From the application or standby server, you can view the option details after it is installed.

Follow these steps:

  1. Log in to the following server, depending upon your CA SDM configuration:
    • Conventional: Primary or secondary server
    • Advanced Availability: Background server
  2. On the Administration Tab, browse to Options Manager.
    The Option Search page opens.
  3. Search for the option you want to install.
    The Option Detail window opens.
  4. Click Edit.
    The Update Option window opens.
  5. Click Install.
    The Option Detail window displays a refresh message.
  6. Click Refresh.
    The Option Detail window displays the Action Status of the option as "Installed."
  7. Click Close Window.
  8. Depending on your CA SDM configuration,

    Important! Changes in some options do not require you to restart all the servers. Ensure that you read the Server Restart List before restarting any server.
    The Option List displays the updated status of the option when you restart the servers.

You can also install options from the command line using the following script:

$NX_ROOT/bin/pdm_options_mgr -c -b -a pdm_option.inst

Uninstall an Option

You can edit an option to uninstall it. If you are using advanced availability configuration, you can edit an option only from the background server. From the application or standby server, you can view the option details.

Follow these steps:

  1. Log in to the following server, depending upon your CA SDM configuration:
    • Conventional: Primary or secondary server
    • Advanced Availability: Background server
  2. On the Administration Tab, browse to Options Manager.
    The Option Search page opens.
  3. Search for the option you want to uninstall.
    The Option Detail window opens.
  4. Click Edit.
    The Update Option window opens.
  5. Click Deinstall.
    The Option Detail window displays a refresh message.
  6. Click Refresh.
    The Option Detail window displays the Action Status of the option as "Not Installed."
  7. Click Close Window.
  8. Depending on your CA SDM configuration,

    Important! Changes in some options do not require you to restart all the servers. Ensure that you read the Server Restart List before restarting any server.
    The Option List displays the updated status of the option when you restart the servers.

You can also uninstall options from the command line using the following script:

$NX_ROOT/bin/pdm_options_mgr -c -b -a pdm_option.deinst

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.

Server Restart List

Depending upon the CA SDM configuration, restart the following servers:

  • Conventional: Primary server
  • Advanced Availability: Application, Background, and standby servers. The following options do not require you to restart all the servers:
Options Type Options Action
Change Order Category_Defaults, chg_auto_events,
chg_sla
Restart all servers quickly to maintain functionality consistency. Change in these options contains Majic and/ or Spel changes
Email mail_from_address,
mail_login_password,
mail_login_userid,
mail_max_threads,
mail_reply_to_address,
mail_smtp_domain_name,
mail_smtp_hosts,
mail_smtp_host_port,
mail_smtp_security_level
Restart all standby servers and then the current background server.
Issue Mgr iss_auto_events,
Iss_Category_Defaults,
iss_sla
Restart all servers quickly to maintain functionality consistency. Change in these options contains Majic and/ or Spel changes.
LDAP ldap_dn,
ldap_enable_tls,
ldap_group_object_class,
ldap_host,
ldap_port,
ldap_pwd,
ldap_search_base,
ldap_service_type,
ldap_user_object_class,
num_ldap_agents
Restart all standby servers and then the current background server.
Request Mgr Area_Defaults,
auto_events,
cr_sla,
Netres_pty
Restart all servers quickly to maintain functionality consistency. Change in these options contains Majic and/ or Spel changes.
Request-Change-Issue Any_Contact Restart all servers quickly to maintain functionality consistency. Change in these options contains Majic and/ or Spel changes.
Search Engine ebr_cr_where_clause,
ebr_index_queue_timeout,
ebr_iss_where_clause,
ebr_max_qps,
ebr_qps_timeout,
ebr_search_engine_baseport,
ebr_search_engine_host,
ebr_version
Restart all standby servers and then the current background server.
Security force_unique_userid Restart all servers quickly to maintain functionality consistency. Change in these options contains Majic and/ or Spel changes.
Support Automation sa_domsrvr,
sa_primary_domsrvr
Restart all standby servers and then the current background server.
Time-to-Violation ttv_evaluation_delay Restart all standby servers and then the current background server.
Web export_max_fetch_rows No action required. Changes to this option takes effect when the user exports the list.
Web web_wildcard_search Restart all standby servers and then the current background server.
Web Service hmac_algorithm,
rest_webservice_access_duration,
rest_webservice_disable_basic_auth,
rest_webservice_list_max_length,
rest_webservice_list_page_length,
rest_webservice_resources_to_expose,
string_to_sign_fields
Restart all application servers where RESTful Web Services are configured.
Was this helpful?

Please log in to post comments.