AS4 Outbound - Unable to capture recipient AP gateway from logs

kdkmadusanka commented 4 years ago

Hi,

I'm unable to capture the recipient access point gateway from the oxalis logs when sending invoices with oxalis standalone. I'm running java -cp <path-to-oxalis>/oxalis-distribution/bin/*:<path-to-oxalis>/oxalis-as4-dist/* eu.sendregning.oxalis.Main -f <file-name> Is there any way to get the recipient AP gateway from oxalis or am I missing something.

Kindly help. Thanks

FrodeBjerkholt commented 4 years ago

I am not sure if I understand the question - Can you elaborate, please?

kdkmadusanka commented 4 years ago

Hi @FrodeBjerkholt , First of all thank you. Following is the log I'm getting from the oxalis. When I send invoices by executing java command given above. There is a requirement from IMDA (singapore) to capture the access point gateway url/identifier of the receiving party. From the logs I can't identify/capture the recipient AP gateway. Is there any way to do that.? In Oxalis there may be a point where you ping the recipient AP gateway before send right (just assuming). In that point is it possible to get the recipient access point..?

2020-03-11 10:29:18.473 DEBUG 2074 --- [io-8080-exec-13] com.sgebiz.peppol.service.SftpConnect : -11 10:29:17,581 INFO [no.difi.oxalis.commons.settings.SettingsBuilder] Transmission => VERIFIER: default 2020-03-11 10:29:17,582 INFO [no.difi.oxalis.commons.settings.SettingsBuilder] AS4 => HOSTNAME: 2020-03-11 10:29:17,582 INFO [no.difi.oxalis.commons.settings.SettingsBuilder] AS4 => MSGID_GENERATOR: default 2020-03-11 10:29:17,582 INFO [no.difi.oxalis.commons.settings.SettingsBuilder] AS4 => TYPE: peppol 2020-03-11 10:29:17,584 INFO [no.difi.oxalis.commons.settings.SettingsBuilder] Logging => CONFIG: null 2020-03-11 10:29:17,584 INFO [no.difi.oxalis.commons.settings.SettingsBuilder] Logging => SERVICE: logback 2020-03-11 10:29:19.473 DEBUG 2074 --- [io-8080-exec-13] com.sgebiz.peppol.service.SftpConnect : 2020-03-11 10:29:18,631 INFO [no.difi.oxalis.commons.security.CertificateModule] Certificate subject: C=SG, O=Singapore E-Business Pte Ltd, OU=PEPPOL PRODUCTION AP, CN=PSG000206 2020-03-11 10:29:18,632 INFO [no.difi.oxalis.commons.security.CertificateModule] Certificate issuer: CN=PEPPOL ACCESS POINT CA - G2, O=OpenPEPPOL AISBL, C=BE 2020-03-11 10:29:20.473 DEBUG 2074 --- [io-8080-exec-13] com.sgebiz.peppol.service.SftpConnect : 2020-03-11 10:29:19,939 INFO [no.difi.vefa.peppol.security.ModeDetector] Detection error (TEST): Validation of subject principal(CN) failed. 2020-03-11 10:29:19,943 INFO [no.difi.vefa.peppol.security.ModeDetector] Detection error (LOCAL): Certificate should be self-signed. 2020-03-11 10:29:21.473 DEBUG 2074 --- [io-8080-exec-13] com.sgebiz.peppol.service.SftpConnect : 2020-03-11 10:29:21,207 INFO [no.difi.vefa.peppol.security.ModeDetector] Detected mode: PRODUCTION 2020-03-11 10:29:21,225 INFO [no.difi.oxalis.outbound.transmission.MessageSenderFactory] Prioritized list of transport profiles: 2020-03-11 10:29:21,226 INFO [no.difi.oxalis.outbound.transmission.MessageSenderFactory] => peppol-transport-as4-v2_0 2020-03-11 10:29:21,227 INFO [no.difi.oxalis.outbound.transmission.MessageSenderFactory] => busdox-transport-as2-ver1p0r1 2020-03-11 10:29:21,227 INFO [no.difi.oxalis.outbound.transmission.MessageSenderFactory] => busdox-transport-as2-ver2p0 2020-03-11 10:29:21,227 INFO [no.difi.oxalis.outbound.transmission.MessageSenderFactory] => busdox-transport-as2-ver1p0 2020-03-11 10:29:22.474 DEBUG 2074 --- [io-8080-exec-13] com.sgebiz.peppol.service.SftpConnect : 2020-03-11 10:29:30.475 DEBUG 2074 --- [io-8080-exec-13] com.sgebiz.peppol.service.SftpConnect : a5c5b64b-a17b-4e77-b8e5-00d0b7d27800@ip-10-9-2-29.ap-southeast-1.compute.internal transmission took 6352 ms Average transmission time was 6352.0ms Total time spent: 8s Attempted to send 1 files Failed transmissions: 0 Transmission speed 0 documents per second

FrodeBjerkholt commented 4 years ago

I am not sure. This is a question that belongs at the oxalis main repository, since this logging would be independent of the transport profile. I see that the TransmissionTask.java logs the endpoint:

            log.debug(String.format("Message using messageId %s sent to %s using %s was assigned transmissionId %s took %dms\n",
                    transmissionResponse.getHeader().getIdentifier().getIdentifier(),
                    transmissionResponse.getEndpoint().getAddress(),
                    transmissionResponse.getProtocol().getIdentifier(),
                    transmissionResponse.getTransmissionIdentifier(),
                    durartionInMs
            ));

Example from my log:

2020-03-17 09:22:31,912 DEBUG [eu.sendregning.oxalis.TransmissionTask] Message using messageId a6db5790-cd5f-4d8d-95af-8683f7e0245f sent to http://localhost:8080/as4 using peppol-transport-as4-v2_0 was assigned transmissionId 45f035f4-47d9-4cd0-8b14-04b59e56bfaf@host.docker.internal took 1264ms

I also see other log statements that contain the URL of the AP,

OxalisCommunity / Oxalis-AS4

AS4 Outbound - Unable to capture recipient AP gateway from logs #112