A REN (Remote Event Notification) server is used in PeopleSoft primarily for nVision on the web transactions. It also may be used for the optimization engine and that other new crap that PeopleSoft is now pushing. I don't really know a whole lot about.

PSRENSRV runs on the application server.

• Edit the psappsrv.cfg file:

[PSRENSRV]
;=========================================================================
; Event notification server settings
;=========================================================================
; REN Server log trace level.  Use Error, Warning, Notice, or Debug.
log_severity_level=Warning

; REN Server buffer size for HTTP output.  Must not exceed 65536.
io_buffer_size=8192

; REN Servers place these values in the database when creating
; out-of-the-box initialization parameters.
; If commented out, the values "7180" and "peoplesoft.com" are used.
default_http_port=7180
default_auth_token=nextel.com

• Make sure that default_http_port is set to something unused.
• Using 'psadmin', reconfigure the application server to actually start PSRENSRV.
• Start the Application Server.
• psrenconfig.txt contains other interesting parameters that I have not dealt with in this document. (Other Interesting log files at this stage: access.log, PSAPPSERV.LOG)

• Open a Permission list that the user you are using has access to. I like to use PTPT1000 as EVERYONE has access to this Permission List.
• Click on the “PeopleTools” tab and select the “Realtime Event Notification Permissions” link.
• Select “Full Access (All)”
• Select the “Web Libraries” Tab and add “WEBLIB_RPT”

• Navigate to Peopletools → REN Server Configuration → REN Server Configuration. Port number, Application Server Name and Host Machine should match the entries you made in the psappsrv.cfg file.

Pinging the REN Server is a validation that everything went okay with your setup. If it did not, you are SOL and need to do some debugging.

• Navigate to: Peopletools → REN Server Configuration → REN Server Cluster

• The “Ping test” and “Buffer Test” buttons should return meaningful pages.

• “Authentication Domain” should match the Authentication Domain for the Web profile you are using. Remember that the Web Profile's Authentication Domain must start with a period. It should be “.domain.com” NOT “domain.com”