PeopeSoft REN Server Configuration

PeopleSoft REN Server Configuration Author : Creation Date: Last Updated:

Ramesh S Raj March 23, 2010

1

Table of Contents

REN Server Configuration ...............................................................................................................................3 Security ..........................................................................................................................................................10 REN Server ToubleShooting .........................................................................................................................13 Test Scenario .................................................................................................................................................18

2

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.

3

Start Application server.

4

Defining REN Servers Define REN servers on the REN Server Definition page.

REN Server Configuration page

Application Server Domain

Specify 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.

5

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

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 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://:/psreports/ 5) Restart the process scheduler and re-test.

13

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 been entered. 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 URL Note 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 14

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.

15

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.

16

In Report Node Definitions , make sure the URL is has the following format: http://:/psreports/

17

Test Scenario

Submit the process. Select the Type as Window. Format can be any one of the options available.

Once the process is submitted, a window pop’s up with the information of the process as shown below.

The output is shown in the user screen itself as shown below. 18

19