This article outlines the procedures that production campuses should follow to complete the Annual CHRS Connectivity Request for the CHRS Production Support Environment to connect to a campus own masked Campus Solutions (CS) environment.
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.
The annual request must be submitted no later than July 1st each year.
Submit Annual Request
Step 1: Submit a ServiceNow ticket:
- Type: Request
- Category: CMS-CHRS
- Subcategory: Integration
-
Ticket Short Description:
- In the ticket 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:
The CS environment to be connected must be masked.
Step 2: CMS will perform the required steps to configure integration in the designated non-production CHRS environment and will update the ServiceNow ticket to notify the campus that they may proceed with connecting their masked CS environment on a biweekly basis during the dedicated timeframe.
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 6: 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