https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=559309881105001&id=1073353.1&displayIndex=3&_afrWindowMode=0&_adf.ctrl-state=f9r23d5kw_105
Configuring Microsoft IIS 7.0 as an RPS with Version 1.0 Plug-ins
This section describes how to proxy content to a single server configuration of PIA. In a production environment, a multi server configuration would be used to perform these steps to proxy content to your managed server instance of PIA, PIA1, PIA2, and so on.
Microsoft Internet Information Server (IIS) can be configured as a reverse proxy server (RPS) for one or more WebLogic Server instances. Multiple instances can either be independent instances, or grouped into a cluster. When using a reverse proxy, all URLs that are used to access your PeopleSoft application (even URLs that are stored in the database), need to point to the reverse proxy, and not to the WebLogic server.
Oracle only supports IIS 7.0 as an RPS on Windows Server 2008 x64 Standard Edition, or Enterprise Edition environments. These instructions are based on a logical separation of WebLogic Server and Microsoft IIS 7.0, where both web servers are installed on the same machine. If your configuration has WebLogic Server and Microsoft IIS on separate machines, you must perform these additional tasks:
1. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisproxy.dll to c:\inetpub, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server.
2. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisforward.dll to c:\inetpub, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server.
3. In the procedures described below, change any reference to: WL_HOME\server\plugin\win\x64\, to c:\inetpub\, or to the other directory where you copied the two files mentioned above.
Note. In these instructions, make the appropriate adjustments for your server's architecture (32–bit or 64–bit).
To set up a Microsoft IIS 7.0 RPS:
1. Access your installed Microsoft IIS7.0 configuration:
• On a Microsoft Windows server, select Start, Programs, Administrative Tools, Internet Information Service (IIS) Manager.
2. Add a JSP Script Mapping:
• After selecting the Default Web Site in the lefthand pane, locate the Handler Mappings icon in the panel to the right. Right click on Handler Mappings and select “Open Feature”.
• Right click in the new window and select “Add Script Map…”
• Enter ‘*.jsp’ as the Request path. (Do not include quotation marks.)
• Browse to the iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘JSP’.
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
3. Add a WLFORWARD Script Mapping:
• In the same Handler Mappings panel, right click and again select “Add Script Map…”
• Enter ‘*.wlforward’ as the Request path.
• Browse to the same iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘WLFORWARD’.
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
4. Add an ISAPI filter:
• On the Default Web Site, locate the “ISAPI Filters” icon.
• Right click on this icon, and select “Open Feature”.
• Right click in the new window and select “Add…”
• Enter “WLFORWARD” as the Filter name.
• Browse to the iiforward.dll file and add it as the executable.
• When finished, click OK.
5. Provide Necessary Restrictions to the Entire IIS:
• Select the root node with your hostname in the lefthand pane.
• Locate the “ISAPI and CGI Restrictions” icon on the right.
• Right click on the “ISAPI and CGI Restrictions” icon and select “Open Feature”.
• Right click and select “Edit Feature Settings…”
• Ensure that both “Allow unspecified CGI modules”, and “Allow unspecified ISAPI modules” are checked.
• When finished, click OK.
6. Create an IIS Plugin configuration file:
• Create a WL_HOME\server\plugin\win\x64\iisproxy.ini file which contains the following lines. (The file should be placed in the same directory as the two plug-in DLL files that were mentioned at the top of this document.) Set the values appropriately for your environment.
#For a list of all available parameters see:
#http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143049
#
WebLogicHost=<hostname or IP of the WebLogic server to forward requests to>
WebLogicPort=<HTTP port of WebLogic server to forward requests to>
DebugConfigInfo=OFF
Debug=OFF
#
#To proxy all IIS directed requests to WebLogic, set “WlForwardPath=/”
#
#To selectively proxy only PeopleSoft requests to WebLogic, set “WlForwardPath=” to
#the list of PeopleSoft sites to proxy.
#e.g. To proxy requests for only the ‘ps’ and ‘crm’ sites, set WlForwardPath to the following:
#WlForwardPath=*/ps/*,*/crm/*
WlForwardPath=/
#
#If you have specified an AuthTokenDomain during your PIA installation,
#you must set the cookieName for your reverse proxy.
WLCookieName=<CookieName as specified on WebLogic in PORTAL webapps’s weblogic.xml>
7. Set WebLogic Plugin Enabled:
Set the 'WebLogic Plugin Enabled' parameter, as there are a few known issues when not setting this parameter, especially if using https (see document 1300409.1 for details).
a. Log into WebLogic console (using url http://machine-name:port#/console)
b. Click 'Lock & Edit' button on top left page
c. From left menu, choose Environment -> Servers
d. Click the 'PIA' hyperlink on right menu.
e. Go to tab 'Configuration' and sub-tab 'General'
f. At bottom of page, click the 'Advanced' hyperlink
g. Check box next to 'WebLogic Plug-In Enabled
h. Save change
i. Click 'Activate Changes' button on top left page
j. Restart your WebLogic PIA instance.
8. Restart Microsoft IIS:
• Restart the two Windows services: IIS Admin Service, and World Wide Web Publishing Service.
Also, restart your default web site by right clicking on the new Web Site, and selecting: Manage Web Site ? Restart or Start if not started.
9. Start the WebLogic server.
• See Starting WebLogic.
• See Stopping WebLogic.
10. Test your configuration by accessing the Microsoft IIS server by using the URL for your site.
For example, http://IIS_server:port/ps/signon.html.
Note. To connect to Microsoft IIS by using HTTPS, you must install digital certificates on the Microsoft IIS server.
Setting up Multiple Sites on Microsoft IIS 7.0 RPS to point to Different WebLogic Instances:
1. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisproxy.dll to c:\inetpub\Portal90, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server. In the examples below we are using c:\inetpub\Portal90.
2. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisforward.dll to c:\inetpub\Portal90, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server.
3. In the procedures described below, change any reference to: WL_HOME\server\plugin\win\x64\, to c:\inetpub\Portal90, or to the other directory where you copied the two files mentioned above.
Note: Do not use the Default Web Site for the instructions below. Create a new site for each instance you want to create.
1. Access your Installed Microsoft IIS7.0 configuration:
• On a Microsoft Windows server, select Start, Programs, Administrative Tools, Internet Information Service (IIS) Manager.
• Right click on Sites and choose Add Web Site.
• Choose a unique site name
• The Application Pool should match your site name
• Physical path is the location where your iisproxy.ini file will reside for this site
• Change the Port to a port not in use on this machine.
• Host name: Enter the hostname of your web server.
Example:
2. Add a JSP Script Mapping:
• After selecting the new Web Site in the lefthand pane, locate the Handler Mappings icon in the panel to the right. Right click on Handler Mappings and select “Open Feature”.
• Right click in the new window and select “Add Script Map…”
• Enter ‘*.jsp’ as the Request path. (Do not include quotation marks.)
• Browse to the iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘JSP1’. For second site and each additional increment number by 1, for example JSP2, JSP3, etc..
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
3. Add a WLFORWARD Script Mapping:
• In the same Handler Mappings panel, right click and again select “Add Script Map…”
• Enter ‘*.wlforward’ as the Request path.
• Browse to the same iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘WLFORWARD1’. For second site and each additional increment number by 1, for example WLFORWARD2, WLFORWARD3, etc..
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
4. Add an ISAPI filter:
• On the New Web Site, locate the “ISAPI Filters” icon.
• Right click on this icon, and select “Open Feature”.
• Right click in the new window and select “Add…”
• Enter “WLFORWARD1” as the Filter name. WLFORWARD2, etc. for each site.
• Browse to the iiforward.dll file and add it as the executable.
• When finished, click OK.
5. Change Output Caching
• On the New Web Site, locate the “Output Caching” icon.
• Right click on this icon, and select “Open Feature”.
• On the right side click on “Edit Feature Settings”.
• Uncheck “Enable cache” and “Enable kernel cache”.
• When finished, click OK.
6. Provide necessary restrictions to the entire IIS:
• Select the root node with your hostname in the lefthand pane.
• Locate the “ISAPI and CGI Restrictions” icon on the right.
• Right click on the “ISAPI and CGI Restrictions” icon and select “Open Feature”.
• Right click and select “Edit Feature Settings…”
• Ensure that both “Allow unspecified CGI modules”, and “Allow unspecified ISAPI modules” are checked.
• When finished, click OK.
7. Create an IIS Plugin configuration file:
• Create a c:\inetpub\Portal90\iisproxy.ini file which contains the following lines. (The file should be placed in the same directory as the two plug-in DLL files that were mentioned at the top of this document.) Set the values appropriately for your environment.
#For a list of all available parameters see:
#http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143049
#
WebLogicHost=<hostname or IP of the WebLogic server to forward requests to>
WebLogicPort=<HTTP port of WebLogic server to forward requests to>
DebugConfigInfo=OFF
Debug=OFF
#
#To proxy all IIS directed requests to WebLogic, set “WlForwardPath=/”
#
#To selectively proxy only PeopleSoft requests to WebLogic, set “WlForwardPath=” to
#the list of PeopleSoft sites to proxy.
#e.g. To proxy requests for only the ‘ps’ and ‘crm’ sites, set WlForwardPath to the following:
#WlForwardPath=*/ps/*,*/crm/*
WlForwardPath=/
#
#If you have specified an AuthTokenDomain during your PIA installation,
#you must set the cookieName for your reverse proxy.
WLCookieName=<CookieName as specified on WebLogic in PORTAL webapps’s weblogic.xml>
8. Restart Microsoft IIS:
• Restart the two Windows services: IIS Admin Service, and World Wide Web Publishing Service.
Also, restart your new web site by right clicking on the new Web Site, and selecting: Manage Web Site ? Restart or Start if not started.
9. Start the WebLogic server.
• See Starting WebLogic.
• See Stopping WebLogic.
10. Test your configuration by accessing the Microsoft IIS server by using the URL for your site.
For example, http://IIS_server:port/ps/signon.html.
Note. To connect to Microsoft IIS by using HTTPS, you must install digital certificates on the Microsoft IIS server.
11. Go back to the beginning of this section to create a second web site. Make sure you use a different folder to store the iisproxy.ini, iisproxy.dll and iisforward.dll files for each web site.
See Also:
Installing and Configuring the Microsoft IIS7.0 Plug-In: http://download.oracle.com/docs/cd/E15523_01/web.1111/e14395/isapi.htm#BGBFJAEJ
Parameters for Web Server Plug-Ins: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143049
Configuring Microsoft IIS 7.0 as an RPS with Version 1.0 Plug-ins
This section describes how to proxy content to a single server configuration of PIA. In a production environment, a multi server configuration would be used to perform these steps to proxy content to your managed server instance of PIA, PIA1, PIA2, and so on.
Microsoft Internet Information Server (IIS) can be configured as a reverse proxy server (RPS) for one or more WebLogic Server instances. Multiple instances can either be independent instances, or grouped into a cluster. When using a reverse proxy, all URLs that are used to access your PeopleSoft application (even URLs that are stored in the database), need to point to the reverse proxy, and not to the WebLogic server.
Oracle only supports IIS 7.0 as an RPS on Windows Server 2008 x64 Standard Edition, or Enterprise Edition environments. These instructions are based on a logical separation of WebLogic Server and Microsoft IIS 7.0, where both web servers are installed on the same machine. If your configuration has WebLogic Server and Microsoft IIS on separate machines, you must perform these additional tasks:
1. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisproxy.dll to c:\inetpub, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server.
2. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisforward.dll to c:\inetpub, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server.
3. In the procedures described below, change any reference to: WL_HOME\server\plugin\win\x64\, to c:\inetpub\, or to the other directory where you copied the two files mentioned above.
Note. In these instructions, make the appropriate adjustments for your server's architecture (32–bit or 64–bit).
To set up a Microsoft IIS 7.0 RPS:
1. Access your installed Microsoft IIS7.0 configuration:
• On a Microsoft Windows server, select Start, Programs, Administrative Tools, Internet Information Service (IIS) Manager.
2. Add a JSP Script Mapping:
• After selecting the Default Web Site in the lefthand pane, locate the Handler Mappings icon in the panel to the right. Right click on Handler Mappings and select “Open Feature”.
• Right click in the new window and select “Add Script Map…”
• Enter ‘*.jsp’ as the Request path. (Do not include quotation marks.)
• Browse to the iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘JSP’.
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
3. Add a WLFORWARD Script Mapping:
• In the same Handler Mappings panel, right click and again select “Add Script Map…”
• Enter ‘*.wlforward’ as the Request path.
• Browse to the same iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘WLFORWARD’.
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
4. Add an ISAPI filter:
• On the Default Web Site, locate the “ISAPI Filters” icon.
• Right click on this icon, and select “Open Feature”.
• Right click in the new window and select “Add…”
• Enter “WLFORWARD” as the Filter name.
• Browse to the iiforward.dll file and add it as the executable.
• When finished, click OK.
5. Provide Necessary Restrictions to the Entire IIS:
• Select the root node with your hostname in the lefthand pane.
• Locate the “ISAPI and CGI Restrictions” icon on the right.
• Right click on the “ISAPI and CGI Restrictions” icon and select “Open Feature”.
• Right click and select “Edit Feature Settings…”
• Ensure that both “Allow unspecified CGI modules”, and “Allow unspecified ISAPI modules” are checked.
• When finished, click OK.
6. Create an IIS Plugin configuration file:
• Create a WL_HOME\server\plugin\win\x64\iisproxy.ini file which contains the following lines. (The file should be placed in the same directory as the two plug-in DLL files that were mentioned at the top of this document.) Set the values appropriately for your environment.
#For a list of all available parameters see:
#http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143049
#
WebLogicHost=<hostname or IP of the WebLogic server to forward requests to>
WebLogicPort=<HTTP port of WebLogic server to forward requests to>
DebugConfigInfo=OFF
Debug=OFF
#
#To proxy all IIS directed requests to WebLogic, set “WlForwardPath=/”
#
#To selectively proxy only PeopleSoft requests to WebLogic, set “WlForwardPath=” to
#the list of PeopleSoft sites to proxy.
#e.g. To proxy requests for only the ‘ps’ and ‘crm’ sites, set WlForwardPath to the following:
#WlForwardPath=*/ps/*,*/crm/*
WlForwardPath=/
#
#If you have specified an AuthTokenDomain during your PIA installation,
#you must set the cookieName for your reverse proxy.
WLCookieName=<CookieName as specified on WebLogic in PORTAL webapps’s weblogic.xml>
7. Set WebLogic Plugin Enabled:
Set the 'WebLogic Plugin Enabled' parameter, as there are a few known issues when not setting this parameter, especially if using https (see document 1300409.1 for details).
a. Log into WebLogic console (using url http://machine-name:port#/console)
b. Click 'Lock & Edit' button on top left page
c. From left menu, choose Environment -> Servers
d. Click the 'PIA' hyperlink on right menu.
e. Go to tab 'Configuration' and sub-tab 'General'
f. At bottom of page, click the 'Advanced' hyperlink
g. Check box next to 'WebLogic Plug-In Enabled
h. Save change
i. Click 'Activate Changes' button on top left page
j. Restart your WebLogic PIA instance.
8. Restart Microsoft IIS:
• Restart the two Windows services: IIS Admin Service, and World Wide Web Publishing Service.
Also, restart your default web site by right clicking on the new Web Site, and selecting: Manage Web Site ? Restart or Start if not started.
9. Start the WebLogic server.
• See Starting WebLogic.
• See Stopping WebLogic.
10. Test your configuration by accessing the Microsoft IIS server by using the URL for your site.
For example, http://IIS_server:port/ps/signon.html.
Note. To connect to Microsoft IIS by using HTTPS, you must install digital certificates on the Microsoft IIS server.
Setting up Multiple Sites on Microsoft IIS 7.0 RPS to point to Different WebLogic Instances:
1. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisproxy.dll to c:\inetpub\Portal90, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server. In the examples below we are using c:\inetpub\Portal90.
2. From the WebLogic server, copy WL_HOME\server\plugin\win\x64\iisforward.dll to c:\inetpub\Portal90, or to any other directory where an administrator has appropriate access to it on your Microsoft IIS server.
3. In the procedures described below, change any reference to: WL_HOME\server\plugin\win\x64\, to c:\inetpub\Portal90, or to the other directory where you copied the two files mentioned above.
Note: Do not use the Default Web Site for the instructions below. Create a new site for each instance you want to create.
1. Access your Installed Microsoft IIS7.0 configuration:
• On a Microsoft Windows server, select Start, Programs, Administrative Tools, Internet Information Service (IIS) Manager.
• Right click on Sites and choose Add Web Site.
• Choose a unique site name
• The Application Pool should match your site name
• Physical path is the location where your iisproxy.ini file will reside for this site
• Change the Port to a port not in use on this machine.
• Host name: Enter the hostname of your web server.
Example:
2. Add a JSP Script Mapping:
• After selecting the new Web Site in the lefthand pane, locate the Handler Mappings icon in the panel to the right. Right click on Handler Mappings and select “Open Feature”.
• Right click in the new window and select “Add Script Map…”
• Enter ‘*.jsp’ as the Request path. (Do not include quotation marks.)
• Browse to the iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘JSP1’. For second site and each additional increment number by 1, for example JSP2, JSP3, etc..
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
3. Add a WLFORWARD Script Mapping:
• In the same Handler Mappings panel, right click and again select “Add Script Map…”
• Enter ‘*.wlforward’ as the Request path.
• Browse to the same iisproxy.dll file mentioned earlier, and add it as the executable. Name it: ‘WLFORWARD1’. For second site and each additional increment number by 1, for example WLFORWARD2, WLFORWARD3, etc..
• Click on the “Request Restrictions…” button, and uncheck the box titled ‘Invoke handler only if the request is mapped to’.
• When finished, click OK.
• A warning message will appear, asking you if you want to allow the ISAPI extension. Please select “Yes” to continue.
4. Add an ISAPI filter:
• On the New Web Site, locate the “ISAPI Filters” icon.
• Right click on this icon, and select “Open Feature”.
• Right click in the new window and select “Add…”
• Enter “WLFORWARD1” as the Filter name. WLFORWARD2, etc. for each site.
• Browse to the iiforward.dll file and add it as the executable.
• When finished, click OK.
5. Change Output Caching
• On the New Web Site, locate the “Output Caching” icon.
• Right click on this icon, and select “Open Feature”.
• On the right side click on “Edit Feature Settings”.
• Uncheck “Enable cache” and “Enable kernel cache”.
• When finished, click OK.
6. Provide necessary restrictions to the entire IIS:
• Select the root node with your hostname in the lefthand pane.
• Locate the “ISAPI and CGI Restrictions” icon on the right.
• Right click on the “ISAPI and CGI Restrictions” icon and select “Open Feature”.
• Right click and select “Edit Feature Settings…”
• Ensure that both “Allow unspecified CGI modules”, and “Allow unspecified ISAPI modules” are checked.
• When finished, click OK.
7. Create an IIS Plugin configuration file:
• Create a c:\inetpub\Portal90\iisproxy.ini file which contains the following lines. (The file should be placed in the same directory as the two plug-in DLL files that were mentioned at the top of this document.) Set the values appropriately for your environment.
#For a list of all available parameters see:
#http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143049
#
WebLogicHost=<hostname or IP of the WebLogic server to forward requests to>
WebLogicPort=<HTTP port of WebLogic server to forward requests to>
DebugConfigInfo=OFF
Debug=OFF
#
#To proxy all IIS directed requests to WebLogic, set “WlForwardPath=/”
#
#To selectively proxy only PeopleSoft requests to WebLogic, set “WlForwardPath=” to
#the list of PeopleSoft sites to proxy.
#e.g. To proxy requests for only the ‘ps’ and ‘crm’ sites, set WlForwardPath to the following:
#WlForwardPath=*/ps/*,*/crm/*
WlForwardPath=/
#
#If you have specified an AuthTokenDomain during your PIA installation,
#you must set the cookieName for your reverse proxy.
WLCookieName=<CookieName as specified on WebLogic in PORTAL webapps’s weblogic.xml>
8. Restart Microsoft IIS:
• Restart the two Windows services: IIS Admin Service, and World Wide Web Publishing Service.
Also, restart your new web site by right clicking on the new Web Site, and selecting: Manage Web Site ? Restart or Start if not started.
9. Start the WebLogic server.
• See Starting WebLogic.
• See Stopping WebLogic.
10. Test your configuration by accessing the Microsoft IIS server by using the URL for your site.
For example, http://IIS_server:port/ps/signon.html.
Note. To connect to Microsoft IIS by using HTTPS, you must install digital certificates on the Microsoft IIS server.
11. Go back to the beginning of this section to create a second web site. Make sure you use a different folder to store the iisproxy.ini, iisproxy.dll and iisforward.dll files for each web site.
See Also:
Installing and Configuring the Microsoft IIS7.0 Plug-In: http://download.oracle.com/docs/cd/E15523_01/web.1111/e14395/isapi.htm#BGBFJAEJ
Parameters for Web Server Plug-Ins: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143049
