Overview
Condor
See the script mentioned in the
DeploymentInstallation section.
NMI
See the script mentioned in the
DeploymentInstallation section.
The configuration for the NMI is already performed with the installation script. Which nodes should be able to connect to the
MySQL database:
Build System Web Application
- Move from /opt/etics/etc the Tomcat Context file eticsBuildSystemWAContext.xml to ${CATALINA_HOME}/conf/Catalina/localhost
- If the eticsBuildSystemWA.war file is not in the /opt/etics/share/webapps/ edit the Tomcat Context File changing the path of the WAR file
- Check that the eticsBuildSystemWAConfiguration.properties file is in the /opt/etics/etc folder and edit it following the instruction within the file.
- If a previous version of the Etics Web Application was installed on Tomcat, delete the folders ${CATALINA_HOME}/work/Catalina/localhost/etics and ${CATALINA_HOME}/webapps/etics
- Restart Tomcat
Build Reactor
Web Reactor
Etics Administration Web Application
- Move from /opt/etics/etc the Tomcat Context file eticsAdministrationWAContext.xml to ${CATALINA_HOME}/conf/Catalina/localhost
- If the eticsAdministrationWA.war file is not in the /opt/etics/share/webapps/ edit the Tomcat Context File changing the path of the WAR file
- Check that the eticsAdministrationWAConfiguration.xml file is in the /opt/etics/etc folder and edit it following the instruction within the file.
- Check that the eticsAdministrationWALog4j.properties file is in the /opt/etics/etc folder and edit it if you want to change the logger properties (default log file: ${CATALINA_HOME}/log/catalina.out).
- If a previous version of the Etics Administration Web Application was installed on Tomcat, delete the folders ${CATALINA_HOME}/work/Catalina/localhost/eticsAdministrationWA and ${CATALINA_HOME}/webapps/eticsAdministrationWA
- Restart Tomcat
TEST:
To test if the deployment is successful try to access the page configured in the configuration file serverPath property
(Usually
https://hostname:8443/eticsAdmin
)
Repository Browser
- Move from /opt/etics/etc the Tomcat Context file eticsRepositoryBContext.xml to ${CATALINA_HOME}/conf/Catalina/localhost
- If the eticsRepositoryB.war file is not in the /opt/etics/share/webapps/ edit the Tomcat Context File changing the path of the WAR file
- Check that the AFS is working and that the Tomcat user has the permission to read the repository folder and subfolders
- If a previous version of the Repository Browser was installed on Tomcat, delete the folders ${CATALINA_HOME}/work/Catalina/localhost/eticsRepositoryB and ${CATALINA_HOME}/webapps/eticsRepositoryB
- Restart Tomcat
TEST:
To test if the deployment is successful try to access the page configured in the configuration file serverPath property
(Usually
http://hostname:8080/repositoryBrowser
)
To check the integrity of the repository, run
http://hostname:8080/repositoryBrowser/repositoryCrawler.jsp
Report Browser (Build System Browser)
- Move from /opt/etics/etc the Tomcat Context file eticsBuildSystemBContext.xml to ${CATALINA_HOME}/conf/Catalina/localhost
- If the eticsBuildSystemB.war file is not in the /opt/etics/share/webapps/ edit the Tomcat Context File changing the path of the WAR file
- Check that the eticsBuildSystemBConfiguration.xml file is in the /opt/etics/etc folder and edit it following the instruction within the file.
- Check that the NMI folder is present and that the Tomcat user has permission to read the folder and subfolders
- If a previous version of the Report Browser was installed on Tomcat, delete the folders ${CATALINA_HOME}/work/Catalina/localhost/eticsBuildSystemB and ${CATALINA_HOME}/webapps/eticsBuildSystemB
- Restart Tomcat
TEST:
To test if the deployment is successful try to access the page configured in the configuration file serverPath property
(Usually
http://hostname:8080/reportBrowser
)
-- Main.mselmi - 15 Nov 2006
Topic revision: r24 - 2006-12-19
- unknown