Connector: HTTPS

The Manta Event System - HTTPS connector provides users with an option to route Manta Events to their own HTTP(S) servers, enabling them to implement their own integrations and custom logic based on an incoming Manta Event. Each Manta Event is sent as a payload of a POST request to a configured REST API endpoint. The user can also configure a one or two-way TLS authentication to secure the communication.

Sample Request

In the following section you can see a sample POST request containing a Manta Event in the request body in JSON format. In the example, a scenario success event, fired on a successful execution of a scenario, is sent to /event/system/rest/endpoint.

POST /event/system/rest/endpoint HTTP/1.1
Header: 
  content-length: 488
  content-type: application/json
  host: localhost:8080
  connection: Keep-Alive
  user-agent: Apache-HttpClient/4.5.13 (Java/17)
  accept-encoding: gzip,deflate

Request parameters:
Body: 
  {
    "name": "SCENARIO_SUCCESS_EVENT",
    "message": "Scenario 'Clean Repository Scenario' successfully finished its execution.",
    "timestamp": 1639662248656,
    "type": "INFORMATION",
    "priority": "HIGH",
    "publicParameters": {
      "scenario": "Clean Repository Scenario"
    },
    "source": {
      "name": "Workflow Execution",
      "sourceId": "2",
      "application": "Manta CLI",
      "workflowExecution": {
        "workflowId": "Clean Repository Scenario",
        "scenarioName": "Clean Repository Scenario",
        "technology": "MANTA",
        "phase": "Analysis",
        "connectionId": ""
      }
    }
  }

Configuration

Users can configure multiple connections to HTTPS servers with different configurations.

  1. To create a new HTTPS Event System connection, go to the Connections tab in the Admin UI, click Add Connection and select the HTTPS Events Plugin option.

    Note: You don’t need to restart the Admin UI service to apply the changes.

The configuration contains a single section with the following basic properties. 

1.  ***HTTPS Connector Enabled*** is the property that states
    whether the connector should be initialized when Manta Service
    Utility is started. **This property must, therefore, be set to**
    ***true*** **for the connector to be successfully initialized.**

2.  ***HTTPS Notification URL*** is the property containing the URL
    to which Manta Events will be sent in a POST request.

3.  ***Log Successful Notifications*** configures the logging of
    successful events—when the value is set to true, all successful
    requests will be logged with INFO severity into the Manta
    Service Utility log file.

  1. Additionally, the one or two-way TLS authentication can be configured by using the advanced configuration. The connector requires a path and password to the truststore/keystore that can be used by the client.

    A picture showing the advanced configuration options for HTTPS connector.

  2. Restart the Manta Service Utility to initialize the connector.