TIBCO Scribe® Architecture

TIBCO Scribe® is a cloud-based integration capability that customers and partners use to build data integrations between any combination of cloud-based and on-premise applications.

TIBCO Scribe® provides a core integration engine and an extensible set of Connectors. Connectors move data between specific applications and data formats.

Connectors insulate the TIBCO Scribe® integration engine from the details of any specific technology that is involved. Connectors extend the integration engine to provide a common user experience to end-users. This helps end-users focus on building the business processes required for a particular integration, rather than the details of specific technologies.

Application Architecture

The following illustration shows the interaction between the components of a typical TIBCO Scribe® deployment. The TIBCO Scribe® SDK provides a means for developers to create custom Connectors that join third-party applications through a TIBCO Scribe® deployment.

Users create integrations through the REST API. Agents then receive commands for those integration processes through the REST API. Data processing occurs between Connectors using an Agent. Agents can be provisioned in the TIBCO Scribe® Cloud, or installed on-premise.

TIBCO Scribe® Key Concepts

You should understand the TIBCO Scribe® concepts described below before developing your own Connector.

TIBCO Scribe®

TIBCO Scribe® provides data integration capability to the user in the form of Solutions. Each Solution solves a data integration problem, such as data replication or data synchronization. Users can configure any number of Solutions. Connectors, built by TIBCO Scribe® or other parties, can become part of the solution to solve a problem.

TIBCO Scribe® Integration Services (IS)

TIBCO Scribe® Integration Services Solutions (IS) integrate data between various online and on-premise datastores. IS Solutions use Integration Maps to map entities, transform field values, and support target operations like create and update. These capabilities are all defined by the Connector. Solutions are triggered to execute On Demand, at a scheduled time, or by using the TIBCO Scribe® Web API.

Event Solutions provide a unique URL per Map to accommodate receiving message payloads, for example a Webhook. Within an Event Solution, you can implement one of the following processing methods: 

  • Synchronous — Processing completes before a response is provided. The design of the Map dictates the content of the reply and where in the process it is sent.
  • Asynchronous — Processing is initiated and only a simple response is provided regardless of the Map's processing status.

Synchronous Event Maps are referred to as Request/Reply Maps since the system calling is looking for a reply with data or processing status. This type of Solution is created within the TIBCO Scribe® and does not require a Connector. End users can configure the Map, determine the payload expected, and provide a response.

Asynchronous Event Maps are referred to as Message Maps. They are implemented using either the FCF or CDK. Message Maps use a built in message queue which is part of TIBCO Scribe®.

TIBCO Scribe® Replication Services (RS)

TIBCO Scribe® Replication Services (RS) provide basic data replication at an API level. Unlike typical database replication, this addresses keeping a copy in sync at the business object or API level. One common use case involves providing customers a way to create a repository for reporting or other data analytics. You can use TIBCO Scribe® RS to easily maintain a copy of your source data in a proprietary format, such as Microsoft Dynamics 365 or Salesforce.com, in another datastore, such as a Microsoft SQL Server or MySQL Server database.


TIBCO Scribe® Agents facilitate communication between the datastores used by a Solution. The Agent provides secure communications to TIBCO Scribe® without opening security holes in your corporate firewall. The Agent communicates with your source and target systems as well as with TIBCO Scribe® in the cloud.

Agent communication with the TIBCO Scribe® Cloud is used to install new connectors, relay the status of a Solution execution, or pick up new instructions, connection settings, Maps, or Solutions. A security configuration option tells the Agent whether or not to store source record data locally preventing the data from leaving the local environment.

TIBCO Scribe® supports both On-Premise and Cloud Agents.


A Connection is the set of login credentials and other parameters needed by a Connector to access an API or datastore. Each Connection contains a separate configuration, for example to provide access to separate SQL Server databases or separate Salesforce instances, such as Sandbox vs. Production.

Connections are required for Fast Connector Messaging Framework Connectors, however, since TIBCO Scribe® is “listening” for a message, credentials are not required. Each Connection configuration has a Label field is provided during the creation of the Connector that is used to identify actions by that Connector in the log. Security is governed by IP Address rules and a unique key in the Endpoint URI. Other security measures can be implemented inside the mapping.


TIBCO Scribe® expects to receive datetime information in UTC from the Connector. TIBCO Scribe® always returns datetime information in UTC. If for any reason your Connector does not use UTC due to a limitation of the API you are using, you may have unexpected results particularly when using datetime as a filter. Be sure to thoroughly document the datetime conventions used.


Each tenant in the TIBCO Scribe® cloud service is called an Organization. An Organization represents the company or entity using the service, and there are three types:

  1. A standard Organization stands alone and represents a single company that buys the TIBCO Scribe® service directly from TIBCO or through a reseller.
  2. A parent Organization belongs to a company that purchases the TIBCO Scribe® iPaaS on a wholesale or OEM basis with the ability to create and manage child Organizations for its customers.
  3. A child Organization falls under a specific parent Organization and represents a company that is a customer of the owner of the parent Organization.

License Considerations

TIBCO Scribe® has different licensing options based either on the number of Connections or the number of customers. Contact TIBCO Sales for more information on the options.


TIBCO Scribe® SDK Overview

Fast Connector Framework (FCF)

Connector Development Kit (CDK)