Start of Content Area

Function documentation Imported Archives (XSLT/Java)  Locate the document in its SAP Library structure

Use

You can also implement XSLT and Java mappings yourself and save them as archives in the Enterprise Services Repository. This enables you to reuse mapping programs that already exist. Mapping programs from imported archives are executed on the J2EE Engine of the Integration Server. 

Note

You can also import archives in the PCK. PCK users should replace the terms Enterprise Services Repository (ES Repository), Enterprise Services Builder (ES Builder), and Integration Builder with PCK in the following sections. 

Prerequisites

You have already implemented an XSLT or Java mapping and packed it in a Jar or Zip file. The file name (including path) of the archive must not be longer than 180 characters.

Caution

In the case of Java archives, it is very important that the archive contains the compiled classes (*class). Java source files are ignored by the Integration Builder and the mapping runtime.

Features

Details about the options that you have in XSLT and Java are contained in the XSLT Mapping  and Java Mapping  sections. It is also possible to call other mapping programs from a mapping program (see: References Between Mapping Programs).

Displaying and Changing Imported Mapping Programs in the Integration Builder

Function

Use

This graphic is explained in the accompanying text Display Program

(corresponds to double-clicking the XSLT program)

Displays the selected XSLT program

This graphic is explained in the accompanying text Change Program

Changes the selected XSLT program. In an Integration Builder editor you can either change lines or import another XSLT program. You must edit Java mappings externally and then import them again.

This graphic is explained in the accompanying text Open in Client Browser

Displays the selected program in the client browser. To display the selected mapping file, start the Integration Builder from the default browser on the PC for class- or xsl-files.

When displaying imported mapping programs, the viewer shows the encryption used to display the characters of a file:

●      In the case of XML files (XML, XSD, XSL), the Integration Builder can determine the encryption exactly, as it is specified in the header of the XML document.

●      The Integration Builder uses a default encryption for all other files: Latin-1 (ISO-8859-1) for files with the extension .properties, and UTF-8 for all others. To change the encryption, use the list box in the header area of the viewer. The options are the standard encryption of Java and Windows operating systems (XP or NT "Cp1252"). You can also enter other encryptions supported by the operating system.

Activities

Importing XSLT and Java Archives

...

       1.      In design maintenance in the Integration Builder, create a mapping object of type Imported Archive (see also: Creating an Object in the Integration Directory or Creating an Object in the PCK).

       2.      Import the archive by choosing Import Archive. Once you have activated the archive other users can export it again.

       3.      Save the archive.

Result

You have saved the mapping programs in the Enterprise Services Repository. To be able to select these mapping programs for a scenario at configuration time, you must assign them to a pair of operations by using an operation mapping.

Note

Operation mappings are not available in the PCK.

 

 

 

 

 

End of Content Area