3.0.0 to 3.1 SHRINE 3.1.0 Upgrade Chapter 6 - Configuration Changes

Clean up shrine.conf

shrine.conf is considerably more compact than in SHRINE 3.0.0. Take this opportunity to clean out the file in older installations. See the example file in shrine-setup/qep-and-adapter-shrine.conf as a starting point.

Remove breakdownResultOutputTypesfrom shrine.conf

Shrine no longer uses broadcasterServiceEndpoint in shrine.conf . Delete that from shrine.conf to save confusion.

Add a Timezone Parameter to mysql URLs in /opt/shrine/tomcat/conf/context.xml (MariaDB only)

Inside /opt/shrine/tomcat/conf/context.xml, add a ?serverTimezone=UTC parameter to each mysql URL. (No change is needed if you are using a different brand of database.)

...
<Context>
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
    <Resource name="jdbc/problemDB" auth="Container" type="javax.sql.DataSource"
              maxTotal="128" maxIdle="32" maxWaitMillis="10000"
              username="shrine" password="demouser" driverClassName="com.mysql.jdbc.Driver"
              url="jdbc:mysql://localhost:3306/shrine_query_history?serverTimezone=UTC"
              testOnBorrow="true" validationQuery="SELECT 1" />
...

Override default logging level from info to debug (Optional)

Override with environmental override in shrine/apps/shrine-api-war/src/main/resources/logback.xml, and shrine/commons/util/src/main/resources/logback.xml

<logger name="net.shrine" additivity="false" level="debug">
 <appender-ref ref="shrine"/>
</logger>

Remove akka and permgen parameters from setenv.sh

With earlier versions of the JDK SHRINE needed a few arguments involving akka and permgen. Remove these. Set -Xmx to use all but one gigabyte of your system's memory. A typical SHRINE setenv.sh will look like:

# Set Tomcat options
export CATALINA_OPTS="$CATALINA_OPTS -server -Xms1024m -Xmx3072m -Duser.timezone=America/New_York"

Ensure that adapterMappingsFileName exists in shrine.conf

Please ensure that the adapterMappingsFileName directive exists in the adapter section in shrine.conf, and that it points to a valid adapter mappings file.

shrine.conf

shrine {
...  
  adapter {
...
    adapterMappingsFileName = "AdapterMappings.csv"
...
  }//adapter
...
}//shrine

Page tree