Page Comparison

...

The needed configuration files should be placed in the directory indicated by the context parameter value.

The specific service page lists the needed configuration files.

The logging setup is done by the logback.xml file and is likely to be similar across the different services, probably only differing to which file the log is written to. Below is an example logback.xml file. The content of the <file>-tag should be altered to reflect the file that is to be logged to.

<configuration>
  <appender name="FILE">
    <file>/tmp/logfile.log</file>
    <append>true</append>
      <encoder>
        <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} \[%thread\] %-5level %logger{36} - %msg%n</pattern>
      </encoder>
  </appender>

  <root level="INFO">
    <appender-ref ref="FILE" />
  </root>

  <logger name="org.bitrepository" level="DEBUG" />
</configuration>

Certificate and keyfile

For collections where encryption, authentication, messagesigning etc is needed, the service needs to have access to its private key and certificate. For this a PEM formatted certificate is needed.

For make a PEM formatted file the attached script pkcs12topem can be used to convert a pkcs#12 formatted certificate and key file to the needed PEM format.

The placement of the PEM file is indicated to the individual service via a properties file located in the services configuration directory. See the individual service page for the properties file.