Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Technical onboarding

Integration Testing Plan

Features that can be used

Level of Assurance - RDIMS 19532524

Statement of Sensitivity - RDIMS 19532575

This guide will help your team integrate Cost Recovery Service Management (CRSM) requirements into your Workload Management (WLM) platform. There are checklists to make sure required data points are captured, as well as descriptions of the various features and UI components that are available for you to use.

Prerequisite: - Following information needs to be obtained through MTOA and CRSM before onboarding CRSM through WLM.

(1) Service Id

Service ID created by MTOA for LoB

(2) Attribute Id

Attributed Id created by MTOA for LoB service. Please note AttributeId is NOT the same as service attributesID.

(3) API Key and JWT token to access MTAPI

API Key and JWT token created by MTOA for LoB

(4) Service Standard

Service Standard created by CRSM for LoB

(5) Service Attributes

Service Attributes created by CRSM for LoB

After obtaining the information above, LoB can use the following sample demo portal project to start the development to onboard with WLM and integrate with CRSM: WLM Demo Portal Repos

LoB just need to send following piece of information in details of Workload Manage, and remaining communication between CRSM will be auto handled by WLM.

RequestTypeId, ServiceId, AttributeId

For Example:
{"RequestTypeId":"022","ServiceId":"9999","AttributeId":-1}

The following diagram illustrates how those independent systems work together internally.

Existing Reference Architecture

Please see attached CRSM Integration Doc for details. As always, please feel free to contact with MOLE team for further help needed.

  • No labels