Execute the scheduled jobs

  • Release version: Washingtondc
  • Updated April 2, 2025
  • 3 minutes to read

    • Execute the scheduled jobs required for the main node relationships. After the scheduled jobs are executed, CSDM objects with their configured relationships are imported into Operational Resilience for reporting.

    Before you begin

    Role required: sn_oper_res.manager

    Before executing the scheduled job, ensure that the following pre-requisites are met.
    1. Before adding any relationships to the records, make sure that the Opres with CSDM header configuration is included in the Main node configuration.
    2. Records for business services, business processes, service offerings, and application services, including all the relationships, have been created in the Main node configurations.
    3. Entity types and pillars have been defined and entities have been generated.
    4. Configuration item (CI) relationships have been created as required for the Main node configuration relationships.
    Once all these pre-requisites are met, you can execute the scheduled job.

    About this task

    Note:

    The Update CSDM and other dependencies, Update other dependencies, and Calculate red flags for CSDM and dependencies scheduled jobs create an entity hierarchy and all types of red flags. All CSDM and red flags are rolled up based on their entity hierarchy.

    The scheduled jobs are configured to run according to the following schedule:
    1. The Update CSDM and other dependencies scheduled job updates CSDM and other dependencies. It is configured to run weekly on Saturdays at midnight local time.
    2. The Calculate red flags for CSDM and dependencies scheduled job calculates the red flags for the CSDM and its dependencies. It is configured to run daily at 3:00 AM local time.
    3. The Update other dependencies scheduled job updates additional dependencies. It is configured to run on demand.

    Operational Resilience administrators can perform all the functions as the Operational Resilience managers. The Operational Resilience users cannot execute the scheduled job but they can verify the records in the entity and entity hierarchy tables.

    Before running the scheduled job, verify that the relationships are set up for an object as shown in the following example.

    CSDM objects.

    Procedure

    1. Navigate to All > system definition > Scheduled Jobs.
    2. Choose the Update CSDM and other dependencies scheduled job.
      The illustration shows the steps executed in the script of the scheduled job.
      1. When the script is run, it cleans all the records in the staging tables. Staging tables are used in Operational Resilience to save the red flags, which are displayed on the dashboard.
      2. Next, it updates the CSDM dependencies by calling the relationship API (Opres with CSDM header Main node configuration).
      3. As the final step, it runs the events for the dependencies in parallel: one for the business service, another for the service offering, and another for the business process dependencies. These events run in parallel to ensure that the scheduled job completes quickly and loads the data efficiently.
      Scheduled job.
    3. Select Execute Now.
      • When the Compute Operational Resilience Compliance scheduled job is executed, the scheduler fetches the Opres with CSDM header Main node configuration.
      • The Opres with CSDM header Main node configuration maintains the following relationship configurations (shows the objects and table names):
        • BS (cmdb_ci_service_business) -> SO (service_offering)
        • SO (service_offering) -> BP (cmdb_ci_business_process)
        • SO (service_offering) -> SO (service_offering)
        • BP (cmdb_ci_business_process)-> AS (cmdb_ci_service_auto)
        • SO (service_offering) -> AS (cmdb_ci_service_auto)
        • BP (cmdb_ci_business_process) -> BP (cmdb_ci_business_process)
        • AS (cmdb_ci_service_auto) -> AS (cmdb_ci_service_auto)
      • Once the scheduled job for Opres with CSDM header has been executed, the hierarchies for the data are created according to the configured relationships.

      The scheduled job creates an entity hierarchy record [sn_grc_m2m_profile_profile] for the existing entities. These entity hierarchy records include upstream and downstream relationships from Business Service (BS), Service Offering (SO), Business Process (BP), and Application Service (AS) records.

      After the scheduled job is executed, all CMDB objects are fetched into Operational Resilience. The following example shows the same business service record with its fetched relationships after running the scheduled job.

      Relationships after running the scheduled job.

      The sample configuration setup illustrated earlier in this section shows that business process BP1 has two dependencies: Acer and PS Apache01.

      Service offering SO1 is the parent table of business process BP1. The dependencies of BP1 are rolled up to the parent table, SO1, as shown in the example.

      Dependencies for SO.

      These dependencies are also rolled up to their parent table, BS1, as shown in the example.

      Dep-after-job.AS-after-job.
    4. Verify that the Main node configuration, node relationship configuration, and node configuration results are displayed correctly.
    5. Verify that staging records are created according to entity hierarchies after running the scheduled job.
      Depending on the installed applications, the staging tables are created in Operational Resilience. For example, when the scheduled job is run, the following staging tables are created.
      • sn_oper_res_failed_control
      • sn_oper_res_risk
      • sn_oper_res_bcm_plan
      • sn_oper_res_vul_profile
      • sn_oper_res_third_party_risk
      • sn_oper_res_task
      • sn_oper_res_change_request
      • sn_oper_res_critical_service_outage
      • sn_oper_res_incident
      • sn_oper_res_issue

      The business views are mapped into the entity hierarchy. Red flags for the entities, such as Failed controls, High risks, Issues, Vulnerability response, are displayed in the reports on the landing page. For more information, see Business services overview tab.