Exporting application metadata

Before any application metadata can be imported, it must first be exported into an XML file.
Note: You can also export metadata using a Command Line Interface (CLI). See Running App Metadata Transport from a CLI.
  1. Open the App Metadata Transport utility (either the form version or the stand-alone version).
  2. On the Action page, select the Export metadata from a source database to an XML file check box, and then click Next.
  3. (Stand-alone version only) On the Source page, select the Source Configuration to use as the source for the metadata.

    When you make your selection, the Source Connection panel displays additional information about the source.

    Note: The form version skips this step. You can use only the configuration in which you are working as the Source.
  4. Click Next.
  5. On the Target page, specify the name for the XML file that is to contain the exported metadata.
    The action to do this depends on where you are using the utility:
    • In the web client, enter the file name into the Export File Name field.
      Note: Make sure you add the .XML extension at the end of the file name. The web client does not add the extension automatically.
    • In either the Windows client or the stand-alone version, you can use the Browse button to launch a Save As dialog box in which you can navigate to the desired location for the file and provide the file name.
      Note: In these cases, the utility appends the .XML extension automatically.
  6. Click Next.
  7. For each of the next series of pages, select the metadata to export, and then click Next.
    For most tabs, you can select none, all, or selected items. In some cases, you can also select only items that are referenced by selected items, as indicated in this table:
    Page Affected data
    IDOs Multiple database tables, such as ido.Collections, ido.Tables, ido.Methods, and others

    Even though multiple tables are affected, the IDO is exported as a single unit, for example, the ido.Collections record and all its children.

    Note: You must select the IDO Project to which the IDO belongs before you can select specific IDOs for export.
    Property Classes Only data in the ido.PropertyClasses tables

    You can also select to have the metadata for property classes referenced by selected IDOs exported.

    IDO Assemblies Only data in the ido.CustomAssembly tables
    Note: In the stand-alone version, this page is labeled Custom Assemblies. It amounts to the same thing.

    You can also select to have the metadata for IDO assemblies referenced by selected IDOs exported.

    Events Application events metadata for a selected Access As value
    Note: You must select an Access As value before this and the following options become available.
    Event Triggers Application event trigger metadata for the previously selected Access As value

    You can also select to have the metadata for event triggers that are referenced by selected events exported.

    Event Handlers All the application event handler metadata for the previously selected Access As value

    You can also select to have the metadata for event handlers that are referenced by selected events exported.

    Event Global Constants All the application event handler global constant metadata for the previously selected Access As value

    You can also select to have the metadata for event global constants that are referenced by selected event handlers exported.

    Replication Documents All Business Object Document (BOD), Inbound Cross Reference, and Outbound Cross Reference metadata for a selected Access As value
    Note: You must select an Access As value before these options and following few become available.

    You can also select to have the metadata for entire replication documents where any portion matches the Access As filter exported.

    Replicaton Document Elements All metadata for replication document elements of the previously selected Access As value

    You can also select to have the metadata for replication document elements referenced by selected replication documents exported.

    Replicaton Document Attributes All metadata for replication document elements of the previously selected Access As value

    You can also select to have the metadata for replication document attributes referenced by selected replication document elements exported.

    Replicaton Document Inbounds All metadata for inbound replication documents of the previously selected Access As value

    You can also select to have the metadata for inbound replication documents referenced by selected replication documents exported.

    Replicaton Document Outbounds All metadata for outbound replication documents of the previously selected Access As value

    You can also select to have the metadata for outbound replication documents referenced by selected replication documents exported.

    Predefined DataViews Multiple database tables, including WBDataViews, WBDataViewLayouts, WBDataViewActions, and others

    This metadata can include multiple DataViews, DataView Layouts, and associated DataView Setup information.

    You can also select specific DataView Actions separately.

    Form Extensions All the Form Extensions data for a particular Access As value
    Note: You must select an Access As value before the selection options become available.
  8. On the Summary page, verify the actions to be performed.
  9. Click Finish.
The App Metadata Transport utility converts the metadata to an XML format and saves it with the designated file name (and path, if applicable).

In the case of the web client version, the browser typically presents the saved file automatically, with the option to open it. If it does not, you can locate the file in your Downloads folder and open it from there.

In the case of the Windows client version and the stand-alone version, the file is saved to the location you designated when naming the file.

In all cases, you can use any good text/code editor to review the saved metadata.

Related topics