WebLogic 8.1 as Reverse Proxy Server

Prerequisite:
1. Setup PIA with weblogic as WebServer or content server.
2. It is recommended that you don’t go for multiple WebServer.

Follow these steps sequentially:

1) Install weblogic in your machine which is going to be your RPS.
Preferably on your C:\ (Default).

2) Now install PeopleSoft Pure Internet Architecture on that machine.

You will find setup in this path where PSOFT89 is your PS HOME
E:\PSOFT89\setup\mpinternet

Select Multi Server Domain as the configuration.
Give Content Server IP address as AppServer Name.
Give application domain Jolt port as JSL port.
Always try to give unique HTTP, HTTPS port number.

Important Checking:

1. Start the server manually, instead of as a service as this should create the msi-config.xml file

2. From your PS_HOME/webserv/WebServerDomain directory copy config.xml to msi-config.xml as the msi-config.xml file is a copy of config.xml. Now you should be able to start WebLogic as a service or manually.



By Default a server named RPS is automatically defined in addition to the main PIA server.

Following settings are applied to RPS:
i)Name: RPS
ii)HTTP Listen Port: 8080
iii) HTTPS Listen Port: 8443
iv)Default Web Application: HTTP Proxy Servlet
v) Address of back-end Web Logic content server: The hostname of the machine from which the PIA setup was run, with the HTTP listen port specified during the PIA setup.

Specifying Back-End Web Logic Content Servers:

You need to define the content server (WEB SERVER which is presently serving request.) if it is in different machine. You can directly edit WEB.XML file. Follow these simple steps to define web logic content servers.

1) Open the WEB.XML in the specified directory and open it in notepad.
PS_HOME\webserv\weblogic_domain\applications\HttpProxyServlet\WEB-INF.

Modify WebLogicHost (Host name) and WebLogicPort ( HTTP port) parameter values.


WebLogicHost
172.17.24.148
Hostname of WebLogic PIA/PORTAL server.



WebLogicPort
8095
HTTP listen port of WebLogic PIA/PORTAL server.


Important Checking:

Make sure that if you have changed the default port for Admin server in config.xml, it needs to be changed in the setenv.cmd file as well.


Your RPS Configuration is complete now start PIA.
Go To Command Prompt
1) startWebLogicAdmin
2) startManagedWebLogic RPS
You can access your peoplesoft login screen through this
http://(machineIP):(HTTPPort)/ ps/signon.html

MachineIP : machine IP where you have created RPS.
HTTPPort : HTTP port of RPS . (Here in the picture 8825)


These problems we may encounter during RPS configuration:


ISSUE 1


After doing a PIA install for PeopleTools 8.44, with Weblogic 8.1, starting the web server as a service fails.The following is in the log file: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The WebLogic Server did not start up properly. Exception raised: 'weblogic.management.configuration.ConfigurationException: [Management:141137]Managed Server was attempting to boot in Managed Server Independence mode, but was unable to complete the boot process as the Managed Server was unable to locate the cached configuration file: c:\psft\webserv\peoplesoft\.\msi-config.xml' Reason: weblogic.management.configuration.ConfigurationException: [Management:141137]Managed Server was attempting to boot in Managed Server Independence mode, but was unable to complete the boot process as the Managed Server was unable to locate the cached configuration file: c:\psft\webserv\peoplesoft\.\msi-config.xml SOLUTION: 1) Start the server manually, instead of as a service as this should create the msi-config.xml file. If the file does not get created do step 2 below. 2) From your PS_HOME/webserv/WebServerDomain directory copy config.xml to msi-config.xml as the msi-config.xml file is a copy of config.xml. Now you should be able to start WebLogic as a service or manually.





ISSUE 2
Unable to boot the Managed Server errors can occur on various scenarios. Please refer to the following cases as to identify which scenarios you're encountering. CASE 1: The Weblogic Admin server starts ok. It is configured to run at 8080 port, instead of 9999 which is the default port. While trying to start the Managed server, it fails to start. The log shows the following messages. Mar 4, 2004 5:04:36 PM CST> SOLUTION: Make sure that if you have changed the default port for Admin server in config.xml, it needs to be changed in the setenv.cmd file as well. CASE 2: Customer is unable to boot the PIA server although the WebLogic Admin server runs fine. PeopleSoft application server domain also boots up fine. In this case, the WebLogic Admin server uses port 9999. 1. Errors found in the PIA stdout log: 2. Errors found in the Weblogic admin log: #### <> <> ####

<> <> ####

<> <> ####

<> <> Comparing the timestamps between the PIA log and the Weblogic Admin log, the Admin server was started at 8:50:12 AM after the PIA managed server at 8:50:02 AM. Do allow sometime for the Weblogic Admin server to be started before starting the PIA server.



ISSUE 3
The following messages are seen in the PIA_stdout.log file showing the server could not contact the Admin server and tried to start on it's own. Java home=/export/spare/psoft/po844/weblogic81/jdk141_03 Java command line=java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Dweblogic.Name=PIA -Dweblogic.management.server=HTTP://nyuck:9999 -Dweblogic.management.username=operator -Dweblogic.management.password=password -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/export/spare/psoft/po844/weblogic81/weblogic81/server/lib/weblogic.policy -Dssl.debug=false -Dps_home=/export/spare/psoft/po844 weblogic.Server java version "1.4.1_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02) Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode) Java home=/export/spare/psoft/po844/weblogic81/jdk141_03 RESOLUTION: In this case the Admin and Managed servers were being started at the same time. The admin server needs to be started first and enough time allowed for it to start up before the managed server can/should be started.





ISSUE: A customer tries to start a Weblogic Server and receives the following authentication error: Attempting to start WebLogic Server 'PIA' java version "1.4.1_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02) Java HotSpot(TM) Server VM (build 1.4.1_03-b02, compiled mode) *************************************************************************** The WebLogic Server did not start up properly. Reason: weblogic.security.SecurityInitializationException: Authentication denied : Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed sin ce the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. SOLUTION: The managed server has not yet connected to an admin server. Make sure you start your admin server then verify that the admin server is up by accessing the console: (http://10.200.129.190:9999/console) and then you'll need to start the managed server. Another possible reason for this error is that your setEnv.sh script needs to be corrected. For one customer their WLS_USER was set to (operator) instead of (system). System is the delivered user default to sign onto the admin server console. Once they corrected the WLS_USER to the default user used to sign onto the admin server and started the PSEMHUB (startManagedWebLogic.sh PSEMHUB) it worked correctly. If you change the user and password for the WebLogicAdmin server then be sure and change it in the setEnv.sh also. Following are the key fields that the startManagedWebLogic.sh script is using to connect with the admin server to start the PSEMHUB as well as the PIA (see below). These must be set correctly. The message indicating the boot.properties file had changed since the initial installation is really referring to the connect user being incorrect in the setEnv.sh script. Once this is corrected there is no need to reinstall the PIA. setEnv.sh is called each time the startManagedWebLogic.sh is run. # WLS_USER - WebLogic ID used to stop and start managed server. User # ID must have be a member of WebLogic defined Operators # group. # WLS_PW - Password of WebLogic user used to start and stop # managed servers. # # ADMINSERVER_PROTOCOL - Protcol managed servers will use when communicating # with an admin server. # ADMINSERVER_PORT - The HTTP/s or t3/s port of the admin server for this # domain. Used for stoping the admin server and optionally # starting managed servers in a clustered configuration. # ADMINSERVER_HOSTNAME - The hostname or IP of the admin server. # ADMINSERVER_SERVERNAME - The WebLogic server instance name of WebLogic admin # server.