Free SAP XI Books,Projects And Interview Questions

SAP XI XSLT/Java

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:25:00 +0530

Use

You can also implement XSLT and Java mappings yourself and save them as archives in the Integration 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.

You can also import archives in the PCK. PCK users can replace the terms Integration Repository, Integration Directory, and Integration Builder with PCK in the descriptions below.

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.

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

For details about the options that you have in XSLT and Java, see 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
Display Program (corresponds to double-clicking the XSLT program)	Displays the selected XSLT program
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.
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 code used to display the characters of a file:

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

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

Activities

Importing XSLT and Java Archives

...

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

2. To import the archive, choose 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 Integration Repository. To be able to select these mapping programs for a scenario at configuration time, you must assign them to an interface pair by using an interface mapping.

Interface mapping is not possible in the PCK.

XSLT Mapping

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:24:00 +0530

Use

Interface descriptions are in the form of XML documents. XSL Transformation (XSLT) is a member of the XML family of languages. It describes how an XML structure is transformed into another XML structure.

Features

XPath and

You can define mappings using XSLT together with XPath. XPath is also a specification of the XML family. Using XPath you can address any node in an XML document. XSLT implements XPath expressions to select substructures of an XML document. Using templates in XSLT you can define the mapping rules for the selected substructures.

You can use the XSLT tags and to include predefined templates for substructures in a complete mapping definition. In this way, you can reuse mappings for data types.

Runtime Constants

In the same way as in Java mappings, the mapping runtime in XSLT programs also returns parameters that you can use to evaluate information in the XSLT program that is not known until runtime:

Mapping Runtime Constants

Constant	Meaning	Relevant for PCK
$MessageClass	Classification of message. Possible values: · ApplicationMessage: Asynchronous or synchronous request message · ApplicationResponse: Response to request message · SystemAck, ApplicationAck, SystemError, ApplicationError: Acknowledgment messages	Yes
$VersionMajor	XI message protocol version. Example: For the XI 3.0 message protocol VERSION_MAJOR = 3 and VERSION_MINOR = 0.	No The PCK only uses message protocol XI 3.0.
$VersionMinor		No
$ProcessingMode	The mode of a message can be synchronous or asynchronous. Correspondingly, these constants can have the value synchronous or asynchronous.	Yes
$MessageId	The message ID. It can change during communication: · Response messages get a new message ID. · If new messages result from a message (the message is copied at multiple receivers), the new messages get new message IDs.	Yes
$RefToMessageId	The ID of a referenced message that belongs semantically to this message. For example, a response message uses this field to note which request message it belongs to.	Yes
$ConversationId	This field is not mandatory in the message. It enables an ID to be used to group messages that belong together. This field is not intended to be used for message serialization and has nothing to do with the serialization context (ABAP proxy runtime, Java proxy runtime).	Yes
$TimeSent	Time stamp specifying when the message was sent by the sender. The format of the time stamp is as follows: YYYY-MM-DDTHH:MM:SSZ The letter ‘T’ separates the date from the time, which is generally specified in UTC. If it is a local time, the closing ‘Z’ is omitted.	Yes
$Interface	Name of the sender interface. As of SAP XI 3.0, use this constant instead of the constant SENDER_NAME used previously.	Yes
$InterfaceNamespace	Namespace of the sender interface. As of SAP XI 3.0, use this constant instead of the constant SENDER_NAMESPACE used previously.	Yes
$SenderParty	Communication party that sent the message.	Yes See also: Communication party
$SenderPartyAgency	Issuing agency for the message sender.	Yes
$SenderPartyScheme	Identification scheme used by the sender.	Yes
$SenderService	Service on the sender side that sent the message. For example, the name of a business system. As of SAP XI 3.0, use this constant instead of the constant SENDER_SYSTEM used previously.	Yes See also: Service
$ReceiverName	Name of the receiver interface.	Yes
$ReceiverNamespace	Namespace of the receiver interface.	Yes
$ReceiverParty	Communication party to receive the message.	Yes See also: Communication party
$ReceiverPartyAgency	Issuing agency for the message receiver.	Yes
$ReceiverPartyScheme	Identification scheme used by the receiver.	Yes
$ReceiverService	Service on the receiver side that receives the message. For example, the name of a business system. As of SAP XI 3.0, use this constant instead of the constant RECEIVER_SYSTEM used previously.	Yes See also: Service
$MappingTrace	Returns a MappingTrace object that you can use to write messages in the monitoring.	No

If you want to access one of the constants in the XSLT program, you first have to declare the constant as a parameter, for example:

Java Enhancements

Moreover, using an XSLT definition you can call external Java methods to convert XML structures. This procedure gives you more flexibility when defining mappings. For more information about XSLT mapping with Java enhancement, see further documentation.

For more information about XSL/XSLT and XPath, see the Web page of the W3 Consortium.

Example

The function for booking a flight contains a parameter for the flight class. The outbound interface represents flight classes as symbolic values; in the inbound interface, flight classes have numerical values. The XSLT section converts the symbolic representation of the source system into the numerical representation of the target system.

The XPath expression match=“//hh:class“ selects the node in the outbound interface. The XSLT statement <xsl:choose> then defines the mapping rule for how the Integration Engine converts the symbolic values in the source system into the numerical values in the target system.

SAP XSLT Mapping with Java Enhancement

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:23:00 +0530

Use

The XSLT specification proposes an enhancement mechanism that enables the system to call external routines from XSLT for transforming XML structures. Java is a programming language that is supported by some Java XSLT processors as an enhancement language.

Using the XSLT mapping with Java enhancement, you can implement mappings quicker and more flexibly.

The working draft of the specification for XSL Transformations (XSLT) version 2.0 (version from December 20, 2001), does not define the features of the enhancement mechanism of the XSL transformation. There are also no accompanying standards that standardize the enhancement mechanism with Java. For this reason, XSLT processors available on the open market vary considerably in this respect.

Below is a description of one of the ways that the SAP J2EE Engine supports the XML Toolkit 2.0.

Activities

To implement an XSLT mapping with Java enhancement, proceed as follows:

...

1. Implement a Java class that contains the static methods of transforming XML documents or structures. Within this Java class you can also write messages to a trace that is visible in the message monitoring using the MappingTrace object.

The PCK does not support the MappingTrace object.

2. Include the method calls in the XSLT mapping program (see below).

3. Import the XSLT mapping program and the Java class as an archive to the Integration Repository. You can also use two different archives. The archive with the Java class must be in the same or an underlying software component version of the XSLT mapping program (see also: XSLT and Java Mapping).

The following example illustrates the procedure using a simple XSLT mapping for a message.

Example

The following table shows the message instance that you want to transfer to the target message, using an XSLT mapping program with Java enhancement.

Source Instance

Target Instance

Robert
White

Robert White

You must link the and <last-name> elements using a concat() Java method. You also want to write a message to the mapping trace in this method. Carry out the following steps in the XSLT mapping program in which you want to call this Java method:

...

1. Declare the Java class with a namespace definition as an attribute of the element. The namespace name can be any string you want; in the example it is called javamap (see below). The name of the namespace comprises the string java: as the prefix, and the complete name of the class. The complete name of a Java class comprises the name of the package and the class name. In the example this is com.company.group.MappingClass.

2. Use to define the parameters that you want to transfer in the method calls. In the example below, three parameters of the concat() method signature are defined correspondingly:

○ The first parameter takes the value of the element.

○ The last parameter takes the value of the element.

○ The parameter name inputparam is defined and enables you to transfer the constants of the StreamTransformationConstants class to the Java program.

In a Java mapping you have to implement the setParameter() method to enable the Integration Server to set the constants at runtime. For XSLT mappings with a Java enhancement it is sufficient to transfer the constants using the inputparam parameter. The mapping runtime sets the parameter. (see also: Java Mapping).

3. The method is called with the element . Specify the method with the corresponding parameters using the attribute select. The name for the namespace javamapreplaces the complete class name as a prefix.

SAP advises you to check the availability of methods before you call them. Test the XSL element using the attribute test, for example.

The XSLT program looks like this:

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:javamap="java:com.company.group.MappingClass">

The concat() class method of the Java class com.company.group.MappingClass groups the values of the and elements of the source instance together in a string that represents the value of the element of the target instance. The method also has the inputparam parameter of the Map type for writing information to the trace. You use this to first fetch a MappingTrace object and then use its methods addInfo()or AddWarning() to transfer messages to the trace:

package com.company.group;

import java.util.Map;
import com.sap.aii.mapping.api.AbstractTrace;
import com.sap.aii.mapping.api.StreamTransformationConstants;

public class MappingClass {

private static AbstractTrace trace = null;

public static String concat(String first,
String last,
Map inputparam)
{
// write trace information
trace = (AbstractTrace)inputparam.get(
StreamTransformationConstants.MAPPING_TRACE );

trace.addInfo(“concat():
\nfirst-name = “ + first +
“\nlast-name = “ + last );

// return concatentation

return first + ' ' + last;
}

//...

}

SAP XSLT Mapping of Adapter-Specific Message Attributes

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:22:00 +0530

The message header of an XI message contains a header for adapter-specific message attributes that the sender adapter can use to write additional information to the message header. This enables sender adapters to write information that is not known until runtime to the message (see: Adapter-Specific Attributes in the Message Header).

To change the fields of this header in a mapping program, you usually use a Java mapping program (see also: Java Mapping of Adapter-Specific Attributes). Nevertheless, you can also use the relevant classes as a Java enhancement in an XSLT program.

In this example, the Java classes for a mapping of the message header for adapter-specific message attributes are used in an XSLT program to change the parameter Directory of the file adapter. The XSLT program is structured thus:

...

1. First, the required Java classes are declared as namespaces:

○ java.util.map to be able to access the constants of the mapping runtime. The header for the adapter-specific message attributes is saved as a Map with the name DynamicConfiguration.

○ com.sap.aii.mapping.api.DynamicConfiguration and com.sap.aii.mapping.api.DynamicConfigurationKey for the header mapping.

2. The parameter name inputparam is defined and enables you to transfer the constants of the StreamTransformationConstants class to the Java runtime.

3. To change the header for the dynamic configuration, the XSLT program gets the Map for the header, creates a key for the parameter Directory in the file adapter, gets the current value for this parameter by using the method get(), links this directory path with the XSLT method concat and replaces the value by using the method put().

XSLT Mapping Program with Java Enhancement

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:map="java:java.util.Map"
xmlns:dyn="java:com.sap.aii.mapping.api.DynamicConfiguration"
xmlns:key="java:com.sap.aii.mapping.api.DynamicConfigurationKey">

select="map:get($inputparam, 'DynamicConfiguration')" />

select="key:create('http://sap.com/xi/XI/System/File', 'Directory')" />

select="dyn:get($dynamic-conf, $dynamic-key)" />

select="concat($dynamic-value, 'subfolder\')" />

select="dyn:put($dynamic-conf, $dynamic-key, $new-value)" />

Error Handling in XSLT

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:22:00 +0530

Use

In substantial XSLT programs it makes sense for the system to display an explanatory message when an error occurs. For this purpose there is the XSLT command . For example, the source document might contain a value that is not expected by the mapping program. In this case the system can display a message, and, if necessary, terminate processing of the mapping.

Alternatively, you can also call a Java method from your XSLT program, which writes information to the trace using the MappingTrace Object. For an example, see the XSLT mapping with Java enhancement section.

The PCK does not support the MappingTrace object.

Integration

Messages that are produced using the XSLT command or the MappingTrace object are visible in the trace function of the technical monitor (also see: Monitoring XML Messages).

Features

The XLST command has the following syntax:

<xsl:message terminate=“[yes|no]“>

The attribute Terminate determines whether processing of the XSLT program should be terminated (terminate=“yes”) or not (terminate=“no”). In both instances you can view the error message text by using the trace function for a message in monitoring (provided that you activated the trace function for the Integration Engine).

Example

The following example of a section of an XSLT program is taken from a mapping program with the name Person2Passenger.xsl. The XSLT commands in this section evaluate the current value of a tag from the source document and map the values as follows:

Source Document	Target Document
0	Mr.
1	Mrs.
(Other)	Mr. or Mrs.

The last instance is an exception for non-interpretable values. To retain this exception in the trace, a message is produced using :

Mr.
Mrs.

Mr. or Mrs.

Gender has neither value 0 nor 1!
"Mr. or Mrs." was chosen for title.

Since the target field can still be completed appropriately, processing is not terminated (terminate=“no“).

Trace Output

In the technical monitor, the section in the trace for the third instance looks as follows:

ENTER" func="CL_XMS_PLSRV_MAPPING~ENTER_PLSRV" />

XSLT transformation: xslt/wsxx/Person2Passenger completed. Gender has neither value 0 nor 1! "Mr. or Mrs." was chosen for title.

EXIT" func="CL_XMS_PLSRV_MAPPING~ENTER_PLSRV" />

Java Mapping

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:21:00 +0530

Purpose

You can implement mapping programs in Java. To process XML documents, use Java API for XML Processing (JAXP), for example. The JAXP supports the Document Object Model (DOM) and the Simple API for XML (SAX). This gives you great flexibility for mapping definitions with Java.

Implementation Considerations

Java mapping programs are not permitted to be stateful. You are therefore not permitted to perform actions such as writing data to a database table during a Java mapping. The Integration Server cannot track such side effects. Therefore, if an attempt is made to resend a message that has not been received by the receiver, the data may inadvertently be written to the database twice in a Java mapping.

If you use JRE classes in your Java mapping programs then the same program restrictions apply as for Enterprise Java Beans (EJBs). For a detailed description of these restrictions, see the relevant EJB specification. It is important that you also refer to the information under Scope of Functions in Runtime Environment (Java Mappings).

Features

The runtime environment for Java mappings has an mapping API. To use Java mapping, you must define a Java class that implements the Java interface com.sap.aii.mapping.api.StreamTransformation. This interface has two methods:

...

● public void execute(java.io.InputStream in, java.io.OutputStream out)

At runtime, the Integration Engine calls this method to execute a mapping. This method contains an input stream for the source document and an output stream for the target document as parameters. These streams are usually XML documents. You can import the substructures to be converted from the input stream and output the converted target document in the output stream.

● public void setParameter(java.util.Map param)

The Integration Engine transfers parameters to the mapping program with this method. It evaluates these parameters at runtime in the method execute(). This enables you to control the process flow of the mapping.

The transferred object that implements the Java interface java.util.Map contains seven key/value pairs as parameters. These correspond to corresponding fields in the message header. Apart from the MAPPING_TRACE constant, the value objects are of type java.lang.String. The key objects are defined in the class com.sap.aii.mapping.api.StreamTransformationConstants:

String Mapping Runtime Constants

Constant	Meaning	Relevant for PCK
MESSAGE_CLASS	Classification of message. Possible values ● ApplicationMessage: Asynchronous or synchronous request message ● ApplicationResponse: Response to a request message ● SystemAck, ApplicationAck, SystemError, ApplicationError: ● Acknowledgment Messages	Yes
VERSION_MAJOR	XI message protocol version. Example: For the XI 3.0 message protocol VERSION_MAJOR = 3 and VERSION_MINOR = 0.	No The PCK only supports message protocol XI 3.0.
VERSION_MINOR		No
PROCESSING_MODE	The mode of a message can be synchronous or asynchronous. Correspondingly, these constants can have the value synchronous or asynchronous.	Yes
MESSAGE_ID	The message ID. It can change during communication: ● Response messages get a new message ID. ● If new messages result from a message (the message is copied at multiple receivers), the new messages get new message IDs.	Yes
REF_TO_MESSAGE_ID	The ID of a referenced message that belongs semantically to this message. For example, a response message uses this field to note which request message it belongs to.	Yes
CONVERSATION_ID	This field is not mandatory in the message. It enables an ID to be used to group messages that belong together. This field is not intended to be used for message serialization and has nothing to do with the serialization context (ABAP proxy runtime, Java proxy runtime).	Yes
TIME_SENT	Time stamp specifying when the message was sent by the sender. The format of the time stamp is as follows: YYYY-MM-DDTHH:MM:SSZ The letter ‘T’ separates the date from the time, which is generally specified in UTC. If it is a local time, the closing ‘Z’ is omitted.	Yes
INTERFACE	Sender interface name. As of SAP XI 3.0, use this constant instead of the constant SENDER_NAME used previously.	Yes
INTERFACE_NAMESPACE	Sender interface namespace. As of SAP XI 3.0, use this constant instead of the constant SENDER_NAMESPACE used previously.	Yes
SENDER_PARTY	Communication party that sent the message.	Yes See also: Communication Party
SENDER_PARTY_AGENCY	Issuing agency for the message sender.	Yes
SENDER_PARTY_SCHEME	Identification scheme used by the sender.	Yes
SENDER_SERVICE	Service on the sender side that sent the message. For example, the name of a business system. As of SAP XI 3.0, use this constant instead of the constant SENDER_SYSTEM used previously.	Yes See also: Service
RECEIVER_NAME	Receiver interface name.	Yes
RECEIVER_NAMESPACE	Receiver interface namespace.	Yes
RECEIVER_PARTY	Communication party to receive the message.	Yes See also: Communication Party
RECEIVER_PARTY_AGENCY	Issuing agency for the message receiver.	Yes
RECEIVER_PARTY_SCHEME	Identification scheme used by the receiver.	Yes
RECEIVER_SERVICE	Service on the receiver side that receives the message. For example, the name of a business system. As of SAP XI 3.0, use this constant instead of the constant RECEIVER_SYSTEM used previously.	Yes See also: Service
MAPPING_TRACE	Returns a MappingTrace object that you can use to write messages in the monitoring.	No

Constraints

Note the following points when using static variables in Java mappings:

...

● Mappings can be executed in parallel. Therefore, several instances of a mapping may access a static field for read or write purposes at the same time.

● If mapping programs are executed more than once, the content of the static field may be lost. The reasons for this are as follows:

○ The content of a static field is lost if the Java class in question is reloaded. This happens after a cache refresh, for example.

○ If the mapping runtime consists of a cluster, the mapping classes on each node of the cluster are loaded separately. Each node has its own static fields.

Static fields can be used for constants and as a buffer, taking the above-mentioned points into consideration.

Example

The following example shows how the MAPPING_TRACE and RECEIVER_NAME parameters are set and evaluated in a Java mapping program:

import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import java.util.HashMap;
import com.sap.aii.mapping.api. AbstractTrace;
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationConstants;

public class JavaMapping implements StreamTransformation {

private Map param = null;
private AbstractTrace trace = null;

public void setParameter (Map param) {
this.param = param;
if (param == null) {
this.param = new HashMap();
}
}

public void execute(InputStream in, OutputStream out) {

try {

trace = (AbstractTrace)param.get(
StreamTransformationConstants.MAPPING_TRACE );
trace.addInfo(‘...’);

// ...

String receiverName = (String)param.get(

StreamTransformationConstants.RECEIVER_NAME);

// ...

}

See also: Special Access to Mapping Runtime Constants.

SAP XI Runtime Environment Java Mappings

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:20:00 +0530

Use

The Integration Server (or the PCK) uses the runtime environment for Java mappings to execute Java mapping programs. In addition to the mapping API you can use other standard libraries of the SAP J2EE server in loaded Java mapping programs.

Prerequisites

You are using the SAP NetWeaver Developer Studio.

To be able to write a mapping program in your Java development environment, the Java runtime environment (JRE) of the SAP J2EE server must be consistent with the JRE version of your Java development environment.

Features

The mapping runtime environment consists of the following runtime components:

● The Java runtime environment (JRE) of the SAP J2EE server

● The mapping API (see: Java Mapping)

○ sapxmltoolkit
The SAP XML Toolkit for Java contains a JAXP implementation.

○ com.sap.mw.jco
The SAP Java Connector enables ABAP-APIs to be called from the Java mapping. See the corresponding Javadoc documentation in the SAP Developer Network at https://www.sdn.sap.com/irj/sdn/javadocs (SDN user required).

○ com.sap.tc.Logging
The SAP Logging Service enables integration with the SAP Web AS Management tools. See the corresponding Javadoc documentation in the SAP Developer Network at https://www.sdn.sap.com/irj/sdn/javadocs (SDN user required).

Java programs that are loaded in an imported archive can use classes from the JRE, the mapping API, and these three standard libraries.

Search Path for Classes in Java Mapping Programs (Integration Server)

The mapping runtime environment is determined by the software component version and the namespace of the Java mapping to be executed. The environment also has a specific search sequence when loading the classes. If the mapping runtime environment finds a class in a path, the search is terminated and the subsequent paths are ignored. The paths are searched in the following sequence:

...

1. The paths of the JRE of the J2EE server

2. The path in which the mapping API is saved and the path of the standard libraries (SAP XML Toolkit, SAP Java Connector, SAP Logging Service), see above

3. Imported archives in the same namespace and the same software component version as the Java mapping to be executed

4. Imported archives in the same namespace and a subordinate software component version

5. Imported archives in other namespaces of the software component version

6. Imported archives in other namespaces of subordinate software component versions

Note that you can only load a class from the other namespaces if it is unique there.

If you use JRE classes in your Java mapping programs then the same program restrictions apply as for Enterprise Java Beans (EJBs). This includes the following, for example (for a detailed description, see the relevant EJB specification):

● Do not load a JDBC driver to use them directly. Instead, use the mapping lookup API (see: Mapping Lookups), or the JDBC Connector Service in the SAP J2EE Engine.

● Do not use the package java.io to write directly to files, or use it to read directly from files.

● Do not use a class loader in your classes.

● Within a Java mapping program, do not call java.lang.System.exit() or java.lang.System.setProperties().

● Do not create or use any threads.

● Do not use any network sockets.

It is important that you also refer to the introductory notes and restrictions in Java Mapping.

Search Path for Classes in Java Mapping Programs (PCK)

The mapping runtime environment of the PCK does not recognize software component versions. Therefore, fewer paths are searched during class loading. If the mapping runtime environment finds a class in a path, the search is terminated and the subsequent paths are ignored. The paths are searched in the following sequence:

...

1. The paths of the JRE of the J2EE server

2. The path in which the mapping API is saved and the path of the standard libraries (SAP XML Toolkit, SAP Java Connector, SAP Logging Service), see above

3. Imported archives in the same namespace as the Java mapping to be executed

4. Imported archives in namespaces other than that of the Java mapping to be executed

Note that you can only load a class from the other namespaces if it is unique there.

You cannot use a class loader in the classes of an imported archive.

Activities

Accessing the Runtime Environment in the SAP NW Developer Studio

● To access the mapping API, you must include the Jar file aii_map_api.jar in your class path. The Jar file is located in the following directory:

///j2ee/cluster/server/apps/sap.com/com.sap.xi.services/

● To include the three J2EE standard libraries in the class path of the NetWeaver Developer Workplace, call the Set Additional Libraries... function in your Eclipse project by calling the context menu and selecting the libraries com.sap.tc.Logging, com.sap.mw.jco, and sapxmltoolkit.

SAP XI Executing Value Mappings

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:19:00 +0530

Use

At configuration time you complete a value mapping table in the Integration Directory. In this table, values that are identical semantically are summarized in a group.

The mapping runtime provides an API to determine a target value for a source value during a Java mapping.

Features

Source and Target Representation

It is possible for an object (for example, a material number) to be identified differently at the receiver than at the sender (see: Value Mapping Table); in this case, an object is said to have different representations. An object representation consists of:

· A value mapping context to differentiate mappings from different applications

· An agency, which manages an identification scheme (for example, a company)

· The identification scheme used (for example, the scheme “customer number”)

· The value of the object, which is dependent on the identification scheme, the issuing agency, and the value mapping context

The package com.sap.aii.mapping.value.api contains the interfaces IFIdentifier, IFRequest, and IFResponse. You request objects for these interfaces to describe such representations. You use IFIdentifier to construct IFRequest, and when you execute the value mapping an object of type IFResponse is returned.

To make a value mapping request, use an object of type IFRequest. You construct the request by using a source label, a target label (both are objects of type IFIdentifier), and the source value. The result of the value mapping is an object of type IFResponse, which you can use to query one or more target values in addition to the information in the request.

Alternatively, you can execute a value mapping by transferring all required values to the method executeMapping() in a call (see below).

To make a request and execute a value mapping, you use a factory class and a service class. The methods of these classes are described below. The interface methods consist merely of access methods for the respective values:

Methods of the Interface IFIdentifier

Method	Return Value for Label
public java.lang.String getContext();	Value mapping context
public java.lang.String getAgency();	Agency
public java.lang.String getScheme();	Identification scheme

Methods of the Interface IFRequest

Method	Return Value of the Value Mapping Request
public IFIdentifier getSourceIdentifier()	Source label
public IFIdentifier getTargetIdentifier()	Target label
public java.lang.String getSourceValue()	Source value

Methods of the Interface IFResponse

Method	Return Value of the Value Mapping Result
public java.lang.String getSingleTargetValue()	Individual target value. If no valid target value is found, the method returns the null value. If more than one target value is found, the method returns the first value (determined randomly). To make sure that there is only one target value, use the method countTargetValues(). To query null values, you can also use the method hasTargetValues().
public java.lang.String[] getTargetValues()	All possible result values for the request
public int countTargetValues()	Number of result values
public boolean hasTargetValues()	true, if there is at least one result value; false if not.
public IFIdentifier getSourceIdentifier()	Source label
public IFIdentifier getTargetIdentifier()	Target label
public java.lang.String getSourceValue()	Source value

Mapping Request

The package com.sap.aii.mapping.value.api provides the following classes:

· XIVMFactory, to instantiate objects of type IFIdentifier and IFRequest

· XIVMService, to execute the value mapping

Methods of Class XIVMFactory

Method	Use
public XIVMFactory()	Constructor
public static IFIdentifier newIdentifier( java.lang.String context, java.lang.String agency, java.lang.String scheme)	Returns a label for the transferred values
public static IFRequest newRequest( IFIdentifier sourceIdentifier, IFIdentifier targetIdentifier, java.lang.String sourceValue)	Returns a value mapping request for a source label, target label, and source value

Methods of the Interface XIVMService

Method	Use
public XIVMService()	Constructor
public static java.lang.String executeMapping( IFIdentifier sourceIdentifier, IFIdentifier targetIdentifier, java.lang.String sourceValue) throws ValueMappingException	Returns a result value
public static IFResponse executeMapping(IFRequest request) throws ValueMappingException	Returns a value mapping result for a value mapping request
public static IFResponse[] executeMapping(IFRequest[] requests) throws ValueMappingException	Returns the value mapping results for several value mapping requests
public static java.lang.String executeMapping( java.lang.String sourceContext, java.lang.String sourceAgency, java.lang.String sourceScheme, java.lang.String sourceValue, java.lang.String targetContext, java.lang.String targetAgency, java.lang.String targetScheme)	Returns the result value If no result value exists, or an exception was thrown during execution of the value mapping, the method returns the null value

The exception ValueMappingException of the method executeMapping() is only thrown if an error occurs during the execution of the value mapping or if the value cannot be mapped for other reasons.

SAP XI Java Mapping of Adapter-Specific Message Attributes

kjkrish.sites@gmail.com (SAP Technology) — Fri, 16 Jan 2009 11:18:00 +0530

Use

Furthermore, developers have read and write-to access to adapter-specific attributes from within a Java mapping program.

Integration

XSLT programs (J2EE) and message mappings have mapping runtime constants that enable developers to access the same Java classes for adapter-specific-attribute mappings as in Java mapping programs (see XSLT Mapping of Adapter-Specific Attributes or Accessing Adapter-Specific Attributes). Mapping programs executed on the Integration Server and mapping programs for the PCK runtime both support this kind of access.

There is a separate interface for ABAP mappings (see the interface documentation for the interface IF_MAPPING_DYNAMIC_CONF).

Features

The key for accessing the value of an adapter-specific attribute comprises a namespace belonging to the adapter and an attribute name. The file adapter has the following attributes, for example.

Example Attributes of the File Adapter

Adapter Namespace	Attribute Name	Attribute Value
http://sap.com/xi/XI/System/File	Directory	C:\tmp\
http://sap.com/xi/XI/System/File	FileName	test-input.xml

The adapter namespace comprises the namespace in the Integration Repository in which the adapter metadata for the adapter is saved and the name of the adapter metadata object. The adapter namespaces for the adapters shipped by SAP therefore have the following format:

http://sap.com/xi/XI/System/

The adapter metadata objects are located in the namespace http://sap.com/xi/XI/System of software component SAP BASIS.

Mapping API

The classes for accessing the adapter-specific attributes are part of the mapping API (package com.sap.aii.mapping.api):

● com.sap.aii.mapping.api.DynamicConfigurationKey

Class used to create a key object for an adapter-specific attribute. The key object comprises the adapter namespace and the attribute name.

● com.sap.aii.mapping.api.DynamicConfiguration

Class used to read, change, or delete the value of an adapter-specific attribute. In a method, you use objects of type DynamicConfigurationKey to access the attributes.

For more information about the mapping API in SAP NetWeaver 2004 SPS14, see SAP Developer Network at https://www.sdn.sap.com/irj/sdn/javadocs (SDN user required).

Adapter-Specific Attributes and Multi-Mappings

In multi-mappings, there are multiple message headers with adapter-specific attributes. The mapping API can only access one message header. This has the following consequences depending on whether there are multiple source or target messages:

● 1:n Transformation

If there are multiple target messages, the header for the adapter-specific attributes is copied for each message. This means that you can only create one header for all adapter-specific attributes, and not individual headers.

● n:1 Transformation

This variant is only possible for multi-mappings in integration processes. If there is more than one source message, read-access to the adapter-specific attributes of the various message headers is not possible at runtime.

● m:n Transformation

All afore-mentioned restrictions apply here. Developers can at most write the same adapter-specific attributes for all target messages to the header, without read-access to the attributes of the source messages. m:n transformations are only supported within integration processes.

List of SAP XI TCODES

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:05:00 +0530

1.SXMB_IFR -> Start Integration Builder
2.SXMB_MONI -> Integration Engine - Monitoring
3.SXI_MONITOR -> XI: Message Monitoring
4.SXI_CACHE -> To Access IS runtime cache
5.sxi_cache -> XI data directory cacheidx1 -> idoc adapter
6.idx2 -> idoc metadata
7.idx5 -> monitocr idoc adapter
8.sm21 -> log di sistema
9.st22 -> dump abap (analisi di eccezioni)
10.smq1 -> messages inbound e outbound queue
11.smq2 -> messages inbound e outbound queue
12.smicm -> J2EE administration
13.st06 -> stato della macchina cpu memory filesystem machine status - cpu, 14.memory and file system.
15.st03 -> workload.
16.scc4 -> visualizza mandanti del sistema
17.we20 -> partner profiles
18.sale - ale settings
19.rz10 - edit system profile
20.sm59 ->mantain rfc destinations
21.bd64 -> mantain distribution model (trasformazioni)
22.SU01 -> users
23.AL08 -> list all logged users(user login logon)
24.SE10 -> Change Request
25.SE09 -> Change Request
26.WE05 -> All idocs
27.WE19 -> IDoc Test Tool
28.WE21 -> port definition
29.SE11 -> Data dictionary
30.SM21 -> log sistema xi
31.se37 -> mantain funcion modules
32.SICF -> http server configuration
33.SMGW -> trace, alzare livello di trace.
34.BD13 ->
35.BD64 -> modelli di distribuzione
36.pfcg -> Roles
37.tabella TSTC -> sap transactions codes
38.tabella TSTCT -> transaction descriptions
39.STMS -> transports management
40.SPAM -> apply ABAP support packages
41.SPAU -> manage objects after apply support packages
42.SE01 -> manage change requests
43.SLDCHECK -> Test SLD Connection
44.SLDAPICUST-> SLD API Customizing
45.SXMB_ADM -> Integration Engine - Administration
46.SXMB_MONI_BPE -> Process Engine - Monitoring
47.SE38 -> ABAP Editor
48.SE11 -> ABAP Dictionary
49.ST22 -> ABAP dump analysis
50.SPROXY-> ABAP Proxy Generation
51.SE80 -> Object Navigator
52.ABAPDOCU -> ABAP Documentation and Examples
53.SE24-> Class Builder
54.SM21-> Online System Log Analysis
55.SMQ1-> qRFC Monitor (Outbound Queue)
56.SMQ2-> qRFC Monitor (Inbound Queue)
57.RZ70-> SLD Administration
59.SM58-> Asynchronous RFC Error Log
60.SM59-> RFC Destinations (Display/Maintain)
61.SMICM-> ICM Monitor
62.WE60-> Documentation for IDoc types
63.BD87-> Status Monitor for ALE Messages
64.IDX1-> Port Maintenance in IDoc Adapter
65.IDX2-> Meta Data Overview in IDoc Adapter
66.WE05-> IDoc Lists
67.WE02-> Display IDoc
68.WE19-> Test tool
69.WE09-> Search for IDocs by Content
70.WE20-> Partner Profiles
71.WE21-> Port definition in XI
72.SE16-> Data Browser
73.SE93-> Maintain Transaction Codes
74.SM30-> Call View Maintenance
75.SU01-> User Maintenance
76.SM02-> System Messages

SWXF_PBUILDER -> for Detail BPM Process

SMQS - > to register the destination in QOUT scheduler

WEOUTQUEUE - > to start the queue processing

SMQR - > to register the queue

Idxpw - > to activate the IDOC message package

IDXP - > to monitor the message packages.

SAP Display SAP Directories SAP Transaction Code

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:04:00 +0530

AL11 RSWATCH0 Display SAP Directories

SAP Display table buffer (Exp. session) SAP Transaction Code

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:04:00 +0530

AL12 RSDBBUFF Display table buffer (Exp. session)

SAP Display Shared Memory (Expert mode) SAP Transaction Code \

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:04:00 +0530

AL13 RSTUNSHM Display Shared Memory (Expert mode)

SAP Customize SAPOSCOL destination SAP Transaction Code

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:03:00 +0530

AL15 RSHOSTLD Customize SAPOSCOL destination

Specify field group authorization SAP Transaction Code

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:02:00 +0530

AO91 RACSTABL Specify field group authorization

Logical field groups SAP Transaction Code

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 12:02:00 +0530

AO92 RACSTABL Logical field groups

KOBRA: Archiving SAP Transaction Code

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 11:58:00 +0530

ARKO RVEXARIN KOBRA: Archiving

TCode for Bill of Exchange List

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 11:56:00 +0530

F.25

SAP XI Connectivity

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 11:53:00 +0530

The following graphic provides an overview of all the components that can communicate with the Integration Server:

All the systems either send messages to, or receive messages from the Integration Server. It is the task of the Integration Server to distribute the messages received according to the rules that are configured in the Integration Directory. In this way, messages can be exchanged between all systems in a heterogeneous system landscape, regardless of whether a message was sent to the Integration Server using an adapter or the proxy runtime.

The Integration Server is set up for asynchronous communication. Synchronous communication is supported as required.

Therefore, you can exchange messages using Process Integration as soon as a runtime component can communicate with the Integration Server. The following sections describe the various communication parties of the Integration Server:

Communication Using Proxy Runtime

Communication Using Adapter Runtime

Communication with Embedded Process Integration

Communication Using Industry Standards (RosettaNet)

Communication Between PI Landscapes.

To conclude, the various options available for connecting systems to the Integration Server are summarized under the term Connectivity.

SAP Communication Using Proxy Runtime XI Connectivity

kjkrish.sites@gmail.com (SAP Technology) — Mon, 12 Jan 2009 11:52:00 +0530

Proxies are interfaces that are generated in application systems to communicate with the Integration Server. Proxy ‘originals’ are located in the Integration Repository, not in the application system. At design time, you use the Integration Builder to create the message interfaces you want to generate proxies for in application systems. The following graphic illustrates a proxy generation example using message interfaces:

The message interface determines which proxy objects are generated:

· Classes (Java, ABAP Object) are generated for outbound interfaces. By calling a method of the class you can transfer your data to the proxy runtime, which constructs the message and forwards it to the Integration Server. Proxies for outbound interfaces are called client proxies.

· Interfaces (Java, ABAP object) that are generated for inbound interfaces have to be implemented by the application for receiver processing. The proxy runtime calls this processing automatically once it has received an appropriate message. Proxies for inbound interfaces are called server proxies.

As illustrated in the graphic, you can generate proxy objects for an interface object in different systems. Only one version of the generated proxy can exist in a system, however. The generated objects are not client-specific if the system is an ABAP application.

Integrating Business Systems by Using SAP ABAP Proxies XI Connectivity

kjkrish.sites@gmail.com (SAP Technology) — Fri, 9 Jan 2009 16:26:00 +0530

The following documentation describes an integration scenario in which the business system, which is connected to the Integration Server by means of ABAP proxies, takes on the role of either a sender system or a receiver system, or both.

Use

SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.

SAP systems up to and including Release 4.6 are not able to exchange data by using XML messages and http. Such systems can only connect to the Integration Server by means of the IDoc adapter or the RFC adapter.

To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.

Description

You can use executable ABAP proxies to exchange messages between a business system and the Integration Server. Executable ABAP proxies are shipped by SAP with all platform-independent message interfaces. However, you have to generate these proxies first before you can use them for your own interfaces.

An application in a business system calls a client proxy to send a message. The proxy runtime receives the message and the Integration Server processes it.

To forward messages to a receiver business system, the proxy runtime receives the message on the receiver system, and then calls the ABAP class that implements the relevant server proxy.

The local Integration Engine has the task of a message sender or receiver here. It does not perform any mapping or routing actions.

Example

A SAP Web AS 6.40 system uses a client proxy to send a message to the Integration Engine. The message is processed by the Integration Server. Two receivers are determined:

· Another Web AS 6.40 system

· A system that cannot receive XML messages directly (for example, an SAP 4.0B system)

On the receiver side, the SAP Web AS 6.40-based system receives a message, which is used by a server proxy to call the ABAP class. The other receiver system must be connected by means of the IDoc adapter or the RFC adapter.

Integrating Business Systems by Using Java Proxies Process Integration XI

kjkrish.sites@gmail.com (SAP Technology) — Fri, 9 Jan 2009 16:26:00 +0530

The following documentation describes an integration scenario in which the business system, which is connected to the Integration Server by means of Java proxies, takes on the role of either a sender system (using client proxies) or a receiver system, or both.

Use

SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use Java proxies to connect to the Integration Server.

SAP systems up to and including Release 4.6 are not able to exchange data by using messages and http. Such systems can only connect to the Integration Server by means of the IDoc adapter or the RFC adapter.

To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the Java proxy interface (based on the adapter framework).

Description

You can use executable Java proxies to exchange messages between a business system and the Integration Server. Executable Java proxies are shipped by SAP with all platform-independent message interfaces. However, you have to generate these proxies first before you can use them for your own message interfaces.

An application in a business system calls a client proxy to send a message. Proxy runtime receives the message from a business sender system and the Integration Server processes the message further.

To forward messages to a receiver business system, the proxy runtime receives the message in the receiver system, and then calls the Java class that implements the relevant server proxy.

Example

A SAP Web AS 6.40 system uses a client proxy to send a message to the Integration Engine. The message is then processed by the Integration Server. Two receivers are determined:

· Another Web AS 6.40 system

· A system that cannot receive messages directly (for example, an SAP 4.0B system)

On the receiver side, the SAP Web AS 6.40-based system receives a message, which is used by a server proxy to call the Java class. The other receiver system must be connected by means of the IDoc adapter or the RFC adapter.

Communication Using Adapter Runtime Process Integration XI

kjkrish.sites@gmail.com (SAP Technology) — Fri, 9 Jan 2009 16:25:00 +0530

A central component of the adapter runtime is the Adapter Framework, with services for messaging, queuing, and security handling. The adapter framework supports the JCA standard (JCA: J2EE Connection Architecture) and communicates with Resource Adapters, which are either a component of usage type Process Integration or are provided by SAP partners. All adapters shipped by SAP are resource adapters, apart from the IDoc adapter.

The following adapter components are based on the adapter framework:

● Adapter Engine (J2EE): For adapter communication within a system network.

Partner Connectivity Kit (J2EE): Enables business partners who do not have Process Integration installed to receive and send messages (see: Integrating Smaller Business Partners with the PCK).

The following graphic provides an overview:

The Adapter Engine and the Business Process Engine are tightly linked to the Integration Engine. Whether the Adapter Engine is employed or not depends on the requirements of the collaborative process.

● You normally use the central Adapter Engine; it covers the conversion of the majority of collaborative processes within a system landscape.

● You can use the non-central Adapter Engine when you require it to work closer to the application systems. This may be necessary if a system is separated from the Integration Server by a firewall.

Both the central and non-central Adapter Engines are configured centrally in the Integration Directory, and a central monitor. The Partner Connectivity Kit (PCK), on the other hand, has to be configured locally because Process Integration is not installed.

The Plain J2SE Adapter Engine is only used in a few special cases. In this case, configuration and monitoring are both local.

Integrating Business Systems By Using the IDoc Adapter XI Connectivity

kjkrish.sites@gmail.com (SAP Technology) — Fri, 9 Jan 2009 16:25:00 +0530

The following documentation describes an integration scenario in which the business system, which is connected to the Integration Server by means of the IDoc adapter, takes on the role of either a sender system or a receiver system, or both.

Use

SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the IDoc adapter (or the RFC adapter). You can also connect non-SAP systems as sub-systems.

SAP recommends that you only use the IDoc adapter to integrate business systems with the Integration Server if such a scenario represents significant advantages for your business, for example, connecting business systems or integration processes that were previously not integrated. You must only change existing functioning IDoc communication scenarios (ALE scenarios, for instance) so that IDoc traffic is diverted to the Integration Server if this will result in significant improvements over the current set-up. An example of such a situation would be that you want to make the IDoc data available to additional receivers in the form of XML messages, or if you require an additional mapping. For information about configuring the IDoc adapter, see IDoc Adapter

Description

A business system is connected to the Integration Server by means of the IDoc adapter and exchanges IDocs with the IDoc adapter.

The IDoc adapter receives an IDoc from the business system and converts it into an XML message that is processed further by the Integration Server.

To forward an XML message to a receiver business system by using the IDoc interface, the IDoc adapter receives the message from the Integration Server, converts it into an IDoc, and then sends this IDoc to the business system.

Example

A SAP Release 4.0B system sends an IDoc of type MATMAS01 to the IDoc adapter on the Integration Server. The IDoc is converted to an XML message and processed further by the Integration Server. Two receivers of the IDoc data are determined

● Another SAP Release 4.0B system

● An SAP System, which is able to receive XML messages directly

The IDoc adapter at the outbound channel of the Integration Server converts the XML message back into an IDoc of type MATMAS01 and sends this to the 4.0B system. The other SAP system on the other hand simply receives an XML message.

Integrating Business Systems by Using the RFC Adapter Process Integration XI Connectivity

kjkrish.sites@gmail.com (SAP Technology) — Fri, 9 Jan 2009 16:24:00 +0530

The following documentation describes an integration scenario in which the business system, which is connected to the Integration Server by means of the RFC adapter, takes on the role of either a sender system or a receiver system, or both.

Use

SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the RFC adapter (or the IDoc adapter). For information about configuring the RFC adapter, see RFC Adapter.

Non-SAP programs that use the RFC SDK can only be used with the RFC adapter when there is a repository that contains the required metadata.

Description

A business system is connected to an Integration Engine by means of the RFC adapter. It exchanges data with the RFC adapter by using the RFC protocol.

The RFC adapter receives an RFC call from the business system and converts the RFC data into an XML message that is processed further by the Integration Engine.

To forward an XML message to a receiver system by using the RFC interface, the RFC adapter receives a message from the Integration Engine, converts it into an RFC call, and then executes this call.

Example

In a typical RFC scenario there is a sender and a receiver. The sender executes an RFC call from which it creates an XML message that is sent to the receiver. In a synchronous RFC call, the data from the response from the receiver is sent back to the original sender in the same way by using RFC protocol.

SAP does not recommend diverting an existing, functioning RFC connection between two SAP business systems so that the data passes through the Integration Server.