Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Next »

  • Just copied this over. This needs to be rewritten to v8 - still references the Design tab - needs new screen shots of buttons, icons, and screens where appropriate. Laura Knowles

Use operations to collect all the information needed to define exactly what a particular integration process does and when it should start.

Note: Projects are deployed to an Environment in Jitterbit Harmony.  You will need to create at least one Environment before you will be able to create an operation

Note: Operations reside within a project. You will need to create a project before you can create an operation. See Getting Started Screen for more information.

Create Operation

  • There are several ways you can start to create a new operation:
    • Select New in the File menu, then choose New Operation from the sub-menu
    • Choose New Operation from the top-toolbar
    • Right-click on Operations in the hierarchical tree in the Design tab in the left pane of the screen, then choose New Operation from the popup menu.
  • Your new empty operation appears in its own New Operation tab in the right pane of the window.

Configure the Operation

  • Type a name into the Name field in the operation image.
  • To enter operation properties, click the inverted arrow.
    • (Optional) You can enter a description of the operation in the Description field.
  • Specify the operation's Activity by selecting one of the following from the Activity selection list:
    • Archive - is used to move files from one location to another. No transformation or manipulation of the file occurs between the source and target systems. You only need to select a file Source and a file Target.
    • Transformation - this is the default operation type that is used to manipulate or change data as it passes from a source to a target system. See Data Transformation How-Tos  for steps to create different kinds of transformations.
    • Web Service Call - consists of two transformation: the first transforms data into a web service request and the second transforms data from a web service response to a target system. See Calling a Web Service for more information.
    • Hosted Web Service - consists of two transformations:  the first transformation has a web service request structure as source and the second has web service response as target. See Creating a Hosted Web Service for more information.
    • Script: is used to run a sequence of scripts without sources, targets or transformations.
  • (Optional) If you want to run another operation once this operation has successfully completed, OnSuccess select a pre-defined operation from the list, or Create New.
  • (Optional) If you want to run another operation if this operation fails to complete,  OnFailure select a pre-defined operation from the list, or Create New.
  • (Optional) To run this operation on a Schedule select an existing schedule or Create New.
  • (Optional) All other operation properties are available in the Options section. These include:
    • Log warnings and errors: check if you want to log warnings and errors generated during a transformation to a log file that can be viewed on the Error screen.
    • Run In Debug Mode: check if you want to log debug messages to files on the server. This is mostly for debugging problems during testing and should not be turned on in production. For more details, click here.
    • Do not use processed files check if you don't want to record this operation's source file transfer history.
    • Enable chunking: check if you want Jitterbit to process data to the target system in chunks. The Chunk Size tells Jitterbit how many source records to process per thread, and Max Number of Threads tells Jitterbit how many concurrent threads to process. This allows for faster processing of large data sets and is also used to address record limits that various web service based systems impose when making a request. The Source Chunk Node and Target Chunk Node enable the user to define what constitutes a transaction and should be set for hierarchical data structures and XML.
    • See Operation Options for additional information.

Validate and Save the Operation

  • After configuring the operation, you can run a quick check to validate that all components of the operation have been configured correctly:
  • Select Project Validation from the View menu. The Validation tab will appear below your operation screen.
  • If any problems are found, the Validation View will display each component where a problem was discovered. Click on any component to get more details on the nature of the problem.
  • Click the Save button in either the main toolbar or in the operation screen's toolbar. The name of your newly saved operation will appear in the Operations part of the project tree.

Related Topics:

  • No labels