Data Packager

Service Request v2 is one of infrastructure microservices which helps to create and manage the service requests using the API interface.

It also captures the status of each service request from creation to closure. So, after installation of SRMS2.0 wired with fulfilment system, it’s important to validate whether the created service request reaches fulfilment system and updates the service request with appropriate status. To achieve this, SRMS2.0 provides data packager as an out of the box solution.

SRMS2.0 data packages are similar to all the microservices in terms of packaging structure, adhering to naming standards for all data records, grouping data records based on service request type, provide correct guideline for data package deployment and simplify the data package deployment steps.

Data packages are available for consumption in zip format as shown in the screenshot below:

Above two zip files must be deployed one by one. First demo-bootstrap should be deployed and then followed by demo-data.

ms-servicerequestv2-demo-bootstrap.zip

In ms-servicerequestv2-demo-bootstrap.zip, the following elements are available.

• Configurations required for the deployment of data records present in demo-data.zip.
• API endpoints associated with each data record. (In E2E wired environment, service request configurations must be deployed in SRMS2.0, Python scripts must be deployed in GCMS, Adapter templates must be deployed in Adapter MS. So to deploy all the demo data records in their respective microservices, API end points are mandatory.)
• Http methods (POST/PUT/GET/DELETE) are required for deploying each data records deployment
• Component name of each demo data records. For example, servicerequest or adapter or genericconfig.
• Type of each demo data records. For example, schema or adapters or templates or python-extension.

ms-servicerequestv2-demo-data.zip

In ms-servicerequestv2-demo-data.zip, the following elements are available.

• Demo data records deployment sequence definition. (Demo-data.zip may contain multiple data records but can be deployed in controlled sequential order)
• Demo data records of orderChequebook service request type (containing service request configurations, adapter templates and python scripts)
• Demo data records are grouped based on service request type for making deployment job easy. It helps to deploy demo data records selectively.

When this zip file is deployed,

• New ‘orderChequebook’ service request type is created along with the virtual table named as servicerequest.orderChequebook and the same configurations are stored in GCMS tables (config store).
• Adapter templates are created in Adapter MS and the same configurations are stored in GCMS tables (config store). Adapter templates support transformation and routing of service requests from SRMS2.0 to Transact and vice versa.
• Python Scripts are deployed in GCMS. It helps to perform validations and to provide lookup values.

Refer Deploying Data Package to know more about deploying the data packages and the data records present inside the packages using existing temenos data packager technology solution.