Running

Running a phoss SMP

After starting up the SMP and navigating to the respective address in your browser (e.g. http://localhost:8080/smp or http://localhost:80 or http://smp.example.org - whatever address and port you are using) you will see an overview of all service groups managed on this server.

Default login

To login to the management area use the username [email protected] and the password password for the initial login. Afterwards modify this in the user management!

General requirements

Peppol SMP specification

According to the Peppol specification an SMP MUST run in the root of a domain (like http://smp.example.org) and must use port 80. Additionally https MUST NOT be used for the GET requests defined by the SMP specification (because the responses are electronically signed anyway). See the latest Peppol SMP Specification for confirmation.

OASIS SMP specification

The OASIS SMP specification in combination with the OASIS BDXL specification allows for the usage of an SMP under arbitrary URLs (different protocols, domains, contexts and ports).

Reverse Proxy Server specifics

Please see the special requirements for different application servers before deploying:

• Apache httpd
• nginx
• IIS

Application Server specifics

Please see the special requirements for different application servers before deploying:

• Apache Tomcat
• WildFly
• Oracle WebLogic

Production configuration

You may use the default WAR file for your SMP server if you specify the absolute paths to the application.properties configuration via the respective system properties config.resource, config.resources, config.file or config.url when you start your application server. See https://github.com/phax/ph-commons/wiki/ph-config for the details of the configuration resolution logic. See Configuration for the content of the SMP configuration file.

Example system properties when the file resides in directory /var/smpserver/:

-Dconfig.file=/var/smpserver/application.properties

If the Directory integration is enabled, the Directory configuration should reside in the same file.

Note: in case of external properties files all data paths in the configuration files (like keystore or truststore paths) should be specified absolute.

See also security related configuration items.