HP XML Accelerator for SAP NetWeaver PI User Guide Version 1.
Copyright © 2010 Hewlett-Packard Development Company, L.P. 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.
Table of Contents 1 Installing the XML Accelerator.......................................................................................4 Introduction............................................................................................................................................4 What is being installed?..........................................................................................................................4 What is the SAP XML Accelerator?.......................................
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.
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.
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.
NOTE: An example would be /sapmnt//exe/jvm/linuxx86_64/ dapjvm_5.1.015/sapjvm_5. e. f. 7. SAP Instance: A list of SAP instances is displayed. Choose which SAP instance is to be used by the HP XML Acceleration Software. 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. Add the following to the JVM(s) classpath using the SAP config tool: • //lib/tarari_xtr_load.
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.
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.
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.
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.
3. 4. (Optional) Select Overwrite existing jar if you want the new converted JAR file to overwrite the name of a previously converted file. (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.
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. 3. 4. 5. 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. In the Output Document field, enter a full pathname for the output file from the test.
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.
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.
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.
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.
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 Unit
audit(5) A manpage. The manpage name is audit, and it is located in Section 5. Command A command name or qualified command phrase. Computer output 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.
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/ /build”. For JAVA_HOME default to $JAVA_HOME environment variable.
B Error guide Number Message Action Severity 1 There is no agent available to process the command. The agent is not loaded or an hardware error occurred. Make sure the agent is loaded. If Error not load the driver again and check if the agent is loaded correctly. 2 The agent driver is not loaded. Load the driver and check if the driver is loaded. 5 The encoding specified is an Check if the input XML document Warning unsupported character encoding.
Number Message Action 25 The job queue is full for job submission. If the problem persists report the Error problem to the Support Center. 26 Flow channel block error Check the syslog for indication of Error source of error and report the problem to the Support Center. 30 Failed to initialize agent properly. Check the syslog for indication of Error source of error and report the problem to the Support Center. 40 Unable to map internal buffer.
Number Message Action Severity application should handle appropriately. Otherwise report the problem to the Support Center. 62 Token buffer overflow. Check the syslog for indication of Error source of error and report the problem to the Support Center. 63 Error in obtaining a mapped buffer. Check the syslog for indication of Error source of error and report the problem to the Support Center. 64 An error occurred while freeing Check the syslog for indication of Error a buffer.
Number Message 77 Unable to initialize stream ID to Check the syslog for indication of Error be used for streaming XML source of error and report the input. problem to the Support Center. 78 This is not an xtr package. Stream ID is not initialized. Make sure the xtr package is installed. 79 The number of processes exceeded the specified XCX_MAX_NUM_PROCESS environment variable value or the maximum supported number for accelerated XML processing.
Number Message Action Severity 1013 The doc status token is not in the Check the syslog for indication of Error tokenization output. source of error and report the problem to the Support Center. 1014 Unexpected tokenization output Check the syslog for indication of Error length. source of error and report the problem to the Support Center. 1015 XML appears to be a denial of services attack. Make sure the input document is Warning valid.
Number Message Action Severity the problem to the Support Center. 26 6003 The desired property is not valid If the application is calling the Error for this node type cursor interface make sure the logic is correct. Otherwise report the problem to the Support Center. 6004 Root node not present Report the problem to the Support Error Center. 6005 No context node yet If the application is calling the Error cursor interface make sure the logic is correct.
Number Message Action Severity 12031 Insufficient value available for target element {element_name} to create the minimum number of target elements. Make sure the source document contains sufficient values to generate the target element or check if the mapping rule that generates values for the element is correct. Warning 12032 No value available for the required attribute {attribute_name}.
Number Message Action Severity in the Graphical Mapping Tool. Otherwise report the problem to the Support Center. 28 12044 Referencing an uninitialized graphical variable {variable_name}. 12046 An error occurred when reading Report the problem to the Support Error from the mapping input stream Center. or writing to the mapping output stream. 12047 An unexpected runtime error occurred when performing the mapping. Report the problem to the Support Error Center.
