Customization Resource Bundle Recommendations

There are a variety of recommendations for working with customization resource bundles.

• You can use customization resource bundles only for OData SDK clients (Android and iOS).
• The expected format of the customization resource bundle is a JAR archive that contains MANIFEST.MF.

  • The manifest file must include these properties:
    • Customization-Resource-Bundle-Name
    • Customization-Resource-Bundle-Version
  • The property values cannot include a colon (":").
  • Sybase recommends the file size not exceed 5MB. File size is not enforced, but the larger the file, the slower the performance, subject to device platform hardware capabilities.

  See Managing Customization Resource Bundles in Developer Guide: Unwired Server Management API for information about the administration API that allows programmatic access to this functionality.

• You can deploy the same customization resource bundle to different applications, and it is treated independently for each application. The primary key is: application ID, customization resource bundle name, and version.
• Each deployed customization resource bundle:
  • Belongs to one and only one application. If you delete an application, all associated customization resource bundles are deleted as well. This implies that the actual binary is stored twice when assigned to two application IDs.
  • Is applicable only to:
    • The application to which it belongs.
    • The application connections that have the same application ID.
    • The application connection templates that have the same application ID.
  • Takes effect only when it is assigned to one or more application connections.
  • Is not assigned, by default, to either application connections or application connection templates.
  • Must be assigned explicitly by configuring an application connection or application connection template to use a customization resource bundle.
    Note: The application connection assignment configuration overrides that of the application connection template.
  • Can be exported to the same JAR file being deployed, meaning the format does not change.
• You can deploy 0, 1 or more customization resource bundles to one application as long as the name and version combination is unique.
• For each application connection or application connection template, you can assign only one primary customization resource bundle. Any deployed customization resource bundle is accessible to any application connection, regardless if assigned to the application connection properties or application connection template. This knowledge about the bundle name version allows any authenticated device/application user to access any customization resource bundle stored in the server.
• You can delete a customization resource bundle only if it is not assigned to any application connection and application connection template with the same application.