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, install the Introscope Enterprise Manager, and install and configure Introscope Agent.
In a clustered environment, you must install the Introscope Agent on each server node in the cluster. Repeat the Introscope Agent install and configure tasks on each server node. Introscope Enterprise Manager can be installed on any of the server nodes.
-javaagent:C:/SAP/MobilePlatform3/Introscope_Agent/wily/Agent.jar -Dcom.wily.introscope.agentProfile=C:/SAP/MobilePlatform3/Introscope_Agent/wily/core/config/IntroscopeAgent_SMP.profile -Dcom.wily.introscope.agent.agentName=SAPMobilePlatform -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 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 measured twice.
|SMP|Dispatcher Authentication||Time to authenticate client.|
|SMP|ODataProxy|Back end||Time to send and receive an HTTP request of an OData source, such as the SAP NetWeaver Gateway.|
|SMP|Application Connections|ApplicationODataProducer|createEntity||Create a new entity representing a client registration.|
|SMP|Application Connections|ApplicationODataProducer|getEntity||Retrieve an entity representing a client registration.|
|SMP|Admin|Process||Process a request from Management Cockpit.|
Introscope provides the ability to trace requests from clients. Introscope refers to this feature as a Transaction Trace Session. You can trace requests by either User ID or Request Header.
In the New Transaction Trace Session dialog, select User ID from the list.
Select equals, and enter the User ID. The User ID is the value provided by the client for authentication, and appears in Management Cockpit, under Application Registrations as the User Name.
Alternately, if the client specifies an HTTP header value of either X-SUP-APPCID or X-SMP-APPCID, you can filter transactions by the header value. The HTTP Cookie value with the same name does not work for filtering transactions.
In the New Transaction Trace Session dialog, select Request Header from the list.
Enter either X-SUP-APPCID or X-SMP-APPCID, depending on which header the client sends.
Select equals, and enter the APPCID sent by the client. The APPCID appears in Management Cockpit, under Application Registrations as the Registration ID.