Closed LasseAtomic closed 3 years ago
This is probably a question you should ask at the oxalis repository. Please note that the standalone sender is not intended to be used for sending a lot of messages. You should use the Transmitter interface in your own code. Then you have much more control.
Moved to Oxalis rep https://github.com/difi/oxalis/issues/486
Thank you for response. I'm aware of it is just a simple sender.. I just fear (based on Danish NemHandel) that we often will need the URL and Certicate and timestamp to do debug.
Hi Guys
I'm new in peppol and have setup Tomcat Oxalis inbound and for now the standalone application for outbound. But how can I log that the document is actually send, get a "proff of sending"
My goal would be a commandline respons / xml resoponsefile / easily parsed logfile / ??? that could give me
Can I get that somehow from the standalone sender?
AS I see it.
In the command line it says: "6cccc3d3-6451-41c4-9fdc-487453e3e1e4@EDI01 transmission took 4273 ms Attempted to send 1 files Failed transmissions: 0" So here I can see the GUID and that is was ok (1 attempt, 0 errors), but hard to parse. And 100 attempted, 1 failed is a bad message to get :-)
I get a.receipt.dat file.
This file includes MY signature, sender and reciever id, but nothing about the endpoint url, endpoint signature or my document id. So what does this mean?? A file was sent ok?? Do I even know it is sent ok with this file? The root xml name confuses me "DeliveryNonDeliveryToRecipient"
In my log file I get info about endpoint and payload Address: AS4-URL Content-Type: application/soap+xml;charset=UTF-8 ResponseCode: 200 ExchangeId: d48e79af-608c-4625-9f08-8160696ddd9d ServiceName: outbound-service PortName: port PortTypeName: DummyImpl Headers:
Payload:
So here I can see the endpoint, but stil not my message id..not even in the message payload