- For provisioning Android device applications, the file must be named “Sybase_Messaging_” followed by the package name with a “.cfg” extension. Any non-alphanumeric characters in the application ID will be replaced with underscores to avoid any conflicts with operating system restrings. For example, if the package name is “myApplication:1.0”, the file would be:
Sybase_Messaging_myApplication_1_0.cfg.
- For provisioning BlackBerry device applications, the file must be named “Sybase_Messaging_” followed by the Application ID with a “.cfg” extension. Any non-alphanumeric characters in the Application ID will be replaced with underscores to avoid any conflicts with operating system restrings. For example, if the Application ID is “myApplication:1.0”, the file would be:
Sybase_Messaging_myApplication_1_0.cfg.
- For provisioning Windows Mobile or Win32 device applications, the file must be named “Sybase_Messaging_” followed by the Application ID with a “.cfg” extension. Any non-alphanumeric characters in the Application ID will be replaced with underscores to avoid any conflicts with operating system restrings. For example, if the Application ID is “myApplication:1.0”, the file would be:
Sybase_Messaging_myApplication_1_0.cfg.
- For provisioning the Hybrid Web container used for Mobile Workflow, the file must be named "Sybase_Messaging_”, followed by the application ID (HWC), with a .cfg extension. Any non-alphanumeric characters in the application ID are replaced with underscores to avoid any conflicts with operating system restrings. For example, if the Mobile Workflow package application ID is "myApplication:1.0," the file would be:
Sybase_Messaging_myApplication_1_0.cfg.
Note: When configuring the connection settings for the Hybrid Web Container, settings are applied for the Hybrid Web Container. These settings are not per mobile workflow application.