Enabling discovery of Sybase Dataservers
Dataservers that have /opt/sybase specified as their installation directory and have their startup files at the default location are automatically detected by BMC Database Automation (BDA) without any configuration changes.
BDA can be directed to look for Sybase Dataservers homes in locations other than /opt/sybase by adding HOME entries in the /app/clarity/dagent/etc/sybase_instances.conf file on the agent. For example, if a Sybase Dataserver is installed in /app/clarity/example, the following entry in the sybase_instances.conf file would allow BDA to discover the Dataserver:
In each Sybase Dataserver home on an agent that BDA has discovered or has a HOME entry in the sybase_instances.conf file, it will look for the files that are used to start Sybase Dataservers (referred to as RUN files) in their default location within each home, i.e., $SYBASE/*/install/RUN_* (where $SYBASE refers to the Sybase home directory). If a Sybase Dataserver's RUN file has been moved to some place other than this default location, BDA can still be directed to process that file through adding an INSTANCE entry in the sybase_instances.conf file. For example, if a Dataserver home is in /app/clarity/example but there is also a RUN file that is used to start a server at /home/sybase/startup/RUN_serverName, the following entries in the sybase_instances.conf file would allow BDA to discover all the Sybase Dataservers whose RUN files are in /app/clarity/example/*/install/RUN_* and the Sybase Dataserver started by /home/sybase/startup/RUN_serverName:
HOME /app/clarity/example
INSTANCE /home/sybase/startup/RUN_serverName