CHRS Knowledge Base

Configure Campus Masked CS to CHRS

Updated on

This article provides guidance for CHRS production campuses on the steps to follow when configuring their Campus Solutions environment connection a CHRS environment.

Overview

If you're setting up a campus-owned masked CS environment, ensure that you've submitted either a temporary or annual request. Please note that databases are not provided to campuses for testing scenarios requiring full integration between CS and CHRS (e.g., Tools Testing, MP Validation). In such cases, campuses must supply their own masked CS database to connect to a CHRS non-production 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

example domain status

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/)

example of CS database page first half of page
example of CS database page second half of page

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

If you're verifying the integration setup of your production Campus Solutions (CS) environment, these Service Operations should be active.

Step 7: Establish and verify the database link from Campus Solutions (CS) to CHRS.

exec
system.csu_dblinks.build_hrxcs('hachr***');
Click to copy

Before executing, confirm the target database name.

Step 8: Refresh the Crosswalk table using the CHRS XRef Refresh process

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Previous Article (job aid) Annual Connectivity Request (CS/CHRS)
Next Article (job aid) Request a CHRS environment connection to a CFS database
Do you need an article? Contact Us