Originally posted by: cemeinz
Hello!
This came to my mind:
If I understood you right, you send a corrupt message to the server in order to get a fault message back? Well, maybe the server / web service itself is configered in a way, that corrupt message will produce him a HTTP 500 error response. This error let your mapping fail. I would prefer to use the INGORE parameter.
Example taken from the online library:
<hr />
Command:
-I 404:410
Result:
* The adapter ignores errors of type 404 (not found).
* The adapter ignores errors of type 410 (gone).
This lets your mapping runs through if you parametrized with -I 500.
I tested it with my on running and working example just seconds ago. I produced a HTTP 500 with a corrupt message, but my mapping runs through "mapping completed successfully" and wrote the response including the fault message onto my file system.
Message was edited by: cemeinz
Message was edited by: cemeinz
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange