Exporting from the Command Line

You can export elements from the model using the following syntax:

Export.exe [-q] [-s DatabaseInstance] –m ModelName  
[–a] [–l LogFileName ] –f Filename ElementName [–bi] [-nc] [-nu] [-nd] 
ElementName2 [-nc] [-nu] [-nd] ElementName3 …

You can export the changed elements from the model using the following syntax:

Export.exe {-se|-si|-sd| “DATE”} [-q] 
[-s DatabaseInstance] –m ModelName  [–a] [–l LogFileName] 
–f Filename ElementName [-nc] [-nu] 
[-nd] ElementName2  [-nc] [-nu] [-nd] Elementname3 …

Where,

Syntax	Description
[ ]	Denotes an optional argument.
-a or /a	Specifies that the log entries are to be appended to the end of the log file rather than replacing the existing contents.
-b BatchFileName or /b BatchFileName	Specifies the full path of the export batch file. Specifies the qualified names of the elements to be exported in the batch file. *Note:* Specify flag “#BATCH_EXPORT” as the first line and only one qualified element name at each line in the export batch file.
–bi	Specifies that the elements are to be exported to Business Integrator. *Notes:* You can use this argument only with -q, -a, -s, -m, -l, and -f arguments. If -bi is set, you cannot use the -b argument. If -bi is set, PModel file is not supported. If -bi is set, the arguments -nc, -nu, -nd, -sd, -se, -si, -smb, -b, and -vf are ignored. BI export supports only the objects that can accept automatic entries. If the instance derives its definition from a Primitive type, this export extracts the Primitive definition of the instance.
ElementName	Specifies the qualified names of the elements to be exported from the model.
-f Filename or /f FileName	Specifies the full path of the export file.
-l LogFileName or /l LogFileName	Specifies a different log file name to use rather than the default.
-m ModelName or /m ModelName	Specifies the name of the model within the database instance. This is a required parameter.
-nc or /nc	Specifies that the children of the element should not be exported.
-nd or /nd	Specifies that the documentation of the element should not be exported.
-nu or /nu	Specifies that the UML diagrams of the element should not be exported.
-q or /q	Specifies that the export should be quiet, that is, the progress dialog box is not displayed. If running in quiet mode, all required parameters must be given. The export exits with an error if all required parameters are not defined.
-s DatabaseInstance or /s DatabaseInstance	Specifies the SQL Server database instance. If this parameter is omitted, the file exports from the local machine.
-sd “DATE” or /sd “DATE”	Specifies that changes made since a specified date are to be exported. The format for the date is “mm/dd/yyyy hh:mm:ss”.
-se or /se	Specifies that changes made since the last export are to be exported.
-si or /si	Specifies that changes made since the last import are to be exported.
-smb or /smb	Specifies that elements that have been imported after the Migration Database has been base lined are to be exported.
-vf or /vf	Specifies the version file to be exported. The -vf option is available only on the export command line and should be used with the version control feature.

For example, at the command prompt type:

To write export messages to a log file:

Export –s <server name> -m <model name> -f <filename.model> -l <log file path name> <Segment Name>

Where, Export –s localhost –m Meta –f Meta.model –l Meta.log MYSEG

Note: The log file is created only if error or warning messages are generated. If the export runs to completion without generating any error or warning messages then no log file is created.

To export those elements which have changed since a specific date:

Export –s <server name> -m <model name> -f <filename.model> -sd <date> <Segment Name>

Where, Export -s localhost -m Meta -f Meta.model -sd 07/27/2006 MYSEG

Note: The date string format is determined by the regional settings currently in effect.

To export those elements which have changed since the last export:

Export –s <server name> -m <model name> -f <filename.model> -se <Segment Name>

Where, Export -s localhost -m Meta -f Meta.model -se MYSEG

To export those elements which have changed since the last import:

Export –s <server name> -m <model name> -f <filename.model> -si <Segment Name>

Where, Export -s localhost -m Meta -f Meta.model -si MYSEG

Note: The –sd, -se and –si options are mutually exclusive.

The Export window is displayed which shows the progress of the Export action.

Note: The default directory should be /NGEN/Bin/

To export multiple elements in batch by using export batch file:

Export -s <server name> -m <model name> -f <filename.model> -b <filename.bch>

Note: For example, the content of the export batch file (filename.bch) might look like the following:

#BATCH_EXPORT

Segment1.Ispec1

Segment1.Ispec2

To export the elements from command line to business integrator:

Export -q -s <server name> -m <model name> -f <filename.model> <segment name> -bi

For example, the following command can be used to export to business integrator:

Export.exe -s localhost -m SystemModeler1 -f “C:\Temp\BIModel.model” Segment1.Ispec1 -bi