Overview

As soon as CIS mobile is installed and running, no further routine action is necessary. However, in order to have a look at the ongoing operations there are several tools and protocols available for users and administrators.

Listed below are some of the possibilities. You can choose topics in the navigation-tree to get further details and instructions.
Check status

Essential information in CIS mobile consists of metadata concerning users logged into the system: the resources and applications they are using and the action they are taking. Some tools that can deliver this kind of information are:
 
The menu "active users" in the CIS mobile settings:
If users are logged on to CIS mobile you can see their IP-address, time of logon, the number of dialog steps taken and amount of data they have transferred.

to display this kind of information you have to be logged on as a user with administrator privileges.

Menu "active user sessions" in the S10 Repository:
Here you can find much the same information as shown in the "active users" tool, as well as the PID (Process Identifier) for each user-process. A new user-process is started by the dispatcher every time a user logs on to CIS mobile and can be debugged, e.g. with Visual Studio.

Task Manager und Resource Monitor:
The resources that an active CIS mobile user session consumes can be analysed by looking at the corresponding process in the windows task manager. Primarily this is the cpu-usage and allocated memory. The Resource Monitor can provide additional information as to disk-access, transferred network data, etc.

Eventlog in the S10 Repository:
Default events like a logon or logoff of any user and information about the license (expiry date, maximum of concurrent sessions) are written in the event log. Details of errors that have occurred can also be found here in most cases.
 
Displaying a trace

If an error occurs it may be neccessary to have a better look at the process flow of a user session, together with data requested and delivered from the server. This can be done with the tools below:

Trace in the S10 Repository:
Mainly the called methods for requesting data with input- and output parameters are listed here, such as requsts to the database, RFC calls and method-calls in the main application.

Protocols created by the IIS:
When the extended protocol is activated  in the IIS it will create a text file containing all HTTP queries to and the answers from the IIS. The query header contains metadata such as the time it was made and its destination. If you also want to see the wording you should use a specialized tool like fiddler (http://fiddler2.com).
Debugging

Debugging CIS mobile can be done with several tools:

HTML and JavaScript:
In all modern browsers the so called "developer tools" can help you to debug javascript. In internet explorer they can be activated by pressing F12 on the keyboard. It is also possible to start CIS mobile as an HTA application without starting IIS. Here the data request to the SAP system using the SAP GUI scripting interface will become visible, which is normally not the case.

ABAP:
The ABAP function modules and programs used by CIS mobile can be shown or edited by using the transaction SE37 or SE38. Please activate the ABAP debugger to analyse the process flow. 

VB.NET:
Most of the business logic of CIS mobile is implemented in VB.net methods. You can debug any process running, or create a new session that you can stop at any desired position in the code. We recommend Visual Studio from Microsoft which is also available as a free express version.
 
Device-dependent hints

CIS mobile is designed as an HTML5 web application and should therefore function and look the same on most modern devices and browsers.  Nevertheless, there are several unique features of some mobile devices that may have to be taken into account and even make the application easier. On the iPad, for example, it is possible to put an icon on your home-screen that will start CIS mobile as a full-screen applcation.