16. Managing and Deploying Applications : How You Can Import and Export Applications and Components : Export Applications and Components : Command Line Method of Exporting an Application to a File
 
Share this page                  
Command Line Method of Exporting an Application to a File
To export an application to a file using the command line, enter the following command at the command line:
w4gldev backupapp out database application file [-appsource]
          [-xml [-xmeta]] [-uusername] [-vversion]
          [-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-A] [-t]
Note:  The following parameters and flags are available from the command line:
database
Specifies the name and location of the database in which the application resides
application
Specifies the name of the application to export
file
Specifies the name of the file to which the application will be exported
-appsource
Specifies that only application source information (application properties and included applications) will be included in the export file; no component information will be written to the file. Selecting this option is useful when you want to recreate an empty application from an empty export file before importing its components.
-xml
Specifies XML format
-xmeta
Specifies whether the original XML metadata (AlterBy, AlterDate, Creator, CreateDate) is exported to the XML component file. If this parameter is not included, OpenROAD assigns new metadata to the exported component. To use this parameter, you must also specify -xml as the file output 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.
-vversion
Specifies the version of the application to export
-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.
-t
Specifies that transactions are committed after each component is deleted from the database
Important!  Using this parameter decreases contention and log file use. However, if your database server terminates abnormally or the BackupApp utility is aborted before completion, only some of the application components are deleted.