Documentation Primetime Primetime Digital Rights Management Help

Configure Tomcat configure-tomcat

Last update: Mon Oct 02 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

On the Individualization server, modify Tomcat’s conf/server.xml file to include additional information in the access log. You can use this information for reporting purposes.

Locate the configuration for the AccessLogValve in server.xml and modify the pattern as shown here:

code language-none

code language-none
`<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="%h %{x-forwarded-for}i %l %u %t "%r" %s %b %{request-id}r" resolveHosts="false"/>`

<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="%h %{x-forwarded-for}i %l %u %t &quot;%r&quot; %s %b
%{request-id}r" resolveHosts="false"/>

%{x-forwarded-for}i will record the value of the x-forwarded-for header. If you use an Apache reverse proxy to forward requests to the Tomcat server, this header will contain the original client’s IP address, whereas %h records the Apache server’s IP address. %{request-id}r will record the request identifier, which corresponds to the request ID contained in the Individualization application log.

Edit conf/server.xml and set the unpackwars property to false.

For both the Individualization and Key Generation servers, it is a good idea to edit conf/server.xml and set the unpackwars property to false. Otherwise, when you update the WARs, you may have to clean out the unpacked WAR folders as well.

NOTE

Future DRM clients will require you to enable and configure the CORS (Cross-Origin Resource Sharing) filter that is available for Tomcat. Currently, no DRM clients have this requirement.

recommendation-more-help

6586e0f0ff95af3ee5405884