To configure Sybase database monitoring, we will require ASE Monitoring Server (not the ASE) to be installed on the Controller (refer to “How does the monitoring work in LoadRunner?” for monitoring concepts). Furthermore, we will require an additional DLL in Controller for it to work. From the Monitor Reference, the DLL is named, libct.dll. That is for version 12. While in version 15, it’s named libsybct.dll. ASE in short for Adaptive Server Enterprise is a database product from Sybase. To get the latest copy of the ASE server can be obtained from the Sybase website.

• Downloading the installation requires the registration with Sybase. Registration process is hassle-free without any approval needed and you will be able to proceed with download once the registration completes.
• Upon full installation, all components are installed which includes the ASE database and the ASE Monitoring Server. Sample databases are provided in this installation if you required them.
• Both servers are not started by default. Therefore, you will need to configure them and start them up manually.
• To start the server go to START > Programs > Sybase > Adaptive Server Enterprise > Server Config.
• To start the ASE Monitoring Server, go to Service of Windows and find Sybase MONServer_<ASE Monitoring Server Name>.
• Alternatively, the ASE Monitoring Server can be booted from configuring the ASE Monitoring Server. Details for booting the ASEMS can be found in the additional resources.

NOTES

• Controller uses ASE Monitoring Server to monitor and not ASE and therefore, there is a need to ensure the ASE Monitoring Server is started, properly configured and accessible by the Controller.
• Login information to configure the ASE and ASE Monitoring Server are; Login: sa, Password: <blank>
• There maybe a difference of the filenames for the DLLs being used by ASE Open Client Connectivity. The filenames in v15 is libsybct.dll as compared to libct.dll in v12.
• Replacing the file libct.dll with a renamed libsybct.dll (libsybct.dll renamed to libct.dll) in the Controller does not have any impact to the monitoring.
• When configuring the ASE Monitoring Server in the Controller, in the Monitored Server Machines, put the machine name on the network (not the Sybase ASE server itself). In the Resource Measurements on the server machine, put the ASE Monitoring Server name (not the Sybase ASE server itself)

TROUBLESHOOTING

• After installing the Sybase ASE. Ensure that monitoring can be performed by the ASE Monitoring Server on the local machine. Use the Sybase Central console to perform the previous mentioned, by adding the “Monitor” folder. If the monitoring failed, it maybe the case that the ASE Monitoring Server is not started or configured properly. From here, troubleshoot accordingly.
• If monitoring was successful from ASE Monitoring Server locally, use dsedit tool from Sybase client to ensure connectivity.
• If dsedit tool locates the ASE and ASE Monitoring Server successfully, but connectivity fails when connecting via Controller, there might be a configuration problem on the Controller-side.

ADDITIONAL RESOURCES

• http://www.sypron.nl/main.html -Webpage that contains Sybase ASE information.
• http://www.sypron.nl/get_ase_soft.html – Download information for Sybase ASE
• http://www.sybase.com/ase_1500devel – Downloading Adaptive Server Enterprise version 15.0 Developer’s Edition
• http://www.isug.com/Sybase_FAQ/ASE/section1.6.html#scview – Information on ASE Monitoring Server
• http://manuals.sybase.com/onlinebooks/group-as/asg1250e/monbook – Monitoring Server; Information on methods of booting the ASE Monitoring Server.