Modifying Manifest Files for Siebel Mobile Disconnected

The cache manifest file specifies the resources that Siebel Open UI must download to the disconnected client for offline use. Each application uses a separate cache manifest file that uses the following format:

application_name.manifest

where:

application_name identifies the name of the Siebel application, such as Siebel Service for Mobile. Siebel Open UI converts this name to lower case and replaces each space that the name contains with an underscore. For example, siebel_service_for_mobile.manifest is the cache manifest file that Siebel Open UI uses for Siebel Service for Siebel Mobile Disconnected.

Manifest files reside in the following folder on the Mobile Web Client:

AI_INSTALL_DIR\applicationcontainer_external\siebelwebroot\language_code\siebel_service_for_mobile.manifest

Siebel Open UI includes only the cache manifest files that it requires to support the Siebel application that you deploy.

For more information about the language_code, see Languages That Siebel Open UI Supports.

To modify manifest files for Siebel Mobile Disconnected

Add resources to the cache manifest file that your application uses, as necessary.
If your deployment requires custom resources to run an application offline, then you must add these resources to the cache manifest file that this application uses. For example, assume you must configure Siebel Open UI to run Siebel Service for Siebel Mobile Disconnected so that it can download the following resources, and then use them while the client is offline:
- my_style.css
- my_image.png
- my_script.js
In this situation, you can create a file named my_cache.manifest that includes the following information:
```
CACHE MANIFEST   
# 2012-4-27:v1   
# Explicitly cached 'master entries'.   

CACHE:   
files/my_style.css   
images/my_image.png   
scripts/my_script.js
```
The cache manifest file must use the HTML 5 standard. This standard allows you to run a Perl script in Step 4 that merges your custom cache manifest files into the predefined application cache manifest files. Siebel Open UI includes this script starting with the Siebel CRM 8.1.1.10 Quick Fix release.
Make a backup copy of the predefined manifest file that you must modify.
For example, siebel_service_for_mobile.manifest. You modify this file in Step 4.
It is recommended that you do this backup because the script that you run in this task modifies the siebel_service_for_mobile.manifest file. You can use this backup if you encounter a problem when running this script.
Open a Windows command line on the computer where the manifest files reside, and then navigate to the following folder (if doing this task on the Siebel Server):
```
AI_INSTALL_DIR\applicationcontainer_external\siebelwebroot\language_code
```
Enter the following command:
```
Perl mergemanifest.pl -s my_cache.manifest-d application_name.manifest
```
where:
- my_cache.manifest specifies the source manifest file. If you do not include the -s switch, then Siebel Open UI uses the custom.manifest file, by default.
- application_name.manifest specifies the destination manifest file. You must include the -d switch.
For example:
```
Perl mergemanifest.pl -s my_cache.manifest -d siebel_service_for_mobile.manifest
```
This command merges the custom manifest file that you modified in Step 1 into the predefined siebel_service_for_mobile.manifest file. Note the following:
- You must run this script any time you modify your cache manifest file or do an upgrade.
- You must make sure the source and destination files exist.
- This script adds the CACHE, NETWORK, and FALLBACK sections that reside in the my_cache.manifest, if they exist, to the end of the corresponding sections that reside in the siebel_service_for_mobile.manifest file. Your custom entries take precedence over the predefined Oracle entries that reside in this file.
- If a file contains more than one CACHE section, NETWORK section, or FALLBACK section, then this script merges these sections into one section. For example, if two CACHE sections exist, then this script merges these CACHE sections into a single CACHE section. This merge does not modify the sequence where the entries reside in the files.
- The script does not add duplicate entries to the destination file. If the merge results in duplicate entries, then Siebel Open UI removes the first duplicate from the destination file. It adds this removed entry to the destination.log file that resides in the folder where the destination file resides.
- The script does not include empty lines in the destination file.
- This script creates the destination .log file every time it runs.
- If the script finishes the merge, and if the result of this merge is identical to the destination file, then the script does not update the destination file, and the destination file retains its original timestamp.