Update the test integration template - SDV integration
You want to test the integration before using it in production, so you're going to first update the templates to create a test integration. After testing is complete, you will update the templates to establish the production integration.
Table 2-19 SDV integration xml elements that require updates (Parent file: CTMS_SDVParentIntegration_Std.xml)
XML element | Details |
---|---|
StudyId |
Enter the Oracle Clinical One Platform study GUID. You can locate the GUID on the General tab under Study Settings. For more information, see Open the study's settings Note: If you are configuring this as a tenant-level integration, do not update this element and see, Configure a tenant-level integration. |
Mode |
If your intention is to test the integration, enter test. Note: The mode aligns with the Oracle Clinical One Platform study container. You will update this to active when you're ready to Configure the production integration. |
C1UserCredentials |
Enter the Oracle Clinical One Platform credential key name. For more information, see Create Credentials. |
C1UserName | Enter the user name for the Oracle Clinical One Platform integration user created as a prerequisite. For more information, see Source Data Verification (SDV) Integration. |
Table 2-20 SDV integration xml elements that require updates (Sub integration file: CTMS_SDVSubIntegration_Std.xml)
XML element | Details |
---|---|
StudyId |
Enter the Oracle Clinical One Platform study GUID. If you are configuring this as a tenant-level integration, do not update this element. |
Mode |
If your intention is to test the integration, enter test. Note: The mode aligns with the Oracle Clinical One Platform study container. You will update this to active when you're ready to Configure the production integration. |
C1UserCredentials | Enter the Oracle Clinical One Platform credential key name. For more information, see Create Credentials. |
C1UserName | Enter the user name for the Oracle Clinical One Platform integration user created as a prerequisite. For more information, see Source Data Verification (SDV) Integration. |
APIUserCredentials | Enter the CTMS credential key name. For more information, see Create Credentials. |
CtmsUserName |
Enter the user name for the UAT CTMS integration user created as a prerequisite. For more information, see Source Data Verification (SDV) Integration. Note: For the test integration, enter the user name created in the UAT Change Request (CR), and when the time comes, update this value to the user name created in the Production Change Request (CR). |
The next step is to Upload the integration template.
Parent topic: Update an integration template