CUSTOMER

SAP Afaria
Document Version: 7 SP05 - 2014-09-03

Server Monitoring
Table of Contents
1 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Viewing the Server Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 Viewing Diagnostic Dashboard Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2 Configuration for Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Configuring Log Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

2.2 Configuring Log Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Server Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Information Collected by Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1.1 Alerts Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1.2 Connections Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1.3 Device Triggered Actions Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.1.4 File Transfers Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.1.5 iOS Connection Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1.6 Messages Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1.7 Policy Delivery Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1.8 Replication Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2 Viewing Additional Server Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

3.3 Exporting a Log View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.4 Viewing the Server Messages Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 Configuration for Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 Viewing Raised Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.2 Acknowledging an Alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

4.3 Deleting an Alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.4 Viewing Pending Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.5 Creating an Alert Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.6 Creating a Contact for Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.7 Configuring an Alert Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.8 Viewing Defined Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

4.9 Creating a New Event for Configuring an Alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

CUSTOMER Server Monitoring

2 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents
1 Server
The Afaria server is the central point for all Afaria operations. In the Afaria Administration console, the Server
page is the landing page for the server dashboard, logs, alerts, configuration, and user roles.

1.1 Viewing the Server Dashboard

Server dashboard lets you monitor and examine current server activity for the Afaria master and farm servers,
such as for current and recent errors or for non-iOS device sessions.

Procedure

1. On the Home page, click Server.

2. On the left toolbar, click Server Dashboard.

1.2 Viewing Diagnostic Dashboard Details

The diagnostic dashboard is a consolidated list of various Afaria operational checks and results. The dashboard
also provides navigation to the configuration page of a diagnostic check.

Context

The diagnostic checks are carried out at regular prescheduled intervals, and the results are stored in the
database. The typical time interval between the checks is five minutes for all the checks, except the Afaria Server
service check, which runs every time the page refreshes.

The diagnostic dashboard retrieves the latest result from the database. The icon associated with a check
indicates the status of the check (passed or failed), and is continuously updated based on the diagnostic status in
the database.

Note
The dashboard checks are specific to each defined tenant.

Server Monitoring CUSTOMER

Server © 2014 SAP SE or an SAP affiliate company. All rights reserved. 3
Procedure

1. On the Home page banner, click Server.

2. On the left toolbar, click Server Dashboard.
3. Select Diagnostics tab and then select a diagnostic check to view the test results.

For any selected diagnostic check, the test result includes:

○ Purpose and limitations of the diagnostic

○ Timestamp of the most recent diagnostic check
○ Estimated time for the next diagnostic check
○ Diagnosis or result of the check
○ Troubleshooting tips for any failed checks
4. (Optional) Click the Configuration icon to open the configuration page for the selected diagnostic.
The configuration label and icon appear only if the selected diagnostic is configurable at the current tenant
level. Some of the items are configurable only at the system tenant level.

Note
Many of the configuration items in the Diagnostics tab are optional. A 'failed' status for such items do not
indicate that they must be configured for the successful operation of Afaria.

CUSTOMER Server Monitoring

4 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Server
2 Configuration for Logging
Configure the type, detail level, and cleanup frequency for Afaria server-side logging.

2.1 Configuring Log Options

Configure the Afaria server-side logging options by type and detail level. By default, all logs are enabled.

Procedure

1. On the Server page, on the left toolbar, click Configuration Server Log Option .
2. Click Disable every log below to disable all logging options or select logs to enable in different areas:

○ Message log – records information, warning, and error messages specific to the server.
○ Replication log – records replication-specific information, warning and error messages.
○ Session log – records information about past sessions, such as the channel involved, the end time and
duration, the user and computer information, and the session event status.
○ Session event detail – records log details at the object level pertaining to File Transfers or Sessions.
○ Device action log – records information about actions occurring on the devices.
○ Alert log – enables the server to log both raised events and closed alerts on your server.

Administrative actions performed by the user is recorded in system logs. The user or role executing the action
is recorded in the log entries by the logged in user.
3. Click Save.

2.2 Configuring Log Cleanup

You can specify how often the SAP Afaria server deletes log files.

Procedure

1. On the Server page, on the left toolbar, click Configuration Server Log Cleanup .
2. Perform one of the following tasks:
a) To enable log cleanup, select the Enable check box and specify the age (in days) at which the SAP Afaria
server deletes the log files in the Number of days field.
b) To disable log cleanup, clear the Enable check box.

Server Monitoring CUSTOMER

Configuration for Logging © 2014 SAP SE or an SAP affiliate company. All rights reserved. 5
 c) To restore log cleanup default settings, click Reset to defaults.
3. Click Save.

CUSTOMER Server Monitoring

6 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Configuration for Logging
3 Server Logs
Logs let you monitor and examine historical server activity for each tenant, such as for raised events and alerts,
device sessions, file transfers, policy delivery, and general operations.

You can view logs of all tenants from a system tenant. On a non-system tenant, you can view logs specific to the
tenant.

3.1 Information Collected by Logs

Each log collects specific information about servers, devices, connections, and policies.

3.1.1 Alerts Log

The Alerts log includes raised events and closed events.

The log includes:

● Raised events – includes the name of the event; computer on which the event occurred; time the event
occurred; time the event was received at the server; any relevant details; component-specific error code
associated with the event; and server that received the event.
● Closed alerts – includes the name of the alert; name of the contact (if any) assigned to the alert; time the alert
was raised, acknowledged, or closed; any closing remarks the contact had about the alert; identification
number assigned to this alert; and server that received the alert.

3.1.2 Connections Log

The Connections log includes information about past sessions for Android, Windows CE, Windows Mobile, and
Windows devices.

An entire session channel set's sendlist processing is aggregated into a single unit and occurs with the first
sendlist instance in the channel set. Therefore, all of the sendlist logging for a channel set occurs with the first
channel in the set that contains a sendlist.

The log includes:

● All – includes all session information such as all attempts to upload or download files, or the status of past
communications sessions.
● All last 24 hours – for sessions run during the previous 24 hours, includes all session information such as all
attempts to upload or download files, or the status of past communications sessions.
● Failed – includes all failed sessions.
● Failed last 24 hours – for sessions run during the previous 24 hours, includes all failed sessions.
● Sorted by Channel last 24 hours – for sessions run during the previous 24 hours, includes all sessions, sorted
by channel.

Server Monitoring CUSTOMER

Server Logs © 2014 SAP SE or an SAP affiliate company. All rights reserved. 7
● Sorted by Channel – includes all sessions, sorted by channel.
● Sorted by Client – includes all sessions, sorted by device or group.
● Sorted by Client last 24 hours – for sessions run during the previous 24 hours, includes all sessions, sorted by
device or group.

3.1.3 Device Triggered Actions Log

The Device Triggered Actions log includes successes or failures for connections initiated by device-side schedules
for Windows Mobile, and Windows devices.

The log includes:

● All – includes all actions and data associated with a device-side schedule. Consider these items about logged
entries:

○ When either the device or a server reside in a time zone that is subject to Daylight Saving Time, it is
possible for the log to reflect a time stamp that is an hour ahead or behind the time the event actually
occurred.
○ Windows computers do not log the connection that was initiated by an enrollment policy's “initial
connection” setting.
● Log only actions – reserved for future use.

3.1.4 File Transfers Log

The File Transfers log includes every instance of the server sending or receiving a file.

The log includes:

● All – includes all file transfer information such as all attempts to upload or download files, or the status of past
communications sessions.
● Failed – includes all failed file transfers or sessions.
● Sorted by Channel – includes all file transfers, sorted by channel.
● Sorted by Client – includes all file transfers, sorted by device or group.

CUSTOMER Server Monitoring

8 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Server Logs
3.1.5 iOS Connection Log

The iOS Connection log captures the timing and sequence of actions occurring between the Afaria enrollment
server and the iOS devices.

3.1.6 Messages Log

The Messages log includes information for monitoring general server operations, and identifying and diagnosing
issues.

The log includes:

● All – includes all actions taken by the server such as features enabled, polices created, and polices edited.
● Errors – includes all errors that occurred at the server.
● Errors in session – includes all errors that occurred at the server, sorted by session.

3.1.7 Policy Delivery Log

The Policy Delivery log records the nature and status of a policy at the device. The ability to capture data may vary
by device type.

3.1.8 Replication Log

The Replication log includes information for replication operations, and identifying and diagnosing issues.

The log includes:

● All – includes all actions and components involved in replication.

● File transfers – includes information about the transfer of data associated with replicated channels.
● Sessions – includes information about each session.

3.2 Viewing Additional Server Logs

View server logs other than the Messages log, such as the File Transfers log or Policy Delivery log.

Context

View additional server logs by selecting a view.

Server Monitoring CUSTOMER

Server Logs © 2014 SAP SE or an SAP affiliate company. All rights reserved. 9
Procedure

1. On the Server page, click Server Log, on left toolbar.

2. Select an item from the list.
3. On the left toolbar, click Select View, to view additional items on the log.

4. On the Home page, on the Server tile, clickServer log to open the Server Log page to the Messages log.
5. On the left toolbar, click Select View to open the Server Log dialog.
6. Select a log from the list, then click Select on the dialog toolbar.

3.3 Exporting a Log View

Export the log list in its current state with any filters or sort applied. You can export to Excel, Word, and CSV.

Procedure

1. On the Home page, on the Server tile, clickServer log to open the Server Log page to the Messages log.
2. (Optional) To export a different log view, on the left toolbar, click Select View and select another log.
3. (Optional) Filter or sort list according to preferences.
4. On the left toolbar, click Export View.
5. Select the content type and the format type, then click OK.

3.4 Viewing the Server Messages Log

View the Messages log, which includes information for monitoring general server operations, and identifying and
diagnosing issues.

Procedure

1. On the Home page, on the Server tile, clickServer log to open the Server Log page to the Messages log.
2. (Optional) Filter or sort list according to preferences.

CUSTOMER Server Monitoring

10 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Server Logs
4 Configuration for Alerts
Alerts increase the visibility of system event that may require your attention.

4.1 Viewing Raised Alerts

View the alerts raised by the server and take actions accordingly.

Context

Alerts provide notification when some incidents arise on the Afaria server, server components, or devices so that
you can acknowledge and resolve them. The Server > Alert page displays detailed information about the alerts
raised by the server.

Procedure

1. On the Home page, click Server.

2. On the left toolbar, click Alert.
3. Select Raised Alert tab to view the list of alerts raised.
4. (Optional) To view additional details related to an alert, select the alert and click Inspect on the top toolbar.

4.2 Acknowledging an Alert

Acknowledge an alert raised to inform others that the alert has been noticed and is being worked on.

Context

Acknowledging an alert does not close it; acknowledging lets others know that steps are being taken to resolve the
alert. Acknowledging the alert stops any response that was defined for the alert, such as paging or sending e-mail
to a contact.

Server Monitoring CUSTOMER

Configuration for Alerts © 2014 SAP SE or an SAP affiliate company. All rights reserved. 11
Procedure

1. On the Server > Alert page, select Raised Alert tab to view the list of alerts raised.
2. Select the alert and click Acknowledge on the top toolbar.
3. In the confirmation dialog box, click Yes, Continue to acknowledge the alert.
The state of the alert changes from Unacknowledged to Acknowledged.

4.3 Deleting an Alert

Delete an alert to remove it from the list of raised alerts when no further action is required on the alert. You can
delete either an acknowledged alert or an unacknowledged alert.

Procedure

1. On the Server Alert page, select Raised Alert tab to view the list of alerts raised.
2. Select the alert and click Delete in the top toolbar.
3. (Optional) In the Server alert > Delete raised alert dialog box, enter any comments you have about deleting
the alert.
4. Click OK.
The alert is deleted from the raised alerts list. The deleted alert details are available in the Alerts Log.

4.4 Viewing Pending Alerts

View alerts for which at least one associated event has occurred.

Context

Alerts having multiple associated events can cause pending alerts, when any one of the events associated with the
alert occurs.

Procedure

1. On the Server Alert page, select Pending Alert tab to view the list of alerts that are pending.

CUSTOMER Server Monitoring

12 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Configuration for Alerts
2. (Optional) To view additional details related to a pending alert, select the alert and click Inspect on the top
toolbar.

4.5 Creating an Alert Definition

Create an alert to define the events and actions related to the alert.

Prerequisites

Before creating an alert, create alert contacts, configure alert response addresses for messages to contacts and
for sending SNMP traps to IP addresses.

Context

No alerts will appear on the Raised Alerts page until you have defined and enabled them.

Procedure

1. On the Server Alert page, select Defined Alert tab to view the list of alerts defined.
2. On the top toolbar, click New to open the Add alert dialog.
3. On the Alert properties page, define an alert’s general properties, such as name and priority, and enable the
alert, if required.
4. On the Assigned events page, assign events that raise the alert by selecting one or more events from the
Available events list and click Add.
You can specify any combination of system-defined and user-defined events to trigger an alert.
You can remove an event from the Assigned events list by selecting it in the Assigned events list box and
clicking Remove.
5. On the Alert response page, indicate how you want the server to respond when an alert is raised.
You can select any of the following options:

○ To contact a person, select the contact name and specify the message to deliver to e-mail or pager.
○ To send an SNMP trap to a server, select Send SNMP trap.
○ To run an executable file, browse and select the file.
6. (Optional) On the Alert threshold page, specify the number of times an event or set of events must occur
during a certain time period to raise an alert.
Select Unlimited to raise the alert if the number is met, without regard to the time period.
7. (Optional) On the Alert response repeat interval page, specify how often you want the system to repeat the
response until the alert is acknowledged and the number of times to repeat the response.

Server Monitoring CUSTOMER

Configuration for Alerts © 2014 SAP SE or an SAP affiliate company. All rights reserved. 13
 Click Unlimited to raise the alert if the number is met, without regard to a time window.
8. Click Save.

4.6 Creating a Contact for Alerts

Create a contact who is responsible for handling raised alerts.

Procedure

1. On the Server Alert page, select Defined Contact tab to view the list of contacts.
2. Click New in the top toolbar.
3. Enter the contact details such as name, pager or mobile number, and e-mail address.
4. Click Save.

4.7 Configuring an Alert Response

Configure an alert response to designate the mail server where your contacts reside or the IP address where you
can forward SNMP traps.

Context

You can configure alert responses from any of the following pages: Defined Alert, Defined Event, or Defined
Contact.

Procedure

1. On the Server Alert page, select Defined Alert, Defined Event, or Defined Contact tab.
2. Click Configure alert response on the top toolbar.
3. In the Server Alert > Configure alert response dialog box, specify a host name for the mail server, or enter an
IP address for forwarding SNMP traps.
4. Click OK.

CUSTOMER Server Monitoring

14 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Configuration for Alerts
4.8 Viewing Defined Events

View the system-defined and user-defined events on the system.

Context

Defined Events page displays the event details such as event name, description, and the component associated
with the event. A component indicates a general category for grouping events based on a functional area of the
product.

Procedure

1. On the Server Alert page, select Defined Event tab to view the list of alerts.
2. (Optional) To view the alert associated with an event, select the event and click Inspect assigned alert on the
top toolbar.

4.9 Creating a New Event for Configuring an Alert

Create custom events to trigger alerts in the system.

Context

You can define events that work alone or together with other system-defined events to trigger an alert on your
system. Any event you define on your server appears as “User-defined.”

Procedure

1. On the Server Alert page, select Defined Events tab to view the list of alerts defined.
2. Click New in the top toolbar.
3. Enter the event details such as a unique event name and description.
The component field displays the default value “User-Defined.” You cannot edit this value.
4. Click Save.

Server Monitoring CUSTOMER

Configuration for Alerts © 2014 SAP SE or an SAP affiliate company. All rights reserved. 15
Important Disclaimers on Legal Aspects
This document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO
WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.

Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with respect to this document and no contractual obligations
or commitments are formed either directly or indirectly by this document.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. Regarding link classification, see: http://
help.sap.com/disclaimer.

CUSTOMER Server Monitoring

16 © 2014 SAP SE or an SAP affiliate company. All rights reserved. Important Disclaimers on Legal Aspects
Server Monitoring CUSTOMER
Important Disclaimers on Legal Aspects © 2014 SAP SE or an SAP affiliate company. All rights reserved. 17
www.sap.com/contactsap

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.