Publishing Customer-Specific Enhancements 

Use

We recommend you publish customer-specific enhancements for CATS notebook in the same way SAP Mobile Engine applications are published. You must compile the data definitions and your enhancement’s implementation in a ZIP file. The format must be compatible with the Mobile Engine.

The following provides you with a number of notes for creating this ZIP file. For more information, see the documentation on the Mobile Engine.

Prerequisites

You must store your data definitions in the following directory:

<meroot>\wwwroot\te_customer\extensions

Replace the character string <meroot> in this path specification, with the directory in which you have installed the Mobile Engine.

This specification affects the following files:

·        ci_types.xml (field types)

·        ci_records.xml (structures)

·        ci_tables.xml (tables)

·        CI_CATSDB_REC.xml and CI_CATSDB_TAB.xml (customer-specific fields in table CATSDB)

ZIP files contain two types of directory specifications:

...

       1.      Directory specifications that do not contain a file. They ensure that the system creates the specified directory when unpacking data from the ZIP file.

Example:  wwwroot/me/templates/customer_report_01/99/

       2.      Directory specifications that do contain a file. They ensure that the system creates the specified file in the specified directory when unpacking data from the ZIP file.

Example:  wwwroot/me/templates/customer_report_01/99/cats_report_01_de.htrc

If the ZIP files for your customer-specific enhancements contain directory specifications without files, the directory specifications must not relate to SAP directories that are created by the Mobile Engine. Otherwise, data could be lost when you de-install your customer-specific enhancements.

Example: wwwroot/me/services/ (this directory was created by the Mobile Engine)

ZIP files for your customer-specific enhancements may contain directory specifications with files that relate to SAP directories.

Example: wwwroot/me/services/customer_report_01.srvc

Procedure

Create ZIP File

Use the following stack processing file (batch program) as a template. Replace the character string in pointed parentheses with your customer-specific specification.

cd <meroot>

set basedir=c:\customer

rem Java – Add enhancements

jar cfM <customer-zip>.zip lib\<customer>.jar

rem Mimes for Customer Services

jar ufM %basedir%\<customer>.zip wwwroot\me\mimes\<customer-dir>

rem Customer Service File

jar ufM %basedir%\<customer-zip>   wwwroot\me\services\<customer_service>.srvc

jar ufM %basedir%\<customer-zip> wwwroot\me\templates\<customer_service>

rem Customer Repository

jar ufM %basedir%\<customer-zip> wwwroot\te_customer

Check Directory Specifications

After you have created the ZIP file, you can use the following command to display the directory specifications contained in the file: jar tf <customer-zip>. Check if the directory specifications fulfill the criteria listed above.