Export XML file from server

Produces a XML File representation of a remote EDMdatabase model.
The XML File format is defined in ISO 10303-28: XML representation for EXPRESS-driven data. A XML File is also referred to as a Part 28 file.
This is one of the file exchange formats of ISO 10303, and can be used to exchange data between two EDMdatabases or between an EDMdatabase and any application that conforms to ISO 10303-28. The produced file can also be used for long time archiving of the data.
The Header Section part of the XML file can be produced from the specified existing header model in the EDMdatabase or a default Header Section will be produced when no header model is specified. A header model is a model of the HEADER_SECTION_SCHEMA defined in ISO 10303-21.
Arguments:

Server context name:	Specify name of server context. When activating the Select button, the name of all defined server contexts will be displayed in the related selection list.
Remote repository:	Specify the name of the remote repository holding the model to be exported. Repository names are case sensitive. When activating the Select button, the name of all open remote repositories will be displayed in the related selection list.
Remote model:	Specify the name of the remote model to be exported. Model names are case sensitive. When activating the Select button, the name of all open models located in the repository(ies) specified by the <Remote repository> argument will be displayed in the related selection list..
Remote header model repository:	Specify the name of the remote repository holding the XML Header Model to be exported. Repository names are case sensitive. When activating the Select button, the name of all open remote repositories will be displayed in the related selection list.
Remote header model:	Specify the name of the STEP Header Model in the remote EDMdatabase that will be mapped to the Header Section in the resulting step file. STEP Header Model names are case sensitive. There are several ways to customize one or more STEP Header Models in EDMsupervisor, among others the 2 following ways: 1) Edit an existing STEP file and import this file by the command Data>ImportModel. 2) Create a STEP Header Model by the command sequence: Data>Create>Model , Data>Open>Model , Data>Create>Instance , and Data>Close>Model . When activating the Select button, the names of all STEP Header models in the EDMdatabase will be displayed.
XML file:	Specify the name of the XML file produced by this command. The default file extension is ".xml”. When activating the Select button, a window is opened to allow browsing the directory structure and select/specify the desired file.
Diagnostic file:	Specify the file name for diagnostic information generated by this command. If no file name is supplied, all diagnostic information will be displayed in the EDMsupervisor output window. When activating the Select button, a window is opened to allow browsing the directory structure and select/specify the desired file.
Remote XML configuration:	The name of the XML configuration to apply. XML Configurations are unique within the scope of an Express Schema. See ISO 10303-P28 for more about XML configuration.

Options:

accumulating command output:	A global option that appends the command output to the EDMsupervisor output window. Otherwise the output window is refreshed and only the last command output is displayed.
match selected input:	A global option that specifies that only items that partly or exactly matches the string in the related argument input field when activating a Select button, will be in the selection list. An empty (blank) string will match all items. This option has no effect on file name arguments.
kept STEP identifiers:	A STEP Identifier model will be created and connected to the data model created by this operation. The STEP Identifier model will keep the correspondence between the STEP file entity instances and the EDM instanceID. The command Data>ShowStepIdentifier can be used to display the stepID corresponding to an EDM instanceID and vice versa. The EDMmodelChecker can optionally output the stepID of failing instances on the validation report.
EDM identifiers:	Specifies that the EDMdatabase instanceID will be used as instance identifiers in the STEP Physical File such that it will be easy to find the correspondence between a mapped instance on the STEP file and the same instance in the EDMdatabase.
no header change:	Specifies that the header model specified by the <Remote header model> argument will be mapped to the actual STEP file without any changes. Normally the mapping method, time stamp, and schema name will be provided by the EDMstepHandler function. No information will be provided by the EDMstepHandler when this option is set. This argument is only effective when a header model is specified in the <Remote header model> argument.
compressed_file:	The resulting exported XML file will be in a compressed file format.
show file:	The resulting exported XML file will also be displayed in the default Internet Browser.