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, install the SAP Mobile Platform Introscope Agent, and configure the agent.
-javaagent:C:\\SAP\\MobilePlatform3\\Introscope_Agent\\wily\\Agent.jar -Dcom.wily.introscope.agentProfile=C:\\SAP\\MobilePlatform3\\Introscop_Agent\\wily\\core\\config\\IntroscopeAgent_SMP.profile -Dcom.wily.introscope.agent.agentName=SAP Mobile Platform -XX:-UseSplitVerifier
Edit the IntroscopeAgent_SMP.profile file to specify the server name and port number where Enterprise Manager was installed.
Modify introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=localhost to correspond with the installed Enterprise Manager host, instead of localhost.
Modify introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=6001 to correspond with the installed Enterprise Manager host's port, which is 6001 by default.
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.
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 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.