Examine the generated files.
- WorkflowClient.xml – this file establishes the mapping
between the XML messages and JSON calls to and from the
SAP Mobile Server server.
Note: The generated
WorkflowClient.xml does not include a completed
notification, so if you want the Hybrid App to be
server-initiated, you must write the Notification section. See
Creating Notifications to Make the Hybrid App
Server-Initiated.
- WorkflowMessage.js – defines some convenient functions for
accessing incoming application messages.
- Workflow.js – contains functions map to the MBO's
operations and object queries. The contents depend on the MBOs you select when
you run the wizard, since the wizard generates only the JavaScript API functions
for the selected MBOs.
- These files are static, container related, commonly used JavaScript libraries
and are copied from the
<SMP_HOME>\UnwiredPlatform\Mobile SDK
HybridApp\API\Container folder.
- Callbacks.js –
Hybrid Web Container callback functions.
- SUPStorage.js – client side key/value storage.
- hwc-comms.js – native container functions that are
invoked from the custom code.
- Camera.js – functions for accessing the device's
native camera functionality.
- Timezone.js – utility functions for getting the
local time.
- hwc-utils.js – native
Hybrid Web Container utility functions.
- Certificate.js – functions for processing
certificates.
- json2.js – functions for processing JSON data.
- ExternalResource.js – functions for accessing
external resources.
- datajs-1.0.2.js – functions for communicating
through an OData protocol.
- PlatformIdentification.js – utility functions for
checking the platform.
- hwc-api.js – native
Hybrid Web Container functions that allow users
access to Hybrid App metadata and notifications
from the custom code.