DevOps Edition for Continuous Integration 10.4 | Integration Server Administrator's Guide | Using an HTTP Interceptor | Consideration for Creating an HTTP Interceptor
 
Consideration for Creating an HTTP Interceptor
Keep the following information in mind when creating an HTTP interceptor:
*You can register only one HTTP interceptor per Integration Server.
*The class that contains the HTTP interceptor must implement the com.softwareag.is.interceptor.HTTPInterceptorIFC interface and provide implementations of both methods in the class, specifically preProcess and postProces. For more information, see the webMethods Integration Server Java API Reference.
*Using an HTTP interceptor delays processing of a request. Any logic the preProcess method executes to determine whether or not to continue with request processing needs to be done synchronously. However, if the preProcess method includes logic that can be done asynchronously by spawning off another thread, regular processing can proceed as quickly as possible.
*Using an HTTP interceptor delays sending of the response.
*An HTTP interceptor cannot modify the content of the HTTP request or response. For an HTTP request, Integration Server passes the HTTP interceptor a byte array representation of the input stream. When the HTTP interceptor completes execution, as long as the interceptor does not throw an HTTPInterceptorException to reject the HTTP request, normal Integration Server processing continues with the original input stream.

Copyright © 2017-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.
Innovation Release