Skip to Content

Necessity:


Often IT infrastructure comprises of SAP and non-SAP systems. You will agree that usually SAP is the backbone of the enterprise, but the non-SAP systems or components are equally critical for an end-to-end business process.

Let me provide an example here. Amongst the ERP, CRM, SCM or any other SAP system, you may find a non-SAP Tax software system such as Taxware, Vertex, etc. Also, due to the shared nature of these products, they might run on a separate server. It is this Tax calculation system that is in the critical path and its uptime is equally important.

So, the question now is how do we monitor this equally critical component in our IT landscape? Well, we got multiple choices and one of the obvious choice is use the enterprise monitoring tool(s) (such as IBM Tivoli, CA, BMC, etc). However the SAP Basis Administrators are comfortable with the CCMS tree view of monitoring or receiving alerts in email from the CCMS Central monitoring system. Also, the SAP Basis Administrators need to know first if the Tax system (or any other critical non-SAP system) is getting into Warning or Critical situations. How about if we can let this non-SAP system being integrated into the SAP CCMS monitoring infrastructure?

h1. The Agents:

The SAP monitoring tools, namely SAPOSCOL and SAPCCMS agents are designed to monitor the server and operating system irrespective of whether the server runs an SAP instance or not. And how could it not, or else we wouldn’t have been able to monitor the SCM Livecache, SCM Optimizer, TREX engine and Database instances installed on their own servers without technically any SAP instances on them. The only difference would be that they report back the monitoring data to the SAP SID they belong to.

h1. How-to:

Following paragraphs describe how to setup the SAPOSCOL and SAPCCMS agents on a completely non-SAP system and monitor them via any SAP system (ABAP stack mandatory) or through the Central Monitoring System, which in most typical cases is your SAP Solution Manager system.

h2. Assumption:

Monitored server runs Windows. However, do recognize that this should also works on all operating systems’ for which the SAP agents are available, including 32-bit and 64-bit architectures.

h2. Configuration Steps:

Monitored System:


Create a service for the SAPOSCOL using command: ntscmgr install SAPOsCol -b
%HOSTNAME%\saploc\prfclog\saposcol.exe -p service

    1. Start the services from Windows Services if they are already not running.
    2. h3. Central System / Monitoring System:
  • Login to client 000
  • Create the CSMREG user from RZ21 ->

Technical Infrastructure -> Configure Central System -> Create CSMREG User.

    1. Go to RZ21 and from the menu select Technical Infrastructure -> Configure Central System -> Create the start file CSMCONF for agents
    2. Copy this file onto the C:\usr\sap\prfclog directory along with other files on the monitored machine.
    3. Ensure steps 1 through 5 are complete on the monitored system before continuing from here.

Go to RZ21 and select +Agents for Remote Systems +radio button in the Topology group box to ensure the SAPCCMSR agent for this host is running and connected.

    1. Alternatively you can also check the status of the RFC destination with the hostname of your system that is automatically created as a part of the CCMS agent registration process in steps 7 through 11 in the section “Monitored system” above
    2. Now we will create a Monitor for this host and other hosts.
    3. From RZ20, select +Extras -> +Activate Maintenance Functions
    4. Select change mode
    5. Click on Create button and name the monitor as “Non-SAP Servers” or any other name of your choice
    6. Click on the name you created in #11 above and click on the change button.
    7. This opens up all the available MTEs for monitor. Make sure to select all MTEs with the text having the hostname of your server.

h2. Use Cases:  

Hardware

Hardware information such as CPU, Memory, NIC’s, Disk drives or file systems, etc

OS Monitoring

CPU Utilization, Top Processes, Memory Utilization, Paging rate, Event Viewer / OS SysLog, etc.

Log file monitoring

Using log file templates as mentioned in the help section below, we can scrape for errors in application specific log files. Link to help – http://help.sap.com/saphelp_nw73/helpdata/en/44/917917bec2591be10000000a1553f7/frameset.htm

Auto reaction methods

 Use standard autoreaction methods such as CCMS_OnAlert_Email  as provided in the help (link below) to generate email alerts  [http://help.sap.com/saphelp_nw73/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm | http://help.sap.com/saphelp_nw73/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm]

 

 

 

 

 

h1. Scope for additional functionality:

(not covered in this blog)

With the SAP CCMSPING agents, we can also configure Availability monitoring as described in the help section – http://help.sap.com/saphelp_nw73/helpdata/en/38/9e100dd7980fffe10000009b3810a5/frameset.htm

 

 

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply