(Click to open topic with navigation)

You are here: Manual Installation > Upgrading > Upgrading Moab Web Services

2.23 Upgrading Moab Web Services

This topic provides instructions to upgrade Moab Web Services to the latest release version.

These instructions assume you are upgrading MWS from version 8.0 or later. If you are upgrading MWS from a version prior to 8.0, contact your Adaptive Computing account manger for more information.

You must deploy Moab Web Services on the same host as Moab Server (Moab Server Host). For documentation clarity, these instructions refer to the host for Moab Server and MWS Server as the MWS Server Host.

2.23.1 Before You Upgrade

MWS requires Tomcat 7. It is also recommended that you upgrade to Java 8.

2.23.1.A Upgrade to Tomcat 7

Tomcat 7 is required to run MWS 9.0 and later.

On the MWS Server Host, do the following:

  1. Check your Tomcat version. 
    [root]# rpm -qa tomcat
tomcat-7.0.33-4.el6.noarch
  2. If your Tomcat version is prior to 7, upgrade Tomcat.
    [root]# service tomcat6 stop
[root]# chkconfig tomcat6 off
[root]# yum install tomcat

2.23.1.B Upgrade to Java 8

Oracle Java 8 Runtime Environment is the recommended Java environment, but Oracle Java 7 is also supported. All other versions of Java, including OpenJDK/IcedTea, GNU Compiler for Java, and so on cannot run MWS.

If you wish to upgrade to Java 8, refer to the 2.5.2.A Install Java instructions.

2.23.2 Upgrade Moab Web Services

You must complete the tasks in 2.23.1 Before You Upgrade before upgrading MWS.

On the MWS Server Host, do the following:

  1. If you are upgrading Moab Web Services from a version prior to 9.1.0, confirm the MongoDB database is upgraded to 3.2.x. See Upgrading to MongoDB 3.2.x for more information.
  2. Create a directory for which you will extract the contents of the MWS download tarball. For example: 
    [root]# mkdir /tmp/mws-install
[root]# cd /tmp/mws-install
  3. Download the latest MWS build from the Adaptive Computing website.
  4. In the directory you created earlier, extract the contents of the MWS download tarball and then change directory into the extracted directory. For example: 
    [root]# tar xvzf mws-9.1.0.tar.gz
[root]# cd mws-9.1.0
  5. Deploy the updated mws.war to Tomcat.

    If your prior MWS version had tomcat 6, you should have stopped the tomcat6 service when you upgraded to Tomcat 7 (required). See 2.23.1.A Upgrade to Tomcat 7 for more information.

    [root]# service tomcat stop
[root]# rm -rf /usr/share/tomcat/webapps/mws /usr/share/tomcat/webapps/mws.war
[root]# cp mws.war /usr/share/tomcat/webapps/
[root]# chown -R tomcat:tomcat /usr/share/tomcat/webapps/mws.war
  6. Back up the MWS home directory and create the required destination directory structure. 
    [root]# cp -r /opt/mws /opt/mws-<version>-backup
[root]# mkdir -p \
   /opt/mws/etc/mws.d \
   /opt/mws/hooks \
   /opt/mws/log \
   /opt/mws/plugins \
   /opt/mws/spool/hooks \
   /opt/mws/utils
[root]# chown -R tomcat:tomcat /opt/mws
[root]# chmod -R 555 /opt/mws
[root]# chmod u+w \
   /opt/mws/log \
   /opt/mws/plugins \
   /opt/mws/spool \
   /opt/mws/spool/hooks \
   /opt/mws/utils

    Where <version> if the product version being backed up.

  7. Copy the extracted utility files to the utility directory created above and give the tomcat user ownership of the directory.
    8. [root]# cd utils
[root]# cp * /opt/mws/utils
[root]# chown tomcat:tomcat /opt/mws/utils/*
  8. Merge the changes in the /tmp/mws-install/mws-9.1.0/mws-config.groovy file into your existing /opt/mws/etc/mws-config.groovy.

    1. Depending on your current MWS version, do the following as needed:

      • If Insight is part of your configuration:
        • remove the Insight PostgreSQL information (dataSource_insight.username, dataSource_insight.password, dataSource_insight.url); prior to version 9.1.

          Version 9.1 removed the Insight PostreSQL database.

        • add the health check information for the Insight Server (insight.server, insight.command.port, insight.command.timeout.seconds); prior to version 9.0.2.

          insight.server is the DNS name of the host on which the Insight Server is running.

      • If Viewpoint is part of your configuration, register Viewpoint as client; prior to version 9.0
      • Change the moab.messageQueue.port to 5570; prior to version 8.0
      • Configure and appender for the audit log; prior to version 8.0
      • Change the layout to "new com.ace.mws.logging.ACPatternLayout()" for the output format of each log entry; prior to version 8.0
      • Remove the mws.suite parameter and the mam.* parameters (they have been moved to /opt/mws/etc/mws.d/); prior to version 8.0
    2. Confirm the value for moab.messageQueue.secretKey matches the value located in /opt/moab/etc/moab-private.cfg; if you have not yet configured a secret key, see Secure communication using secret keys.
    ClosedExpand to see an example of the merged /opt/mws/etc/mws-config.groovy file for MWS 9.1.0.
    // Any settings in this file may be overridden by any
// file in the mws.d directory.

// Change these to be whatever you like.
auth.defaultUser.username = "moab-admin"
auth.defaultUser.password = "changeme!"

// Moab Workload Manager configuration.
moab.secretKey = "<ENTER-KEY-HERE>"
moab.server = "localhost"
moab.port = 42559
moab.messageDigestAlgorithm = "SHA-1"

// MongoDB configuration.
// grails.mongo.username = "mws_user"
// grails.mongo.password = "<ENTER-KEY-HERE>"

// Insight configuration.
// insight.server = "localhost"
// insight.command.port = 5568
// insight.command.timeout.seconds = 5

// Message bus configuration.
moab.messageQueue.port = 5570
// moab.messageQueue.secretKey = "<ENTER-KEY-HERE>"
mws.messageQueue.address = "*"
mws.messageQueue.port = 5564

// Sample OAuth Configuration
grails.plugin.springsecurity.oauthProvider.clients = [
		[
				clientId            : "viewpoint",
				clientSecret        : "<ENTER-CLIENTSECRET-HERE>",
				authorizedGrantTypes: ["password"]
		]
]

// Sample LDAP Configurations

// Sample OpenLDAP Configuration
//ldap.server = "192.168.0.5"
//ldap.port = 389
//ldap.baseDNs = ["dc=acme,dc=com"]
//ldap.bindUser = "cn=Manager,dc=acme,dc=com"
//ldap.password = "*****"
//ldap.directory.type = "OpenLDAP Using InetOrgPerson Schema"

// Sample Active Directory Configuration
//ldap.server = "192.168.0.5"
//ldap.port = 389
//ldap.baseDNs = ["CN=Users,DC=acme,DC=com","OU=Europe,DC=acme,DC=com"]
//ldap.bindUser = "cn=Administrator,cn=Users,DC=acme,DC=com"
//ldap.password = "*****"
//ldap.directory.type = "Microsoft Active Directory"

log4j = {
	// Configure an appender for the events log.
	def eventAppender = new org.apache.log4j.rolling.RollingFileAppender(
			name: 'events', layout: pattern(conversionPattern: "%m%n"))
	def rollingPolicy = new org.apache.log4j.rolling.TimeBasedRollingPolicy(
			fileNamePattern: '/opt/mws/log/events.%d{yyyy-MM-dd}',
			activeFileName: '/opt/mws/log/events.log')
	rollingPolicy.activateOptions()
	eventAppender.setRollingPolicy(rollingPolicy)

	// Configure an appender for the audit log.
	def auditAppender = new org.apache.log4j.rolling.RollingFileAppender(
			name: 'audit',
			layout: new com.ace.mws.logging.ACPatternLayout("%j\t\t\t%c{1}\t\t\t%m%n"))
	def auditRollingPolicy = new org.apache.log4j.rolling.TimeBasedRollingPolicy(
			fileNamePattern: '/opt/mws/log/audit.%d{yyyy-MM-dd}',
			activeFileName: '/opt/mws/log/audit.log')
	auditRollingPolicy.activateOptions()
	auditAppender.setRollingPolicy(auditRollingPolicy)

	appenders {
		rollingFile name: 'stacktrace',
				file: '/opt/mws/log/stacktrace.log',
				maxFileSize: '100MB'
		rollingFile name: 'rootLog',
				file: '/opt/mws/log/mws.log',
				maxFileSize: '100MB', //The maximum file size for a single log file
				maxBackupIndex: 10, //Retain only the 10 most recent log files, delete older logs to save space
				layout: new com.ace.mws.logging.ACPatternLayout(), //Configures the output format of each log entry
				threshold: org.apache.log4j.Level.ERROR //Ignore any logging entries less verbose than this threshold

		appender eventAppender
		appender auditAppender
	}

	// NOTE: This definition is a catch-all for any logger not defined below
	root {
		error 'rootLog'
	}

	// Individual logger configurations
	debug 'com.ace.mws',
			'grails.app.conf.BootStrap',
			'grails.app.controllers.com.ace.mws',
			'grails.app.domain.com.ace.mws',
			'grails.app.filters.com.ace.mws',
			'grails.app.services.com.ace.mws',
			'grails.app.tagLib.com.ace.mws',
			'grails.app.jobs.com.ace.mws',
			'grails.app.gapiParsers',
			'grails.app.gapiRequests',
			'grails.app.gapiSerializers',
			'grails.app.translators',
			'plugins'	// MWS plugins

	info 'com.ace.mws.gapi.Connection',
			'com.ace.mws.gapi.parsers',
			'grails.app.service.grails.plugins.reloadconfig',
			'com.ace.mws.gapi.serializers'

	off 'org.codehaus.groovy.grails.web.errors'

	// Logs event information to the events log, not the rootLog
	trace additivity: false, events: 'com.ace.mws.events.EventFlatFileWriter'

	// Logs audit information to the audit log, not the rootLog
	trace additivity: false, audit: 'mws.audit'
}
  9. Merge any changes supplied in the new mws-config-hpc.groovy file in to your installed /opt/mws/etc/mws.d/mws-config-hpc.groovy.
  10. Remove all plugins from /opt/mws/plugins except for those that you may have created. The presence of obsolete plugins can prevent MWS from starting up. Out-of-the-box plugins will be recreated when MWS is restarted.
    [root]# cd /opt/mws/plugins
[root]# rm *.jar
  11. Verify the Tomcat user has read access to the /opt/mws/etc/mws-config.groovy and /opt/mws/etc/mws.d/mws-config-hpc.groovy file.
  12. Verify the following lines are added to the end of /etc/tomcat/tomcat.conf.
    CATALINA_OPTS="-DMWS_HOME=/opt/mws -Xms256m -Xmx3g -XX:MaxPermSize=384m -Dfile.encoding=UTF8"
JAVA_HOME="/usr/java/latest"

    MaxPermSize is ignored using Java 8; and therefore can be omitted.

  13. Start Tomcat.

    You will need to start the "tomcat" service. Starting the "tomcat6" service will install the wrong version of Tomcat.

    [root]# service tomcat start
  14. Visit http://localhost:8080/mws/ in a web browser to verify that MWS is running again.

    15. You will see some sample queries and a few other actions.

  15. Log into MWS to verify configuration. (The credentials are the values of auth.defaultUser.username and auth.defaultUser.password set in /opt/mws/etc/mws-config.groovy.)

    16. If you encounter problems, or if MWS does not seem to be running, see the steps in 5.3 Moab Web Services Issues.

© 2016 Adaptive Computing