Hello Dave,
at first the documents <a href="http://service.sap.com/sapidb/011000358700002365562002E/SAPOSCOL15EXTEN.pdf">SAPOSCOL: Properties, Installation, and Operation</a> and <a href="http://service.sap.com/sapidb/011000358700003240702001E/AGEN47EN.pdf">CCMS Agents: Features, Installation and Usage</a> contain valuable information, starting with an introduction to the programs and also offering detailed information about the special functions such as process and logfile monitoring.
Some hints for installing saposcol and sapccmsr to Non-SAP servers:
Although you don't need to use the directories normally used in an SAP system I would still recommend to create the /usr/sap directory as basis for the work directories of saposcol and sapccmsr (personally I create <i>/usr/sap/bin</i> for the executables, <i>/usr/sap/tmp</i> for the work directory (<i><X>:\usr\sap\prfclog</i> on Windows). Within /usr/sap/tmp the directories <i>procmon</i> and <i>logmon</i> for process and logfile monitoring.
This way the programs can use the default values for the directories.
As the executables are normally not located within the path, sapccmsr needs to know where to find saposcol and its log file. This is necessary to be able to stop and start the saposcol, display its logfile and request the hardware info and system log using transaction OS07. To ensure this functionality you have to create a profile for the agent, including at least the following parameters:
DIR_PERF=/usr/sap/tmp
DIR_WORK_SAPOSCOL=/usr/sap/tmp
exe/saposcol=/usr/sap/bin/saposcol
(directories based on the recommendation given before)
For details about these parameters have a look into the documents mentioned above.
Don't forget to add a carriage return to the last line of the profile when working on Windows (normally I add simply the # as comment into the last line). Otherwise it could happen on windows that the last line is not processed correctly and any parameter written in this last line is ignored
On Windows sapccmsr will be automatically installed as service, saposcol can also be installed as service, e.g. using ntscmgr.exe (can be found in the executable directory of an SAP instance running on Windows).
On Unix, use a script, init.d or whatever to start the programs.
In both cases, sapccmsr has to be registered and started using the profile described above, e.g.
/usr/sap/bin/sapccmsr -DCCMS pf=/usr/sap/tmp/agent.pfl
(when registering, replace the option <i>-DCCMS</i> with <i>-R</i>. Especially on Windows you have to use the complete path for both executable and profile when registering sapccmsr. Otherwise these files will not be found when started as service.
Something else? Don't know. This should be enough information to get agent and saposcol running (could be quite worth a blog
Regards, Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.