Replies: 1 comment
|
@kirti2001: As communicated more than 8 months ago, Oxalis 7.x / Oxalis-AS4 7.x has been frozen and is no longer under active development. Please migrate to Oxalis-NG for ongoing enhancements, maintenance, and support. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We are using Oxalis 7.2.0
We are preparing for the OpenPeppol SML insourcing migration.
The migration guide on https://www.oxalis.network/openpeppolsml documents the configuration change for Oxalis-NG:
lookup.locator.hostname=participant.sml.prod.tech.peppol.org
From inspecting the source code, we found that:
conf/oxalis.confusing Typesafe Config.peppol-lookup-4.2.1contains the default values:mode.PRODUCTION.lookup.locator.hostname = edelivery.tech.ec.europa.eu
mode.TEST.lookup.locator.hostname = acc.edelivery.tech.ec.europa.eu
Could you please clarify the recommended migration approach for Oxalis 7.2.0?
Specifically:
Is Oxalis 7.2.0 + peppol-lookup-4.2.1 supported for the OpenPeppol SML insourcing migration?
Is the recommended approach to override the following properties in
conf/oxalis.conf?mode.PRODUCTION.lookup.locator.hostname=participant.sml.prod.tech.peppol.org
mode.TEST.lookup.locator.hostname=participant.sml.test.tech.peppol.org
Or is there another recommended configuration or library upgrade for legacy Oxalis?
The current migration documentation appears to describe only the Oxalis-NG configuration, so we'd like to confirm the correct approach for users still running Oxalis 7.x.
Thank you.
Kirti
All reactions