Skip to end of metadata
Go to start of metadata

Design Studio Configuration

Overview

This topic includes documentation on configuring each project item that can be used to build a Design Studio project:

  • Operations
    Operations are used to define what your integration process should do and when it should be done. Operations can call one another based on conditions or events such as On Success or On Failure.
  • Transformations
    Data can be transformed between a source and target system using any of the systems and data formats that Jitterbit supports. Depending on the source and target system selected, the transformation wizard takes the user through a set of steps to define the information required to perform the transformation.
  • Sources and Targets
    source defines properties of the system that Jitterbit connects to and retrieves data from. A target defines the properties of a system that Jitterbit needs to connect to and post data to. The system properties vary depending on the type of source or target you choose.
  • Web Services
    Jitterbit lets you access SOAP web services as part of your transformation process. To call a SOAP web service using Jitterbit, you need to define web service method transformations to deal with the input and output of the web service and an operation to hold everything together.
  • Hosted HTTP Endpoints
    A Hosted HTTP Endpoint represents a URL with one or more operations associated with it. When the URL is accessed the configured operations are triggered with the request data as input (if any). The endpoint can be configured to return a target file or the contents of a data element as a response.
  • File Formats
    Jitterbit allows you to use simple or complex file types as sources or targets during the data transformation process. Simple files have the same data row type throughout the text document, while complex files contain multiple file row types such as header or summary rows.
  • Schedules
    Within Jitterbit, operations can be executed a number of ways, such as manually, automatically via an API call, or automatically via a schedule. This page covers setting up a schedule to run your operation automatically.
  • Scripting
    Scripts, written using either the Jitterbit Script Language or JavaScript, are used to manipulate data or to perform logic checks. Conditions also fall under the scripting category, providing a simple, visual way to create conditional operations (such as “If this...then that”), without needing to create a script.
  • Formula Builder
    You can enhance and refine your wizard-created data processes by using the Jitterbit Formula Builder to enter Jitterbit Scripts. The Formula Builder includes a drop-down allowing you to view the tool's interface in either Business Analyst or Developer modes.
  • Variables
    Variables are used to allow for the dynamic configuration of endpoints, to support passing of data between operations, and to drive detailed integration logic with transformation scripts. Jitterbit supports multiple types of variables with varying scope, including local, global, project, and Jitterbit variables.
  • Jitterbit Entities
    Jitterbit Entities are only used in the creation of OData Services. A Jitterbit Entity defines a database or SAP endpoint, a selection of tables, and a selection of fields that provide the data to an OData Service.
  • Salesforce Wave Analytics (Einstein Analytics)
    Salesforce Einstein Analytics is designed to provide the ability for any Salesforce end-user to analyze data and build personalized charts and dashboards. It is designed to be mobile-ready and provides a platform to build powerful analytical apps.
  • Jitterbit Connect Wizards
    Jitterbit ConnectTM is a wizard-based integration tool built directly into Jitterbit. The wizard creates all of the complex, detailed operations and components of a transformation. Two types of wizards are available: The Jitterbit Connect Salesforce Wizards and the Jitterbit Connect Standard Wizards.
  • Connectors
    Jitterbit Harmony's wizard-driven connectors allow you to create and connect with enterprise system endpoints to bring in functions and data for use in Jitterbit integrations. You can use native enterprise system query languages to retrieve information and processes.
  • Apply Plug-ins
    Plug-ins are available to act on sources, targets and web service calls and can be called from scripts using the RunPlugin method. This means you can easily add encryption, compression, and much more to files moving through the Jitterbit transformation pipeline.
Search in This Topic

 

  • No labels