Customized HTTP header field and HTTP status code for SALT
(Doc ID 2402425.1)
Last updated on MARCH 01, 2019
Applies to:Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.2.2 and later
Information in this document applies to any platform.
QUESTION 1 ::
Is it possible to change HTTP response code when exception raises in Tuxedo side? (Depending on the exception there will be different HTTP-codes).
Do you have an example or some extra info to do it?
QUESTION 2 ::
Enhance "HTTP response code" functionality in SALT with below features ::
1. If possible prefer to manage the response code for HTTP in any other field. Customer have some tools that they use to implement tuxedo services which make use of rcode.
2. Enhance the JAVA server, and pass the response code in the call info, which we have talked. The advantage is this solution has no impact to user messages, and the may be extended easily. The disadvantage is that it needs much efforts in compare to other solutions.
3. Provide an env variable, which indicates an FML32 field that SALT can read the response code from the returned error buffer, SALT also can delete or keep the field in conversation to JSON data, based on the instructions provide the env variable. This solution may cost less efforts, but the disadvantage is that customer has to return the FML32 buffer.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document