ren server configuration

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.

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. Port Number

Specify the HTTP port number on which this REN server is addressed.

Change the HTTP port value if multiple REN servers run on

the same host machine.Process Instance Reserved for future use.

Clustering REN Servers Configure a REN server cluster using REN Server Cluster pages.

6

By default, if you start a REN server from PSADMIN without configuring a REN server cluster, then a cluster is created with a cluster ID RENCLSTR_000n REN Server Cluster ID The ID of this REN server cluster. State Flag

Select Active or Inactive.

This flag determines whether the cluster can receive new client requests. For

scalability, configure multiple REN server clusters with the same ownership

and set them to active status. Then the reporting window and customer chat

applications will direct new client requests to a randomly chosen active REN

server cluster. If all clusters are inactive, the client receives an error message.

If the cluster supports MCF servers, current chat sessions continue

even after a cluster is inactive. But the MCF system does not route

an additional requests to an inactive cluster.

Inactivate a cluster before deleting the cluster, or before removing

a member REN server from the cluster. You can inactivate a REN

server cluster without deleting the cluster.REN Server Cluster Root Path The default REN server cluster root path is /psren. Change this so multiple REN server clusters are addressable through a single reverse proxy server. REN Server Cluster URL

The REN server cluster URL is the address used to reach the REN server cluster

internally.

This is the URL used by internal processes. If the MCF cluster is served by a

REN server cluster, the Cluster URL is that of the switch or load balancer

in front of the clustered REN servers. The cluster URL must be unique for

each cluster. No two clusters can address the same cluster URL. Specify the

cluster URL in the form <http://<DNS_machine_ name>:<port>, where:

7

• <DNS_machine_name> is the server machine name recognized by your DNS.

• <port> is the REN server port number; the default value is 7180.

This port number is the REN server port number or the port number

of a proxy server, load balancer, or other front end.

• The protocol must be HTTP; it cannot be HTTPS.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. The buffer test bypasses REN server

security, 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.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 Browser URL

may be different from the Cluster URL, which should not have to go through any

firewall, reverse proxy server or other outward-facing security barrier. If the REN

server is reached through a load balancer, switch, or reverse proxy server, specify

the fully-qualified URL of that device as accessed from the user’s browser. The

URL must be the address of the gateway machine (proxy server, load balancer, or

SSL accelerator). Specify the address in the form http: or https://<DNS_machine_

name>.<domain_name>:<port>, where: • <DNS_machine_name> is the server

machine name recognized by your DNS. • <domain_name> is the full-qualified

domain name recognized by your DNS. • <port> is the REN server port number;

the default value is 7180. This port number is the REN server port number or the

port number of a proxy server, load balancer, or other front end.Ping Test

Click Ping to initiate a test of the REN server specified in the

Browser URL fields. Failure may indicate that a URL or authorization token is

incorrectly specified, the REN server is not running, or that single sign-on is not

implemented.Authorization Token Specify the authorization token domain. This must be the same as specified in the PeopleSoft Internet Architecture installation.

Configuring REN Server Ownership

8 REN Server Cluster OwnerSelect the owner of this REN server cluster from the drop-down

list. Options are:

• All

• MCF

• Optimization

• Reporting

Specifying an owner for a REN server cluster limits client access to that

cluster. This is useful for ensuring performance under load, and security.

Specifying an owner for a REN server cluster supports security. For

example, users without Reporting permissions cannot launch the report

window, and users without MCF permissions cannot start the MultiChannel

Console, or masquerade to the REN server as an MCF agent.

Configuring REN Server Cluster Members

9

REN Server ID Select a REN server from the drop-down list. Each REN server can only belong to one REN server cluster.

Security Defining Permission Lists for REN Server Access Define access to REN servers in the appropriate permission lists.

10 To define access to REN servers in a permission list:

1. Select PeopleTools, Security, Permissions & Roles, Permission Lists.

2. On the search page, search for and select your permission list.

3. On the Permission List page, select the PeopleTools tab.

4. Click “Realtime Event Notification Permissions.”

5. On the REN Permissions page, select your permissions.

To enable REN server access for roles defined with the current permission list, select Full

Access. For example, users who require access to the MultiChannel Console must have

Full Access defined for the MCF Agent permission.

The MultiChannel Console link appears in the header for any user with full access permissions

defined for the MCF Agent object. However, the user must also be configured as an

MCF or CTI agent to access the MultiChannel Console.On the Permission List page, select the Web Libraries tab. Make sure that there is an entry for WEBLIB_RPT. If it is not there, then please add the library in. Once that is added, click on the edit link and make sure that the access permissions are set to full access.

12 Ping Test. Run the Ping Test from REN server Cluster Page. This should show the “Ping Test for REN Server” page as show below

12 Ping Test. Run the Ping Test from REN server Cluster Page. This should show the “Ping Test for REN Server” page as show below. 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 status window changes from 'Queued' to 'Processing' to 'Success'.

However, the report is never displayed. Instead, the following error is displayed:

Error 404—Not Found

Even though the report is not displayed, process monitor shows that it was successfully created and posted.

No errors are present in any logs including PSRENSRV_MMDD.log and DSTAGNT_MMDD.LOG)

The issue can be reproduced with the following steps:

1. Run a report to window

2. Pop up window is displayed and status changes from ‘Queued’ to ‘Processing’ to ‘Success’

3. Then the following error is displayed: Error 404 – Not foundCause

The report node is not configured correctly. The 'URL' value is incorrect. When you run a report to window,

this URL is used to view the report from the Report Manager. Since the value is incorrect, the Report

Manager cannot retrieve and display the report.Solution

Do the following:

1) Log into the PeopleSoft application.

2) Navigate to PeopleTools->Process Scheduler->Report Nodes.

3) Select the Report Node you're using when outputting the report to window.

4) Correct the URL value. It should have the following format:http://<machine name>:<port number>/psreports/<PeopleSoft site name> 5) Restart the process scheduler and re-test.

14

Communication with REN Server failed Issue

When trying to run the Ping Test from the REN server configuration > REN server cluster page, 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.

Navigate to PeopleTools > Security > Permissions and Roles > Permission Lists. 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, if that user is

different than the one that you are currently logged in as. Once the permission list is up, go to the

PeopleTools tab. Click on the "Realtime Event Notification Permissions" link in the middle of the page. On

the next page, make sure that the access code for Reporting Window is set to full access.

Next, go to the Web Libraries tab. Make sure that there is an entry for WEBLIB_RPT. If it is not there, then

please add the library in. Once that is added, click on the edit link and make sure that the access

permissions are set to full access.Make sure to save the changes before exiting.

Next, navigate to PeopleTools > Portal > Node Definitions and click search to bring up all of your

nodes. 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 beenentered. Finally, navigate to PeopleTools > Security > Security Objects > Single Signon. Make sure that your default local node is listed there. Case #2

If using an authentication domain, 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 URLNote that authentication domain is required if the web server and REN server are not on the same box.' If authentication domain is specified in REN configuration, include the authentication domain in the sign on url when logging in to application Case # 3

This case applies to PeopleTools 8.44 only. If the initial PIA deployment did not specify an Authentication

Domain, but the environment now has one, it is necessary to add the Authentication Domain to the active

Web Profile. Navigate to PeopleTools > Web Profile. Search for and select the active Web Profile. (If you

do not know what Web Profile is currently active, check your configuration.properties file. It will tell you what

Web Profile is currently active). Once you have the Web Profile up, the first tab should be labeled

"General". Make sure the field for Authentication Domain field on the General tab has your company's

Authentication Domain (ex. mycompany.com). Make sure to save your changes and bounce the web server

for the change to take effect, then go back and try running your Ping Test.Case # 4:

One customer reported that in their REN Server Configuration > REN Server Definition page, the Application

Server Domain name was case sensitive. After they changed the Application Server Domain name to match

how it was defined through PSADMIN (in this case, to include lowercase characters), they were able to

15 access the REN server. Case # 5:

If you are still having issues after trying the suggestions above, then try clearing cache in case some Ren

configuration changes were made, but cache was not cleared afterwards. To clear cache, bring down the

PIA web server and the application server and clear the cache. Also, clear the cache and cookies from your

browser and close all browser sessions. Restart the PIA web server and application server. Then run ping

test again.

Verify the following:

If the initial PIA deployment did not specify an Authentication Domain, but the environment now has one, it is

necessary to add the Authentication Domain to the active Web Profile. Navigate to PeopleTools > Web

Profile. Search for and select the active Web Profile. (If you do not know what Web Profile is currently

active, check your configuration.properties file. It will tell you what Web Profile is currently active). Once you

have the Web Profile up, the first tab should be labeled "General". Make sure the field for Authentication

Domain field on the General tab has your company's Authentication Domain (ex. mycompany.com). Make

sure to save your changes and bounce the web server for the change to take effect, then go back and try

running your Ping Test.

Navigate to PeopleTools > Portal > Node Definitions and click search to bring up all of your nodes. 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.

ren server configuration

Documents