This document is designed to provide users with answers to frequently asked questions related to database maintenance, non-prod environments and clones for CHRS.
Database Maintenance - CHRS
When CHRS database is down for an extended time (Tools, CHRS implementation, etc.), specific steps are taken to ensure minimum impact to the CS and CFS environments.
Campuses
- Communicate to campus employees/POIs about the upcoming maintenance for CHRS and encourage all employees/POIS to make any personal data updates in CHRS prior to the maintenance.
- In CS:
- Run HR Table Refresh in CS (this will allow for static data during CHRS downtime)
- Pause Automated Processes (BUSN Email Previsioning, Schedule Jobs, etc.)
- Review both Synchronous Messages to confirm NO errors
- In CFS:
- Review Asynchronous Messages to confirm NO errors
App Dev- HR/CHRS
- Send a bulletin regarding CHRS going down and being back up.
- Review both Synchronous and Asynchronous Messages to confirm NO errors in CHRS
- Open ServiceNow tickets and work directly with CO Tech Services for
- All CHRS scheduled job processes PAUSED for ALL Campuses
- To use “lock and unlock” scripts to prevent all employees/POIs from accessing CHRS during the maintenance
Yes, the CHRS Non-PRD Clone Schedule is located here.
The following would be impacted:
- Assigning instructors to classes
- Work study processing.
- Personal Data cannot be saved in CS-Admissions will not function.
- Student Center (baseline may need a modification to address this).
The following would be impacted:
- Adding / updating ChartFields: Fund, Account, Program, Project, or Class
- Journal generation of HR data from the HR_ACCTG_LINE table which published the journal ID back to CHRS
- Messages will error out and Campus IB Administrators will need to resubmit the messages when HCHRPRD IB is back up
If the CHRS database is down, then a notification will be sent to the campuses and no Asynchronous or Synchronous messages will go in or out of CHRS.
When a CS campus is down for an extended time (Tools, CHRS implementation, etc.), specific steps are taken to ensure that only the campus going through the maintenance is impacted.
Campuses
- Communicate to campus employees/POIs and share employees/POIs about the upgrade.
- Submit a ServiceNow ticket with the required 'lock and unlock' scripts for both employees and POIs. These scripts must cover both the CHRS and CS environments and be provided to the Upgrade Team
- In CS:
- Review both Synchronous Messages to confirm NO errors..
- Pause Automated Processes (BUSN Email Previsioning, Schedule Jobs, etc.).
App Dev- HR/CHRS (in CHRS)
- Review both Synchronous Messages to confirm NO errors in CHRS
- Open ServiceNow tickets and work directly with CO Tech Services to PAUSE the following three CHRS job processes during any CS downtime:
- CSU Employee Refresh
- CSU POI Status Update
- CSU WorkStudy Data Refresh
A variety of locations through CS will fail without the DB link from CS. For example
- Add/Update Person
When a CFS is down for an extended time (Tools, CHRS implementation, etc.), specific steps are taken to ensure that only the campus going through the maintenance is impacted.
Campuses
- Communicate to campus employees/POIs and share employees/POIs about the upgrade.
App Dev - CFS
- Send a bulletin regarding CFS going down and being back up.
App Dev-HR/CHRS
- Review Asynchronous Messages to confirm NO errors prior to CFS down time in CHRS.
- Resubmit all Ayshcrnonous messages if errors occur, once CFS is back in CHRS.
All CHRS DB Links will fail and all Ayshcrnonous messages will go into a queued state until they can be resubmitted. The CHRS App Dev team will be responsible for resubmitting all Ayshcrnonous messages in CHRS when able.
Non-Prod CHRS
Campuses will receive the following non-production environments:
- 1 HR 9.0 legacy environment
- 5 CS environments
Yes, CHRS will have daily clones of production, Sunday through Thursday. Campuses can learn more about the clones by visiting the CHRS Non-Production page.
Campuses have the option to designate one of their CS non-production environments to connect to a CHRS Production Support database (H*CHRPSA/H*CHRPSB). To do so, campuses must submit an annual request identifying the selected CS non-production environment. CHRS App Dev will then establish the connection from the CHRS non-production environment to the designated CS non-production database.
It is the campus’s responsibility to configure and maintain the connection from their CS non-production environment to the CHRS non-production environment.
Job Aid: Annual Connectivity Request
For requests related to Tools Testing, MP Validation, or similar scenarios, please refer to the following job aid: Requesting CHRS environment to connect to CS environment Job Aid.
For requests related to the annual connection, please refer to the following job aid: Annual Connectivity Request
No. Campuses that do not wish to provide one of their own CS masked database, they will not have integration connection with a CHRS Production Support database.
Campuses should refresh their masked Campus Solutions (CS) environment to align with the CHRS Production Support Environment selected during the ServiceNow ticket submission.
Yes, absolutely! In most cases, a database link provides sufficient access for development and testing directly within Campus Solutions (CS) without the need for full integration. However, if a campus requires full integration beyond the established connection, a ServiceNow ticket must be submitted.
Job Aid: Connect CS to CHRS (DB Link Only)
Job Aid: Requesting CHRS environment to connect to CS environment Job Aid.
Yes
No
Submit a ServiceNow ticket.
In order to adjust the TNS for the new database take the following template and exchange ??? for the campus letter.
ca???waa =
(description =
(address_list =
(address = (protocol = tcp)(host = ca???waa7.cmsdc.calstate.edu)(port = 1521))
)
(connect_data = (server = dedicated)(service_name = ca???waa))
)example: ??? -> BAK thus cabakwaa or ??? -? EB thus caebwaa
cabakwaa =
(description =
(address_list =
(address = (protocol = tcp)(host = cabakwaa7.cmsdc.calstate.edu)(port = 1521))
)
(connect_data = (server = dedicated)(service_name = cabakwaa))
)Campuses can manually configure integration in their CS non-production environments by referring to the Configure Campus Masked CS to CHRS Job Aid.
For campuses that wish to automate the process for CS databases connecting to either H*CHRPSA or H*CHRPSB, based on the annual request submitted, please ensure your script includes, at a minimum, the following:
- Activate Domain Status
- Navigation: Menu > PeopleTools > Integration Broker > Service Operations Monitor > Administration > Domain Status
- Update Service Operation URLs for CSU_SEC_USERID and CSU_PROVISION_INT
- Navigation: Menu > PeopleTools > Integration Broker > Integration Setup > Service Operation
- Tips for Updating:
- URL prefixes differ between Production and Non-Production environments (Non-Prod example: http://chr.hrdev.cmsdc/calstate.edu/)
- The database name should be H*CHRPSB or H*CHRPSB based on anual request submitted.
- Establish the DB Link
- Refresh the Crosswalk Table using the CHRS XRef Refresh process
-----------------------------------------------------------------------------------
-- Update the Rest base URL for Service Operations for Remote CHRS database
-----------------------------------------------------------------------------------
UPDATE PSOPERATION
SET IB_RESTBASE_URL = 'https://chr.hrdev.cmsdc.calstate.edu/PSIGW/RESTListeningConnector/HACHRPSB/CSU_SEC_USERID.v1/'
WHERE IB_OPERATIONNAME = 'CSU_SEC_USERID_POST';
COMMIT;
SELECT * from PSOPERATION where IB_OPERATIONNAME = 'CSU_SEC_USERID_POST';
------------------------------------------------------------------------------------
UPDATE PSOPERATION
SET IB_RESTBASE_URL = 'https://chr.hrdev.cmsdc.calstate.edu/PSIGW/RESTListeningConnector/HACHRPSB/CSU_PROVISION_INT.v1/'
WHERE IB_OPERATIONNAME = 'CSU_PROVISION_INT_POST';
COMMIT;
SELECT * from PSOPERATION where IB_OPERATIONNAME = 'CSU_PROVISION_INT_POST';
-----------------------------------------------------------------------------------
****Bounce is required****----------------------------------------------------------------------------
----CSU XREF table refresh in CS.
----------------------------------------------------------------------------
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;
----------------------------------------------------------------------------------For CS non-production databases that will not be automatically connected to H*CHRPSA or H*CHRPSB, please ensure your script includes, at a minimum, the following:
- Inactivate Service Operation URLs for CSU_SEC_USERID and CSU_PROVISION_INT
- Navigation: Menu > PeopleTools > Integration Broker > Integration Setup > Service Operation
--------------------------------------------------------------
--- Inactivating Service Operations
--------------------------------------------------------------
Update PSOPRVERDFN
SET ACTIVE_FLAG = 'I'
WHERE IB_OPERATIONNAME IN ('CSU_SEC_USERID_POST', 'CSU_PROVISION_INT_POST', 'CSU_MDH_POST', 'CSU_MDH_LOCAL');
Update PSOPRVERDFN
SET ACTIVE_FLAG = 'I'
WHERE IB_OPERATIONNAME = 'CSU_CHRS_CS_INTEGRATION_POST';
COMMIT;
****Bounce is required**** End of Article