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. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. [. . . ] 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 DTD or XSD file name defining the XML message used in this operation. The name of the XML root element. Destination Topic Message Format Request XML Root Element Persistent Message Whether to make published messages available to durable subscribers. When true, published messages are available to durable subscribers. PutGet Operation (request/reply) options To set up an operation instance of type PutGet Operation in SAP BusinessObjects Data Services, complete the following fields in the Administrator. 79 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. For parallel (asynchronous) processing of messages coming from real-time service, more than one copy is used. If the sequence of messages is important (synchronous processing), more than one thread should not be used. (Multiple copies of realtime services must be supported by multiple instances of Request/Reply. ) The default is 1. Enter a negative number to indicate the operation should be retried indefinitely. Operation retry count Operation retry inter- The amount of 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. 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 maximum time (in milliseconds) the operation should wait for the reply message. Request Queue Reply Queue Timeout Continue After Error Whether to continue after encountering an error. · When true, the operation instance remains in start stage even after the error. · When false, the operation instance stops after the error occurs during the process. Request Format The DTD or XSD file name that defines the Request XML message used in this operation. 80 2010-12-02 Using the JMS adapter Field Description Request XML Root Element Reply Format The name of the XML root element in the Request DTD or XSD. The DTD or XSD file name that defines the Reply XML message used in the operation. Reply XML Root Ele- The name of the XML root element in the Reply DTD or XSD. [. . . ] Inside the Connector tag, add/update the value of the keystoreFile and keystorePass parameters. The keystoreFile parameter should contain the *. keystore file path created when generating the keystore. The keystorePass parameter should contain the password used to create the keystore when generating it. 156 2010-12-02 Legacy adapter information 3. You might also need to modify the wrapper. properties file in the LINK_DIR\ext\webserv er\conf directory. [. . . ]