sdeploy syntax summary

The sdeploy utility command is used to analyze systems, build maps in the system, and generate and deploy systems.

The .msd file is a required field and is the name of the system definition file, located on disk, that needs to be analyzed, compiled, generated, or deployed to the specified server. The system definition file can have any number of systems in it.

If you make modifications, such as changing the number or order of input or output cards in your maps, you must open the .msd file in the Integration Flow Designer and save the changes in the file there to synchronize the changes before you can deploy the system using the sdeploy utility command.

If the full path of the .msd file name is not specified, the sdeploy command will search for the .msd file in the current directory. Because the sdeploy command expects the map source definition (.msd) file to be specified after it, if the .msd file is not specified, the following error message will display on the console:


"Invalid or empty map source file. Cannot open file path\command_parameters"

The following is the syntax of the sdeploy utility command:


sdeploy <.msd file>
      -L
      - or -
sdeploy <.msd file> 
       -A [-K] [-NO] 
          <ANALYZE OPTIONS | BUILDMAPS OPTIONS 
          |GENERATE OPTIONS>
       [(-LOG [. | <log file name/location>]
           [-FAIL] [-VERBOSE] [-APPEND])
       | -NOLOG]
      - or -
sdeploy <.msd file> <system> [-NO] 
          <ANALYZE OPTIONS | BUILDMAPS OPTIONS 
          |GENERATE OPTIONS| DEPLOY OPTIONS>
       [(-LOG [. | <log file name/location>]
           [-FAIL] [-VERBOSE] [-APPEND])
       | -NOLOG]