Provision devices with a simple text configuration file that can be parsed by the client and from which data is then imported.
The configuration file allows you to configure the connection settings for the Hybrid Web Container. These settings are not per mobile workflow application.
- Create a text file named "Sybase_Messaging_”, followed by the application ID, with a .cfg extension. For example: Sybase_Messaging_HWC.cfg
- Enter the desired settings information in the .cfg file. See Mobile Workflow Connection Settings Configuration File.
- Save the .cfg file and place it either on the flash card for the device or simulator, or at a fixed platform specific location for each client.
- Android – the Android client searches the root of the flash card ("/sdcard/"), followed by the client file root (“/data/data/com.sybase.workflow/files.”).
- BlackBerry – the BlackBerry client searches the root of the flash card (“fileconn.dir.memorycard”), followed by the client file root (“file:///store/home/user/”).
- iOS – client support provisioning only through Afaria client deployment.
- Windows Mobile – the Windows Mobile client searches the root of any flash cards, followed by the root of the file system.
When the Mobile Workflow application is started, a search is performed for the provisioning file only if the device is not yet configured. Unconfigured is defined as missing one or more of the required connection properties (server name, port, user name, activation code, and so on).
- Log in to Sybase Control Center and register the Mobile Workflow application connection as described in the topic Registering and Reregistering Mobile Workflow Application Connections.
- Start the Mobile Workflow application on the device.
The settings are automatically picked up by the Hybrid Web Container.