Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Developing for webMethods OneData | REST Web Services | The Exception Queue and REST Services
The Exception Queue and REST Services
RESTful web services are routed through the data acquisition framework. Therefore, the exception queue is available to all of the DML operations performed using REST services. To enable the exception queue, set the request parameter partialCommit=true (the default setting). Once the queue is enabled, as records are extracted from the source, any exceptions that occur are sent to the exception queue.
Note: JSON REST APIs do not support the exception queue. For details, see Advantages and Limitations of JSON Over XML REST APIs.
There are different methods for retrieving records from the exception queue depending on whether the REST call was made using an implicit or explicit interchange mapping:
*Implicit interchange mapping. The output XML from the response contains an identifier tag. This tag has a unique token for the RESTful session that was executed. Use the token to retrieve exception queue records after you select RESTful Web Service for the exception queue type.
*Explicit interchange mapping. Use one of the interchange mappings to retrieve data from the exception queue just as you would after selecting the exception queue type as Interchange.

Copyright © 2011-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.