Configuration for Remote File Monitoring via (S)FTP
The monitoring of files on remote (S)FTP servers was initially developed for cloud-based applications like SuccessFactors, but works with pretty much any server that runs an (S)FTP server.
This monitoring allows you to monitor files on servers where you cannot install a diagnostics agent and hence cannot monitor directly.
Interface Channel Configuration
Before you can set up the remote file monitoring you have to make sure the following prerequisites are met:
- SAP Solution Manager is running on SAP Solution Manager 7.1 SP 14 or higher
- The remote server where the file is located must run an (S)FTP server
- You have to create an (S)FTP endpoint to this server in Solution Manager
Creating an (S)FTP Endpoint
The easiest way to create an endpoint is via transaction S2S_SETUP in SAP Solution Manager. In the transaction navigate to "Standalone (S)FTP" and create an new endpoint.
Click "Add" to create a new Standalone (S)FTP server. Don't get confused by the labels asking for "Cloud" Services. As mentioned before (S)FTP file monitoring was initially developed for the cloud applications, but it will work with any (S)FTP server.
This activity will create an unspecific system in the LMDB that serves as the shell for the (S)FTP endpoints.
After the creation of the Standalone (S)FTP you have to create endpoint. Click the "Add" button in the table below to create a new endpoint.
Enter the required information. Please make sure that the file you want to monitor is accessible via (S)FTP and the user has the required authorizations. We basically use the same infrastructure as the (S)FTP file transfer (if any) and hence the same user would suffice.
After the endpoint was created you will notice that it has gotten an ID. This ID we will use later on to assign the endpoint to the interface channel.
Available Monitoring Templates
The following template is available to monitor files on remote hosts:
|File (Remote)||This monitor uses a direct native access to the remote (S)FTP server. it is not necessary to have a diagnostics agent installed on the SFTP server. One of the Solution Manager Diagnostics agents will be used during the setup. The diagnostics agent will connect from the Solman network segment, only the access to the remote SFTP server is required (host, port).|
To create a channel select the "File" with the monitoring template File (Remote).
As source or target system you should choose the type Technical System and select the system which is the partner of this interface on premise and the type "Unspecific Managed Object" for the remote server. Don't worry about how the file information is collected just yet. You will later on define which agent you want to use to collect the information.
Monitoring Template “File (Remote)”
|Metric Name||Description||MAI Category||SP|
|Size of File||This metric measures the total size in Byte of the configured file(s).||Performance||7.1 SP14|
|File exists||Availability of configured files||Availability||7.1 SP14|
|Age of File||This metric measures the time (in min) since last modification of the configured file(s).||Performance||7.1 SP14|
After creating the channel you now maintain the files that you want to monitor.
- Endpoint ID: ID of the (S)FTP endpoint created in the basic cloud setup
- File name: the name of the file you want to monitor
- Folder name: The directory on the remote host where the file is located. You cannot use wildcards for this field.
- Group variants?: Group metric variants if more than one file matches the selection criteria.
On the Metric Configuration tab you simply select the metrics you want to monitor.
There are no metric specific parameters to maintain.
For this interface type by default the metrics are collected by the diagnostics agent of SAP Solution Manager. You can see this in the step Activation. Select the metric you want to collect. Under the interface channel table a new panel appears. Make sure you look at the tab "Overview".
The collector context is where you determine the agent to collect the information. As mentioned before by default for remote files SAP Solution Manager is collected. This is the recommended setup and you should leave it this way.
Advanced Configuration for Collector Context
If you want you could select another collector context here, e.g. if you have a specific agent installed on a host or system you want to use or if you need to use another agent because network restrictions on the SAP Solution Manager agents. When you select host or system a drop-down box will appear for you to select the host or system. The host or system do not have to be part of the ICMon scenario, to be selected here.
However to enable another host or system to collect the information you have to move the (S)FTP configuration. Per default when you maintain an (S)FTP standalone server in transaction S2S_SETUP the login and connection information to the (S)FTP server are stored in the scope of the Solution Manager diagnostic agent(s).
The easiest way to enable the complete free selection of agents and systems is to move this configuration to the "Global" scope where it is accessible for all agents.
Note down the information here (you need to know the password for the FTP user as it is not saved in plaintext).
Change back to the "Global" scope and switch to change mode.
In change mode click "Add Property"
Enter the required information and press OK. Repeat this for each of the (S)FTP properties. Make sure to select "Secure Property" when you enter the password.
You new properties are added to the end of the list. Save to push the new properties to all agents.
if you only want to save the properties on a specific agent you could do this as well. It is done the exact same way, just instead of the "Global" scope you select the scope of the agent you want to change.
After saving you can select whatever agent you want in the scope selection of the IF channel activation. Please note, that only hosts and systems that have SMD agents installed make sense obviously.
In the step "Activation" you can also maintain the thresholds for the metrics.