QAD 2017 Enterprise Edition > User Guides > System Administration > Reports and Utilities > Command Line Application Control
  
Command Line Application Control
The application control program, applicationcontrol.p, can be used to start and stop applications and daemons (except the Report daemon), and to perform a command-line synchronization. This program lets you perform application maintenance from the command line, without launching the application interface.
The application options include the ability to start the application with or without housekeeping, which deletes inactive data from the database. The Synchronize options include the ability to synchronize all or specific application components
The command line syntax for applicationcontrol.p is:
_progres -p applicationcontrol.p -param <options> -b > <LogFile>
where <options> is a string to pass options to the program, and has the format -<option> [<value] [-<option> [<value]].
You can configure the following options:
• URL
Specify the appserver URL with the following syntax:
appserver://<HostName>:<NameServerPort>/<AppServiceName
• PROPATH
Indicate the propath to be used by the _progres session in cases where the logic is run in the process itself rather than on the central appserver. You indicate the propath when you have not specified an appserver URL.
• ACTION
Specify an action to be performed. The <value> string can be one of the following:
StartApplication
StartApplication_no_housekeeping
StopApplication
StopApplication_no_wait
StartDaemon [<DaemonName>]
Use this option to start a new instance of the named daemon. If you do not specify a daemon, the system starts all configured daemons.
StopDaemon <DaemonName>
This option sends a stop request for all instances of the named daemon.
DaemonStatus [<DaemonName>]
This returns status information for the named daemon, for example:
Daemon Name: XmlDaemon
[Status] Status: Active
[Status] #Running instances: 2
[Status] Proces Ids: 1884, 4856
[Status] Start date of daemon: 04/12/2007
[Config] Log file: /users/xyz/logs/xmldaemon.log
[Config] Startup folder: /users/xyz/daemons/xmldaemon
[Config] Daemon login: user
[Config] XML input folder: /users/xyz/daemons/
xmldaemon/input
ResetDaemonConfiguration [<DaemonName>]
Note: If the daemon is not specified, the system returns the status of all defined daemons in the system
ResetDaemonConfiguration [<DaemonName>]
By default, this resets all daemons, but by specifying a Daemon name as an extra parameter, it can be limited to one daemon only.
Use ResetDaemonConfiguration when you are copying an application database from one environment to another. This ensures that daemon configurations are reset to initial values, and prevents daemons from using previous.
By default, this resets all daemons, but you can limit the reset to a single daemon by specifying the daemon name as an extra parameter.
Synchronize [Full|Limited|Topic<XX>]
This performs a full or limited synchronization, or for specified topics.
Each topic is represented by a topic number, as listed in Synchronization Topic List. The Synchronization Type column indicates if the topic is automatically included in limited or full synchronizations if you do not specify it by number.

Synchronization Topic List
 
Synchronization Topic
Topic Number
Synchronization Type
Languages
1
LIMITED
Areas, Classes, and Activities
2
FULL
Default Activities
3
FULL
Shared Set Types
4
LIMITED
Stored Searches Defaults
5
FULL
Superuser Role
6
FULL
Report Strings
7
FULL
Daemons
8
FULL
Settings Configuration
9
FULL
Users
10
LIMITED
Default Entity
11
FULL
Translations
12
FULL
System
14
FULL
Resources
15
FULL
Default Roles
16
FULL
GL Types
101
LIMITED
Daybook Types
102
LIMITED
Profile Types
103
LIMITED
Exchange Rate Types
104
LIMITED
Address Types
106
LIMITED
GL System Types
107
LIMITED
Currencies
108
FULL
Business Relations
109
FULL
SAF Concept
110
LIMITED
Countries
111
FULL
Rounding Methods
112
FULL
Domains
113
FULL
China Accounting Interface Reports
114
FULL
China Accounting Interface Filter
115
FULL
Bank Account Validations
116
LIMITED
Non Taxable Tax Group
117
LIMITED
Example: Use the following command to run the application installed to the directory C:\qad2008 and to check the status of the XML daemon running on this server. You must include the \lib and Progress procedure library directories in the propath. The command displays the command results in the log file vek.log.
_progres -p applicationcontrol.p -param "-PROPATH C:\qad2008\fin\lib,C:\qad2008\fin\qadfin.pl -ACTION DaemonStatus[xmldaemon]" -b > vek.log