Customer MDM Search Process API
Support
GitLab: [pharma-cmg-cust-search-proc]
SLA Tiers
Note: the build status is only available on the Roche Corporate Network.
Name | Limit |
---|---|
GOLD | 1000 Requests per Minute |
Roche Generic Account and Cloud Certificate
This is the time to create your Roche Generic Account and generate your Roche Cloud Certificate for API authentication purpose. Please follow the 2 steps below:
- Create your [Roche generic account (link to the process)][5]
- Generate a cloud certificate from your generic account, please follow the instructions [from this article (link to the process)][6]
Please note that we are asking for 2 different generic accounts and certificates: one for NON-PROD environments (DEV, TEST, STAGE) and one for PROD environments (PROD). If you already have generic accounts and certificates from previous projects, you can reuse them (as far as you have 2 different ones: one for NON-PROD and one for PROD).
Additional note: we are asking to start this process before submitting your request in Anypoint Exchange as this is a separated process driven by identity management. This request can take some time, starting it early emough can help speeding up the process.
How do I connect to Test?
Endpoints URLs:
- https://prod-de-c1.apis.roche.com/pharma-cmg-cstmdm-srch-proc/v1/
- https://stage-de-c1.apis.roche.com/pharma-cmg-cstmdm-srch-proc-stage/v1/
- https://test-de-c1.apis.roche.com/pharma-cmg-cstmdm-srch-proc-test/v1/
- https://dev-de-c1.apis.roche.com/pharma-cmg-cstmdm-srch-proc-dev/v1/
Note: only v1 is available so far. Take [version] as v1.
When making a request the client id and client secret must be provided as part of basic authentication & in the header parameters:
- client_id
- client_secret
The Client SSL certificate must also be provided.
All our API's are secured with 2 factor authentication (SSL + Client id, secret enforcement).
- Any consuming system would need a "Client Authentication Certificate" to access the Mulesoft API. This can be obtained in two ways
Option 1: Consuming systems can get their own certificate and it must be signed by a well known CA. Self-signed certificates are not allowed.
Option 2: Roche side product owner can request internal certificate by following the instructions listed below
Once the certificate is obtained, Mulesoft team will whitelist the serial number of this certificate on Mulesoft.
Typically for each project, request 2 certificates (each certificate will require its own generic ID) - one for calling non-prod APIs and one for production APIs.
- Client ID, Secret
Roche side product owner will work with the Mulesoft team to have dedicated credentials generated for Consuming System (Ex: RoME).
This step will be done once we start the Mulesoft development.
How do I report bugs or production incidents?
Incidents can be raised through ServiceNow end user portal:
Prod: https://roche.service-now.com/service_portal?id=sc_cat_item&sys_id=6547856adbaf845cbd13f687f496194f
Non-Prod: https://roche.service-now.com/service_portal?id=sc_cat_item&sys_id=df701d6adb27c45cbd13f687f49619e9
You can also do it via the ServiceNow backend portal and assign the incident to GIS operations service and group:
- Service: GIS API Delivery Service
- Assignment group: GIS MuleSoft Support Team
Please find the steps to complete this here: https://rochewiki.roche.com/confluence/display/APIGOV/How+to+create+an+Incident
How do I request for more information?
A request should be raised in Service Now for any technical information or for change/update deployment configuration. These requests are sent to the MuleSoft support team.
Please find the steps to complete this here: https://rochewiki.roche.com/confluence/display/APIGOV/How+to+Create+a+Request
How do I request for new features?
New API project feature(s) or API project change request (not deployment related) should be raised by creating a new demand. This demand will be sent to GIS ICC where engagement will begin.
Please find the steps to complete this here: https://sites.google.com/roche.com/gis-icc/contact-us
Contacts
Role | Name | Role Description | Contact |
---|---|---|---|
API Owner | Yash Agarwal | The API Owner is the primary person who is responsible for prioritizing the feature backlog as well as determining if approval can be granted to any new consumer. The API Owner is accountable for the SLAs, Exchange content detail and accuracy of their API in Mulesoft Exchange. API Owner also is the one who can onboard consumers. | yash.agarwal@businesspartner.roche.com |
API Architect | Brahmanand Prusty | API Architect is the primary person responsible for the API’s Architecture and Design. Other Solution Architects and Solution Engineers who are looking forward to reusing this asset may reach out to API Architect address any technical questions they have in case the documentation of each of the end points published in exchange via RAML is not self explanatory. | brahmanand.prusty@contractors.roche.com |