Monday, 15 September 2014
Tuesday, 13 May 2014
IIS 7 Configuration
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
Thursday, 8 May 2014
how to change the PSNT to PSNT1
hi ps gurus.
i have an issue with process scheduler server PSNT.
client requirement is to show the PSNT1 instead of PSNT
is it possible to make rename, if it is possible, in how many table we have to change the PSNT server name.
with regards
durga prasad
i have an issue with process scheduler server PSNT.
client requirement is to show the PSNT1 instead of PSNT
is it possible to make rename, if it is possible, in how many table we have to change the PSNT server name.
with regards
durga prasad
Thursday, 10 April 2014
ORA-12557: TNS:protocol adapter not loadable
Uninstall Client Oracle Software and Reinstall. nothing else
Friday, 4 April 2014
How to configure the Application online Help in peoplesoft 8.53
Configure
Online help for PeopleTools 8.53 and Application FSCM 92
a)
Configure
Online People Books for PeopleSoft PeopleTools 8.53
b)
Configure
Online People Books for PeopleSoft Application FSCM 9.2
a)
Configure
Online People Books for PeopleSoft PeopleTools 8.53
1)
Download PeopleSoft PeopleTools 8.53 Online Help
- Revision 1 (V37628-01.zip) file from Oracle Software Delivery Cloud.
2)
Unzip this file to
D:\PS\webserv\FI92PRD\applications\peoplesoft\PORTAL.war
You can
find pt853pbr1 folder under the
PORTAL.war
Now
open PIA , Go to Main Menu à
People Tools à
Web Profile à
Web Profile Configuration
Help URL: In this text field you have to specify the
URL like below for the Help link in PIA
3)
Shutdown the Application Server and Web Server
and delete the cache of both the domains and restart the two domains. Log on to
PIA , you can find the Help link at the
top-right corner of PIA.
Testing: open PIA
and go to any page than click Help link, it
will open a new browser with the page
information.
b)
Configure
Online People Books for PeopleSoft Application FSCM 9.2
1)
Download PeopleSoft Application PeopleSoft
Financials and Supply Chain Management 9.2 Online Help (through Update Image 4)
from Oracle Software Delivery Cloud.
2)
Create one new folder. Copy downloaded zip file
to the new folder and unzip it. After unzipping it will create one folder name
with fscm92pbr2. Open this folder,
here you can find 2 zip files (apphelp.zip
and helpupdate76782.zip) and one text file (README.txt). Open the text file, here we can see all the steps how
to configure the application online books.
3)
Copy the content in the README.txt and paste it to Word Document.
4)
Extract the contents of apphelp.zip to the
folder where you extracted the PeopleTools online help files.
D:\PS\webserv\FI92PRD\applications\peoplesoft\PORTAL.war\ pt853pbr1
5)
Check the revision number of the common.js file
in your installed PeopleSoft Online Help website to determine whether you need
to install the update to the PeopleSoft Online Help website
(helpupdate76782.zip).
6)
Open the installed common.js file through web
browser.
Check the $revision number (66117r1$), If no revision information appears, or if the revision number is less than the number that appears at the beginning of this README.txt (76782$) file, then you need to install the update to the PeopleSoft Online Help website.
Now it has the $revision number 66117$ and it is less than the 76782$.
That means you have to update the
PeopleSoft Online Help website with helpupdate76782.zip
file.
Unzip and merge this helpupdate76782.zip file to
D:\PS\webserv\FI92PRD\applications\peoplesoft\PORTAL.war\ pt853pbr1
7)
Open common.js in a text editor which is located
in
D:\PS\webserv\FI92PRD\applications\peoplesoft\PORTAL.war\pt853pbr1\js
folder
8)
Uncomment lines for product line that are not
installed by using //
//prodlines[prodlines.length] =
"crm"; //Customer
Relationship Management
//prodlines[prodlines.length] =
"elm"; //Enterprise Learning
Management
//prodlines[prodlines.length] =
"epm"; //Enterprise
Performance Management
prodlines[prodlines.length] =
"fscm"; //Financials Supply
Chain Management
//prodlines[prodlines.length] =
"hcm"; //Human Capital
Management
//prodlines[prodlines.length] =
"cs"; //Campus Solutions
prodlines[prodlines.length] =
"pt"; //PeopleTools
//prodlines[prodlines.length]
= "ps"; //Portal Solutions
And save it.
9)
Shutdown the Application Server and Web Server
and delete the cache of both the domains and restart the two domains.
Testing:
open PIA and go to any Application related page than click Help link, it will open a new browser with
the page information.
Friday, 21 March 2014
Tuxedo tuning
Tuning Tuxedo Processes using PeopleSoft delivered tools
PeopleSoft delivers tools that can be used to monitor the
Tuxedo processes themselves. You can
gather data on which servers are being used, how many clients are connected,
who is connected, what types of services they are accessing and what the
running services are doing. The Tuxedo
command line can be accessed by running psadmin and selecting option 5 from the
main administration menu: 5) TUXEDO command line (tmadmin) A list of all commands available can be
accessed by typing “help” on the command line.
There are a couple of commands that can be used on a regular basis to
obtain a fairly accurate assessment of what the application server is up to.
·
psr:
printserver This will
print server statistics on a per server basis.
This is a great command to use to figure out which servers are working
the most. The last column – Current
Service will tell you the services that are being run at the time that you
issue the command. The defined services
can be obtained by typing:
·
psc: print service This will print
out a list of all of the services that have been defined to the application
server, and how often that service has been accessed. This is invaluable for obtaining information
about what services users are accessing most.
This information can be used to size servers accordingly, i.e. adding or
reducing the number of active servers.
·
pclt: print client This will print information about
users accessing the Application Server, and which client computers they are
accessing from. Client status is also
obtained with this command – Busy, Wait, etc..
·
pq: print queue This will print out
information about requests that are currently in the queue. This information is invaluable for sizing the
number of servers (psappsrv, pssamsrv, psqcksrv) that are needed for any given
environment. The general rule is that
there should never be more than 5 requests in a queue at a given time. A more realistic approach is that no more
than 3 requests should be in a single queue at any given time. If there are more than three requests in a
queue, chances are that people will notice a performance change.
Some services take longer than others, given what they are
doing. RAMLIST, which handles drop down
list boxes takes a much shorter time than PPRLOAD or PPRSAVE, which handle
panel builds and panel saves, respectively.
The quick services should never be queued for more than a few seconds,
since they process quickly. If your
“quick” services are being queued, you should make sure that enough psqcksrv
servers are running.
You can monitor which queues are slowing things down using pq. You can
see what clients are accessing the Tuxedo domain using pclt. You can find out which servers are being used
the most using psr.
Also, since the Tuxedo processes (servers) that interact
with the database on behalf of the client are not multithreaded, they are
executing a single command at a time.
This means that if you have a service in a queue that is taking an
excessive amount of time in the database, other processes may have to wait
behind it in the queue, If no other servers are available. This would equate to a loss of
performance. This is a perfect example
of why one would want to monitor queues.
If you have 4 PSQCKSRV servers running, expect to see an equal amount of
work done by each process. If all
instances are busy, and additional services are waiting in queue, it is an
indication that you need more servers.
The psr command explained
The following screen shot shows the output of the psr
command:
> psr
Prog Name Queue Name Grp Name
ID RqDone Load Done Current Service
--------- ---------- --------
-- ------ --------- ---------------
BBL 40448 SITE1 0
196 9800 ( IDLE )
PSAPPSRV APPQ APPSRV 1
299 14950 ( IDLE )
PSAUTH 00001.00001 BASE 1
158 7900 ( IDLE )
PSAPPSRV APPQ APPSRV 2
316 15800 ( IDLE )
PSAPPSRV APPQ APPSRV 3
318 15900 ( IDLE )
PSQCKSRV QCKQ APPSRV 50
4512 225600 ( IDLE )
PSQCKSRV QCKQ APPSRV 51
4432 221600 ( IDLE )
PSQCKSRV QCKQ APPSRV 52
4386 219300 ( IDLE )
PSQCKSRV QCKQ
APPSRV 53 4386
219300 ( IDLE )
PSSAMSRV SAMQ APPSRV 100
1036 51800 ( IDLE )
WSL 00001.00020 BASE 20 0
0 ( IDLE )
·
The Prog Name is the name of the Application Server process that is
being displayed.
·
The Queue Name is used internally by Tuxedo, and does not affect tuning
at this point.
·
The Grp Name is used internally by Tuxedo as well. You can filter on groups.
·
The RqDone column displays the amount of requests processed.
·
The Load Done column is incremented by a specified value every time the
server processes a request or executes a service. This is helpful, because as you are
monitoring, you can tell if the Current
Service is the same from the last refresh time, or if it is a new request.
·
The Current Service displays the name of the Application Server service
that is currently being executed. You
can get a list of all services by typing psc, which will be shown shortly.
The pclt command explained
> pclt
LMID User Name Client Name Time
Status Bgn/Cmmt/Abrt
--------------- ---------------
--------------- -------- ------- -------------
SITE1 psoftfn WSH 28:06:43 IDLE 0/0/0
SITE1 psoftfn WSH 28:06:43 IDLE 0/0/0
SITE1 psoftfn WSH 28:06:43 IDLE 0/0/0
SITE1 AKUAN STN5 2:29:53 BUSY/W 0/0/0
SITE1 AGEPIGON STATION 3 0:03:15 IDLE/W 0/0/0
SITE1 AGEPIGON
STATION 3 0:04:37
IDLE/W 0/0/0
SITE1 psoftfn tmadmin 2:16:45 IDLE 0/0/0
·
The User Name column displays the name of the User, as defined in
PeopleSoft
·
The Client Name column displays the NetBIOS name of the computer that
the client is accessing the application server from.
·
The Time column displays the time in HH:MM:SS that that particular user
has been active. You can deduce from the
Time status of some servers (WSH) how long the application server has been up
and running.
·
The Status column shows the current status of that client. Busy indicates that the client has requests
pending in the application server.
·
Bgn/Cmmt/Abrt – Begin/Commit/Abort Transaction data
The pq command explained
> pq
Prog Name Queue Name
# Serve Wk Queued # Queued Ave. Len
Machine
--------- ------------------- --------- --------
-------- -------
PSQCKSRV QCKQ 4 - 0 -
SITE1
PSAUTH 00001.00001 1
- 0 -
SITE1
PSSAMSRV SAMQ 1 - 0 -
SITE1
WSL 00001.00020 1
- 0 -
SITE1
BBL 40448 1 - 0 -
SITE1
PSAPPSRV APPQ 3 - 0 -
SITE1
·
Prog Name is the name of the PeopleSoft-defined server that will
run. PSQCKSRV handles non-conversational
SQL calls. PSAUTH is the server that
handles logins to the PeopleSoft database, PSSAMSRV handles conversational SQL
requests. The WSL is the WorkStation
Listener. The WSL handles connections
between the clients and the WorkStation Handler (WSH). The BBL is the Bulletin Board Liaison, and it
oversees all of the processes, servers, and queues. Think of it as acting like an Air Traffic
Controller. Finally, the PSAPPSRV
handles Panel Builds, Panel Saves, and the cache. Each PSAPPSRV started maintains an individual
cache, even within the same domain.
·
The Queue Name column displays a list of currently defined queues. These are used internally. Services for the PSAPPSRV are queued to the
APPQ, services for PSSAMSRV are queued to the SAMQ, and services for the
PSQCKSRV are queued to the QCKQ. A
single queue can service many servers.
If there are four PSQCKSRV servers defined, there is a single queue,
QCKQ that holds PSQCKSRV requests for all four servers.
·
The # Serve column displays the number of the current servers in the
Prog Name column that are currently running. In the above example, the first line indicates
that there are 4 PSQCKSRV processes running.
Each of these processes handles requests from the Queue Name listed above.
·
# Queued displays the number of these types of services currently
in queue. If you have a lot of services
in queue, something is wrong with your configuration. You should rarely see queued services.
Tuesday, 18 March 2014
how to install the weblogic through command line
how to execute the weblogic .jar file through command prompt.
1) open command prompt
2) go to where the jarfile is located
example
C:\Weblogic>java -jar wls1036_generic.jar
(Here wls1036_generic.jar located in C:\WebLogic\wls1036_generic.jar)
crystal installation in peoplesoft 8.53
Use of Crystal Reports for PeopleSoft
1) Crystal Reports allows you to generate both standard and custom-printed reports containing data from your PeopleSoft applications.
2) We can use Crystal Reports 2011 or Crystal Reports 2008 to create and edit report definitions for your PeopleSoft application.
3) PeopleSoft applications are configured to work with Crystal Reports runtime environments.
4) This runtime engine supported for both Crystal Reports versions for PeopleSoft PeopleTools 8.53 and .NET Framework 4 (Crystal Reports version for Visual Studio 2010)
5) If you use PeopleTools 8.53 and the Applications 9.2 or 9.1 use Crystal Reports 2008 formate.
6) Download Crystal Reports 2008 trail version and .Net Framework 4 (Crystal Reports version for Visual Studio 2010) from www.sap.com/sapcrystal.
7) Install the Crystall Reports 2008 and .Net Framework 4
8) Crystal Executables are installed on "C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86".
9) You have to assign this Executable path to CrystalEXEPath Variable under the Crystal in the Process Scheduler Configuration file psprcs.cfg
10) Assign this executale path in configuration manager Crystal/Bus. Interlink/JDeveloper tab and assing the peoplesoft C:\PT8.53\crw path to Default Crystal Reports.
11) Install PeopleSoft ODBC Driver and Crystal Runtime by psodbccrinst.exe
which is located in C:\PT8.53\bin\client\winx86\psodbccrinst.exe
12) Run the psodbccrinst.exe, this installation performs Install PeopleSoft ODBC driver, Create PeopleSoft People Tools ODBC Data Source Name and Integrates the SAP Crystal Reports .NET runtime engine for Framework 4 with the PeopleSoft environment.
13) Check the whether the PeopleSoft ODBC driver and DSN installed or not while running the odbcad32.exe file which is located in C:\Windows\SysWOW64\odbcad32.exe
14) Reconfigure the Process Scheduler Domain and make it up and running.
15) Login PIA and run one crystal job to test our configurations settings are for crystal reports working properly. Run status must be Success and Distrubution Status must be Posted.
1) Crystal Reports allows you to generate both standard and custom-printed reports containing data from your PeopleSoft applications.
2) We can use Crystal Reports 2011 or Crystal Reports 2008 to create and edit report definitions for your PeopleSoft application.
3) PeopleSoft applications are configured to work with Crystal Reports runtime environments.
4) This runtime engine supported for both Crystal Reports versions for PeopleSoft PeopleTools 8.53 and .NET Framework 4 (Crystal Reports version for Visual Studio 2010)
5) If you use PeopleTools 8.53 and the Applications 9.2 or 9.1 use Crystal Reports 2008 formate.
6) Download Crystal Reports 2008 trail version and .Net Framework 4 (Crystal Reports version for Visual Studio 2010) from www.sap.com/sapcrystal.
7) Install the Crystall Reports 2008 and .Net Framework 4
8) Crystal Executables are installed on "C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86".
9) You have to assign this Executable path to CrystalEXEPath Variable under the Crystal in the Process Scheduler Configuration file psprcs.cfg
10) Assign this executale path in configuration manager Crystal/Bus. Interlink/JDeveloper tab and assing the peoplesoft C:\PT8.53\crw path to Default Crystal Reports.
11) Install PeopleSoft ODBC Driver and Crystal Runtime by psodbccrinst.exe
which is located in C:\PT8.53\bin\client\winx86\psodbccrinst.exe
12) Run the psodbccrinst.exe, this installation performs Install PeopleSoft ODBC driver, Create PeopleSoft People Tools ODBC Data Source Name and Integrates the SAP Crystal Reports .NET runtime engine for Framework 4 with the PeopleSoft environment.
13) Check the whether the PeopleSoft ODBC driver and DSN installed or not while running the odbcad32.exe file which is located in C:\Windows\SysWOW64\odbcad32.exe
14) Reconfigure the Process Scheduler Domain and make it up and running.
15) Login PIA and run one crystal job to test our configurations settings are for crystal reports working properly. Run status must be Success and Distrubution Status must be Posted.
Subscribe to:
Comments (Atom)