CHRS Knowledge Base

CSU IB Monitor in CHRS

Updated on

Overview

The CSU IB Monitor is a view-only page that allows campuses to review CHRS integration configuration and Synchronous/Asynchronous transaction statuses. Campuses are not responsible for monitoring or managing integration messages; the CHRS App Dev team uses Nagios to monitor integrations hourly and creates tickets for errors requiring investigation. Once a ticket is generated and reviewed by the CHRS App Dev team, the campus contact, listed in the Production SME Contact List, will be notified of the cause and any required next steps.

Errors displayed in the Asynchronous and Synchronous sections are systemwide and may relate to any campus; they are not specific to the campus viewing the page.

Security

Campuses will have a view only role to view the information on the page. To access the page, campus users will need CHR_PT_IB_SUPPORT. 

Menu > PeopleTools > Integration Broker > CSU CHRS IB Monitor

Page Details

First image is the full view of CSU IB Monitor page. Below first image are enlarged images of each section of the IB monitor page.

screen shot of full IB Monitor page

1. IB Error Summary - Asynchronous Transactions

  • integration between CHRS and CFS uses Asynchronous messages
  • Errors generally will occur during the campuses LCD processing or if one of the systems are down
  • Rate per minute shows the number of transactions occurring for this message type within a minute
 IB Monitor page error summary fields

2. IB Error Summary - Synchronous Transactions

  • integration between CHRS and CS uses Synchronous messages
  • Rate per minute shows the number of transactions occurring for this message type within a minute
 IB Monitor page error summary fields

3. Domain Status

  • Indicates if the Application Server Path is active
 IB Monitor domain status image

4. Node Setup

  • Local Node for CHRS is required and should be active.
  • Remote Node for CFS is required in CHRS and should be active.
 IB Monitor node setup image

Remote Node for CS is no longer needed in CHRS.

5. Service Operation Setup

  • Each service operation plays a part in how the bio/demo details flow between CHRS and CS.
  • The CSU_CHRS_CS_INTEGRATION Service Operation does not have a Rest Base URL, because it relies on the campus URL located under URL Maintenance.  This is also the only Service Operation that goes to CS from CHRS.
  • CSU_PROVISION_INT and CSU_SEC_USERID are both Service Operations that have a Rest Base URL with the CHRS database name inside the link. This is also the only Service Operations that come in to CHRS from CS.
 IB Monitor service operation setup image

6. URL Maintenance

  • Each campus must have a URL present with the campus database name displayed in the link itself.
 IB Monitor url maintenance image

End of Article

Next Article (job aid) CSU Missing User Profile
To request a new article or update: Contact Us