Restarting DOORS Database server if DOORS Web Access crashes

Answer

It is required to restart the DOORS Database server (doorsd) for enabling and disabling DCN (Data Change Notifications).

During a normal startup and shutdown of the DOORS Web Access components, it is not necessary to restart the DOORS Database server.

However, if DOORS Web Access hangs or goes down, as long as DOORS Database server itself doesn't go down, we can restart the other components and connect to the server.

The following points describe which components need to be restarted during a DOORS Web Access crash:

• If the DOORS Web Access Broker or the Broker machine goes down then to get DOORS Web Access working again we must restart only the DOORS Web Access Broker and DOORS Web Access Tomcat Server.
• If the DOORS Database server (doorsd) or the DOORS Database server machine goes down then to get DOORS Web Access working again we must restart the whole DOORS Web Access stack (i.e. DOORS Web Access Broker, DOORS Database server, DOORS Web Access InterOp and DOORS Web Access Tomcat Server).
• If the DOORS Web Access InterOp server (all Interop instances or some) goes down then to get DOORS Web Access working again we can simply restart Interop instances. While operations that were in-flight at the time that the failure occurred will need to be resubmitted, it will not necessitate a restart of the whole stack.
• If the DOORS Web Access Tomcat Server or the Tomcat machine goes down then to get DOORS Web Access working again we need to only restart the Tomcat server. While operations that were in-flight at the time that the failure occurred will need to be resubmitted, it will not necessitate a restart of the whole stack.