Child pages
  • How to Update to Variations Webapps 6.1

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

How to Update to Variations Webapps 6.1

This page explains how to upgrade from 6.0 to 6.1 for the Variations web applications (Web Services, Web UI, and Access Manager). If you have any questions about or problems with the update process, please contact Chris Colvard (812-856-0026, cjcolvar@indiana.edu).

To see a list of changes, see the 6.1 changelog in our JIRA bug tracker:
https://bugs.dlib.indiana.edu/secure/ReleaseNote.jspa?projectId=10170&version=10535

Step 1. Upgrade the Variations Webapps from 6.0 to 6.1

Note: The upgrade process will stop your Variations web applications. You will also have to allow time for some hand-editing of configuration files to preserve your local customizations. And finally you will have to restart your Variations web applications.

To install the new webapps, execute the following commands from your tomcat directory, /usr/local/tomcat, as the user tomcat.

  1. Download the 6.1 version of variations-ws-server.war, variations-ui-web.war, and variation-mgmt-web.war.
  2. First, undeploy the existing webapps and back them up:
    mv /usr/local/tomcat/webapps/variations-ws-server.war /usr/local/tomcat/webapps/variations-ws-server.war.6.0
    mv /usr/local/tomcat/webapps/variations-ui-web.war /usr/local/tomcat/webapps/variations-ui-web.war.6.0
    mv /usr/local/tomcat/webapps/variations-mgmt-web.war /usr/local/tomcat/webapps/variations-mgmt-web.war.6.0
  3. Check that the webapps have been undeployed by seeing if the directories of the same name are gone: ls /usr/local/tomcat/webapps
  4. Perform the following configuration changes to the Variations webapp configuration files as follows:
    • /usr/local/tomcat/conf/variations-ws-server/config.xml:
      1. Change the variations2.dir system property's value to the one below:
        Code Block
                        <systemproperty>
                                <name>variations2.dir</name>
                                <value>/usr/local/tomcat/webapps/variations-ws-server/WEB-INF/conf/variations3/</value>
                        </systemproperty>
        
    • /usr/local/tomcat/conf/variations-ws-server/accessPolicy-ws.xml:
      1. If you haven't edited this file, you may copy the corrected version of this file from /usr/local/tomcat/webapps/variations-ws-server/WEB-INF/conf/accessPolicy-ws.xml and skip the step below.
      2. Uncomment the EDIT_LEASE Action element:
        Code Block
                        <Action>
                            <ActionMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
                                <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">EDIT_LEASE</AttributeValue>
                                <ActionAttributeDesignator DataType="http://www.w3.org/2001/XMLSchema#string" AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id"/>
                            </ActionMatch>
                        </Action>
        
    • /usr/local/tomcat/conf/variations-ui-web/config.xml:
      1. Add a configuration for the lease web service inside the <webservices> element. Replace the url's hostname, username, and password with the appropriate values (these are the same as in the other webservice tags):
        Code Block
                        <lease>
                                <url>http://example.example.edu/variations-ws-server/lease/</url>
                                <username>tomcatuser@localhost</username>
                                <password>password</password>
                        </lease>
        
      2. Add an attribute to the <servletcontext> element to allow web player statistics to appear alongside Variations server statistics by having the web player log to the Variations server's log server. Change example.example.edu to be the host of your Variations server:
        Code Block
                        <attribute>
                                <name>uiLoggingRemoteHost</name>
                                <value>example.example.edu</value>
                        </attribute>
        
  5. Deploy the downloaded webapps by copying them into tomcat's webapp directory
  6. That's it! Check that the newly deployed webapps are functioning properly.