Exporting Metadata Using FileWatcher (File Approach)

Procedure

  1. Complete the required FileWatcher setup.
    1. The following sample FileWatcher section must be present for exporting metadata: 
            <DataSet type="single" >
            <Name>Export</Name>
            <Credential domain="GLN">
              <Identity>0040885020007</Identity>
               <!-- Set this to point to the source enterprise -->                     </Credential>
            <Action>DataServiceQuery</Action>
               <URIInfo scheme="local">
                  <Relative>MQ_COMMON_DIR</Relative>
                   <URI>source/metadata/export</URI> 
                  <!-- Directory where                         request XML will be put-->
               </URIInfo>
      </DataSet>

      In this example, the credential section is set to use a credential of the source company from which the export of metadata is to be done. The credentials can belong to any valid TIBCO MDM supported domain.

    2. Ensure that PollingInterval is set to a non-zero value to turn on polling by FileWatcher. For example: 
      <PollingInterval>600</PollingInterval>

      In the above example, the polling interval is set to 10 minutes.

  2. Create an Export Request XML.
    • Create as many transaction sections as the number of entities that need to be exported. Keep in mind that only one command and entity are supported within a transaction.
      Note: Copy metadata does not support multiple transactions in SQL Server.
    • Set command type to Query.
    • Set the type and name of entity to be exported.
    • All entries are case-sensitive.
  3. Copy the Export Request XML into the directory monitored by FileWatcher. In the above example, copy the file into the $MQ_COMMON_DIR/source/metadata/export/incoming directory.

    You can monitor the export from the event log of TIBCO MDM. You can also look at $MQ_HOME/log/dataservice.log.

Result

A JAR file is generated as a response to the export request. The JAR file is copied to a location specified in the metadata migration workflow ($MQ_COMMON_DIR/standard/workflow/wfin26dataservicev2.xml). The JAR file can also be downloaded from the Event Log.