Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Macro name changed from html to html-bobswift during server to cloud migration processing.

...

Description

Performs a bulk export of all records in your Controller database.
 
The location of the export is specified by the Export Path (opswise.export.path) Universal Controller system property.
 
The default directory, where $CATALINA_HOME is the base Tomcat installation directory, is either:

Html bobswift
<ul>
<li> <code>$CATALINA_HOME/opswise_export</code>
<li> <code>$CATALINA_HOME\opswise_export</code>
</ul>

Each export creates a sub-directory under the specified path in the following format:
 
WWW_MMM_DD_HH_MM_SS_TZ_YYYY-BULK_EXPORT

Html bobswift
<ul>
<li> <code>WWW</code>: 3-Letter Weekday
<li> <code>MMM</code>: 3-Letter Month
<li> <code>DD</code>:  Day
<li> <code>HH</code>:  Hour
<li> <code>MM</code>:  Minute
<li> <code>SS</code>:  Second
<li> <code>TZ</code>:  Time Zone
<li> <code>YYYY</code>: 4-Digit Year
</ul>
Note
titleNote

Export Bulk performs a similar function as the Bulk Export Server Operation, but not Bulk Export with Versions.

Syntax

uagcmd ops-export-bulk global parameters
 

Note
titleNote

For backward-compatibility, you can exclude uagcmd from the command line for this function and all pre-6.2.0.0 CLI functions.

Example

Panel
html-bobswift
<pre>uagcmd ops-export-bulk 

-c config.cfg

Html bobswift
 </pre>

Anchor
ops-export trigger
ops-export trigger
Export Trigger

Anchor
export trigger
export trigger
Description

Performs an export of the specified trigger(s) and all the associated record(s). For example, if you export one trigger, the CLI also exports the calendar used in the trigger and all tasks launched by the trigger. The CLI creates a separate XML file for each record type and generates the output directory and file names using a date and timestamp, plus an internal record identifier generated by the Controller.
 
All exported XML definition files will be saved to a timestamped directory under the path defined by the Export Path Universal Controller system property. The following illustrates a sample output directory and exported data:
 

 

Syntax

uagcmd ops-export-trigger global parameters trigger-name=name [trigger-type=type]
 

Note
titleNote

For backward-compatibility, you can exclude uagcmd from the command line for this function and all pre-6.2.0.0 CLI functions.

Parameters

Html bobswift
<ul>
<li> <code>trigger-name=</code> <br>Required; Name of one or more 

triggers. Wildcards

Html bobswift
 are supported. 
<li> <code>trigger-type=</code> <br>Optional; If you used a wildcard in <b>trigger-name</b>, you can use <b>trigger-type</b> to narrow down the selection to a specific type of trigger. Allowable values are (not case sensitive): <b>cron</b>, <b>time</b>, <b>file_trigger</b>, <b>temporary</b>, <b>task_monitor</b>, <b>manual</b>, <b>application_monitor</b>. </ul>

Example

This example exports all triggers whose name begins with SF:
 

Panel
html-bobswift
<pre>uagcmd ops-export-trigger 

-c config.cfg

Html bobswift
 trigger-name=SF* </pre>

Anchor
ops-import-bulk
ops-import-bulk
Import Bulk

Description

Performs a bulk import of records into your Controller database.
 
The location from where records are imported is specified by the System Default CLI Bulk Import Path (opswise.bulk_import.path.default) Universal Controller system property.
 
The default directory, where $CATALINA_HOME is the base Tomcat installation directory, is either:

Html bobswift
<ul>
<li> <code>$CATALINA_HOME/opswise_import</code>
<li> <code>$CATALINA_HOME\opswise_import</code>
</ul>
Note
titleNote

The data being imported must have been exported using the Export Bulk command.

Syntax

uagcmd ops-import-bulk global parameters
 

Note
titleNote

For backward-compatibility, you can exclude uagcmd from the command line for this function and all pre-6.2.0.0 CLI functions.

Example

Panel
Html bobswift
<pre>uagcmd ops-import-bulk 

-c config.cfg

Html bobswift
</pre>

Anchor
ops-import-trigger
ops-import-trigger
Import Trigger

Description

Imports into your Universal Controller database the trigger records in the path specified in the import-file= parameter.

Syntax

uagcmd ops-import-trigger global parameters import-file=file
 

Note
titleNote

For backward-compatibility, you can exclude uagcmd from the command line for this function and all pre-6.2.0.0 CLI functions.

Parameter

  • import-file=
    Required; Path containing one or more XML files that were exported via ops-export-trigger or via the Universal Controller user interface using the Export -> XML feature.
     

    Note
    titleNote

    This is the path on the Controller server where the XML files are stored, not a local path to where the command is run.

Example

Panel
Html bobswift
<pre>uagcmd ops-import-trigger -

-c config.cfg

Html bobswift
 import-file=ops\import</pre>