smp monitoring.pdf

SAP Mobile Platform:

English

SMP Monitoring

Business Process Documentation

SAP Best Practices SMP Monitoring

© SAP AG of 37

Contents

Server Monitoring and Analysis .............................................................................................................. 3

1 Managing a Cluster .......................................................................................................................... 3

1.1 Restarting a Cluster Node ........................................................................................................ 4

1.2 Deleting a Cluster Node ........................................................................................................... 4

2 Managing Server Log Files .............................................................................................................. 5

2.1 Setting Server Log File Size ..................................................................................................... 5

2.2 Viewing Server Log Files .......................................................................................................... 6

2.3 Configuring Agentry Application Logs ...................................................................................... 9

2.4 Viewing Agentry Logs ............................................................................................................. 12

3 Workload Analysis with Wily Introscope ........................................................................................ 19

3.1 Using Introscope Agent for Workload Analysis ...................................................................... 20

4 SAP License Auditing .................................................................................................................... 23

4.1 Generating and Sharing the SAP Audit Measurement File .................................................... 23

4.2 SAP Application Users Tracked with SAP License Audit Overview ....................................... 23

4.3 SAP Audit Measurement File Log Information ....................................................................... 25

5 Monitoring and Analysis with SAP Solution Manager .................................................................... 25

5.1 Integrating SAP Solution Manager ......................................................................................... 26

5.2 Viewing Workload Analysis Data ............................................................................................ 27

5.3 Viewing Change Analysis Data .............................................................................................. 29

5.4 Viewing Technical Monitoring Data ........................................................................................ 35

5.5 Viewing Client Tracing ............................................................................................................ 36


© SAP AG of 37

Server Monitoring and Analysis

Server features that enable you to monitor system health, and analyze problems that can affect server

performance or cause a disruption in the production environment.

In this section:

Managing a Cluster

Managing Server Log Files

Workload Analysis with Wily Introscope

SAP License Auditing

Monitoring and Analysis with SAP Solution Manager

1 Managing a Cluster

View and manage all server nodes in a cluster from a single location. You can view the state of each

server node, view error messages, and drill down to view additional details. You can restart a node

that is online, delete a node that is offline, and launch the administrative portal of another node in the

cluster.

Procedure

1. From Management Cockpit, select Cluster.

2. View status information for an SAP Mobile Platform Server in a cluster node.

Field Description

<server_node_name> SAP Mobile Platform host name, in the format <server_name.domain>.com.

Version No SAP Mobile Platform version.

Status Online indicates the server is running; Offline indicates it is not. Additional status

messages may be included, such as "Restart Required!"

3. (Optional) Select a server node to view additional details.

Field Description

Running

Time

Total hours the SAP Mobile Platform Server has been running.

URL Management Cockpit URL in the format https://<host_name>:<https_admin_port>/Admin/. Click the

hyperlink to launch the administrative portal of the selected node.

http://help.sap.com/saphelp_smp305svr/helpdata/en/35/432ebe430a4dd59f7a4bf88073483e/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2ff422700610148251ca12ece15dbb/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2eeacc70061014bc8bd65bf65f3c7d/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2209fa70061014b87dfc451b68db41/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/93/677a020f9d4193897ae1d750c990c8/content.htm


© SAP AG of 37

Field Description

Version SAP Mobile Platform version.

Bind

Address

The address used for cluster communications; for example

https://<host_name>:<https_admin_port>.

Last

Online

The number of hours since the server was last online (if available).

4. (Optional) Restart the server node (available only if the node is online).

5. (Optional) Delete the server node (available only if the node is offline).

6. (Optional) Click the hyperlink to launch the administrative portal of the selected server node.

In this section:

Restarting a Cluster Node

Deleting a Cluster Node

1.1 Restarting a Cluster Node

Restart an SAP Mobile Platform Server node as needed, for example, in order for configuration

changes to take effect.

Context

You can only restart a server if it is currently active, meaning in online mode.

Procedure


2. View status information for all SAP Mobile Platform servers in the cluster node.

3. Select a server node to view its details, and click Restart. During the restart, the server's

services are down, so no status is visible. Remain on the screen during the restart.

4. Wait for a while, and then refresh the screen to verify the server node restarted.

1.2 Deleting a Cluster Node

Remove an SAP Mobile Platform Server node from a cluster, for example, if the server node fails.

When the server node is again available, it will automatically re-attach itself to the cluster.

Context

The node must be in offline mode. You cannot remove a node that is in online mode.

http://help.sap.com/saphelp_smp305svr/helpdata/en/39/22a1e293bf4ecf98b8b47794df6b1e/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/b7/04c36172c944798e07e85a51e6720d/content.htm


© SAP AG of 37

Procedure


2. View status information for all SAP Mobile Platform servers in the cluster node. You can also

select a server node to view its details.

3. Select a server node with an offline status, and click Delete.

4. Check the Cluster tab of any server node that is running to verify the deleted node was

removed from the cluster.

2 Managing Server Log Files

Server log files can be used for troubleshooting application problems. Log files contain information

from all server logging components. Use the Logs & Traces view to filter SAP Mobile Platform log

information to more easily identify the source of the problem. Agentry log files cannot be viewed in the

Logs & Traces view.

In this section:

Setting Server Log File Size

Viewing Server Log Files

Configuring Agentry Application Logs

Viewing Agentry Logs

2.1 Setting Server Log File Size

Manually set the server log file size, and the number of rollover archive files to maintain in the

serviceability.xml configuration file.

Context

By default:, the server log files grow to 20MB before rolling over, and 12 archived file instances are

retained (for a total of 13 files, named <hostname>-smp-server.log, <hostname>-smp-server_1.log,

<hostname>-smp-server_2.log, and so forth).Upon reaching the maximum size, the log overwrites the

oldest archived file, and a new log is created. Since the log fills up quickly, establish a file size and

rollover policy that meets your record-keeping and troubleshooting needs. For example, you might

want to keep more and smaller files, and you might want to copy archive files to storage for later

analysis before they are overwritten.

You must have sufficient file space to support your decision. To calculate log file system usage, use

this formula:

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2a8a54700610149baa9567f371a490/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2a2b1a70061014881af8ef7bf89e94/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/0b/6c4248969242e1b19374af8f15bba7/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2a2f75700610149eedec4ab0a24c8d/content.htm


© SAP AG of 37

(Max - Min + 2) * Size = System Usage

If you have sufficient file space, SAP recommends:

MinIndex = 1; MaxIndex = 9

MaxFileSize = 20MB

(9 - 1 + 2) * 20MB = 200MB

Procedure

1. From File Manager, navigate to <SMP_HOME>\Server\log\Server\configuration\ .

2. Open serviceability.xml in an editor such as Microsoft WordPad.

3. Set server log file values:

a. Search for <appender name="LJS_LOG_FILE".

b. <rollingPolicy

class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

c. <FileNamePattern>log/<hostname>-smp-

server_%i.log</FileNamePattern>

d. <MinIndex>1</MinIndex>

e. <MaxIndex>12</MaxIndex>

</rollingPolicy>

<triggeringPolicy

class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

<MaxFileSize>20MB</MaxFileSize>

</triggeringPolicy>

f. For rolling policy, set the number of archived file instances. For example, change the

<MaxIndex>12</MaxIndex> value from 12 (the default) to 20 to create more

archived files.

g. For triggering policy, set the server log size. For example, change the

<MaxFileSize>20MB</MaxFileSize> value from 20MB (the default) to 5MB to

create smaller archive files:

h. Compare the server log system usage requirements:

Default:

(12 - 1 + 2) * 20MB = 260MB

Updated:

(20 - 1 + 2) * 5MB = 105MB

4. Save and close the file.

5. Restart SAP Mobile Platform Server for the changes to take effect.

2.2 Viewing Server Log Files


© SAP AG of 37

View lists of rolling server logs by type, including SAP Mobile Platform Server, and Agentry, from a

single screen. Select a log file to drill down and view the raw data in the log file. The type of

information captured in the logs files is determined by the log level set for the individual logging

components on the Settings tab.

Context

Note: You can also view server log entries using the Logs & Traces view. The Logs & Traces view

enables you to filter log and trace information by logging component and other criteria, and download

log and trace files.

Note: In a clustered server environment, the server log only shows information for the node to which

Management Cockpit is connected, and not synchronized across the nodes in the cluster. Connect

Management Cockpit to another node to view its server log.

Procedure

1. From Management Cockpit, select the Logs tab, and select Log Files.

2. Under SAP Mobile Platform Log, view the list of rolling logs for <hostname>-smp-server.log.

Select a log file, using the Date Time stamp as a guide, to view log file contents. For example,

select <hostname>-smp-server1.log to view its contents.

3. Expand Agentry Log to view the list of Agentry server logs. For example, select events.log to

view its contents.

In this section:

SAP Mobile Platform Server Log File

2.2.1 SAP Mobile Platform Server Log File

The SAP Mobile Platform server log file captures server activity according to the log level set.

Server Log Format

Note: You can also view server log entries using the Logs & Traces view. The Logs & Traces view

enables you to filter log and trace information by logging component and other criteria, and download

log and trace files.

The following is an excerpt from a typical server log file. See the list of columns below the example,

for a description of output columns. The system inserts the pound sign (#), if information is not

included for the column.

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2a774570061014b075f6155f85057b/content.htm


© SAP AG of 37

COLUMNS:Time|TZone|Severity|Logger|ACH|User|Thread|Bundle

name|JPSpace|JPAppliance|JPComponent|Text|

SEVERITY_MAP:FINEST|Information|FINER|Information|FINE|Information|CONFIG|I

nformation|DEBUG|Information|PATH|Information|INFO|Information|WARNING|Warn

ing|ERROR|Error|SEVERE|Error|FATAL|Error

HEADER_END

2013 07 26 14:39:29#0-

700#INFO#com.sap.core.js.mbeanserver.registerer.bundle.Activator##anonymous

#Start Level Event Dispatcher###An MBeanServer has already been registered

as an OSGi service. Nothing to register.|

2013 07 26 14:39:29#0-

700#INFO#com.sap.core.js.monitoring.sapjvm.SAPJVMMetrics##anonymous#Compone

nt Resolve Thread (Bundle 281)###JVM Vendor is: SAP AG|

2013 07 26 14:39:29#0-

700#INFO#com.sap.core.js.monitoring.MBeanManager##anonymous#Component

Resolve Thread (Bundle 281)###MBeanServer:

com.sun.jmx.mbeanserver.JmxMBeanServer@25edb870|

2013 07 26 14:39:29#0-

700#INFO#com.sap.core.js.monitoring.MBeanManager##anonymous#Component

Resolve Thread (Bundle 281)###activate() is called with:

org.eclipse.equinox.internal.ds.impl.ComponentContextImpl@5db2c30d|

2013 07 26 14:39:30#0-

700#INFO#com.sap.persistence.dbtech.osgi.Activator##anonymous#Start Level

Event Dispatcher###----- registered DataSourceFactory service for MaxDB ---

--|

2013 07 26 14:39:31#0-

700#INFO#com.sap.persistence.hdb.osgi.Activator##anonymous#Start Level

Event Dispatcher###----- registered DataSourceFactory service for SAP In-

Memory Computing Engine -----|

Column Description

Time The date and timestamp of the log item, in the format YYYY MM DD HH:MM:SS.

TZone The time zone, if included.

Severity The log level, for example, DEBUG, PATH, INFO, WARN, ERROR, and FATAL. This value

depends on the log level set for the system logging component.


© SAP AG of 37

Column Description

Logger The system logging component, such as

com.sap.persistence.dbtech.osgi.Activator.

ACH Not currently used

User A system user, or anonymous.

Thread The thread used to communicate.

Bundle Name The bundle name, such as (Bundle 281).

JPSpace Not currently used

JAppliance Not currently used

JPComponent Not currently used

Text Message text for the logged item.

2.3 Configuring Agentry Application Logs

Configure settings for Agentry logs. Agentry log file settings are configured as part of defining the

application. Log settings apply to all applications, not just the currently selected application.

Context

Some Agentry settings apply only to the selected application, and other settings apply to all Agentry

applications. When you change settings in a section marked "Affects All Agentry Applications", keep

in mind that all Agentry applications are affected.

Note Some entries require an SAP Mobile Platform Server restart.

Procedure

1. From Management Cockpit, select Applications Configure App Specific Settings .

2. Under Logging (Affects all Agentry Applications), edit log settings.

Definition Values Description

Event Log

File

Valid file name or path

and file name. Default:

events.log

The file to which event log items are written. You can change the

default to specify a different file name or location. The path can be

relative to the server installation folder; or a full path that includes the

drive letter. Requires server restart.


© SAP AG of 37

Maximum

Log Size

Numeric value, assumed

to be in bytes. Default: 0

The maximum size of the log file in bytes. A value of 0 indicates no

maximum size. Any other value results in the log file rolling over when

the file exceeds the value set here.

Log Roll

Time

Time of day in 24-hour

clock format (HH:MM).

Default: 1:00am

The time at which to roll log files. The server must be running for the

files to roll over at the specified time. Requires server restart.

Log Rolls At

Time

Boolean value of true or

false. Default: true

Whether to roll the log files based on the time in Log Roll Time.

Requires server restart.

Message

Log File

Valid file name or path

and file name. Default:

messages.log

The file to which message log items are written. You can change the

default to specify a different file name or location. The path can be

relative to the server installation folder; or a full path that includes the

drive letter. Requires server restart.

3. Restart SAP Mobile Platform Server if you changed any setting that requires it.

In this section:

Agentry Logs

Purging Agentry Logs

2.3.1 Agentry Logs

Use Management Cockpit to manage Agentry log files. You can enable or disable the various files,

specify how log file are generated (based on a processing thread, or more narrow areas of

functionality), and set the verbosity level of the message contents.

The log messages generated by the SAP Mobile Platform Server are categorized as follows:

Server: Messages that are generated as a result of Agentry application processing. The

contents are an inclusive set of the other categories, with the messages including all those

related to any processing performed by the SAP Mobile Platform Server.

User: Messages that are specific to a single user. User logs are inclusive of system

connection and client communication logs, with the messages including all those related to

any user-specific processing performed by the SAP Mobile Platform Server.

System Connection: Messages that result from processing back-end data synchronization

for a specific system connection. The contents are messages that result from processing the

various synchronization definitions within the application. Each system connection within an

application has its own set of log messages that you can individually enable and configure.

Client Communications: Messages that result from client-server communication. These

messages include IP addresses and port numbers, socket opening, data transfer in both

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/303196700610149ee8d9c461a29049/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/8e/16f301aa8c4a708e0cf2d20eeaa9db/content.htm


© SAP AG of 37

directions, and other messages sent between the Agentry client and SAP Mobile Platform

Server.

The contents of all log messages, regardless of category, include both error messages and

informational or status messages. Each message includes a date and timestamp, precise to the

millisecond. The verbosity of the messages generated is configured when the category of log

messages are enabled.

Log Messages Versus Log Files

Log messages generated by the Agentry application are stored in log files. When enabling and

configuring the logging behavior of the Agentry application, the contents of the log messages are

configured. In addition, the files into which those messages are written is also configured. By default,

when a log message category is enabled, those messages are written to a log file for a processing

thread. Each Agentry application processing thread has its own log file containing all messages

generated by the Agentry application for processing within that thread, and for the category of log

messages that have been enabled.

As an optional additional method for storing log messages, each category of log messages can be

written to a category-specific log file. When this is enabled, all log messages generated by the

Agentry application for a specific category are written to the same log file, regardless of processing

thread. The messages within the category-specific log files are grouped by the processing thread.

Therefore, a category log file contains log messages resulting from processing related to that

category.

In addition to the thread log files, you can generate log files by category:

Server category: Server-ServerName.log, where ServerName is the System Name

specified in the Agentry application definition. By default, the category is Agentry.

User category: User-UserID.log, where UserID is the user’s Agentry client login ID.

System connection category: BackEnd-SystemConnection.log, where

SystemConnection is the name of the system connection section (for example, SQL-1,

Java-2).

Client communications category: FrontEnd-FrontEndType.log, where

FrontEndType is the connect type (for example, WebSockets Front End).

Configuring the log files to generate separately based on the log message category has a negative

impact on Agentry application performance, as multiple processing threads are logging messages to

the same physical log file. One message at a time is written to such a log; therefore, each thread must


© SAP AG of 37

wait until the log file is available before it can write its log message. SAP recommends that you

configure log files in this manner only in a development environment.

All log files are written to the Agentry application folder in <SMP_HOME>\log\agentry. Log files are

rolled over periodically, during SAP Mobile Platform Server start-up or restart, and, on command, to

the subdirectory rolled.

2.3.2 Purging Agentry Logs

Agentry application logs are rolled (moved) automatically to the \rolled directory, and are stored until

you purge them. Decide how long you want to keep the Agentry log files, then delete the files

manually, or archive them to storage for later analysis.

Context

The Agentry log files are in <SMP_HOME>\logs\agentry\rolled\<yyyy-mm-dd-HHMMSS>, where

<yyyy-mm-dd-HHMMSS> represents the date and time the log files were moved into the directory. If a

version, such as <-1> or <-2> is appended to the file name, it indicates that the logs were rolled twice

in the same second (this happens only rarely, when a large volume of data is added to a log file).

Rolled files are the same as the originals, such as events.log, messages.log, shutdown.log, and

startup.log.

Procedure 1. Navigate to <SMP_HOME>\logs\agentry\rolled.

2. Identify the log files to purge.

3. Delete the files, or archive them for later use.

2.4 Viewing Agentry Logs

View a list of Agentry log files, and rolled-over Agentry server logs from a single screen, and access

log file data in individual files.

Context

Note In a clustered server environment, the Agentry logs only show information for the node to which

Management Cockpit is connected, and are not synchronized across the nodes in the cluster.

Connect Management Cockpit to another node to view its Agentry logs.

Procedure

1. From Management Cockpit, select the Logs tab, and select Log Files.


© SAP AG of 37

2. Expand Agentry Log to view the list of Agentry server logs.

3. Select a log file to view details. Examples (your list will vary depending on your Agentry

implementation):

o events.log

o messages.log

o startup.log

o <app-id> thread-<xxx>.log

o rolled – select to view rolled-over Agentry log files, organized into file folders by date.

o BackEnd-Java-<x>.log

o BackEnd-SQL-<x>.log

o BackEnd-FileSystem-<x>.log

o BackEnd-HTTP-XML-<x>.log

o BackEnd-OData-<x>.log

In this section:

Agentry messages.log File

Agentry events.log File

Agentry startup.log File

Agentry app-id thread-xxx.log File

2.4.1 Agentry messages.log File

The messages.log file contains log items that are related to client-server messaging. Each

message and response sent between SAP Mobile Platform Server and Agentry client is one log item.

The information in each item includes the date and time of the message, the Agentry client’s IP

address, the type of message or response, and other message information.

The messages log persists until one of the following occurs:

The log files are rolled by SAP Mobile Platform Server, at which point they are moved to a

backup folder named rolled, in a subdirectory named for the date and time. By default, this

occurs once every 24 hours, provided SAP Mobile Platform Server is running. With a change

to the application configuration, this file may also be moved to a backup location based on file

size.

SAP Mobile Platform Server is shut down and restarted. In this case, the messages.log file

is moved to the backup folder rolled, in a subdirectory named for the date and time.

The messages.log file cannot be disabled.

Messages Log Format

The following is an excerpt from a typical messages.log file.

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/303a03700610149ac9d0b1c68038cb/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/3035ce70061014a269e67f88249d46/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2a680e70061014b640a9a6ddeb37e8/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/2a6c9170061014b7d18f19c3d84aa0/content.htm


© SAP AG of 37

I, 9, 1, 10, 09/12/2013 17:11:18, , 0, 70, , ANGEL: B0A6D984-

C97B-4275-B7E4-AEB8FC9D5210

Q, 9, 1, 10, 09/12/2013 17:11:18, , 0, 70, user1, ANGEL: B0A6D984-

C97B-4275-B7E4-AEB8FC9D5210

A, 9, 1, 10, 09/12/2013 17:11:18, , 0, 70, user1, ANGEL: B0A6D984-

C97B-4275-B7E4-AEB8FC9D5210

S, 9, 1, 10, 09/12/2013 17:11:22, 22, 23, 70, user1, ANGEL: B0A6D984-

C97B-4275-B7E4-AEB8FC9D5210

C, 9, 1, 10, 09/12/2013 17:11:22, , 23, 70, user1, >unknown<

Message State: A single character indicating the state of the message in relation to SAP

Mobile Platform Server.

Message Code: A numeric value that identifies the type of message. See Message Codes for

more information.

Subsystem Code: Either 1 or 20. This is a deprecated value that varies only for older SAP

products built on Agentry 2.0 code libraries.

Message Number: A number assigned by the Agentry client that increments for each

message sent.

Date and Time: The date and time the message was received by the SAP Mobile Platform

Server. This is always the date and time of the SAP Mobile Platform Server host system.

Response Code: A numeric code that indicates the response to the message. The message

codes “S” and “R” each have a different set of possible response codes. For all other

message codes, the response code column is blank.

Data Sent/Data Received: A running total of the amount of data sent and received by the

SAP Mobile Platform Server per message, with a value in bytes.

User ID: ID of the user to which the message belongs. It is normal for the user ID to remain

blank for messages with a message state of “I”.

Client Location: IP address of the client device. It is normal for the client location to be

unknown for messages with a message state of “C”.

Table 1: Message States—Synchronous Communication

State Name Description

I Incoming Message is being received from the client.

Q Queued Message is decoded, and placed in an SAP Mobile Platform Server work queue; the

user is identified.

A Active A previously queued message is being processed by the SAP Mobile Platform

Server.


© SAP AG of 37

Table 1: Message States—Synchronous Communication


S Sent Response SAP Mobile Platform Server sent information or an acknowledgement to the client.

R Received

Response

A client response has been received by SAP Mobile Platform Server.

C Complete Message processing is complete.

Table 2: Push Message States—Asynchronous Communication


O Outgoing Message is being sent to the client.

T Trying SAP Mobile Platform Server is attempting to connect to a client

L Linked SAP Mobile Platform Server has successfully connected to a client.

W Waiting SAP Mobile Platform Server failed in an attempt to connect to a client. It will attempt

the connection again.

R Received

Response

SAP Mobile Platform Server has received a client response.

S Sent Response SAP Mobile Platform Server sent information or an acknowledgement to the client.

C Complete Message processing is complete.

X Cancelled SAP Mobile Platform Server cancelled the message to the client.

F Failed Message failed. SAP Mobile Platform Server will not retry.

Message codes indicate the type of message being processed or sent, and are found in the Message

Code column of the messages.log file.

Table 3: Log Message Codes

Code Description

2 Client logout request

3 Client login request

7 Client user password change request

200 Transaction instance sent to SAP Mobile Platform Server from the client


© SAP AG of 37

Table 3: Log Message Codes

Code Description

201 Client has made a fetch processing request

202 Client system information message sent to SAP Mobile Platform Server

203 Client has requested an object be reloaded/refreshed

204 Client has requested the definition of an object

205 Client has requested the definition of a fetch

206 Client has requested the definition of a transaction

207 Client has requested the definition of a screen set

208 Client has requested the definition of an action

209 Client has requested the definition of a rule

210 Client has requested the definition of a report

211 SAP Mobile Platform Server has pushed an object or messages to the client

212 Client has sent an enable push message to SAP Mobile Platform Server for the user

213 Client has requested the definition of a style be sent

622 Client has requested that all complex tables be updated

623 Client has requested that all data tables be updated

2.4.2 Agentry events.log File

The events.log file records various SAP Mobile Platform Server events that occur at run time.

Events include startup and shutdown, opening and closing connections to the application’s system

connections, loading of client-server communication components, memory usage, thread expansion,

and used and available storage.

The events log persists until one of the following occurs:

The log files are rolled by SAP Mobile Platform Server, at which point they are moved to a

backup folder named rolled, in a subdirectory named for the date and time. By default, this

occurs once every 24 hours, provided the SAP Mobile Platform Server is running. With a

change to the application configuration, this file may also be moved to a backup location

based on file size.


© SAP AG of 37

SAP Mobile Platform Server is shut down and restarted. In this case, the events.log file is

moved to the backup folder rolled, in a subdirectory named for the date and time.

The events.log file cannot be disabled.

The following is an excerpt from a typical events.log file.

07/31/2013 01:45:00, 0, 0, 0, Thr 548, Rollover

time

07/31/2013 02:42:09, 0, 0, 7, Thr 548,

07/31/2013 03:42:10, 0, 0, 7, Thr 548,

07/31/2013 04:42:11, 0, 0, 7, Thr 548,

07/31/2013 05:42:12, 0, 0, 7, Thr 548,

07/31/2013 06:42:13, 0, 0, 7, Thr 548,

07/31/2013 07:42:14, 0, 0, 7, Thr 548,

07/31/2013 08:42:15, 0, 0, 7, Thr 548,

07/31/2013 09:42:16, 0, 0, 7, Thr 548,

07/31/2013 10:42:17, 0, 0, 7, Thr 548,

07/31/2013 11:42:18, 0, 0, 7, Thr 548,

07/31/2013 12:42:19, 0, 0, 7, Thr 548,

07/31/2013 13:42:20, 0, 0, 7, Thr 548,

07/31/2013 14:42:21, 0, 0, 7, Thr 548,

07/31/2013 15:42:22, 0, 0, 7, Thr 548,

07/31/2013 16:42:23, 0, 0, 7, Thr 548,

Each log message is written to a single line that begins with a timestamp. The next three columns,

separated by commas, are the message type, message group, and the message ID. A message type

of 1 indicates an error message, while a message type of 0 indicates an informational message. The

message type is followed by the thread ID, denoted by the text Thr, and finally the message itself.

2.4.3 Agentry startup.log File

The Agentry startup.log file records various SAP Mobile Platform Server start-up events, for example,

when Agentry log files, threads, and configuration files start.

Agentry startup.log File

This is an excerpt from a typical Agentry startup.log file.

14:40:21 07/26/2013: Starting server (64-bit Windows)

14:40:21 07/26/2013: Reading system ini file.

14:40:22 07/26/2013: ID: Agentry, Name: ???, Location: ???

14:40:22 07/26/2013: Starting log file.


© SAP AG of 37

14:40:22 07/26/2013: Loading message groups.

14:40:22 07/26/2013: Starting threads.

14:40:22 07/26/2013: 1 initial threads. Threads will auto-scale.

14:40:22 07/26/2013: Starting Server: Agentry v7.0.0.352

14:40:22 07/26/2013: Event: 0, 2, System Startup

14:40:22 07/26/2013: Loading 1 front ends

14:40:22 07/26/2013: Loading front end from angelvine.dll

14:40:22 07/26/2013: ANGEL Front End: loading configuration

14:40:22 07/26/2013: Event: 17, 14, ANGEL Front End v7.0.0.352

14:40:22 07/26/2013: Loading front end from angelvine

14:40:22 07/26/2013: HTTPS Front End: loading configuration

14:40:22 07/26/2013: Event: 17, 14, HTTPS Front End v7.0.0.352

14:40:22 07/26/2013: Event: 0, 2, Loading the Agentry Server's

public/private key for password exchanges.

14:40:22 07/26/2013: Event: 0, 2, Key pair loaded successfully.

14:40:22 07/26/2013: Starting Server Agent.

14:40:22 07/26/2013: Agentry: Starting threads.

14:40:22 07/26/2013: 1 initial threads. Threads will auto-scale.

14:40:22 07/26/2013: Agentry: Adding messages.

14:40:22 07/26/2013: Event: 1, 4, Agentry v7.0.0.352

14:40:22 07/26/2013: Loading 1 agents

14:40:22 07/26/2013: Loading agent from ag3.dll

14:40:22 07/26/2013: Starting Server

14:40:22 07/26/2013: Server: reading ini file

14:40:23 07/26/2013: [System Connections] not found - please use editor to

publish application then restart the server.

14:40:23 07/26/2013: Exception: 14:40:23 07/26/2013 : 25 (General), Unknown

Exception ([System Connections] section not found in Agentry.ini file

(Publish from editor to correct), ),

agent\ChickamingAgent.cpp#2450:ChickamingAgent::startup

14:40:23 07/26/2013: Event: 20, 4, Server v7.0.0.352

14:40:23 07/26/2013: Starting front ends

14:40:23 07/26/2013: ANGEL Front End: Starting threads.

Time: the date and time of the log item, including milliseconds, in the format HH:MM:SS

MM/DD/YYYY.

Message Text: the message text associated with the start-up event. Some messages

indicate a message category, such as Event, Agentry, Server, and Exception.


© SAP AG of 37

2.4.4 Agentry app-id thread-xxx.log File

The Agentry <app-id> thread-<xxx>.log file records SAP Mobile Platform Server events for each

Agentry application.

Agentry app-id thread-xxx.log File

Excerpts from typical Agentry <app-id> thread-<xxx>.log files.

2014/05/05 18:09:25.195: Opening log file

2014/05/05 18:09:25.195: +

Thread=31240<..\multithreading\win32\Thread.cpp:150>

2014/05/05 18:09:25.195: + Thread

Pool=com.sap.mobile.northwind<..\agentry\threadManager.cpp:339>

2014/05/05 18:09:25.195: +

WorkFunction=000000004AFDF7D8<..\agentry\threadManager.cpp:343>

...

2013/07/26 14:40:23.176: Opening log file

2013/07/26 14:40:23.176: + Thread=4924

2013/07/26 14:40:23.176: + Server=Agentry

2013/07/26 14:40:23.176: + Server=Agentry

2013/07/26 14:40:23.176: Server: [System Connections] section not

found (Publish from editor to correct)

2013/07/26 14:40:24.640: Closing log file

Time the date and time of the log item, including milliseconds, in the format YYYY/MM/DD

HH:MM:SS.

Message Text the thread identifier, application identifier, and associated messages.

3 Workload Analysis with Wily Introscope

Wily Introscope is a third-party diagnostic tool that can be integrated into your system landscape to

quickly isolate and resolve performance issues through workload data, basic tracing functionality, and

historic diagnostics data. Administrators can use performance data points for several metrics to

assess overall performance of the system.

The Enterprise Manager serves as the central repository for all Introscope performance data and

metrics collected in an application environment. The SAP Mobile Platform Introscope agent collects

key performance metrics, which you can review using the Introscope Enterprise Manager dashboard

user interface. When SAP Mobile Platform is included as part of a broader SAP system, you can view

the Introscope performance data and metrics using the SAP Solution Manager dashboard. See


© SAP AG of 37

http://help.sap.com/solutionmanager for more information about using the SAP Solution Manager for

workload analysis.

To use Introscope with SAP Mobile Platform Server, install Introscope Enterprise Manager and

configure the SAP Mobile Platform Introscope Agent.

Note: Introscope Enterprise Manager is not installed by SAP Mobile Platform; you must download and

install it separately before you can use this method of monitoring.

In this section:

Using Introscope Agent for Workload Analysis

3.1 Using Introscope Agent for Workload Analysis

Wily Introscope is a third-party diagnostic tool that provides workload data, basic tracing functionality,

and historic diagnostics data. To use Introscope with SAP Mobile Platform Server, you need to install

the Introscope Enterprise Manager, and install and configure Introscope Agent.

Installing Introscope Agent

1. Navigate to the SAP Service Marketplace Software Download Center (login required).

2. In the left pane, select Support Packages and Patches Browse our Download Catalog ,

then select SAP Technology Components SAP Solution Manager SAP Solution

Manager 7.1 Entry by Component Agents for Managed Systems .

3. Select the supported Introscope Agent and follow the screen prompts for download.

Note For information about the supported version of Introscope Agent, see SAP Product Availability

Matrix (PAM) http://service.sap.com/pam . Click the Mobile link at the top of the page. Scroll to find

the appropriate product and version in the product list. In the upper right corner of the SAP Mobile

Platform PAM screen under the Essentials heading, click Open in New Window to open the Support

Matrices for SAP Mobile Platform 3.0 documentation.

Installing Introscope Enterprise Manager

1. Download Introscope Enterprise Manager from the SAP Service Marketplace Software

Download Center. The Introscope Enterprise Manager is located in the SAP Solution

Manager Software Downloads section:

a. Navigate to the SAP Service Marketplace Software Download Center (login

required).

b. In the left pane, select Support Packages and Patches Browse our Download

Catalog , then select SAP Technology Components SAP Solution Manager

SAP Solution Manager 7.1 Entry by Component Wily Introscope .

http://help.sap.com/solutionmanager

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/306c72700610148635ba5ae6c07ad0/content.htm

http://help.sap.com/disclaimer?site=https://support.sap.com/swdc

http://help.sap.com/disclaimer?site=https://support.sap.com/pam

http://help.sap.com/disclaimer?site=https://support.sap.com/swdc


© SAP AG of 37

c. Select the supported Introscope Enterprise Manager and follow the screen prompts

for download.

2. Install Introscope Enterprise Manager.

Note: For information about the supported version of Introscope Enterprise Manager, see SAP

Product Availability Matrix (PAM) http://service.sap.com/pam . Click the Mobile link at the top of the

page. Scroll to find the appropriate product and version in the product list. In the upper right corner of

the SAP Mobile Platform PAM screen under the Essentials heading, click Open in New Window to

open the Support Matrices for SAP Mobile Platform 3.0 documentation.

Configuring Introscope Agent for SAP Mobile Platform Server

Configure the supported Introscope Agent on SAP Mobile Platform Server to analyze performance

metrics using the Introscope Enterprise Manager dashboard user interface.

Note: Do not configure or enable the agent unless the supported Introscope Enterprise Manager

version is already installed in the production environment.

1. Download the file attachments in SAP Note 1911963 to

<SMP_HOME>\Introscope_Agent\wily\core\config\.

2. Open the <SMP_HOME>\server\props.ini file, and add the following lines immediately below

the lines that begin with -Dcom:

3. -javaagent:C:/SAP/MobilePlatform3/Introscope_Agent/wily/Agent.jar

4. -

Dcom.wily.introscope.agentProfile=C:/SAP/MobilePlatform3/Introscope_A

gent/wily/core/config/IntroscopeAgent_SMP.profile

5. -Dcom.wily.introscope.agent.agentName=SAPMobilePlatform

6. -XX:-UseSplitVerifier

7. Restart SAP Mobile Platform Server for the change to take effect.

Configuring the IntroscopeAgent_SMP.profile File

Edit the IntroscopeAgent_SMP.profile file to specify the server name and port number where

Enterprise Manager was installed.

1. Open the <SMP_HOME>\Introscope_Agent\wily\core\config\IntroscopeAgent_SMP.profile file

as follows:

a. Modify introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=localhost to

correspond with the installed Enterprise Manager host, instead of localhost.

http://help.sap.com/disclaimer?site=https://support.sap.com/pam

http://help.sap.com/disclaimer?site=http://service.sap.com/sap/support/notes/1911963


© SAP AG of 37

b. Modify introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=6001 to

correspond with the installed Enterprise Manager host's port, which is 6001 by

default.

2. Restart SAP Mobile Platform Server.

SAP Mobile Platform Metrics Collected By Introscope

You can view the metrics collected by the SAP Mobile Platform Server in Introscope. Be aware that

some metrics are contained and measured as part of other metrics, as identified below, and could be

inadvertently be measured twice.

Table 1: Introscope Metrics for SAP Mobile Platform

Metric Description

SMP|Dispatcher Authentication Time to authenticate client.

SMP|ODataProxy|Backend Time to send and receive an HTTP request of an OData source, such as

the SAP NetWeaver Gateway.

SMP|Core

Services|Registration|Create

Create a new entity representing a client registration.

SMP|Core

Services|Registration|Retrieve

Retrieve an entity representing a client registration.

SMP|Admin|Process Process a request from the Management Cockpit.

Introscope Transaction Trace Sessions with SAP Mobile Platform

Introscope includes the ability to trace requests from clients. Introscope refers to this feature as a

Transaction Trace Session. The requests traced may be filtered by User ID or by Request Header.

To filter by User ID in the dialog named “New Transaction Trace Session”, select “User ID” in the

dropdown list. Then, select “equals”. Finally specify the User ID. The User ID is the same as the User

Name shown in the SAP Mobile Platform Administration display of Application Registrations. The

User ID is the same value provided by the client for authentication.

Alternately, if the client specifies an Http header value of either X-SUP-APPCID or X-SMP-APPCID,

then transactions may be filtered by a header value. The Http Cookie value with the same name will

not work for filtering transactions. In the dialog named “New Transaction Trace Session”, select

“Request Header” in the dropdown list. Input either X-SUP-APPCID or X-SMP-APPCID, depending

upon which header the client is sending. Then, select “equals”. Finally specify the value sent by the

client. The value for the APPCID is shown in the Management Cockpit display of Application

Registrations and is labeled Registration ID.


© SAP AG of 37

4 SAP License Auditing

The SAP License Audit feature in SAP Mobile Platform Server enables you to generate an SAP Audit

measurement file in accordance with the SAP License Auditing process.

The SAP License Audit feature measures the total number of users registered with SAP Mobile

Platform Server, as well as the number of users per SAP application. The results are used to

generate the SAP Audit XML file, which you can send to SAP according to the instructions in your

SAP License Audit notice.

In this section:

Generating and Sharing the SAP Audit Measurement File

SAP Application Users Tracked with SAP License Audit Overview

SAP Audit Measurement File Log Information

4.1 Generating and Sharing the SAP Audit Measurement

File

Use Management Cockpit to generate an audit measurement file that you can send to SAP for

uploading to the SAP Global Auditing License Service.

Procedure

1. In Management Cockpit, select the Reporting tab, and select License and Auditing.

2. Click SAP Auditing Export.

3. Select a location for the file, and click Save.

4. When you are ready to share the measurement results, send the file to SAP as instructed in

your SAP License Audit notice.

Note: For information about uploading the audit measurement file to SAP Global Auditing

License Service, see supporting SAP documentation at https://support.sap.com/keys-

systems-installations/Measurement.html .

4.2 SAP Application Users Tracked with SAP License Audit

Overview

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/220e2f70061014a81ba326ad0cb89e/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/22178970061014a457f5d06dba5ed9/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/7c/221bf670061014ae89fe86acac4c93/content.htm

http://help.sap.com/disclaimer?site=https://support.sap.com/keys-systems-installations/Measurement.html

http://help.sap.com/disclaimer?site=https://support.sap.com/keys-systems-installations/Measurement.html


© SAP AG of 37

Review a list of application users that are tracked with the Global License Auditing Service. These

application users are identities registered with SAP Mobile Platform during automatic on-boarding, or

when the user is manually registered by an administrator.

Note: Application users for applications created with Sybase Mobile Platform 2.1 or earlier are not

included in the audit measurement results.

ID Unit

S001 SAP Mobile Platform User

S005 SAP Employee Lookup Mobile User

S010 SAP Leave Request Mobile User

S015 SAP Travel Receipt Capture Mobile User

S020 SAP Travel Expense Approval Mobile User

S025 SAP HR Approvals Mobile User

S030 SAP Cart Approval Mobile User

S035 SAP Timesheet Mobile User

S040 SAP Sales Order Notification Mobile User

S045 SAP Material Availability Mobile User

S050 SAP ERP Order Status Mobile User

S055 SAP CRM Retail Execution Mobile User

S060 SAP Field Service Mobile User

S065 SAP EAM Work Order Mobile User

S070 SAP ERP Quality Issue Mobile User

S075 SAP Customer and Contacts Mobile User

S080 SAP GRC Access Approver Mobile User

S085 SAP GRC Policy Survey Mobile User

S090 SAP Payment Approvals Mobile User

S095 SAP Customer Financial Fact Sheet Mobile User

S100 SAP Interview Assistant Mobile User


© SAP AG of 37

S105 SAP Transport Notification and Status Mobile User

S110 SAP Transport Tendering Mobile User

S115 SAP Manager Insight Mobile User

S120 SAP Electronic Medical Record Mobile User

S125 SAP Sales Mobile User

4.3 SAP Audit Measurement File Log Information

When you generate the SAP audit measurement file, information about that generation is written to

the SAP Mobile Platform Server log with the string GLAS.

The table below lists the log-level information for log entries that are associated with the SAP Audit

Measurement file.

Log Level Description

ERROR Used for unchecked exceptions, or checked exceptions that block application information collection

or measurement generation and cannot be recovered.

WARNING Used when an SAP-built application is not found during file generation.

INFO This log level is used to provide information about key points in the file generation such as:

Application information collection start

Application information collection completion

Measurement generation start

Measurement generation completion

5 Monitoring and Analysis with SAP Solution

Manager

SAP Solution Manager enables you to centralize, enhance, automate, and improve the management

of your entire SAP landscape.When SAP Mobile Platform is included as part of a broader SAP

system, you can use SAP Solution Manager to access supportability features such as change

analysis, workload analysis, and system availability.


© SAP AG of 37

First, configure SAP Solution Manager to recognize SAP Mobile Platform, then you can use the

Solution Manager dashboard to:

Perform end-to-end workload analysis for native and hybrid apps Solution Manager is

integrated with Wily Introscope to extend the workload analysis feature for the larger

enterprise system. Once you have configured the Introscope agent on SAP Mobile Platform

Server, the agent captures the workload metrics, which you can review using either Solution

Manager or the Introscope Enterprise Manager dashboard. For a list of the metrics collected

for workload analysis, see Using Introscope Agent for Workload Analysis.

Perform end-to-end change analysis Solution Manager periodically retrieves server- and

application-level configurations from SAP Mobile Platform. You can use the Solution Manager

dashboard to review and discover any configuration changes that have been made over a

specific period of time. This information is especially useful when ad hoc changes cause

disruption in a productive system. This change analysis approach identifies problems by

comparison, which is faster and easier than drill-down methods of root cause analysis.

Technical availability monitoring Solution Manager provides a central point of access for

monitoring a system's technical availability for SAP Mobile Platform. This allows you to use

the Solution Manager dashboard to evaluate SAP Mobile Platform's overall system status in

the mobile system landscape.

Note: For information about installing, configuring, and using SAP Solution Manager, see

http://help.sap.com/solutionmanager. For information about installing and configuring Diagnostics

Agent for Solution Manager, see Step by step how to install Diagnostics Agent and connect the agent

to adaptive computing .

In this section:

Integrating SAP Solution Manager

Viewing Workload Analysis Data

Viewing Change Analysis Data

Viewing Technical Monitoring Data

Viewing Client Tracing

5.1 Integrating SAP Solution Manager

Integrate SAP Solution Manager with SAP Mobile Platform by setting up and configuring your system.

Procedure

1. Install SAP Mobile Platform Server. For more information, see Installation: SAP Mobile

Platform Server.

http://help.sap.com/solutionmanager

http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-26888

http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-26888

http://help.sap.com/saphelp_smp305svr/helpdata/en/3c/36733474c44e79b8268e2d55f135f5/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/91/42038fc8a547168e1e58de8a810b34/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/8b/bdd82857654efc8aea51eabdfcdb5c/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/78/f1009584c74858ba2f437c9c7226f2/content.htm

http://help.sap.com/saphelp_smp305svr/helpdata/en/13/e0f3f14ea04d64957bdd663ec23f4d/content.htm


© SAP AG of 37

2. Follow the instructions in SAP Note 1911963 – CA Introscope Instrumentation for SAP Mobile

Platform 3.0 .

Note In SAP Mobile Platform 3.0 and later, the Introscope Agent is packaged in the SAP

Mobile Platform installer. When following the instructions in the above note, you need not

install the Introscope Agent. The installation directory for the Introscope Agent is in:

<SMP_HOME>\IntroscopeAgent.

3. Follow the instructions in SAP Note 1990123 – Managed System Configuration for SAP

Mobile Platform 3.0 with SAP Solution Manager 7.1

Note:

o SAP Note 1990123, and some SAP Solution Manager documentation refer to Sybase

Unwired Platform, the predecessor to SAP Mobile Platform. All references to Sybase

Unwired Platform denote SAP Mobile Platform.

o For technical availability monitoring to work correctly for multiple server nodes,

maintain each node separately in the Landscape Management Database (LMDB).

You must perform the managed system configuration steps in SAP Note 1990123

separately for each server node.

4. Download the latest version of the config.xml file to the Solution Manager system, from SAP

Note 1259109 – Latest Version of Configuration File for E2E CA, EA, WA

5.2 Viewing Workload Analysis Data

View data collected for workload analysis using SAP Solution Manager.

Procedure

1. In Solution Manager, navigate to transaction solman_workcenter Root Cause Analysis

End-to-End Analysis .

2. Select the system maintained in LMDN, and click Workload Analysis Start New Window

http://help.sap.com/disclaimer?site=https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3139313139363326







© SAP AG of 37

A new window displays workload analysis data.

3. Click the SAP Mbl Platform Runtime - SVR tab.

4. To see data for all SAP Mobile Platform Server hosts, click on the drill-down button on the

rows for Host Name and Instance Name.


© SAP AG of 37

You can view additional SAP Mobile Platform Server data on the Top SQL Statements and

Host tabs.

5. To see a graphical representation of the data, log in to Introscope at: http://<Introscope

Manager host>:8081/webview and select the Agent Host. You can see the SAP Mobile

Platform metrics under the following package:

o doAuthentication (time taken to onboard to SAP Mobile Platform) – Introscope

Manager Investigator Agent Host SUP Java Server Agent Name SMP

Dispatcher Filter doAuthentication doFilter

o On Premise Connectivity Server (time spent in the back-end server) – Introscope

Manager Investigator Agent Host SUP Java Server Agent Name SMP

ODataProxy

o com.sap.mobile.platform.server.proxy.core.handler.proxyservlet (SAP Mobile

Platform processing time indicates the amount of time spent in SAP Mobile Platform

Server) – Introscope Manager Investigator Agent Host SUP Java Server

Agent Name Servlets

com.sap.mobile.platform.server.proxy.core.handler.proxyservlet

5.3 Viewing Change Analysis Data

View data collected for change analysis using SAP Solution Manager. SAP Mobile Platform Server

collects change analysis data for both application configuration and system configuration.


© SAP AG of 37

Prerequisites

Configure one of the imported certificates—SAPNetCA or SSO_CA—for SAP Mobile Platform

Server port number 8083. The certificate is issued for the fully qualified domain name of the

server host.

Implement the instructions in SAP Note 2075691 – CCDB extractor for SMP 3.0 SP04 ends

with an error: MultiExtractor E2E_CCDB_SMP3_EXTRACTOR Error:

"SYSTEM_FAILURE(97)"

Procedure

1. To view change analysis data for application configurations:

a. In Solution Manager, navigate to transaction solman_workcenter Root Cause

Analysis System Analysis

Note

SAP Note 1990123 and some SAP Solution Manager documentation refer to

Sybase Unwired Platform, the predecessor to SAP Mobile Platform. All

references to Sybase Unwired Platform denote SAP Mobile Platform.

b. Select the technical system, and click Change Reporting.

In the window that opens, you can find the database configuration and changes under

DBSTORE.

On the right side of the window, choose an entry to see its configuration.

To see the meaning of numerical property IDs, see Application Configuration IDs.

2. To view change analysis for system configuration:

a. Navigate to transaction solman_workcenter Root Cause Analysis End-to-End

Analysis .





© SAP AG of 37

b. Select the system maintained in the Landscape Management Database (LMDB), and

click Change Analysis Start New Window

A new window displays change analysis data, including changes to server

configuration files, such as props.ini.

In this section:

Application Configuration IDs

5.3.1 Application Configuration IDs

In SAP Solution Manager, you can view message IDs that identify current application settings,

endpoint configurations, push settings, password policies, and so on.

Android Google Cloud Messaging

Message ID Description

3200 Google Cloud Messaging (GCM) enabled

http://help.sap.com/saphelp_smp305svr/helpdata/en/56/e58299d5a54c84bf98f5c84e61bb57/content.htm


© SAP AG of 37

3201 GCM registration ID

3202 GCM sender ID

Apple Push Notification Service


2600 Apple Push Notification Service (APNS) enabled

2601 APNS alerts

2602 APNS badges

2603 APNS sounds

2605 APNS alert message

2606 APNS device token

BlackBerry Push


2700 BlackBerry push enabled

2701 Device PIN

2702 BlackBerry Enterprise Server (BES) push listener port

2705 Push application ID

2606 Push base URL

2608 Push listener status

2609 Push listener port

2610 Push listener type

Windows 8 Push


3400 Windows Notification Service (WNS) enabled

3401 WNS channel URI

Microsoft Push Notification Service


© SAP AG of 37


1 Connection server name

2 Connection server port

3 Connection farm ID

7 Connection domain

20 Connection use HTTPS

1200 Device model

1201 Device subtype

1202 Device phone number

1203 Device International Mobile Subscriber Identity (IMSI)

1300 Device advanced keep live

1301 Device advanced log items

1302 Device advanced trace level

1303 Device advanced trace size

1304 Device advanced allow roaming

1305 Device advanced relay server URL suffix

2001 Server publication key

2300 Custom 1

2301 Custom 2

2302 Custom 3

2303 Custom 4

2902 Application identifier

3000 Proxy application endpoint

3001 Proxy push endpoint

3100 Password policy enabled

3101 Default password allowed

3102 Password minimum length


© SAP AG of 37

3103 Password has digits

3104 Password has uppercase

3105 Password has lowercase

3106 Password has special characters

3107 Password expires in <N> days

3108 Password minimum number of unique characters

3109 Password lock timeout

3110 Password retry limit

3301 Capability password policy

3402 Microsoft Push Notification Service (MPNS) enabled

3403 MPNS channel URI

Application Settings


2903 Customization bundle ID (resource bundle)

2907 Notification mode

3303 Application version

3304 SDK version that the application supports

Pseudo Settings


3300 Capability HWA

3302 Capability client callable

20101 Device type

20102 Device ID

20103 Application connection ID

20104 Account user name

20105 Account code


© SAP AG of 37

20201 Last update time (Greenwich Mean Time)

20202 Group name

20203 Configuration ID (for device or template)

20301 Cache-only properties

20302 Application connection locked

Internal Properties


2900 Security configuration

2904 Role

3001 Push endpoint

4000 Connection log level

4001 Upload logs

4002 Log entry expiration

5001 Remote URL

5002 Endpoint name

5003 Anonymous access

6000 Business Transaction XML (BTX) end-to-end trace level

7000 Fiori feature vector policy all enabled

5.4 Viewing Technical Monitoring Data

View data collected for technical monitoring using SAP Solution Manager.

Prerequisites

Follow the instructions in SAP Note 2057141 – Grey Metrics in Technical Monitoring after upgrading

to SOLMAN SP12




© SAP AG of 37

Procedure

1. In Solution Manager, navigate to transaction solman_workcenter Technical Monitoring

System Monitoring .

2. Select the system maintained in LMDB, and click System Monitoring Start New Window

A new window displays all SAP Mobile Platform Server nodes in the system. To view

technical monitoring data for each node, expand Instance Availability in the right pane.

5.5 Viewing Client Tracing

In SAP Solution Manager, view and analyze end-to-end tracing information for clients.

Procedure

1. In a Web browser, access

https://sq7.wdf.sap.corp:44390/webdynpro/dispatcher/sap.com/tc~smd~navigation/Standalon

eApp?APP_ID=RCA_E2E_TRACE&sap-language=EN

2. Log in:

http://help.sap.com/disclaimer?site=https://sq7.wdf.sap.corp:44390/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=RCA_E2E_TRACE&sap-language=EN

http://help.sap.com/disclaimer?site=https://sq7.wdf.sap.corp:44390/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=RCA_E2E_TRACE&sap-language=EN


© SAP AG of 37

o User name – sapsupport

o Password – support

3. After the page loads, enter mobile as the filter, and click Search.

Tracing information appears for the application with which you registered the user.

smp monitoring.pdf

Documents

sap solution manager

sap application users

contents server monitoring

sap license auditing

analysis server features

sap mobile platform

viewing server log files

viewing workload analysis