CIDNotification.war & Compactrecon.war update
- 23 Jul 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
CIDNotification.war & Compactrecon.war update
- Updated on 23 Jul 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
CI-Notification service must be set up using a separate Tomcat service, where CIDSaas must be running, you can set up this with a standalone instance having CIDSaas, CIDNotification & Crossrecon.war or you can deploy Schedular Tomcat service along with CI-Server one of the nodes.
- Create a new folder with today's date in the agent server and copy the new CIDNotification.war & Crossrecon.war
- Stop the agent Tomcat service.
- Create the new backup folder inside today's date folder where you copied the new agent folder.
- Take a backup of the CIDNotification folder from the tomcat and copy it to the backup folder.
- After taking the backup, delete the CIDNotification folder from Tomcat.
- Change the server shutdown port from -1 to 9005 in the server.xml file of tomcat: <Server port="9005" shutdown="SHUTDOWN">
- Uncomment the Connector port in the server.xml file of tomcat and alter the port:<Connector port="9009" protocol="AJP/1.3" redirectPort="8443" />
- Change the Tomcat default port:
<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="9443" /> - The CIDNotification.war files are to be deployed in the webapps directory of Tomcat.
- Update the following properties files from the said directory for CIDNotification.war.
opt/cidserver/tomcat/schedular-tomcat-9.0.73/webapps/cidnotification/WEB-INF/classes/- application.properties
- saas.properties
- log4j.properties
- Update the following properties files from the said directory for Crossrecon.war.
opt/cidserver/tomcat/schedular-tomcat-9.0.73/webapps/Crossrecon /WEB-INF/classes/- application.properties
- rabbitmq.properties
- log4j.properties
- Start the Tomcat services.
Was this article helpful?