16. Managing and Deploying Applications : How You Can Import and Export Applications and Components : Import an Application : Command Line Method of Importing an Application from a File
 
Share this page                  
Command Line Method of Importing an Application from a File
To import an application from a file, start the backup app utility from the command line:
w4gldev backupapp in database application file
          [-xml] [-uusername] [-e] [-f]
          [-n{prompt|abort|replace|version}] [-m] [-t]
          [-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-A]
The following parameters and flags are available from the command prompt:
database
Specifies the name and location of the database in which the application resides
application
Specifies the name of the application to import
file
Specifies the name of the file from which the application or component is being imported
-xml
Specifies XML format
-uusername
Lets you use this command as if you were another user, username.
Notes:
You, not username, own all files created by OpenROAD.
This entry field can be used only if Execute in Background is enabled.
-e
Specifies that the component's 4GL script and any errors should be written to the Trace window, if any component has compilation errors
-f
Forces compilation of the application components before they are loaded into the database.
If there is a compilation error, the component is still loaded into the database, but is marked as “out of date.”
If you do not include this parameter, components are copied into the database marked “out of date,” and are compiled the first time you compile or run the application.
-noption
Specifies how to treat name conflicts. The option can be one of the following values:
prompt
Requests a prompt when there is a conflict
abort
Directs OpenROAD to abort this utility and to back out any components that were already added
replace
Replaces the old component with the new component
version
Specifies that if an application or application component being imported already exists, the existing application or component is versioned before being replaced
Default: abort
-m
Merges the components from the input file into the existing application
-t
Specifies that transactions are committed after each component is added to the database
Important!  Using this parameter decreases contention and log file use. However, if your database server crashes or the ImportApp utility is aborted before completion, only some of the application components are loaded.
-T
Controls the display of the Trace window by entering one of the following values:
yes
Specifies that the Trace window appears but suppresses all informational system messages
yes,min
Specifies that the Trace window appears minimized as an icon, and all informational system messages are suppressed
yes,logonly
Specifies that the Trace window does not appear, but all messages are saved in a log file without informational system messages
all
Specifies that the Trace window does appear and all messages are written
all,min
Specifies that messages are written to the Trace window, which appears minimized as an icon
all,logonly
Specifies that the Trace window does not appear, but all messages are saved in a log file
no
Specifies that the Trace window does not appear, and no log file is created
-A
Appends the trace output of the current command to the end of the existing error log file.
Note:  The error log file, w4gl.log, is located in %II_SYSTEM%\ingres\files.