Enabling Tivoli Storage Manager web client access in a Cluster Environment

If the Tivoli® Storage Manager web client access is needed during a failover condition, you must configure the Tivoli Storage Manager web client acceptor daemon (CAD) associated with the cluster to failover along with the cluster resource.

1. Set up the CAD to manage the web client and scheduler. Tivoli Storage Manager CAD should be set up to manage schedulers as well as web client access. This reduces the number of daemons that need to be configured as cluster applications and thus simplifies the configuration and administration. When a failover occurs, the Tivoli Storage Manager CAD starts on the node that is managing the takeover.
2. Update the managedservices option in the system-options file dsm.sys on each node for each server stanza, as shown below for NodeA

   Servername        clinton_NodeA
   nodename          NodeA
   commmethod        tcpip
   tcpp              1500
   tcps              clinton.sanjose.ibm.com
   tcpclientaddres   nodeA.sanjose.ibm.com
   passwordaccess    generate
   passworddir       /A1/tsm/pwd
   schedlogn         /A1/tsm/dsmsched.log
   errorlogname      /A1/tsm/errorlog.log
   managedservices   webclient schedule

3. Set up the CAD to use a known HTTP port. By default, the CAD uses HTTP port 1581, when available, for the web client access. If this port is not available, the CAD finds the first available port, starting with 1581. In a failover condition of an active-active cluster configuration, a failover cluster host system is probably running multiple instances of the CAD. If default settings are used for the HTTP port, the failover node uses any available port for the CAD being failed over, since the default port is probably in use by the failover host's current CAD processes. This causes problems for the web client associated with the CAD that failed over, as the new HTTP port is not known to the web client users. You might use the httpport option to specify the specific ports for the web client access for each resource. This allows you to always use the same port when connecting from a web browser, independent of the node serving the cluster resource. Add the httpport option in the system-options file (dsm.sys) on each node for each server stanza as follows, making sure that each stanza uses a unique value:

   Servername        clinton_NodeA
   nodename          NodeA
   commmethod        tcpip
   tcpp              1500
   tcps              clinton.sanjose.ibm.com
   tcpclientaddres   nodeA.sanjose.ibm.com
   passwordaccess    generate
   passworddir       /A1/tsm/pwd
   managedservices   webclient schedule
   schedlogn         /A1/tsm/dsmsched.log
   errorlogname      /A1/tsm/errorlog.log
   httpport          1510
   
   
   Servername        clinton_NodeB
   nodename          NodeB
   commmethod        tcpip
   tcpp              1500
   tcps              clinton.sanjose.ibm.com
   tcpclientaddres   nodeB.sanjose.ibm.com
   passwordaccess    generate
   passworddir       /B1/tsm/pwd
   managedservices   webclient schedule
   schedlogn         /B1/tsm/dsmsched.log
   errorlogname      /B1/tsm/errorlog.log
   httpport          1511
   
   
   Servername        clinton_NodeC
   nodename          NodeC
   commmethod        tcpip
   tcpp              1500
   tcps              clinton.sanjose.ibm.com
   tcpclientaddres   nodeC.sanjose.ibm.com
   passwordaccess    generate
   passworddir       /C1/tsm/pwd
   managedservices   webclient schedule
   schedlogn         /C1/tsm/dsmsched.log
   errorlogname      /C1/tsm/errorlog.log
   httpport          1512