REN Server Configuration Create REN servers. Configure REN servers. Determine REN server configuration options. Cluster REN servers. Create REN servers Depending on your requirements, choose one of two REN server creation and configuration options: To create a REN server with default configuration parameters, create an application server domain using PSADMIN and select feature 8, Event Notification, from the quick-configure menu. Configure a REN server from the REN Server Configuration pages (PeopleTools, REN Server Configuration). Define the REN server using a new application server domain name and host machine name and associate the REN server with a new or existing REN server cluster. Then create the associated domain, selecting feature 8, Event Notification, from the quick-configure menu. Note.You can create only one REN server per application server domain. Step1 Create a REN server with the default configuration parameters, Create an application server domain using PSADMIN. Specify parameters in the PSRENSRV section of PSADMIN domain configuration as shown below. 4 Defining REN Servers Define REN servers on the REN Server Definition page. . Clustering REN Servers Configure a REN server cluster using REN Server Cluster pages. Port Number Specify the HTTP port number on which this REN server is addressed.5 Application Server DomainSpecify the application server domain serving this REN server. Host Machine Specify the hostmachine on which the specified application server domain runs. . Change the HTTP port value if multiple REN servers run on the same host machine. Process Instance Reserved for future use. 6 By default. Change this so multiple REN server clusters are addressable through a single reverse proxy server. State Flag Select Active or Inactive. configure multiple REN server clusters with the same ownership and set them to active status. REN Server Cluster URL . You can inactivate a REN server cluster without deleting the cluster. If the cluster supports MCF servers. Inactivate a cluster before deleting the cluster. This flag determines whether the cluster can receive new client requests. then a cluster is created with a cluster ID RENCLSTR_000n REN Server Cluster ID The ID of this REN server cluster. current chat sessions continue even after a cluster is inactive. But the MCF system does not route an additional requests to an inactive cluster. REN Server Cluster Root Path The default REN server cluster root path is /psren. For scalability. If all clusters are inactive. Then the reporting window and customer chat applications will direct new client requests to a randomly chosen active REN server cluster. the client receives an error message. or before removing a member REN server from the cluster. if you start a REN server from PSADMIN without configuring a REN server cluster. load balancer. The protocol must be HTTP. If the REN server is reached through a load balancer. REN Server Browser URL The REN server browser URL is the address used by external clients and by agent chat to reach the application served by this REN server cluster. the REN server is not running. it cannot be HTTPS. Authorization Token Specify the authorization token domain. This port number is the REN server port number or the port number of a proxy server. switch. which should not have to go through any firewall. <port> is the REN server port number. Failure may indicate that a URL or authorization token is incorrectly specified.The REN server cluster URL is the address used to reach the REN server cluster internally. the Cluster URL is that of the switch or load balancer in front of the clustered REN servers. load balancer. The buffer test bypasses REN server security. No two clusters can address the same cluster URL. The Browser URL may be different from the Cluster URL. This port number is the REN server port number or the port number of a proxy server. If the MCF cluster is served by a REN server cluster. load balancer. specify the fully-qualified URL of that device as accessed from the user¶s browser. This is the URL used by internal processes. or that single sign-on is not implemented. the default value is 7180. This must be the same as specified in the PeopleSoft Internet Architecture installation. or SSL accelerator). Ping Test Click Ping to initiate a test of the REN server specified in the Browser URL fields. The URL must be the address of the gateway machine (proxy server. Configuring REN Server Ownership . the default value is 7180. where: <DNS_machine_name> is the server machine name recognized by your DNS. or other front end. Specify the cluster URL in the form <http://<DNS_machine_ name>:<port>. Specify the address in the form http: or https://<DNS_machine_ name>. <domain_name> is the full-qualified domain name recognized by your DNS. where: 7 <DNS_machine_name> is the server machine name recognized by your DNS. <port> is the REN server port number. reverse proxy server or other outward-facing security barrier. Buffer Test Click Buffer Test to initiate a test of the REN servers¶ ability to break up and send a large file using multiple internal buffers. and does not depend on specified domain names (authorization token). so you can use it to verify that the REN server is running on the network. or other front end. The cluster URL must be unique for each cluster.<domain_name>:<port>. or reverse proxy server. and security. Configuring REN Server Cluster Members . and users without MCF permissions cannot start the MultiChannel Console. For example. This is useful for ensuring performance under load. or masquerade to the REN server as an MCF agent.8 REN Server Cluster OwnerSelect the owner of this REN server cluster from the drop-down list. users without Reporting permissions cannot launch the report window. Specifying an owner for a REN server cluster supports security. Options are: All MCF Optimization Reporting Specifying an owner for a REN server cluster limits client access to that cluster. 9 REN Server ID Select a REN server from the drop-down list. . Security Defining Permission Lists for REN Server Access Define access to REN servers in the appropriate permission lists. Each REN server can only belong to one REN server cluster. The MultiChannel Console link appears in the header for any user with full access permissions defined for the MCF Agent object. Permission Lists. click on the edit link and make sure that the access permissions are set to full access.´ 5. For example. If it is not there.10 To define access to REN servers in a permission list: 1. select your permissions. Make sure that there is an entry for WEBLIB_RPT. select the Web Libraries tab. select the PeopleTools tab. users who require access to the MultiChannel Console must have Full Access defined for the MCF Agent permission. the user must also be configured as an MCF or CTI agent to access the MultiChannel Console. Once that is added. Security. then please add the library in. On the Permission List page. On the REN Permissions page. . search for and select your permission list. Select PeopleTools. However. 3. Permissions & Roles. 4. On the search page. On the Permission List page. 2. Click ³Realtime Event Notification Permissions. To enable REN server access for roles defined with the current permission list. select Full Access. . 11 . . This should show the ³Ping Test for REN Server´ page as show below . Run the Ping Test from REN server Cluster Page.12 Ping Test. . Pop up window is displayed and status changes from µQueued¶ to µProcessing¶ to µSuccess¶ 3. 4) Correct the URL value.12 Ping Test. Since the value is incorrect. 2) Navigate to PeopleTools->Process Scheduler->Report Nodes. Solution Do the following: 1) Log into the PeopleSoft application. When you run a report to window.LOG) The issue can be reproduced with the following steps: 1. No errors are present in any logs including PSRENSRV_MMDD. the Report Manager cannot retrieve and display the report. This should show the ³Ping Test for REN Server´ page as show below. Run a report to window 2. 14 Communication with REN Server failed Issue . process monitor shows that it was successfully created and posted. Instead. Test is sucessful if ³Events Sent´ and ³Events Received´ both reach the same final Value and also if ³Content to Send´ and ³Content received´ are the same REN Server ToubleShooting Error 404²Not Found Symptoms When running a report to window. the report is never displayed. the following error is displayed: Error 404²Not Found Even though the report is not displayed. It should have the following format: http://<machine name>:<port number>/psreports/<PeopleSoft site name> 5) Restart the process scheduler and re-test. However. Then the following error is displayed: Error 404 ± Not found Cause The report node is not configured correctly.log and DSTAGNT_MMDD. 3) Select the Report Node you're using when outputting the report to window. The 'URL' value is incorrect. the status window changes from 'Queued' to 'Processing' to 'Success'. Run the Ping Test from REN server Cluster Page. this URL is used to view the report from the Report Manager. If the initial PIA deployment did not specify an Authentication Domain. mycompany. Click on the name link for the default local node and make sure that the Authentication Option is set to password and that a password has been entered.properties file. Once you have the Web Profile up. Case # 4: One customer reported that in their REN Server Configuration > REN Server Definition page.' If authentication domain is specified in REN configuration. Next. navigate to PeopleTools > Security > Security Objects > Single Signon. Navigate to PeopleTools > Web Profile. On the next page. make sure that the access code for Reporting Window is set to full access. Search for and select the active Web Profile. Make sure the field for Authentication Domain field on the General tab has your company's Authentication Domain (ex. Click on the "Realtime Event Notification Permissions" link in the middle of the page. Once that is added. then please add the library in. they were able to 15 access the REN server. Case #2 If using an authentication domain. Select the primary permission list that is tied to the user profile that you are testing with. You will also have to grant permissions to the USER ID that is configured for your Process Scheduler database signon settings. Finally.When trying to run the Ping Test from the REN server configuration > REN server cluster page. Make sure to save your changes and bounce the web server for the change to take effect. the browser returns a pop-up box with the message "Communication with REN Server failed (HTTP 403 Forbidden)" "Unable to connect to the RenServer" Solution Case # 1: Make sure that you have the proper REN server permissions configured. Make sure that your default local node is listed there. It will tell you what Web Profile is currently active). but the environment now has one. Case # 5: . make sure that the REN server configuration is specifying the domain: -Navigate to PeopleTools -> REN Server Configuration -> REN Server Cluster -Select your REN Server Cluster -Verify 'Authentication Domain' has been specified -Verify that the domain is specified in the 'REN Server Browser URL Note that authentication domain is required if the web server and REN server are not on the same box. to include lowercase characters). navigate to PeopleTools > Portal > Node Definitions and click search to bring up all of your nodes. then go back and try running your Ping Test. Make sure that there is an entry for WEBLIB_RPT.44 only. Make sure to save the changes before exiting. go to the Web Libraries tab. Once the permission list is up. include the authentication domain in the sign on url when logging in to application Case # 3 This case applies to PeopleTools 8. go to the PeopleTools tab. it is necessary to add the Authentication Domain to the active Web Profile. the Application Server Domain name was case sensitive. Sort so that your default local node is listed at the top. if that user is different than the one that you are currently logged in as. Navigate to PeopleTools > Security > Permissions and Roles > Permission Lists. Next.com). If it is not there. click on the edit link and make sure that the access permissions are set to full access. check your configuration. After they changed the Application Server Domain name to match how it was defined through PSADMIN (in this case. (If you do not know what Web Profile is currently active. the first tab should be labeled "General". To clear cache. then try clearing cache in case some Ren configuration changes were made. . Once you have the Web Profile up. Make sure to save your changes and bounce the web server for the change to take effect.properties file. bring down the PIA web server and the application server and clear the cache. but the environment now has one. Then run ping test again. It will tell you what Web Profile is currently active). but cache was not cleared afterwards. it is necessary to add the Authentication Domain to the active Web Profile. mycompany. Also. Navigate to PeopleTools > Portal > Node Definitions and click search to bring up all of your nodes.If you are still having issues after trying the suggestions above. the first tab should be labeled "General". Verify the following: If the initial PIA deployment did not specify an Authentication Domain. (If you do not know what Web Profile is currently active. Restart the PIA web server and application server. clear the cache and cookies from your browser and close all browser sessions.com). Sort so that your default local node is listed at the top. Click on the name link for the default local node and make sure that the Authentication Option is set to password and that a password has been entered. then go back and try running your Ping Test. Search for and select the active Web Profile. Navigate to PeopleTools > Web Profile. Make sure the field for Authentication Domain field on the General tab has your company's Authentication Domain (ex. check your configuration. . 16 . 16 vv .