Provisioning The Advanced Provisioning, Configuration, And Simple Monitoring 401 Reference Application
The Advanced Provisioning, Configuration, And Simple Monitoring 401 Reference Application demonstrates how to provision a TIBCO Scribe® Account and all of its required elements using the Web API.
Organization — Each TIBCO Scribe® account is represented by an Organization. The Organization is the container for everything associated with a customer. Organizations can contain child Organizations for further partitioning in an environment where you are managing multiple customers. Before a Solution can be implemented a new Organization needs to be created. Typically, a Parent Organization is setup, and then each customer is added as a child to that parent. The sample shown in the Reference Application shows this case.
Agent — Integration processes are handled by Windows Services called Agents. Agents are standalone and carry out the integration instructions contained in a Solution. They can either be hosted by TIBCO Scribe®, Cloud Agent, or installed on a customer’s server, On-Premise Agent. The Reference Application demonstrates the process of provisioning a Cloud Agent for the new child Organization.
Connectors — TIBCO Scribe® has Connectors for many common business systems, generic technologies, and databases. Install one or more Connectors to communicate with specific business applications or a database. Custom Connectors can be created using our SDK.
Connections — A Connection is the stored configuration of the parameters required by the Connector to access the datastore for a specific application, such as an endpoint and user credentials. In this simple example on the Provision tab, we provide sample Connectors that do not require any configuration for ease of use. Other Connection samples included in the Reference Application code are commented out, but show different implementations, for example Oauth.
Solutions — Solutions contain one or more Maps with integration instructions. Solutions can be cloned making it easier to implement a common design. In the Reference Application, Solution Templates are available and can be cloned, to demonstrate the cloning process. Cloning copies the template and retrieves metadata via the Connectors. Once a Solution Template is copied, it can be modified to customize it for a specific customer. An example of field mapping customization is shown on the following tabs:
- Configure — Update the field mappings on the cloned Solution and customize it for the specific customer. Included are steps to validate and implement the changes.
- Runtime/Monitor — Start and monitor the Solution execution.