European Commission Open e-prior PEPPOL Access Point Configuration and Testing

Transcription

1 EUROPEAN COMMISSION DIRECTORATE-GENERAL INFORMATICS Information systems Directorate European Commission Open e-prior Date: 17/05/2011 Version: 1.0 Authors: Marco Fichera Revised by: Didier Thunus Approved by: Public: Reference Number: Commission européenne, B-1049 Bruxelles / Europese Commissie, B-1049 Brussel - Belgium. Telephone: (32-2) Commission européenne, L-2920 Luxembourg. Telephone: (352)

2 TABLE OF CONTENTS 1. Access point configuration Certificates Configuration of SMP url Configuration of participant IDs Configuration of incoming messages Configuration of outgoing messages Proxy settings Access point testing... 6

3 Document History Version Date Comment Modified Pages /04/2010 Fisrt Draft all /05/2011 General review of the contents and the structure of the document: Added configuration of SMP lookup Added configuration of incoming and outgoing messages Removed test participant IDs configuration all 3

4 1. Access point configuration The PEPPOL Access Point of Open e-prior (hereunder "the Access Point") is able to receive and send messages through the PEPPOL infrastructure according to the BusDox specifications. It needs a few steps of configuration to make it work correctly inside the PEPPOL infrastructure. After downloading the Open e-prior release from OSOR, please follow the instructions described in the next sections. 1.1 Certificates A PEPPOL Access Point uses X.509 V3 certificates to identify senders/receivers and to calculate message signatures. Open e-prior users are responsible for obtaining from PEPPOL a valid production X.509 certificate and the PEPPOL Certificate Authority root certificates, in order to operate the Access Point inside the PEPPOL infrastructure. X.509 certificates are usually stored into key stores and trust stores. The key store contains the certificate used by the Access Point when sending outgoing messages, while the trust store contains the list of trusted certificates used to validate incoming messages. In the Open e- PRIOR PEPPOL Access Point distribution, you can find the two stores at the following paths: <JBOSS_HOME>\server\default\conf\keystores\keystore.jks <JBOSS_HOME>\server\default\conf\keystores\truststore.jks Test certificates are already present inside the two keystores, which can be used only for testing of the Access Point. In order to make the Access Point work inside the infrastructure, please: load the production certificate obtained from PEPPOL in the key store load the PEPPOL Certificate Authority root certificates in the trust store 1.2 Configuration of SMP URL The Access Point can be configured to enable/disable the lookup into a Service Metadata Publisher (SMP) when receiving a message. Please note that, if the lookup is disabled: All incoming messages will be treated as "local" messages and sent directly to Open e-prior (even if the recipient participant ID is not a back-office connected to Open e-prior). The Access Point will only be able to receive messages, and not to send. Indeed, in case of outgoing messages, the address of the recipient Access Point must be discovered using the SMP. The above setting, and the URL of the SMP domain which must be used by the Access Point, have to be set in the following configuration file: <JBOSS_HOME>\server\default\conf\config.properties For the enable/disable flag please use the line: 4

5 org.busdox.transport.metadatapublisher.enablelookup=<true/false> For the url, please set the value in the following line: org.busdox.transport.metadatapublisher.url=<smp_address> where <smp_address> has to be replaced with the actual SMP domain. Please contact PEPPOL in order to latter information. 1.3 Configuration of participant IDs In order to make the Access Point available to receive messages from other Access Points on the network, the participant IDs of the back-offices connected to Open e-prior should be registered into an SMP. Please contact your SMP provider to know how to register your participant IDs. 1.4 Configuration of incoming messages Since PEPPOL transport infrastructure uses certificates to validate the messages during the document exchange, user names are not used in the PEPPOL message headers for authentication/authorization purposes. However, a user name has to be associated with every supplier which has to be configured to use the Access Point, in order to identify the correct supplier agreement when receiving the message. For this purpose, use the following script: INSERT INTO PAP_TB_SUPPLIER VALUES (<supplierid>, <username>); where <supplierid> is the GLN of the supplier which wants to connect to Open e-prior through the Access Point, and <username> is the user name, or one of the user names, linked to the supplier in the Open e-prior database through the Supplier Agreement. Please refer to the e-prior User Activation Procedure for an explanation of the above mentioned values. 1.5 Configuration of outgoing messages Outgoing messages (from back-offices to suppliers) can be configured to be sent to suppliers via the Access Point. For every Interchange Agreement, the user can decide whether or not the Access Point has to be used. A flag must be set in the Open e-prior database for this purpose, using the script below: UPDATE EPR_TB_INTERCHANGEAGR SET ICA_PEPPOL_FLAG='Y' WHERE ICA_AGR_ID = <supplieragreement> AND ICA_IDP_ID = <InternalDepartment> AND ICA_PRF_ID = <profile>; where <supplieragreement>, <internaldepartment> and <profile> are respectively the IDs of the Supplier Agreement, the Internal Department and of the Profile for which the PEPPOL Access Point is to be used. Please refer to the e-prior User Activation Procedure for an explanation of the above mentioned values. 1.6 Proxy settings If your JBoss Server lies behind a proxy, the Access Point must be configured to access the Internet. A properties file, whose path is: <JBOSS_HOME>\server\default\conf\proxy.properties 5

6 has to be configured for this purpose. 2. Access point testing The Access Point distribution comes with a Java testing tool, based on PEPPOL Reference Implementation Busdox client. It can be found under the PeppolTestClient directory on OSOR SVN. The tool allows the user to send an XML document to the Access Point. To configure the client, use the TestClient.properties file under the previous directory. Here are the most important properties to configure: XMLDocumentFile: full path of the document to send. Proxy settings: use these settings if you need to pass through a proxy to access the Internet senderbusinessid and recipientbusinessid: replace these two IDs with the ones you have received from PEPPOL by using the registration form. documentid: the document type (Invoice, Credit Note, etc.) being sent to the Access Point. Some predefined document types are already present in the properties file itself. Choose the one you need by uncommenting the related line. processid: ID of the BII profile which the document is participating in. Some predefined process IDs are already present into the properties file itself. Choose the one you need by uncommenting the related line. To sign outgoing messages and to check responses, the test client uses a keystore and a truststore which is contained under the PeppolTestClient/keystores directory. Here are the paths of the two files: PeppolTestClient\keystores\client-keystore.jks PeppolTestClient\keystores\client-truststore.jks After sending a document via the PEPPOL Test Client, the actual processing by Open e- PRIOR can be verified using the synchronous services (StatusRequest, QueryRequest). 6