aaron-kumar
commented
1 month ago @evanswappf I am providing answers to all your questions posted through various GitHub issues (https://github.com/OxalisCommunity/Oxalis-AS4/issues/259, https://github.com/OxalisCommunity/oxalis/issues/685 and this https://github.com/OxalisCommunity/Oxalis-AS4/issues/261) at same place.
When sending using Oxalis standalone, different cmdline parameters will be used depending upon whether you are sending 1. "point-to-point" (when you want to send to some specific AS4 endpoint instead of retrieving it with SMP lookup) or via 2. "proper SML/SMP lookup". The way you specified parameters in all above mentioned issues, it is for point-to-point connection. You can also see that with warning message in log "Endpoint was set by caller not retrieved from SMP, make sure this is intended behaviour.",
Example command for point-to-point (For internal testing only):
java -classpath "oxalis-distribution-6.7.0-distro/bin/*;oxalis-as4-6.7.0-dist/*" eu.sendregning.oxalis.Main -f .\sample.xml -cert .\cert.cer --protocol peppol-transport-as4-v2_0 -u https://peppol-ap-testbed.appfuxion.com/as4
Here -cert is public key of your AP certificate and URL mentioned with -u is fixed AP URL e.g. https://peppol-ap-testbed.appfuxion.com/as4 . NOTE that you can use point-to-point connection only for internal testing. For production, always send message with proper SML/SMP lookup.
Example command with proper SML/SMP lookup:
java -classpath "oxalis-distribution-6.7.0-distro/bin/*;oxalis-as4-6.7.0-dist/*" eu.sendregning.oxalis.Main -f .\sample.xml
That's it. No need to define certificate, URL, protocol etc, Oxalis automatically take care of that through lookup.
Answer of your additional question and general suggestion for all issue those are posted via GitHub (I will add this as template) :
- You can use P12 certificate containing public and private key directly with Oxalis. No need to convert it into JKS.
- Never share password, certificate and other internal details in Github
- Do not use SNAPSHOT version in production setup (https://peppol-ap-testbed.appfuxion.com/as4/status)
- Your statement like "testbed" etc was misleading as it is easily confused with OpenPeppol testbed but I think here you are referring to your access point (https://peppol-ap-testbed.appfuxion.com)
- Always share complete log file, test file, java version etc by obfuscating internal details It will be quick if you can specify how to reproduce issue.
evanswappf
Hi I encountered issue while sending xml message to testbed using oxalis-standalone by running this command
java -classpath "oxalis-distribution-6.7.0-distro/api/*;oxalis-as4-6.7.0-dist/*;oxalis-distribution-6.7.0-distro/bin/*" eu.sendregning.oxalis.Main -f .\sample.xml -cert .\cert.cer --protocol peppol-transport-as4-v2_0 -u https://peppol-ap-testbed.appfuxion.com/as4Here are the steps I run to send
but seems the testbed didnt receive my xml message. can anyone help on this? thanks. Best regards.