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 Version History

Version 1 Next »

Log In to iHub Site and select Admin in the Header dropdown

ihub admin panel.png

Service Providers Menu

ihub SP menu.png

Create Service Provider

A Service Provider refers to the external system or service that your pipeline interacts with. This could be a database, an API, a cloud service, or any other external resource that your pipeline needs to communicate with to perform its tasks. The Service Provider is responsible for handling the requests and providing the necessary responses or data.

  1. Click on Service Providers Menu → Service Provider Setup

  2. Click “Create New” Button on the bottom of the right pane

  3. Type the Name of the Service Provider

  4. Click SAVE button

Create Credentials

Credentials are the authentication details required to access the Service Provider. These can include usernames, passwords, API keys, tokens, or any other form of authentication needed to establish a secure connection.

  1. Click on Service Providers Menu → Credentials

  2. Click “Create New” Button on the bottom of the right pane

  3. Type the Name of the Credentials (for the Service Provider)

  4. Select Authentication Type and Fill in details/data needed

  5. Click SAVE button

Create Endpoints

Endpoints are specific URLs or network addresses where the Service Provider can be accessed. They serve as entry points for the pipeline to interact with the external service.

HTTP endpoints are used to interact with web services over the HTTP or HTTPS protocols. These endpoints allow your pipeline to send and receive data through web requests, making them ideal for integrating with RESTful APIs, SOAP services, and other web-based services.

SQL endpoints are used to interact with SQL databases. These endpoints allow your pipeline to execute SQL queries, retrieve data, and perform database operations directly.

  1. Click on Service Providers Menu → Endpoints

  2. Click “Create New” Button on the bottom of the right pane

  3. Type the Name of the Endpoint

  4. Select Type Value (HTTP or SQL)

  5. Select Provider

  6. Type HOST (Domain for HTTP or Server endpoint for a SQL)

  7. Select Default Credentials

  8. Click SAVE button

Create Services

Services in pipelines are the specific functionalities or tasks that the pipeline performs using the Service Provider. These can include data retrieval, data processing, API calls, database queries, and more. Each service is a distinct operation that the pipeline executes as part of its workflow.

  1. Click on Service Providers Menu → Services

  2. Click “Create New” Button on the bottom of the right pane

  3. Type the Name of the Service

  4. Select Type Value (HTTP or SQL)

  5. Select Service Provider

  6. Select Direction (Inbound or Outbound)

  7. Click SAVE button

  8. “Versions” Tab will be visible

  9. Click Version tab to Create Input and Output schema

  10. Configure Task or Configure Trigger

  11. Click SAVE button

Direction

Inbound direction refers to data coming into the system.

Outbound direction refers to data going out of the system.

Schema

Input schema specifies the structure of the data that a service or system expects to receive. It defines the required fields, data types, and any validation rules that the incoming data must adhere to.

Output schema defines the structure of the data that a service or system will produce and send back as a response. It ensures that the response data is formatted correctly and contains all the necessary information.

Service (Task or Trigger)

A Task is a service that performs a specific action when it is explicitly called or scheduled. Tasks are typically used for operations that need to be executed on demand or at regular intervals.

Action-Oriented: Performs a defined action, such as data processing, file transfer, or database update.

A Trigger is a service that automatically initiates an action in response to a specific event or condition. Triggers are used to automate workflows based on real-time events.

Reactive: Responds to events in real-time, making it ideal for real-time processing and automation.

  • No labels