Package org.odpi.openmetadata.adapters.connectors.babbage

Class BabbageAnalyticalEngineService

java.lang.Object
org.odpi.openmetadata.frameworks.connectors.Connector
org.odpi.openmetadata.frameworks.connectors.ConnectorBase
org.odpi.openmetadata.frameworks.integration.connectors.IntegrationConnectorBase
org.odpi.openmetadata.adapters.connectors.babbage.BabbageAnalyticalEngineService
All Implemented Interfaces:
AuditLoggingComponent, SecureConnectorExtension, VirtualConnectorExtension, IntegrationConnector
public class BabbageAnalyticalEngineService extends IntegrationConnectorBase
The Babbage Analytical Engine Service is an integration service that ensures that the governance action types attached as catalog targets are regularly invoked to gather and record insight, or, if they are supposed to be long-running, they are still.

  • Constructor Details

    • BabbageAnalyticalEngineService

      public BabbageAnalyticalEngineService()

  • Method Details

    • start

      public void start() throws ConnectorCheckedException, UserNotAuthorizedException
      Indicates that the watchdog action service is completely configured and can begin processing. This is a standard method from the Open Connector Framework (OCF), so be sure to call super.start() at the start of your overriding version.
      Specified by:
      start in interface IntegrationConnector
      Overrides:
      start in class IntegrationConnectorBase
      Throws:
      ConnectorCheckedException - a problem within the watchdog action service.
      UserNotAuthorizedException - the connector was disconnected before/during start

    • refresh

      public void refresh() throws ConnectorCheckedException, UserNotAuthorizedException
      Requests that the connector does a comparison of the metadata in the third party technology and open metadata repositories. Refresh is called when the integration connector first starts and then at intervals defined in the connector's configuration as well as any external REST API calls to explicitly refresh the connector.
      Throws:
      ConnectorCheckedException - a problem with the connector. It is not able to refresh the metadata.
      UserNotAuthorizedException - the connector has been disconnected

    • disconnect

      public void disconnect() throws ConnectorCheckedException
      Disconnect is called either because this governance action service called governanceContext.recordCompletionStatus() or the administrator requested this watchdog action service stop running, or the hosting server is shutting down. If disconnect completes before this watchdog action service records its completion status, then the watchdog action service is restarted either at the administrator's request or the next time the server starts. If you do not want this governance action service restarted, be sure to record the completion status in the engine action.

      The disconnect() method is a standard method from the Open Connector Framework (OCF). If you need to override this method, be sure to call super.disconnect() in your version.

      Specified by:
      disconnect in interface IntegrationConnector
      Overrides:
      disconnect in class IntegrationConnectorBase
      Throws:
      ConnectorCheckedException - a problem within the watchdog action service.