This article provides guidance for production campuses on the steps to follow when requesting a non-production CHRS environment connection to their own masked Campus Solutions environment.
Overview
Databases are not provided to campuses for testing scenarios that require full integration between CS and CHRS, such as Tools Testing, MP Validation, etc. Campuses must supply their own masked CS database to connect to a CHRS non-production environment.
Before submitting the request, campuses are responsible for:
- Ensuring that the refresh of their masked Campus Solutions (CS) environment aligns with the designated CHRS environment.
Once given the green light, campuses must:
- Establish a database link from their masked CS environment to the designated CHRS environment.
- Complete the required integration setup within their own masked CS environment.
Submit Request
Step 1: Submit a ServiceNow ticket:
- Type: Request
- Category: CMS-CHRS
- Subcategory: Integration
-
Ticket Short Description:
- In the ticket short description, indicate that your campus needs to have CHRS connected to your own masked CS environment (example: Request for HACHRPSA to Connect to CAFULTST-Fullerton)
-
Description:
- In the description provide the following:
- CS Database Name
- CS Database Clone Date
- CS URL ( Under CSU_CHRS_CS_INTEGRATION_POST)
- CHRS Database Name
- Reason for Request
- In the description provide the following:
The CS environment to be connected must be masked.
Step 2: CMS will complete the necessary steps to configure integration in the requested non-production CHRS environment, and update ServiceNow ticket that campus can proceed to connect their own masked CS environment.
Configure Campus Masked CS Environment
NOTE: The following steps must be completed by the campus in their own CS environment!
Step 1: Navigate to the Domain Status
- Navigation: Menu > PeopleTools > Integration Broker > Service Operations Monitor > Administration > Domain Status
Step 2: Confirm the Domain Status is active
Step 3: Navigate to the Service Operations page
- Navigation: Menu > PeopleTools > Integration Broker > Integration Setup > Service Operations > General page
Step 4: Confirm that the following Service Operations are active, have the correct URL prefixes, and reference the appropriate CHRS database in the URL.
- CSU_SEC_USERID
- CSU_PROVISION_INT
Use the CSU IB Monitor in CHRS to verify the correct URL prefixes required for the Service Operations (e.g., http://chr.hrdev.cmsdc/calstate.edu/)
Step 5: Confirm that this Service Operations is active.
CSU_CHRS_CS_INTEGRATION_POST
Step 4: Confirm the following Service Operations are inactive as they are related to PDM functionality in CS
- CSU_MDH_POST
- CSU_MDH_Local
Step 7: Create DB link from CS to CHRS
exec
system.csu_dblinks.build_hrxcs('hachr***');Before executing, confirm the target database name.
Step 8: Recreate the Crosswalk table using SQL
DELETE FROM PS_CSU_CHRS_XREF;
INSERT INTO PS_CSU_CHRS_XREF(CSU_CHRS_ID, CSU_CS_ID)
SELECT CSU_CHRS_ID, CSU_CS_ID
FROM PS_CSU_EMPL_MAP_VW@CSU_CS_HR_LINK A , PS_INSTALLATION B
WHERE (B.COMPANY = 'XXX' AND A.BUSINESS_UNIT = 'XXXXX');
COMMIT;Before you execute, update the XXXXX. The campus codes can be located in the CHRS Library.
Step 9: Complete Campus Integration Validation Checklist (Without CMS) to confirm integration is setup correctly between CS and CHRS.
End of Article
0 Comments
Add your comment