Sun Toolkit NetBeans 5.5 Mobile Edition (http://netbeans.org/). 11.3.4 Component Orchestration The functionality of the above components is orchestrated by the main application (see Figure 11.7). As soon as the user selects which scenario is to be run, a specific set of actions are performed. Figure 11.7 depicts a running scenario, communica- tion between internal components of the application, and communication with external entities. 11.4 Secure JAVA Mobile Web Service Application This is a functional description of the developed secure JAVA mobile Web Service application for a purpose of secure communication with the described m-government Service Delivery Platforms Scenario Interface Security Storage Web services Start scenario Request form Show form Submit form Form data Request user credentials Retrieve user credentials Build document request Request SAML token Retrieve SAML token Request sign Signed document Request timestamp Retrieve timestamp Apply WS features WS security applied Send SOAP request Retrieve SOAP response Validate response Response validated Retrieve document response Store document Document stored End scenario Figure 11.7 m-government scenario sequence diagram. SOA-based platform. This JAVA application was developed in the framework of the FP6 SWEB Project. The assumption is that the user already has the JAVA application on his mobile phone/terminal and thus a procedure of downloading and activating the application is beyond a scope of this document. Possible usages are described in [5]. This client application comprises the following functionalities: Graphical User Interface (GUI) for presenting business functionalities to the end user Business (core) functionalities of the application-m-government functional- ity, for example, m-residence certificate Security functionalities Communication The proposed m-government secure JAVA mobile application objects and com- munity are represented in Figure 11.8. On Secure JAVA Mobile Application Business functionality: Security m-residence cert Comm