How to Stop/Start and Deploy Application

In this article we will cover, How to stop, start and deploy application. Also we will go through the steps on how to stop each component of DQ+ like Load Balancer, Application Servers, ApplicationDB and ComputeDB individually.

In DQ+ 2.1.1 and 2.1.2 the stop and start command stop/start all components, except ComputeDB (VerticaDB). In DQ+ 3.0 and later versions, the command will stop/start all components including ComputeDB.

(i) Complete Start/Stop of Application
(ii) Stop/Start Application components individually
(iii) Deployment of Application

(i) Complete Start/Stop of Application:

a- DQ+ 2.1.1 & 2.1.2

• Login into the Maintenance Node and switch to maintenance user (usually the user-name is “sagacity”).
• Change directory to /opt/infogix/sagacity-2.1/bin/
• Execute “./stop” command to stop all the Application components.
• To stop computeDB execute “./stopComputeDB”.
  
  (./stop)
  
  (./stopComputeDB)
  

(In a similar sequence, start the Application)

• Execute “./start” from same directory (/opt/infogix/sagacity-2.1/bin/)
• To start ComputeDB execute “./startComputeDB”
  
  (./start)
  
  
  (./startComputeDB)
  

(b) - DQ+ 3.0 and later version.

• Login into the Maintenance Node and switch to maintenance user (usually the user-name is “sagacity”).
• Change directory to /opt/infogix/sagacity-3.0/bin/
• Execute “./stop” command to stop all the Application components, include ComputeDB.
  
  

• To start the Application execute "./start" from same directory /opt/infogix/sagacity-3.0/bin/. (This will start all the Application component including ComputeDB)
  
  
  
  
  Back to top 
  

(ii)  Stop/Start Application components individually.

To stop and start the individual system components, use the following commands. The commands are available under /opt/infogix/sagacity-3.0/bin

• Application Server
  ./stopApplication
  ./startApplication
  

• ApplicationDB
  ./stopApplicationDB
  ./startApplicationDB
  
  

• ComputeDB
  ./stopComputeDB
  ./startComputeDB
  
  

• Load Balancer
  ./stopLoadBalancer
  ./startLoadBalancer
  

Back to top

(iii) - Deployment of Application

Changes in install.proeprties require re-deployment of an Application. Before re-deploying the Application, make sure all the components are running and functional.

•  Go to /opt/infogix/sagacity-3.0/bin.
• As maintenance user execute "./deploy"
  
  
  
  

Back to top

Note : In 2.1.1, and 2.1.2 Password-less sudo access of maintenance user is required for all above activities. However, in DQ+3.0 after Fix Pack 5 Password-less sudo access of maintenance user is not required.

Back to top