Overview

These sections describe how to configure the Etics BuildSystem WebService and deploy it in Tomcat

WebService Tomcat configuration

The context file for the BuildSystem WebService (BuildSystemService.xml) must be created under the Calatina home directory ($CATALINA_HOME/conf/Catalina/localhost).
This file instruments Tomcat to properly find and upload the WebService contained in the BuildSystemService war file.

<Context path="/BuildSystemService" docBase="/opt/etics/share/webapps/BuildSystemService.war" debug="1" reloadable="1">
</Context>

WebService configuration

The BuildSystem WebService requires the following configuration files (/opt/etics/etc)

1. configuration.xml: this file contains the backend configuration (DB), the logging information and the NMI configuration parameters
2. · log4j.properties log4j configuration parameters
3. scripts.http contains the URL to tell NMI how to run the jobs

• Example of the configuration.xml WebService configuration file:

<?xml version="1.0" encoding="ISO-8859-1"?>
<BuildSystemConfiguration>
   <parameters>
      <param name="submitterClass" value="org.etics.buildsystem.submitter.NmiSubmitter"/>
      <param name="nmiWorkingDirectory" value="/tmp/"/>
      <param name="nmiScriptFileName" value="/opt/etics/etc/scripts.http"/>
      <param name="log4jPropertyFile" value="/opt/etics/etc/log4j.properties"/>
      <param name="log4jRefresh" value="60"/>
   </parameters>
   <daos>
   <dao
            type = "DB"
            subtype = "MySQL-DB"
            daoClass = "org.etics.buildsystem.dao.daoDB"

            dbURL = "jdbc:mysql://$host/$database"
            driverClass = "com.mysql.jdbc.Driver"/>

        <dao
            type = "DB"
            subtype = "Oracle-DB"
            daoClass = "org.etics.buildsystem.dao.daoDB"

            dbURL = "jdbc:oracle:thin:@$hostname:$port:$connectString"
            driverClass = "oracle.jdbc.driver.OracleDriver"/>
   </daos>

   <site>
        <name>etics</name>
            <dao
                type = "DB"
                subtype = "MySQL-DB"
                user = "eticsDBUser"
                password = "eticsDBPassword"
                database = "etics"
                host = "localhost"
                connectString = "jdbc:mysql://localhost/etics"
                port = "nothing"
            />
        </site>
</BuildSystemConfiguration>

• Example of the log4j.properties configuration file

log4j.debug=false
#Etics WebService logger
log4j.logger.org.etics=DEBUG,WebServiceLogFile,console
log4j.additivity.org.etics=false

#Appender console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%d %M %F %L %-5p %x - %m%n

#Appender WebServiceLogFile
log4j.appender.WebServiceLogFile=org.apache.log4j.RollingFileAppender
log4j.appender.WebServiceLogFile.File=/tmp/BuildSystemServiceSoapBindingImpl.log
log4j.appender.WebServiceLogFile.MaxFileSize=2000KB
log4j.appender.WebServiceLogFile.bufferedIO=false
log4j.appender.WebServiceLogFile.immediateFlush=true
log4j.appender.WebServiceLogFile.MaxBackupIndex=1
log4j.appender.WebServiceLogFile.layout=org.apache.log4j.PatternLayout
log4j.appender.WebServiceLogFile.layout.ConversionPattern=%d{ISO8601} %M %F %L %-5p %c - %m%n

#Appender file
log4j.appender.myFile=org.apache.log4j.RollingFileAppender
log4j.appender.myFile.File=/tmp/eticsWebService.log
log4j.appender.myFile.MaxFileSize=200KB
log4j.appender.myFile.MaxBackupIndex=1
log4j.appender.myFile.layout=org.apache.log4j.PatternLayout
log4j.appender.myFile.layout.ConversionPattern=%d %M %F %L %C %-5p %c %x - %m%n

• Example of the scripts.http configuration file

#
# Fetching the scripts from the remote site
#
method = url
url = http://eticssoft.web.cern.ch/eticssoft/repository/org.etics/org.etics.nmi.scripts/0.1.0/noarch/job.tar.gz
untar = true

Remarks: All the configuration files must be located under /opt/etics/etc

Verify the WebService is up and running

Once Tomcat has been started an easy way to verify the Etics WebService is up and running you can open the following URLs from your browser

• http://hostname:8080/BuildSystemService/services/BuildSystemService?wsdl to access the WebService wsdl file
• http://hostname:8080/BuildSystemService/services/BuildSystemService?method=getVersion to display the WebService version
• http://hostname:8080/BuildSystemService/services/BuildSystemService?method=getSchemaInfo to get the Schema version currently being used. This operation will access the DB

In case you have a valid certificate loaded into your browser you can also load the previous URLs connection via https to the 8443 port.

-- MarianZUREK - 08 Nov 2006