HP XML Accelerator for SAP NetWeaver Process Integration User Manual

HP XML Accelerator for SAP NetWeaver PI User Guide

Version 1.0

HP Part Number: AM313-9001A Published: January 2010 Edition: 1

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial

Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under

vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products

and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as

constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Warranty

To obtain a copy of the warranty for this product see the warranty information website:

http://h18004.www1.hp.com/products/servers/platforms/warranty/

1 Installing the XML Accelerator.......................................................................................4

Introduction............................................................................................................................................4

What is being installed?..........................................................................................................................4

What is the SAP XML Accelerator?........................................................................................................4

Prerequisites...........................................................................................................................................5

Hardware...........................................................................................................................................5

Software.............................................................................................................................................5

System Installation Instructions.............................................................................................................6

HP XML Acceleration Software Installation...........................................................................................6

SAP NetWeaver PI Update ....................................................................................................................7

For more information.............................................................................................................................8

General information..........................................................................................................................8

2 XML Accelerator Administration...................................................................................9

Introduction............................................................................................................................................9

What form does the GUI take?...............................................................................................................9

What functionality does the GUI provide?............................................................................................9

3 Using the HP XML Converter for SAP NetWeaver PI...............................................10

Getting Started......................................................................................................................................10

Exporting SAP Mappings.....................................................................................................................10

Converting SAP Mappings...................................................................................................................11

Testing a Compiled Mapping File........................................................................................................13

Using an Accelerated Mapping............................................................................................................13

4 Using the HP XML Adapter for SAP NetWeaver PI..................................................15

Getting Started......................................................................................................................................15

Driver Tab.............................................................................................................................................15

System Mode...................................................................................................................................15

Loading and Unloading the Driver.................................................................................................16

The Driver Info section displays the following information about the XML adapter driver:........16

Device Tab.............................................................................................................................................16

Board Info Diagnostics....................................................................................................................17

Memory Diagnostics........................................................................................................................17

Temperature Diagnostics.................................................................................................................17

Performance Diagnostics.................................................................................................................17

Agent Diagnostics............................................................................................................................17

5 Support and other resources.......................................................................................18

Contacting HP.......................................................................................................................................18

Before you contact HP.....................................................................................................................18

HP contact information...................................................................................................................18

Subscription service.........................................................................................................................18

Documentation feedback.................................................................................................................18

Typographic conventions......................................................................................................................18

A System updates executed by HP installer..................................................................20

B Error guide....................................................................................................................21

Table of Contents 3

1 Installing the XML Accelerator

Introduction

What is this chapter for? Who should read it? What is being installed?

This document explains the prerequisites and how to install the XML Accelerator. This is an advanced install guide for system administrators only. Casual users should consult their support group before continuing.

What is being installed?

The SAP XML Accelerator GUI which allows the user access to the Converter and the Adapter tools. The GUI is an XWindows application that is run on the same server that PI is installed on. The GUI communicates with server components that expose the functionality and configuration options of the XML Accelerator system.

What is the SAP XML Accelerator?

The SAP XML Accelerator is integrated software and special-purpose hardware that is used to accelerate the mappings in SAP NetWeaver XI and PI systems, increasing overall performance. The hardware component is an HP XML Accelerator PCIe card. The software components interface between NetWeaver PI and the XML Accelerator hardware, allowing for transparent use of the Accelerator in normal NetWeaver operation. Included in the software components are facilities for converting graphic mappings to objects that use the Accelerator and tools controlling the configuration and runtime performance of the accelerator. The mapping step that is accelerated by the XML Accelerator can be seen in the NetWeaver PI 7.1 System overview below as ‘MM’

The card looks like the following:

4 Installing the XML Accelerator

Prerequisites

What is needed before the install can begin?

This chapter will detail the software and hardware that the GUI depends on and where to find it.

Hardware

The XML Accelerator software stack and GUI depend on the installation of the XML Accelerator board. This must be installed and correctly configured in the PI system before continuing.

NOTE: The converter component of the XML Accelerator GUI does not require the hardware to be installed, the Adapter GUI does, however.

Software

XML Accelerator Software

The XML Accelerator GUI depends on the XML Accelerator software. To check if this is installed, open a command line on your server and run the following command:

cpp_manager -h

If the command is not found, the required XML Accelerator software is not present, please consult the User Manual that accompanied your XML Accelerator Board.

Java

The Java Virtual Machine version 1.5.0_12 or later is also required. Open a command line and type the following:

java -version

If the command is not found or the version is found not to be 1.5.0_12 or later please download and install the correct version from http://java.sun.com.

Prerequisites 5

System Installation Instructions

1. Install the server following the HP DL580 server installation instructions, see the DL580 User Guide for more information.

NOTE: The server is factory configured with the following options:

• SUSE SLES10 is factory installed on the XML Accelerator. Any operating system

installation steps should be omitted.

• The XML Accelerator is factory configured with a default processor and memory

configuration.

• The XML Accelerator is factory configured with SAS disks, a Networking expansion

card, and fibre channel HBA to support SAN storage.

• The XML Accelerator is factory configured to accept up to a total of 16 SAS disks without

requiring the instillation of an additional disk cage or SAS HBA.

• The XML Accelerator is factory configured with redundant hot plug power supplies.

• The XML Accelerator is factory configured with the battery backed up SAS HBA write

cache

2. Connect and configure networking configurations per site requirements.

3. Install SAP NetWeaver PI per site requirements.

NOTE: The minimum supported release level is PI 7.1.

HP XML Acceleration Software Installation

The base version of the acceleration software comes pre-installed on the server. It can be found on the system at /usr/local/Tarari/. Updated versions are available from the HP software depot. Personalized download instructions will provided separately from this document.

NOTE: Installation must be done as user “root”.

1. Copy the installer binary file to any directory.

NOTE: An example directory would be /tmp, and example release filename would be hpxmlacce_1.2.1.2.bin.

2. Stop the SAP application if it is running. The installation will fail and report an error if SAP NetWeaver is running

3. Navigate to installer directory (e.g. /tmp).

4. Make sure the downloaded installation file is marked as executable by running 'chmod +x hpxmlacce_1.2.1.2.bin'.

5. Run the installer hpxmlacce_1.2.1.2.bin.

6. Respond to the prompts as needed. a. Installation Directory Prompt: Enter the desired directory. The recommended default

location is /usr/local/Tarari.

b. Kernel Source Directory Prompt: Update the directory if the default directory does not

match the current location.

c. Rename Previous Directory: Enter "Yes" if prompted to rename the existing installation

directory.

d. SAP JVM: Enter the current SAP JVM home if the default Java Directory does not match

the SAP JVM directory

6 Installing the XML Accelerator

NOTE: An example would be /sapmnt/<SID>/exe/jvm/linuxx86_64/ dapjvm_5.1.015/sapjvm_5.

e. SAP Instance: A list of SAP instances is displayed. Choose which SAP instance is to be

used by the HP XML Acceleration Software.

f. SAP Profile: A list of SAP profiles is displayed. Choose the profile for the SAP instance

that will be using the HP XML Acceleration Software.

7. Add the following to the JVM(s) classpath using the SAP config tool:

• /<Installation directory>/lib/tarari_xtr_load.jar:/<Installation

director>/lib/tarari_raxj.jar

NOTE: An example would be /usr/local/Tarari/lib/ tarari_xtr_load.jar:/usr/local/Tarari/lib/tarari_raxj.jar

8. Start SAP NetWeaver PI as normal.

9. Import the modified SAP system profile using transaction RZ10. (Utilities->Import profiles

-> Of active servers)

SAP NetWeaver PI Update

In order for NetWeaver PI to utilize the XML Accelerator, a link must be created between PI and the XML acceleration libraries. The linkage is created by importing the XML acceleration jar file into SAP Enterprise Service Builder. This operation must be performed for the initial installation and all subsequent upgrades of the XML acceleration software.

1. Create a new Third-Party Software Component Version in the System Landscape Directory.

NOTE: The new Software Component Version details should reflect the name and version of the XML Acceleration package being installed, for example:

product version: HPXML 1.2 of HP.com

unit: xmlacc

vendor hp.com

name: XTR

version: 1.2.1.2

2. Start the SAP Enterprise Service Builder.

3. Create a new Software Component Version by the "Import from SLD" method. a. Select the newly created SoftwareComponent Version created in step 1 from the System

Landscape Directory.

b. Create a new Namespace within the Software Component Version, for example:

http://accel.hp.com/xmlacc.

4. Copy "/usr/local/Tarari/lib/tarari_xtr.jar" to a client machine.

5. Upload the tarari_xtr.jar file as an "Imported Archive" into the newly created namespace.

6. Create a dependency from any Software Component Version that will use accelerated mappings to the newly created XTR Software Component Version.

a. Open the target Software Component Version screen in the Enterprise Service Builder. b. Switch to the “Details” tab. c. Add the XTR Software Component Version as an “Underlying Software Component

Version”.

SAP NetWeaver PI Update 7

For more information

General information

HP XML Accelerator

http://www.hp.com/go/SAP/xmlaccelerator

SAP NetWeaver PI

http://www.sap.com/platform/netweaver/components/pi/index.epx

8 Installing the XML Accelerator

2 XML Accelerator Administration

Introduction

What is this section for, what is the SAP XML Accelerator GUI, what kind of GUI is it? What does the GUI allow me to do?

This section is for users of the HP XML Accelerator For NetWeaver PI. It is a guide to the administration functions and use of the browser for the Converter and Adapter components of the system. .

What form does the GUI take?

The GUI is a web based interface that is hosted by the same server that PI is installed on. The GUI communicates with server components that expose the functionality and configuration options of the XML Accelerator system.

What functionality does the GUI provide?

The GUI provides access to the two main components of the system, the Converter and the Adapter. The Converter allows the user to convert SAP graphical mappings to work with the Adapter to use the XML Accelerator. The Adapter also has user features which enable control, diagnostics and monitoring of the accelerator system.

The Convertor allows the user to compile and test the Message Mappings for the XML Accelerator. The Adapter user interface features include a component for the driver and a component for the physical XML card. The driver component allows the user to load, unload, inspect and configure the device drivers that are currently operating the XML Accelerator card. The card or hardware component allows the user to activate, deactivate, diagnose, inspect and configure the physical card installed in the SAP server system.

Each of these component features will be expanded upon later in with detailed descriptions of all the configuration options, actions and data views.

Introduction 9

3 Using the HP XML Converter for SAP NetWeaver PI

The HP XML Converter for SAP NetWeaver PI optimizes SAP JAR files to run faster during the XML conversion process.

The SAP NetWeaver technology platform is the technical foundation for all SAP applications. SAP NetWeaver provides the development and runtime environment for SAP applications. It can be used to develop custom applications and to integrate these applications with other applications and systems. SAP NetWeaver uses open standards and industry de facto standards.

SAP NetWeaver Process Integration (PI) is the SAP enterprise application integration software. Customers use this NetWeaver component to facilitate the exchange of information among a company's internal software and systems and those of external parties.

The following figure shows a system overview of SAP NetWeaver PI. The component labeled MM (memory mapping) represents the mapping step that is accelerated by the HP XML Converter.

Getting Started

To run this application, you must be <sid>adm. To start the HP XML Converter for SAP NetWeaver PI, follow these steps:

1. Assuming that the default /usr/local/Tarari/ installation is being used, enter the following command: source:

/usr/local/Tarari/config/set_tarari_environment_variables.csh

2. In an XWindow terminal, enter xtr_gui_compiler at the system prompt.

Exporting SAP Mappings

To export a message mapping for use by the HP XML Converter, follow these steps:

1. Open the desired message mapping in Netweaver PI - Enterprise Service Builder.

2. Press Ctrl-Shift-0 to access the Technical Object Information window.

10 Using the HP XML Converter for SAP NetWeaver PI

3. Save the message mapping JAR file by clicking the button to the right of the field Is Byte Code Available?, as shown in the following figure:

Converting SAP Mappings

To convert SAP mappings to run faster on the adapter, click the Convert tab on the main screen, if necessary. The following window appears:

To convert and optimize an SAP JAR file, follow these steps:

1. Click the Browse button to the right of the Mapping jar-file field and find the JAR file you want to convert.

The application autodetects the file’s mapping class information and displays it in the Mapping class field. If this information is not correct, type the correct information in this field.

2. (Optional) In the XTR jar-file field, enter a name for the converted JAR file. Alternatively, click the Browse button to the right of the field and find the file whose name you want to assign to the converted JAR file.

If you do not enter a file name, the application creates an output file name by adding an _XTR extension to the name of the input JAR file.

Converting SAP Mappings 11

3. (Optional) Select Overwrite existing jar if you want the new converted JAR file to overwrite the name of a previously converted file.

4. (Optional) Select a different Transactions option.

The HP XML Converter identifies transaction processing in message mappings, which enables mappings to be executed more efficiently at runtime. (Transactions are defined as repeated subdocuments nested in an enclosing document.) By default, the HP XML Converter detects transactions automatically so it can create the most highly optimized mapping.

You can disable auto detection of transactions but still use transaction optimization by specifying the transaction boundary. This option is useful if auto detection does not produce optimal acceleration because the converter cannot detect the transaction boundary.

The Transactions options are as follows:

• Auto Detect Transactions: (Default) This is the normal operation of the HP XML Converter

with full optimization.

• Manual Transactions: Select this option if auto detection does not produce optimal

acceleration and if you can specify a transaction boundary in the documents.

If you select this option you must enter a Target Txn (transaction) Node and a Source Txn Node. You describe the nodes using a basic XPath with each axis limited to an element name. You must explicitly specify each step in the ancestry to the node. The Source Txn Node is the containing element of the transaction in the incoming document. The Target Txn Node is the mapped destination of the transaction in the outgoing document.

• Disable Transactions:Select this option to disable transaction recognition and optimization.

Use this option only if the transaction optimization does not produce correct results.

5. Click the Browse button to the right of the Test document field and select a sample input file to be used to test this Message Mapping. As part of verifying the compile, the test file will be run through the original Message Mapping and the XTR version and compared

6. Click Compile.

When the compilation process is complete, the application fills in the name of the output mapping file, as shown in the following figure.

12 Using the HP XML Converter for SAP NetWeaver PI

Testing a Compiled Mapping File

Follow these steps to test a compiled mapping file created with HP XML Converter for SAP NetWeaver PI.

1. Click the Test tab.

The following window appears.

2. In the Input Document field, enter the name of the XML file to use for the test. Alternatively, click the browse button to the right of the field, and select an XML file.

3. In the Output Document field, enter a full pathname for the output file from the test. Alternatively, click the browse button to the right of the field, and select a file name.

4. Click Test to run the test.

5. When the test is complete, compare the test output with an expected output file, using the tool that you normally use to do this.

Using an Accelerated Mapping

To use the accelerated mapping in Netweaver PI, follow these steps:

1. In the Software Component Version and namespace that contained the original Message Mapping, create a new Imported Archive using the output JAR from the HP XML Converter.

2. Create a copy or modify the Operation Mapping associated with the original Message Mapping.

3. Change the Mapping Program type from Message Mapping to Java Class, as shown in the following figure

Testing a Compiled Mapping File 13

4. Select the accelerated mapping class from the newly imported archive.

The Operation Mapping is now ready for use with the accelerated mapping class.

NOTE: The Software Component Version that contains the Imported Archive associated with the accelerated mapping class must list the Software Component Version containing the XTR runtime library as an Underlying Software Component Version.

14 Using the HP XML Converter for SAP NetWeaver PI

4 Using the HP XML Adapter for SAP NetWeaver PI

The HP XML Adapter application is the runtime environment that enables you to use the HP XML Accelerator for SAP NetWeaver PI with SAP Graphical Mappings generated by the Converter (see Chapter 3 (page 10)) and XSLT. With the use of the Adapter application, PI is run normally and no code or operational changes are necessary to accelerate the execution of mappings. The Adapter application consists of a special mapping acceleration processor installed in the HP XML Accelerator, drivers, libraries, and monitoring and diagnostic facilities. The tool described in this manual provides an interface to the monitoring and diagnostic facilities as well as the ability to unload and reload the driver.

Getting Started

This application must be run as user “root”. To start the HP XML Converter for SAP NetWeaver PI, follow these steps:

1. Assuming that the default /usr/local/Tarari/ installation is being used, enter the following command: source:

/usr/local/Tarari/config/set_tarari_environment_variables.csh

2. In an XWindow terminal, enter xtr_gui_adapter at the system prompt.

Driver Tab

The Driver tab appears when you start the HP XML Adapter, as shown in the following figure:

System Mode

The top part of the Driver tab indicates whether the XML Adapter is in Online or Offline mode. Online is the default startup mode, assuming that the adapter driver is loaded.

• In Online mode, the HP XML Adapter is running and XML transactions are occurring. You can view information about the XML adapter (on the Device tab), the driver, and the system activity. As shown in the previous figure, you cannot load or unload the driver while in Online mode.

• In Offline mode, the HP XML Adapter is not running and no XML transactions are occurring. You can load or unload the driver. You can view information about the adapter (on the Device tab). If the driver is loaded, you can view information about the driver.

Getting Started 15

Loading and Unloading the Driver

IMPORTANT: The driver should not be unloaded or loaded while SAP is running.

Normally, the driver is loaded and the XML adapter is in Online mode when you start the HP XML Adapter for SAP NetWeaver PI. To unload the driver, follow these steps:

1. Select Offline as the System Mode.

The Unload button is enabled.

2. Click Unload.

The status changes to Driver is unloaded and the Unload button changes to Load.

When you unload the driver the XML adapter stops working, and the Jobs and Bytes information at the bottom of the tab is reset. If for some reason the XML adapter is not working properly, unloading and reloading the driver may resolve the problem. Unloading and reloading the driver is also a technique for reinitializing the state of the system, which you could use as a diagnostic step in the event of some problem or suspected problem.

To reload the driver after unloading it, click Load.

The Driver Info section displays the following information about the XML adapter driver:

• Version: Driver version.

• Jobs: Number of XML processing jobs submitted and completed since the last time the driver was loaded.

• Bytes: Number of bytes submitted and completed for XML processing jobs since the last time the driver was loaded.

NOTE: The Jobs and Bytes data is reset whenever you unload and reload the driver.

Device Tab

The following figure shows the Device tab:

The Device tab displays the results of various diagnostics that you can run on the HP XML Adapter. The figure shows the results of the Board Info diagnostics. To see other diagnostics results, such as Memory or Temperature, click a different Diagnostics category in the upper left

16 Using the HP XML Adapter for SAP NetWeaver PI

of the tab. The following sections briefly describe the type of information returned for the various diagnostics categories.

Board Info Diagnostics

Most of the Board diagnostic information is self-explanatory. Bus lanes indicates the number of PCIe lanes on the board.

Memory Diagnostics

The Memory diagnostics verify that memory is installed, display the amount of memory, and display the results of a memory test.

Temperature Diagnostics

The Temperature diagnostics return the current temperature of the board and of components on the board. They also display the recommended maximum and minimum board/component temperatures.

Performance Diagnostics

The Performance diagnostics return the maximum bits per second for XML transactions, maximum expected bus bits per second, and maximum expected engine bits per second. They also display results of bidirectional and unidirectional tests.

Agent Diagnostics

The Agent diagnostics return information such as the number of jobs completed by the agents on the board processor, the number of diagnostic flows, and the number of errors of various kinds.

Device Tab 17

5 Support and other resources

Contacting HP

Before you contact HP

Be sure to have the following information available before you call contact HP:

• Technical support registration number (if applicable)

• Product serial number

• Product model name and number

• Product identification number

• Applicable error message

• Add-on boards or hardware

• Third-party hardware or software

• Operating system type and revision level

HP contact information

For the name of the nearest HP authorized reseller:

• In the United States, see the HP US service locator webpage (http://welcome.hp.com/country/

us/en/wwcontact.html.)

• In other locations, see the Contact HP worldwide (in English) webpage:

http://welcome.hp.com/country/us/en/wwcontact.html.

For HP technical support:

• In the United States, for contact options see the Contact HP United States webpage: (http://

welcome.hp.com/country/us/en/contact_us.html)

To contact HP by phone: — Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days

a week. For continuous quality improvement, calls may be recorded or monitored.

— If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more

information about Care Packs, refer to the HP website: (http://www.hp.com/hps).

• In other locations, see the Contact HP worldwide (in English) webpage (http://

welcome.hp.com/country/us/en/wwcontact.html)

Subscription service

HP recommends that you register your product at the Subscriber's Choice for Business website:

http://www.hp.com/country/us/en/contact_us.html.

Documentation feedback

HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to docsfeedback@hp.com.

Include the document title and manufacturing part number. All submissions become the property of HP

Typographic conventions

This document uses the following typographical conventions:

%, $, or #

18 Support and other resources

A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells. A number sign represents the superuser prompt.

audit(5) A manpage. The manpage name is audit, and it is located in

Section 5.

Command

Computer output

A command name or qualified command phrase.

Text displayed by the computer.

Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you

must hold down the key labeled Ctrl while you press another key or mouse button.

ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH.

[ERROR NAME]

The name of an error, usually returned in the errno variable.

Key The name of a keyboard key. Return and Enter both refer to the

same key.

Term The defined use of an important word or phrase.

User input

Variable

Commands and other text that you type.

The name of a placeholder in a command, function, or other syntax display that you replace with an actual value.

[] The contents are optional in syntax. If the contents are a list

separated by |, you must choose one of the items.

{} The contents are required in syntax. If the contents are a list

separated by |, you must choose one of the items.

... The preceding element can be repeated an arbitrary number of

times.

 Indicates the continuation of a code example.

| Separates items in a list of choices.

WARNING A warning calls attention to important information that if not

understood or followed will result in personal injury or nonrecoverable system problems.

CAUTION A caution calls attention to important information that if not

understood or followed will result in data loss, data corruption, or damage to hardware or software.

IMPORTANT This alert provides essential information to explain a concept or

to complete a task

NOTE A note contains additional information to emphasize or

supplement important points of the main text.

Typographic conventions 19

A System updates executed by HP installer

The following items detail the changes made to the Server environment by the XML Accelerator software installer.

Install XTR Acceleration components

• tar -xvf xtr_X.X.X.X.s.tgz

• cd xtr_X.X.X.X.s

• For TARARIROOT default to “/usr/local/Tarari”.

• For KERNELSOURCE default to “/lib/modules/ <kernel-release>/build”.

• For JAVA_HOME default to $JAVA_HOME environment variable.

Build and load driver

• source /usr/local/Tarari/config/set_tarari_environment_variables.bash

• cd $TARARIROOT/src/drivers

• make && make install

• load_xmlcp

Add init.d file to automatically load XTR driver at boot

• Add /etc/init.d/tarari file.

• chkconfig tarari on.

Modify SAP profile

• Add the line: TARARIROOT = /usr/local/Tarari

• Add “$(TARARIROOT)/lib:$(DIR_SAPJVM)/jre/lib/amd64/server” to environment variables:

— LD_LIBRARY_PATH — SHLIB_PATH — LIBPATH

Example output:

SETENV_01 = LD_LIBRARY_PATH=$(TARARIROOT)/lib:$(DIR_SAPJVM)/jre/lib/amd64/server:$(DIR_LIBRARY):%(LD_LIBRARY_PATH) SETENV_02 = SHLIB_PATH=$(TARARIROOT)/lib:$(DIR_SAPJVM)/jre/lib/amd64/server:$(DIR_LIBRARY):%(SHLIB_PATH) SETENV_03 = LIBPATH=$(TARARIROOT)/lib:$(DIR_SAPJVM)/jre/lib/amd64/server:$(DIR_LIBRARY):%(LIBPATH)

• Add a new environment variable: SETENV_xx = TARARIROOT=$(TARARIROOT)

• Add a new environment variable SETENV_xx = XCX_MAX_NUM_PROCESS 2 when the variable has not been set to a higher value.

20 System updates executed by HP installer

B Error guide

SeverityActionMessageNumber

There is no agent available to process the command. The agent is not loaded or an hardware error occurred.

The agent driver is not loaded.2

The encoding specified is an unsupported character encoding.

Invalid parameter such as passing a null pointer or out-of-range value.

Out of virtual memory.7

Internal error occurred inside the accelerator card.

not load the driver again and check if the agent is loaded correctly.

driver is loaded.

has an XML declaration that specifies unsupported encoding (only UTF-8 and ASCII encoding is supported) or the byte order mark (BOM) at the beginning of the document indicates unsupported encoding.

being passed to a user interface. If not check the syslog for indication of source of error and report the problem to the Support Center.

Center.

source of error and report the problem to the Support Center.

ErrorMake sure the agent is loaded. If

ErrorLoad the driver and check if the

WarningCheck if the input XML document

ErrorCheck if an invalid parameter is

ErrorReport the problem to the Support

ErrorCheck the syslog for indication of

Internal software error.10

Out of system resources such as reaching the maximum number of concurrent jobs etc.

An internal agent driver error.12

The document has not been processed.

Buffer pool not initialized.14

An error occurred while performing IO.

The file size is less the minimum required size.

ErrorReport the problem to the Support

Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorIf the application is calling the RAXJ or RAX interface directory make sure the document is tokenized before further processing is made. Otherwise report the problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorMake sure the input XML document is not empty.

The CPP library is not initialized23

source of error and report the problem to the Support Center.

ErrorCheck the syslog for indication of

SeverityActionMessageNumber

The job queue is full for job submission.

Flow channel block error26

Failed to initialize agent properly.

Unable to map internal buffer.40

Failed to unmap internal buffer.41

Unable to create agent channel49

Unable to submit job to hardware.

Unable to retrieve job after it is submitted.

ErrorIf the problem persists report the

problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorIf the problem persists check the syslog for indication of source of error and report the problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

Mismatch between job id submitted and job id retrieved.

Token buffer overflow.62

Error in obtaining a mapped buffer.

An error occurred while freeing a buffer.

Invalid buffer specified.65

Unable to create thread.67

No more tokens to retrieve.68

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorIf the application is calling the RAXJ or RAX interface this indicates there are no more tokens and the application should handle appropriately. Otherwise report the problem to the Support Center.

22 Error guide

The end of token fragment is reached.

InformationIf the application is calling the RAXJ or RAX interface this indicates the end of a token fragment is reached and the

application should handle appropriately. Otherwise report the problem to the Support Center.

SeverityActionMessageNumber

Token buffer overflow.62

Error in obtaining a mapped buffer.

An error occurred while freeing a buffer.

Invalid buffer specified.65

Unable to create thread.67

No more tokens to retrieve.68

The end of token fragment is reached.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

InformationIf the application is calling the RAXJ or RAX interface this indicates the end of a token fragment is reached and the application should handle appropriately. Otherwise report the problem to the Support Center.

Unable to retrieve system statistics.

Agent context block overflow.71

Error is flushing jobs to the agent.

Too many tokens are read into a buffer.

Error in tokenize job cleanup.74

The process or thread has a different job mode than expected.

Flow channel in use76

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorReport the problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

SeverityActionMessageNumber

100

Unable to initialize stream ID to be used for streaming XML input.

This is not an xtr package. Stream ID is not initialized.

The number of processes exceeded the specified

number for accelerated XML processing.

Unable to allocate a job thread info.

Thread info not initialized.81

Thread info is in use.82

Maximum number of allowable application threads reached.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

WarningMake sure the xtr package is installed.

Make sure the XCX_MAX_NUM_PROCESS environment variable is setXCX_MAX_NUM_PROCESS appropriately or the maximumenvironment variable value or number of supported processesthe maximum supported for accelerated XML processing is not exceeded.

ErrorReport the problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorIf the problem persists check the syslog for indication of source of error and report the problem to the Support Center.

111

1001

1004

1005

1006

1007

1008

1009

The TARARIROOTenvironment variable not set.

An XML syntax error is detected when parsing the document.

The output directive specified is not one of the valid value.

The document exhausts the internal resouce of the agent. This could be using up context stack by deeply nested document structure.

An internal error occurred in the tokenizer.

The XML input exceeds the size limit.

The input is an invalid XML document.

requested.

ErrorMake sure TARARIROOT environment variable is set.

InformationMake sure the input document contains well-formed XML.

ErrorReport the problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorBreak down the document into smaller fragments to be processed.

ErrorMake sure the document is valid according to the corresponding schema.

WarningDo not use unsupported feature.An unsupported feature is

1012

24 Error guide

Document is already fully tokenized i.e. the last fragment of the document has been tokenized or the end of root element has been detected if requested.

WarningMake sure the tokenization API is not called after the document is fully tokenized.

SeverityActionMessageNumber

1013

1014

1015

2001

2003

2039

2060

2991

2992

The doc status token is not in the tokenization output.

Unexpected tokenization output length.

XML appears to be a denial of services attack.

Unable to allocate resources required to process XPaths.

Maximum XPaths depth exceeded.

Unexpected end of tokens detected.

Error with internal data structures

XPath group id information is not initialized.

Mixed group and non-group XPath expression load.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

WarningMake sure the input document is valid.

WarningCheck the syslog for indication of source of error and report the problem to the Support Center.

WarningCheck if the XML document has nested element depth greater than

64.

ErrorReport the problem to the Support Center.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

WarningMake sure the XPaths are loaded before XPath processing is made.

WarningMake sure not both group and non-group XPath expressions are loaded.

2998

2999

3010

3011

3012

3013

3020

3990

6001

XPath expression id is out of range.

Attempted to retrieve XPath results without first processing XPaths on the given document.

Compiler called with a bad group size parameter

Compiler called with the sum of the number of expressions <= 0

Compiler called with a null input buffer pointer.

Compiler called with a negative or zero buffer size.

The compiler's parser detected a syntax error in one of the expressions.

Mixed group and non-group XPath expression compile.

An internal error occurred while navigating the cursor

WarningMake sure a valid XPath expression identifier is specified or the correct XPath expression set is loaded.

WarningMake sure XPath processing are called before retrieving the results.

ErrorReport the problem to the Support Center.

WarningMake sure the list of XPath expressions passed to the XPath compiler are valid.

WarningMake sure not both group and non-group XPath expressions are compiled.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

6002

The desired document node was not found.

ErrorIf the application is calling the cursor interface make sure the logic is correct. Otherwise report

the problem to the Support Center.

SeverityActionMessageNumber

6003

11005

11006

The desired property is not valid for this node type

Root node not present6004

No context node yet6005

Unable to create cursor.11002

Undefined prefix.11003

Unresolved entity reference.11004

Unable to find the end of an element.

Unable to find the start of an element.

ErrorIf the application is calling the cursor interface make sure the logic is correct. Otherwise report the problem to the Support Center.

ErrorReport the problem to the Support Center.

ErrorIf the application is calling the cursor interface make sure the logic is correct. Otherwise report the problem to the Support Center.

ErrorReport the problem to the Support Center.

WarningMake sure the prefix is defined in the XML document.

WarningMake sure the entity reference is one of the predefined entity amp lt gt quot or apos.

ErrorReport the problem to the Support Center.

11007

12001

12011

12012

12021

12022

12023

End of document is reached unexpectedly.

The XML accelerator Java library loaded has different version number than the native library.

An error occurred when loading the compiled mapping class data.

The loaded compiled mapping class data contains invalid information.

Unable to obtain a lock during XML Accelerator initialization.

Unable to create a worker thread.

Error in obtaining the Java JVM object.

Unable to attach to a Java thread.12024

No transaction is found.12025

ErrorReport the problem to the Support Center.

WarningMake sure all the native libraries and the Java libraries are of the same version.

ErrorMake sure a valid version of the compiled graphical mapping jar file is loaded.

ErrorCheck the syslog for indication of source of error and report the problem to the Support Center.

ErrorIf the problem persists report the problem to the Support Center.

ErrorReport the problem to the Support Center.

26 Error guide

Unexpected job count.12026

Center.

ErrorReport the problem to the Support

SeverityActionMessageNumber

12031

12032

12033

12034

Insufficient value available for target element {element_name}

of target elements. check if the mapping rule that

No value available for the required attribute {attribute_name}.

Insufficient values in the value queue for the useOneAsMany function.

Insufficient contexts in the context queue for the useOneAsMany function.

contains sufficient values to generate the target element orto create the minimum number

generates values for the element is correct.

contains sufficient values to generate the target attribute or check if the mapping rule that generates values for the attribute is correct.

contains sufficient values to generate the correct values for the useOneAsMany function or check if the mapping rule that generates the values for the useOneAsMany function is correct.

WarningMake sure the source document

12035

12036

12037

12038

12039

12040

Cannot find the indexed {index} value by the CopyValue function.

Invalid string value {string_value} for number.

Invalid sort comparator value {comparator_id}.

The number of items in the key and data list for keyed sort function do not match.

Invalid or not implemented operation called.

Invalid or out of range memory access.

Illegal operation performed.12041

WarningMake sure the source document contains that "index" + 1 values for the CopyValue function.

WarningMake sure the source document contains correct value for numbers or check if the the mapping rule that generates the number is correct.

ErrorReport the problem to the Support Center.

WarningMake sure the number of key value and data value have the same number or check if the mapping rule that generates the key and data values is correct.

ErrorReport the problem to the Support Center.

WarningThis refers to illegal arithmetic operations. Check if there are any value that could cause illegal arithmetic operations or if the mapping rule that generates the numbers produces appropriate values.

12042

Unable to find mapped value for {from_value} by FixedValues or value mapping function.

WarningMake sure the mapped value are defined either in the mapping table for the FixedValues function or via the Value Mapping screen

in the Graphical Mapping Tool. Otherwise report the problem to the Support Center.

SeverityActionMessageNumber

12044

12046

12047

12048

12049

Referencing an uninitialized graphical variable {variable_name}.

An error occurred when reading from the mapping input stream or writing to the mapping output stream.

An unexpected runtime error occurred when performing the mapping.

An error occurred when formatting the number {number}

number characters. rule that generates the number

An error occurred when formatting the date string {date} using format {date_format}.

is set before it is referenced in a mapping rule. Otherwise report the problem to the Support Center.

Center.

make sure it contains valid number value the format patternusing format {number_format}. used is valid and if the mappingThe string may contain invalid

produces valid numbers.

make sure it contains valid date value the format pattern used is valid and if the mapping rule that generates the date value produces valid date value.

WarningMake sure the graphical variable

ErrorReport the problem to the Support

WarningCheck the source document to

12050

12051

12052

12053

An error occurred when invoking the mapping function {function_name}.

The retrieved value for {input_or_output} parameter

type is {parameter_type}. or standard function that uses the

Unimplemented standard function {function_name} is

an older version of the software. or if one is running an older

The function {function_name} cannot be found. Make sure if the correct mapping class is loaded.

Center.

parameters imported into a mapping program. Make sure the{parameter_name} is of incorrect parameter type defined matchestype. Expected type is with what is expected by the user{expected_type} while retrieved

parameter.

mapping class is not compiled by a newer version of the compilercalled. Check if one is running

version of the XML adapter software.

class loaded is the same version used to generate the compiled graphical mapping jar file.

ErrorReport the problem to the Support

WarningThis refers to message mapping

WarningMake sure if the graphical

WarningMake sure the graphical mapping

28 Error guide

HP XML Accelerator for SAP NetWeaver Process Integration User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

HP XML Accelerator for SAP NetWeaver PI User Guide

Table of Contents

1 Installing the XML Accelerator

Introduction

What is being installed?

What is the SAP XML Accelerator?

Prerequisites

Hardware

Software

System Installation Instructions

HP XML Acceleration Software Installation

SAP NetWeaver PI Update

For more information

General information

2 XML Accelerator Administration

Introduction

What form does the GUI take?

What functionality does the GUI provide?

3 Using the HP XML Converter for SAP NetWeaver PI

Getting Started

Exporting SAP Mappings

Converting SAP Mappings

Testing a Compiled Mapping File

Using an Accelerated Mapping

4 Using the HP XML Adapter for SAP NetWeaver PI

Getting Started

Driver Tab

System Mode

Loading and Unloading the Driver

The Driver Info section displays the following information about the XML adapter driver:

Device Tab

Board Info Diagnostics

Memory Diagnostics

Temperature Diagnostics

Performance Diagnostics

Agent Diagnostics

5 Support and other resources

Contacting HP

Before you contact HP

HP contact information

Subscription service

Documentation feedback

Typographic conventions

A System updates executed by HP installer

B Error guide