Unanswered
You shouldn't need to add any headers. The coreflow doesn't directly interact with the network call that calls your core, that is done by Host Adapter down stream. The Bridge/Host Adapter should take care of that for you. Is there a specific reason you need a header, or are you seeing any failures in your testing that would lead to thinking a header is necessary?
37 Views
0
Answers
one year ago
one year ago
Just to add something to this conversation, there are certain times when you want/need to set an element that is in the MsqRqHdr. For example, some JXchange endpoints have a MaxRec element designed to limit the size of response data sets. That element is usually in the MsgRqHdr.
— Ira Williams one year agoYes, the issue that I continue to run into is a 500 Internal Server error. I've tried to improve the logging as much as possible, but my team internally said that Q2 has gone through the natting process for our JXchange environment, and I can't find out whether or not I need to send username and password variables via the xml in the request. Currently when I log the request from
— Caleb Evans one year agorequest = await self.core.build_start_workflow(acctId, custId), it appears to be empty even though I have validated the syntax