Progress OpenEdge

1. Create a service account in OpenEdge with the appropriate permissions for Validio. See Prerequisites.
2. Create a Validio credential to connect to the OpenEdge account. See Add a Progress OpenEdge Credential.
3. Create a Validio source to monitor the tables in the OpenEdge database. See Add a Progress OpenEdge Source.

​

Prerequisites

• Permission to connect to the OpenEdge database.
• SELECT access on each table and view you want Validio to monitor. OpenEdge has no schema-wide or “all tables” SELECT grant, so every table and view must be granted individually.

/*--------------------------------------- Parameters used in this script -------------------------------------------------
Search/replace all instances of these parameters in the script with names of your choice.

validio_user                                      -- Name of the Validio user. Using a new, dedicated user is recommended.
<Some_Password123>                                -- Password for the Validio user.
<schema_to_monitor> [, <schema2_to_monitor>...]   -- Optionally filter access to one or more schemas (owners).

*/------------------------------------------------ Script -----------------------------------------------------

-- A DBA user (e.g. the account used to administer the database) is required to run this setup.

-- Create the Validio user. (Creating the first SQL user also switches the
-- database into enforced-authentication mode.)
CREATE USER 'validio_user', '<Some_Password123>';
COMMIT;

-- No system-table grants are required: OpenEdge exposes the SQL catalog
-- (SYSPROGRESS.*) to all users, which covers Validio's schema/table/view and
-- lineage discovery.

-- Grant read access to the data to validate. OpenEdge has no schema-wide or
-- "all tables" SELECT grant, so each table and view is granted individually.
-- Rather than write them by hand, run the query below to GENERATE the grant
-- statements for every table and view (optionally filtered to specific
-- schemas). Then review the generated statements and run them.
--
-- NOTE: OpenEdge has no "default privileges" mechanism, so these grants apply
-- only to tables and views that exist now. When new tables or views are added
-- that Validio should monitor, re-run this generator and apply the new grants.
SELECT ('GRANT SELECT ON "' || OWNER || '"."' || TBL || '" TO validio_user;') AS stmt
FROM SYSPROGRESS.SYSTABLES
WHERE TBLTYPE IN ('T', 'V')           -- tables and views
  AND OWNER NOT IN ('SYSPROGRESS')    -- exclude the system catalog
--  AND OWNER IN ('<schema_to_monitor>' [, '<schema2_to_monitor>'...])  -- Uncomment to limit to specific schemas
ORDER BY OWNER, TBL;

​

Add a Progress OpenEdge credential

1. Navigate to Credentials and click + New credential.
2. Under Namespace, select a namespace where the resources will be created.
3. For Credential Type, select Progress OpenEdge.
4. Fill in the credential parameter fields. Refer to the Progress OpenEdge Credential Parameters table.
5. (Optional) Click Test credential to validate the connection to the OpenEdge account. If validation fails, check that you provided the correct parameter values and try again.
6. (Optional) Check Use for catalog and schema checks to automatically discover assets and add them to the catalog page.
7. Click Create credential.

​

Progress OpenEdge credential parameters

​

Add a Progress OpenEdge source

1. Navigate to Sources and click + New source.
2. Under Source type, select Progress OpenEdge.
3. Under Config,
   1. Select the valid Credential or create a new credential to authenticate your connection to the database.
   2. You have two options for specifying the dataset and tables to monitor:
      1. Select an existing table — Enter the Schema and Table to specify where the data comes from. Selecting more than one table will create a new source for each table. Refer to the Source Configuration Parameters table.
      2. Use Custom SQL — Write a valid SQL query to specify the data to monitor. See Custom SQL Sources.
   3. Set the Polling schedule, which is how frequently the validators on the source will check for changes.
4. Under Schema, click Continue to automatically infer the schema fields from the tables you selected. If you select many tables, this operation can take a few minutes to complete.
5. Under Source details,
   1. Add Tags to help group related sources or to use for routing notifications.
   2. Add an Owner who will be the contact for incident notifications.
   3. Assign a Priority, which indicates the importance of incidents detected on this source.
6. Click Continue to create the source. Source names are generated automatically and will be displayed when the source creation completes. If there are more than 5 sources, you will see the names for the first five and a count of the remaining sources.

​

Progress OpenEdge source configuration parameters