Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Introduction

The Operation element is part of a specifies the type of file transfer that is to be carried out.

In the XSD schema, the operation is a child of the profile element as is shown in the diagram.

 

 

The Operation element that is selected defines the source and target elements that can be called as well as the transfer options that may be available.

It is required for each file transfer configuration.

Operation - the action JADE is to carry out

 The JADE Client can carry out a number of different operations.

These are:

  • copy - duplicate the files from one location to another
  • move - duplicate the files from one location to another and then delete the original files
  • remove - delete files from a server
  • getlist - obtain a file containing a list of file names  VERIFY DEFINITION

The default value for this parameter is copy. VERIFY

The operation element is mandatory.

Example Configuration using the 'Copy' Operation

An example configuration using the 'Copy' Operation was shown on the Configuring File Transfers with the JADE Client page.

The example was generated using the SOS XML Editor and is shown both as a configuration tree in the editor and as a JADE XML configuration file.

Example Configuration using the 'getlist' Operation

 

The getlist operation requires two child elements:

  • GetListSourceFragmentRef, which includes parameters specifying the fragment parameters to be used to connect to the directory/directories to be listed and
  • SourceFileOptions, which includes parameters specifying the directory/directories to be listed, file selection criteria and whether polling should be carried out.

A target fragment is not required:

  • the ResultSetFile parameter can be used specify a file in which the results of the getlist operation are saved
  • if a ResultSetFile is not specified the default output for getlist is the JADE log4j logger

A simple getlist configuration in the SOS XML Editor is shown in the screenshot below.

The above configuration looks for two files on the 'demo' FTP server on the SOS 'test' subdomain and lists their occurrence in the JADE log file.BLEIBT SO?

The configuration uses an FTPFragment with a basic connection and password authentication to log onto the server.

Two files are specified in the FilePath element.

The following listing shows the XML configuration file generated by the Editor.

A simple profile that looks for 2 files and creates a list showing their occurrence 
 <?xml version="1.0" encoding="UTF-8"?>
<Configurations>
  <Fragments>
    <ProtocolFragments>
      <FTPFragment name="demo-test.sos-berlin.com">
        <BasicAuthentication>
          <Account><![CDATA[demo]]></Account>
          <Password><![CDATA[demo]]></Password>
        </BasicAuthentication>
        <BasicConnection>
          <Hostname><![CDATA[test.sos-berlin.com]]></Hostname>
        </BasicConnection>
      </FTPFragment>
    </ProtocolFragments>
  </Fragments>
  <Profiles>
    <Profile profile_id="ftp_demo_getlist_lorem_ipsum">
      <Operation>
        <GetList>
          <GetListSourceFragmentRef>
            <FTPFragmentRef ref="demo-test.sos-berlin.com" />
          </GetListSourceFragmentRef>
          <SourceFileOptions>
            <Selection>
              <FilePathSelection>
                <FilePath><![CDATA[a/lorem_ipsum_medium.pdf.gz,a/lorem_ipsum_large.pdf.gz]]></FilePath>
              </FilePathSelection>
            </Selection>
          </SourceFileOptions>
        </GetList>
      </Operation>
    </Profile>
  </Profiles>
</Configurations>

A simple profile that uses FTP to look for 2 files on a test host and lists their occurrence in the the JADE log file.

 

 

 

 

 

  • No labels