Managing engines (Continuous Data)
Infrastructure
DCT provides a near real-time list of all connected Continuous Data engines and lists them in an aggregate view. From the below screen, Delphix administrators can easily view and manage their engine connections.
Administrators can manage engine connects via the “Connect Engine” button on the top right corner. By clicking this button, the below dialogue will appear, asking for connection details.
DCT will access the engine as a registered user and, as detailed in the Deployment section, requires both a username and password as well as admin-level access to the engine.
An option is available to configure DCT so that it automatically creates predefined tags on discovered objects ingested from the engine. This can be done in the Tags step of the Connect Engine wizard. Checking the box will make VDBs, dSources, and vCDBs automatically get tagged with the name of their Dataset Group on the engine.
Auto-tagging can modify object access. Review permissions carefully after auto-tagging objects.
All existing and new objects from then on will automatically get the predefined tags, which are no different from ordinary tags that can be added to objects. The auto-tagging configuration can later be updated in the Data Engine Details page by going to the Action menu and selecting Auto-tagging Configuration. This will open up a window with a checkbox to enable or disable auto-tagging.
Disabling auto-tagging will not remove any of the tags that were previously added. Instead, new ingested objects will not have tags automatically applied. In order to delete these tags, this must first be disabled and the tags will need to be deleted manually on all affected objects.
Finally, since auto-tagging can have an impact on access control, non-admins will require special permissions to configure auto-tagging.
To configure auto-tagging when registering an engine for the first time, the Account must have a role with the Configure Predefined Auto Tagging At Registration permission.
To update the auto-tagging configuration on a pre-registered engine, the Account must have the Configure Predefined Auto Tagging on the ENGINE object they wish to update.
Engine overview
Individual engine details can be seen and acted upon by clicking down on a particular engine detailed view. Once clicked, users will be sent to an "Overview" tab that provides relevant metadata related to the engine. From the Actions menu, you can also Deregister an engine.
Deregistering or deleting an engine can also be done via the API with: curl --location --request DELETE '<https://<DCT Host Name>:<Port>/v3/management/engines/<ID or Name of the Engine to be deleted>' \--header 'Authorization: apk <api key for authentication>'
Engine-connected environments
The "Environments" tab presents all environment connections to that particular engine.
Local dSources
The "dSources" tab presents all dSources associated with the selected engine. Clicking the "View" button will link the user directly to the associated dSource page.
Local VDBs
The "VDBs" tab presents all VDBs associated with the selected engine. Clicking the "View" button will link the user directly to the associated VDB page to take action.
Engine-based Operations access
Users are able to audit which users have access to this particular engine, what access group they belong to, and the associated permissions that each user has on this engine. Admins are able to click on the "View" button to access further details under the access control screen related to that specific user.
