User manual BUSINESS OBJECTS DATA SERVICES XI 4.0 INTEGRATOR GUIDE 14.0.0

[. . . ] Integrator's Guide SAP BusinessObjects Data Services XI 4. 0 (14. 0. 0) 2010-12-02 Copyright © 2010 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S. A. in the United States and in other countries. [. . . ] Operations include: · · · · · Put Operation (request/acknowledgment) options PutTopic Operation (request/acknowledgment) options PutGet Operation (request/reply) options Get Operation (request/reply and request/acknowledgment) options GetTopic Operation (request/acknowledgment only) options Note: When specifying a queue or topic, you must provide the JNDI queue name or the MQ queue name as indicated by the Adapter Configuration Type property. Put Operation (request/acknowledgement) options To set up an operation instance of type Put Operation in SAP BusinessObjects Data Services, complete the following fields in the Administrator. 77 2010-12-02 Using the JMS adapter FIeld Description Operation instance Thread count The unique operation instance name. In the Designer, your operation metadata object is imported with this name. The number of copies of Request/Reply operation to run in parallel. For parallel (asynchronous) processing of messages coming from real-time service, more than one copy should be used. But if the sequence of messages is important (synchronous processing), more than one thread should not be used. (Multiple copies of real-time services must be supported by multiple instances of Request/Reply. ) The default is 1. The number of times to retry this operation if it fails. Enter 0 to indicate no retries are to be attempted. Enter a negative number to indicate the operation should be retried indefinitely. Operation retry count Operation retry inter- The time (in milliseconds) to wait between operation retry attempts. val Display name Description Enable The display name of the operation instance. This display name is visible in the Designer's metadata browsing window. The description of the operation instance. This description is visible in the Designer's metadata browsing window. Whether to enable the operation to start at the same time as the adapter instance. · When true, the operation starts when the adapter instance starts. · When false, the operation needs to be started manually from "Adapter Operations Status" window of the adapter administrator. The name of the destination queue where the message will be sent. The DTD or XSD file name that defines the XML message used in the operation. The name of the XML root element. Destination Queue Request Format Request XML Root Element PutTopic Operation (request/acknowledgement) options To set up an operation instance of type PutTopic in the SAP BusinessObjects Data Services, complete the following fields in the Administrator. 78 2010-12-02 Using the JMS adapter Field Description Operation instance Thread count The unique operation instance name. In the Designer, your operation metadata object is imported with this name. The number of copies of Request/Reply operation to run in parallel. For parallel (asynchronous) processing of messages coming from real-time service, more than one copy should be used. [. . . ] In the section Defining the classpath, ensure the following third-party libraries are in the path: wrapper. class_path=$(ACTAHOME)\ext\lib\jnet. jar wrapper. class_path=$(ACTAHOME)\ext\lib\jsse. jar wrapper. class_path=$(ACTAHOME)\ext\lib\jcert. jar 4. After completing the configuration changes, restart the web server. If the web server starts successfully, then you should be able to access any web application supported by Tomcat via SSL. In the Designer, configure the web services adapter by opening the adapter datastore, click Advanced, and enter the client keystore path. 10. 1. 4 Legacy adapter error messages In addition to the error logs, the following list identifies web services client error messages and their descriptions: · Web services client is unable to create a SOAP request to send to a server. [. . . ]