9.9 Updating Graph Definition

This topic describes the systematic instructions to update graph definition.

To update graph definition (run-time parameter and create the batch), follow these steps:
  1. Log in to Compliance Studio and navigate to workspace summary.
  2. On Modeling menu, click Graphs. The Graph Summary page is displayed.

    Figure 9-39 Graph Summary


    Description of Figure 9-39 follows
    Description of "Figure 9-39 Graph Summary"

    Note:

    • The derived entity nodes will be processed (new/updated) and moved to the graph schema only if the date of the graph pipeline execution (START_DATE parameter in the Run time parameters) and FIC_MIS_DATE for the derived entity are the same.
    • Whenever a node is added/deleted from graph pipeline, the population schedule needs to be re-created; so that the graph population schedule would be synchronized with the graph definition with the latest nodes and edges. This step is required to update the respective Scheduler batch-tasks definitions.
    • The Match Ruleset drop-down list will be displayed if it is a Similarity Edge. Any ruleset that is available on this drop-down list should not be edited from the Match Ruleset window.
  3. Select the FINANCIAL_CRIME_GLOBAL_GRAPH, and then click Action icon.
  4. Select Edit to view the graph.
  5. Click Schedule Details tab.

    Figure 9-40 Schedule Details


    Description of Figure 9-40 follows
    Description of "Figure 9-40 Schedule Details"

  6. To edit the schedule of the graph, click Edit under Actions column.
  7. Click Add Schedule to add a new schedule.

    Figure 9-41 Add Schedule Window


    Description of Figure 9-41 follows
    Description of "Figure 9-41 Add Schedule Window"

  8. On the Add Schedule screen, select all the tasks and click Next.
    For more information on how to select/enter the parameters, see Schedule Details section.
  9. Update the value for “$BD_SCHEMA” or “$ECM_SCHEMA”, “$GRAPH_SCHEMA” in the selected task(s) where the value will be respective schema wallet alias. For “$GRAPH_DS”, where the value will be datasource of the graph schema that is attached to the Compliance Studio workspace.

    Figure 9-42 Data Pipeline Parameter


    Description of Figure 9-42 follows
    Description of "Figure 9-42 Data Pipeline Parameter"

    Note:

    For BD graph, $BD_SCHEMA must be selected as the key value for the optional parameter. Similarly, for ECM graph, $ECM_SCHEMA must be selected as the key value for the optional parameter.
    In Load Index group,

    Figure 9-43 Load Index Parameter


    Description of Figure 9-43 follows
    Description of "Figure 9-43 Load Index Parameter"

    For the Pre-configured load index, respective Key fields will be displayed. You can configure the respective key-value in the Value field as required and specified in the following table.

    Table 9-14 Parameter for Load Index

    Name Description Default Value
    datasource Datasource of the graph schema that is attached to the Compliance Studio workspace. -
    loadType Execution Load Type. Available types are full load and delta load.

    Note: In this release, only the delta load is supported.

    		DeltaLoad
    indexName Index name for the graph.

    Note: In this release, only the delta load is supported.

    		-
  10. Enable the Refresh Graph option and click Add icon to refresh the Graph to add optional parameters.

    Figure 9-44 Refresh Graph Parameter


    Description of Figure 9-44 follows
    Description of "Figure 9-44 Refresh Graph Parameter"

    You can configure the respective key-value in the Value field as required and specified in the following table.

    Table 9-15 Parameter for Refresh Graph

    Name Description Default Value
    graphDatasource Datasource of the graph schema that is attached to the Compliance Studio workspace. -
    graphType Execution Graph Type. Available types are OFFLOADED and IN-MEMORY.
    • IN-MEMORY: It collects all the data from the nodes and edge tables and it will be transformed into the Oracle Graph Analytics Engine (PGX).
    • OFFLOADED: It creates only metadata of the executed PGQL query instead of loading the entire graph into the PGX server.

      For more information about offloaded graph type, see the Using Off loaded Subgraph section.

    		OFFLOADED
  11. Click Add. The schedule is added to respective graph. The batch will be executed based on the schedule type.
    The batch can be executed via Scheduler. For more information, see the Schedule Batch or Batch Groups section.

    Note:

    For each pipeline execution, inter and delta tables would be created. When the pipeline is executed for the second time, the tables from the first execution should be deleted which is not currently happening. However, the cleanup happens for the second execution on the next day.

    For example,

    Cleanup does not work for the first run on 1st- Aug and the second run on 1st Aug.

    Cleanup works only when the first run is on 1st- Aug and the second run on 2ndAug.