Overview
The CHRS Production campuses agreed that, each year, a ServiceNow ticket would be submitted to request the automatic biweekly connection of a CHRS Production Support Environment to one of their own masked Campus Solutions (CS) environments.
As part of this agreement, campuses are responsible, on a biweekly basis, for the following actions:
- Ensure that the refresh of their masked Campus Solutions (CS) environment is in alignment with the designated CHRS Production Support Environment.
- Establishing a database link from their masked Campus Solutions (CS) environment to the designated CHRS Production Support Environment.
- Completing the necessary integration setup within their own masked CS environment.
CS Database Refresh Tips
When submitting the refresh request don't forget to:
- Under the Security Setting select "retain target security"
- Make a note after submission that the request is for a "bi-weekly clone recurrence"
Submit Annual Request
Step 1: Submit Optimize Case to CHRS App Dev
- Platform/Product: CHRS 9.2 (Peoplesoft)
- Business Application: Integration - IB (CHRS 9.2)
- Short Description:
- In the short description, provide the campus name and indicate this is the annual connection request (example: Channel Islands - Annual Request for CHRS Connectivity to CS Non-Production Environment)
- 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 (HACHRPSA or HACHRPSB)
- Contact for Request
- Reason for Request
- In the description provide the following:
Step 2: CHRS App Dev will perform the required steps to configure integration in the designated non-production CHRS environment and will update the case to notify the campus that they may proceed with connecting their masked CS environment on a biweekly basis during the dedicated timeframe.
Step 3: Campus Configure Campus Masked CS to CHRS
End of Article