Import an Application

The ImportApp utility lets you copy an entire application from a previously exported text or XML file into a database.

You should run the ImportApp utility with a value for the -n parameter (described in Parameters for the ImportApp Utility) to resolve name conflicts between imported and existing applications and components. Such conflicts can arise in any of the following situations:

• If the name of a component being merged into an existing application already exists in that application

• If you create a new application with the same name as an application that already exists in the database

The most efficient method of accessing the ImportApp utility is from the Develop tab of Workbench.

1. Click the header bar of the Applications portlet on the Develop tab to make it the active portlet.

See the descriptions for each of these parameters in Parameters for the ImportApp Utility.

You can specify the following parameters using the Import an Application dialog:

Specifies the format of the application file to be imported:

Allows OpenROAD to determine the format of the application file. OpenROAD first tries to import using its proprietary format; if this fails, it imports using XML format.

Specifies the name of the file from which the application is being imported. Click Browse to display a standard File Selection dialog.

Specifies the name of the application that is to be created or merged into

Specifies how to treat name conflicts with one of the following values:

Directs OpenROAD to abort this utility and to back out any components that were already added

Specifies that if an application or application component being imported already exists, the existing application or component is versioned before being replaced

If any component has compilation errors, causes OpenROAD to write the component's 4GL script and any errors to the Trace window

Instructs OpenROAD to treat compiler warnings as errors

Merges the components from the input file into the existing application

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.

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.

Lets you use this command as if you were another user, username. This entry field can be used only if Execute in Background is enabled.

Note: You, not username, own all files created by OpenROAD.

Specifies the name of a log file. This entry field can be used only if Execute in Background is enabled and Trace Window is set to Yes. If the log path specified is not a full path, the file is created in the ingres\files directory.

Lets you control display of the Trace window by entering one of the following values:

Specifies that the Trace window appears but suppresses informational messages output by the system

Specifies that the Trace window appears minimized as an icon

Specifies that the Trace window does not appear, and a log file is not created

Note: This entry field can be used only if Execute in Background is enabled.

Appends the trace output of the current command to the end of the existing error log file. Otherwise, that log file is replaced. This entry field can be used only if Execute in Background is enabled.

Note: The error log file, w4gl.log, is located in %USERPROFILE%\AppData\Local\OpenROAD\Profiles\installation_ID. If the -L flag is passed, a new name and location can be provided for the OpenROAD log file.

Begins a new process while you are using this utility.

If enabled, Execute in Background makes Username, Log Path, Trace Window, and Append to Log File available for use.

Note: You can set defaults for this utility using the Set Tool Defaults dialog. see Set Defaults.

Command Line Method of Importing an Application from a File (BackupApp)

To import an application from a file, start the backup app utility from the command line:

w4gldev backupapp in database application file
    [-nowindows] [-xml] [-uusername] [-Lfilename] [-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:

Specifies the name and location of the database in which the application resides

Specifies the name of the file from which the application or component is being imported

Lets the application run without the window manager running. This option does not provide full batch mode execution, because some interaction with the application still may be required through the Trace window.

Lets you use this command as if you were another user, username.

Note: You, not username, own all files created by OpenROAD.

Specifies the name of a log file. If the log path specified is not a full path, the file is created in the %II_SYSTEM%\ingres\files directory.

Specifies that the component's 4GL script and any errors should be written to the Trace window, if any component has compilation errors

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.

Specifies how to treat name conflicts. The option can be one of the following values:

Directs OpenROAD to abort this utility and to back out any components that were already added

Specifies that if an application or application component being imported already exists, the existing application or component is versioned before being replaced

Merges the components from the input file into the existing application

Specifies that transactions are committed after each component is added to the database

Controls the display of the Trace window by entering one of the following values:

Specifies that the Trace window appears but suppresses all informational system messages

Specifies that the Trace window appears minimized as an icon, and all informational system messages are suppressed

Specifies that the Trace window does not appear, but all messages are saved in a log file without informational system messages

Specifies that the Trace window does appear and all messages are written

Specifies that messages are written to the Trace window, which appears minimized as an icon

Specifies that the Trace window does not appear, but all messages are saved in a log file

Specifies that the Trace window does not appear, and no log file is created

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.

An exit code of zero (0) means success; a non-zero exit code indicates an error.

The following example imports an application, “myapp,” from the export file “myapp.bck.” This command also forces the application components to be compiled before being loaded into the database:

The following example replaces the “myapp” application in mydatabase with the application contained in the file “myapp.bck”:

w4gldev backupapp in mydatabase myapp myapp.bck -nreplace

The following example imports the “myapp” application in “mydatabase” with the application contained in the file “myappxml.xml”:

w4gldev backupapp in mydatabase myapp myappxml.xml -xml