This guide provides a basis for parameter and application tuning for IBM® WebSphere® Portal for Multiplatforms Version 6.1.X. Remember that both tuning and capacity are affected by many factors, including the workload scenario and the performance measurement environment. For tuning, the objective of this paper is not to recommend that you use the values we used when measuring our scenarios, but to make you aware of those parameters used in our configuration. When tuning your individual systems, it is important to begin with a baseline, monitor the performance metrics to determine if any parameters should be changed and, when a change is made, monitor the performance metrics to determine the effectiveness of the change.
This updated version of the tuning guide for WebSphere Portal 6.1/6.1.0.X. This update includes newly added tuning sections for z/OS, Solaris, Oracle and much more.
Performance tuning overview
Tuning a WebSphere Portal environment involves tuning and configuring the various systems and components of the environment. This chapter discusses some general concepts and details the specifics of the configuration used in our measurement environments. These specifics entail:
Configuring the application server and the resources defined for that application server
Tuning the database(s) and database server
Tuning the directory server and its database
Tuning the web server and/or proxy server
Tuning the operating system and network
Tuning the WebSphere Portal services
When tuning your individual systems, it is important to begin with a baseline, monitor the performance metrics to determine if any parameters should be changed and, when a change is made, monitor the performance metrics to determine the effectiveness of the change.
In addition to the tuning changes we made in our measurement environments, there are some additional tuning options available which can improve performance in certain circumstances; these will be discussed in a separate section.
Please click here for PDF
Friday, November 12, 2010
WebSphere Portal startup problem
How to Troubleshoot a WebSphere Portal startup problem
This guide will teach you how to troubleshoot a WebSphere Portal startup failure. For the purposes of this guide, a startup failure is defined as being unable to render Portal in the web browser after starting the WebSphere_Portal server even though the server is 'open for e-business'.
When accessing WebSphere Portal in a browser, it is important to keep in mind that you are simply accessing the wps.ear application within the WebSphere_Portal server.
Even though you may see the 'open for e-business' message for the WebSphere_Portal server, this does not guarantee that the wps.ear application itself started successfully.
We will explore three common scenarios:
1. '404 Initialization of one or more services failed' in browser
2. '404 Page Not Found' in browser
3. 'A WebGroup/Virtual Host to handle /wps/portal has not been defined.' or 'Error 404: No target servlet configured for uri: /wps/portal ' in browser
To begin troubleshooting these failures, you will only need the SystemOut.log. This log is located by default in the following directories for Portal v6.0 and v6.1:
Portal v6.0: /log
Portal v6.1: /logs/WebSphere_Portal/
Scenario 1: '404 Initialization of one or more services failed'
If you see this message in your web browser, this is a definitive sign that the wps.ear application failed to start correctly. This can occur for numerous reasons and is often difficult to determine where to start investigating. The following steps should help you determine which errors are relevant:
1. Open the SystemOut.log for the WebSphere_Portal server
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):
Start Display Current Environment
.......
* End Display Current Environment *
HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'
HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:
TRAS0017I: The startup trace state is *=info
If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.
3. Find the following line during this startup attempt:
WSVR0200I: Starting application: wps
4. Find the following line during this startup attempt:
WSVR0221I: Application started: wps
5. Note all error messages that occur between these two lines. These are the ONLY error messages you need to be concerned with. Every other error message that you may see outside of these two lines are irrelevant.
6. See if you can find any “Caused By:” statements in the error messages. These are the most important errors and are the root cause of the issue.
7. wps.ear can fail to start for a variety of reasons so it is not possible to document here every possible issue for a startup failure. If the error message is not obvious, search the WebSphere Portal Support site for any error codes you find to see if there are any known documented issues or apars.
http://www-01.ibm.com/software/genservers/portal/support/
For example, suppose you see messages like this:
[9/10/08 16:16:22:081 CDT] 00000017 VaultServiceI E com.ibm.wps.services.credentialvault.VaultServiceImpl checkSystemDNInitialized EJPSK0028E: Invalid system user DN 'systemcred.dn' property value. Ensure that the DN value is valid in the vault service properties file.
com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=defaultWIMFileBasedRealm
.
.
.
Caused by: com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4001E The 'uid=wpsadmin,o=defaultWIMFileBasedRealm' entity was not found.
at com.ibm.ws.wim.adapter.file.was.FileData.getByDN(FileData.java:929)
at com.ibm.ws.wim.adapter.file.was.FileAdapter.get(FileAdapter.java:798)
You would search for the error codes:
CWWIM4001E EJPSK0028E EJPSG0002E
Scenario 2: 'Page Not Found'
If you see this message in the browser, this typically means one of the following:
- The WebSphere_Portal server is not started
- You are using the wrong port number
- You are using the wrong hostname
For this scenario, we will assume that the server is actually started. The correct values for the port and hostname , from a WAS perspective, are controlled by the Virtual Host configuration in WAS. You can retrieve this information from the SystemOut.log by following these steps:
1. Open the SystemOut.log for the WebSphere_Portal server.
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):
Start Display Current Environment
.......
* End Display Current Environment *
HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'
HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:
TRAS0017I: The startup trace state is *=info
If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.
3. Find where the wps application is started:
WSVR0221I: Application started: wps
4. A few lines before this line, you should see a line similar to this:
SRVE0250I: Web Module WebSphere Portal Server has been bound to default_host[*:10000,*:80,*:10002,*:10038,*:10035].
This line shows you which virtual host wps is mapped to, along with which ports and hostnames are valid. In this example, you see *. This means that any hostname that is valid for the operating system will work here. In some cases you might see a specific hostname:
SRVE0250I: Web Module WebSphere Portal Server has been bound to default_host[hostname:10000,hostname:80,hostname:10002,hostname:10038,hostname:10035].
This means that in order to access this application, you must explicitly use this hostname.
5. Find in the log where the server is open for e-business:
WSVR0001I: Server WebSphere_Portal open for e-business
6. A few lines before this line, you will see several ports being initialized. Check which port is being initialized for WCInboundDefault:
TCPC0001I: TCP Channel TCP_2 is listening on host * (IPv4) port 10038.
CHFW0019I: The Transport Channel Service has started chain WCInboundDefault.
This port must be listed as one of the ports from step 4. This is the port you must use to access wps.
7. Ensure that you are using the correct hostname from step 4 (if *, this can be any valid hostname for the OS) and the correct port from step 6.
http://hostname:port/wps/portal
Scenario 3: 'A WebGroup/Virtual Host to handle /wps/portal has not been defined.' or 'Error 404: No target servlet configured for uri: /wps/portal'
If you see this exception, this means one of the following:
– wps.ear has been uninstalled
– wps.ear is no longer mapped to the WebSphere_Portal server or the Cluster
– The context root for wps.ear is no longer /wps/portal
Follow these steps to determine if something has happened to wps.ear:
1. Open the SystemOut.log
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):
Start Display Current Environment
.......
* End Display Current Environment *
HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'
HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:
TRAS0017I: The startup trace state is *=info
If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.
3. Find the following line during this startup attempt:
WSVR0200I: Starting application: wps
NOTE: If you do not see this line, this is a clear indication that wps has either been uninstalled or is no longer mapped to your server. To check this, do the following:
• Login to server1 or the DMGR
• Navigate to Applications -> Enterprise Applications
• Search for wps
• If do not find it, it has been uninstalled. If you do find it, click the link for it.
• For WAS v6.0.x, click 'Map modules to servers'
For WAS v6.1.x, click 'Manage Modules'
• Ensure that WebSphere_Portal if standalone or the ClusterName if clustered is mapped correctly for this application
4. Assuming you find the line in step 3, double check the context root. Several lines after this line, you should see a line like this:
SRVE0242I: [wps] [/wps] [portal]: Initialization successful.
This is your context root. In this example, it is:
/wps/portal
This can vary. For example:
SRVE0242I: [wps] [/contextRoot] [portal]: Initialization successful.
In this case, it is: /contextRoot/portal
This is what you should be typing to access Portal.
This guide will teach you how to troubleshoot a WebSphere Portal startup failure. For the purposes of this guide, a startup failure is defined as being unable to render Portal in the web browser after starting the WebSphere_Portal server even though the server is 'open for e-business'.
When accessing WebSphere Portal in a browser, it is important to keep in mind that you are simply accessing the wps.ear application within the WebSphere_Portal server.
Even though you may see the 'open for e-business' message for the WebSphere_Portal server, this does not guarantee that the wps.ear application itself started successfully.
We will explore three common scenarios:
1. '404 Initialization of one or more services failed' in browser
2. '404 Page Not Found' in browser
3. 'A WebGroup/Virtual Host to handle /wps/portal has not been defined.' or 'Error 404: No target servlet configured for uri: /wps/portal ' in browser
To begin troubleshooting these failures, you will only need the SystemOut.log. This log is located by default in the following directories for Portal v6.0 and v6.1:
Portal v6.0: /log
Portal v6.1: /logs/WebSphere_Portal/
Scenario 1: '404 Initialization of one or more services failed'
If you see this message in your web browser, this is a definitive sign that the wps.ear application failed to start correctly. This can occur for numerous reasons and is often difficult to determine where to start investigating. The following steps should help you determine which errors are relevant:
1. Open the SystemOut.log for the WebSphere_Portal server
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):
Start Display Current Environment
.......
* End Display Current Environment *
HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'
HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:
TRAS0017I: The startup trace state is *=info
If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.
3. Find the following line during this startup attempt:
WSVR0200I: Starting application: wps
4. Find the following line during this startup attempt:
WSVR0221I: Application started: wps
5. Note all error messages that occur between these two lines. These are the ONLY error messages you need to be concerned with. Every other error message that you may see outside of these two lines are irrelevant.
6. See if you can find any “Caused By:” statements in the error messages. These are the most important errors and are the root cause of the issue.
7. wps.ear can fail to start for a variety of reasons so it is not possible to document here every possible issue for a startup failure. If the error message is not obvious, search the WebSphere Portal Support site for any error codes you find to see if there are any known documented issues or apars.
http://www-01.ibm.com/software/genservers/portal/support/
For example, suppose you see messages like this:
[9/10/08 16:16:22:081 CDT] 00000017 VaultServiceI E com.ibm.wps.services.credentialvault.VaultServiceImpl checkSystemDNInitialized EJPSK0028E: Invalid system user DN 'systemcred.dn' property value. Ensure that the DN value is valid in the vault service properties file.
com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=defaultWIMFileBasedRealm
.
.
.
Caused by: com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4001E The 'uid=wpsadmin,o=defaultWIMFileBasedRealm' entity was not found.
at com.ibm.ws.wim.adapter.file.was.FileData.getByDN(FileData.java:929)
at com.ibm.ws.wim.adapter.file.was.FileAdapter.get(FileAdapter.java:798)
You would search for the error codes:
CWWIM4001E EJPSK0028E EJPSG0002E
Scenario 2: 'Page Not Found'
If you see this message in the browser, this typically means one of the following:
- The WebSphere_Portal server is not started
- You are using the wrong port number
- You are using the wrong hostname
For this scenario, we will assume that the server is actually started. The correct values for the port and hostname , from a WAS perspective, are controlled by the Virtual Host configuration in WAS. You can retrieve this information from the SystemOut.log by following these steps:
1. Open the SystemOut.log for the WebSphere_Portal server.
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):
Start Display Current Environment
.......
* End Display Current Environment *
HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'
HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:
TRAS0017I: The startup trace state is *=info
If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.
3. Find where the wps application is started:
WSVR0221I: Application started: wps
4. A few lines before this line, you should see a line similar to this:
SRVE0250I: Web Module WebSphere Portal Server has been bound to default_host[*:10000,*:80,*:10002,*:10038,*:10035].
This line shows you which virtual host wps is mapped to, along with which ports and hostnames are valid. In this example, you see *. This means that any hostname that is valid for the operating system will work here. In some cases you might see a specific hostname:
SRVE0250I: Web Module WebSphere Portal Server has been bound to default_host[hostname:10000,hostname:80,hostname:10002,hostname:10038,hostname:10035].
This means that in order to access this application, you must explicitly use this hostname.
5. Find in the log where the server is open for e-business:
WSVR0001I: Server WebSphere_Portal open for e-business
6. A few lines before this line, you will see several ports being initialized. Check which port is being initialized for WCInboundDefault:
TCPC0001I: TCP Channel TCP_2 is listening on host * (IPv4) port 10038.
CHFW0019I: The Transport Channel Service has started chain WCInboundDefault.
This port must be listed as one of the ports from step 4. This is the port you must use to access wps.
7. Ensure that you are using the correct hostname from step 4 (if *, this can be any valid hostname for the OS) and the correct port from step 6.
http://hostname:port/wps/portal
Scenario 3: 'A WebGroup/Virtual Host to handle /wps/portal has not been defined.' or 'Error 404: No target servlet configured for uri: /wps/portal'
If you see this exception, this means one of the following:
– wps.ear has been uninstalled
– wps.ear is no longer mapped to the WebSphere_Portal server or the Cluster
– The context root for wps.ear is no longer /wps/portal
Follow these steps to determine if something has happened to wps.ear:
1. Open the SystemOut.log
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):
Start Display Current Environment
.......
* End Display Current Environment *
HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'
HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:
TRAS0017I: The startup trace state is *=info
If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.
3. Find the following line during this startup attempt:
WSVR0200I: Starting application: wps
NOTE: If you do not see this line, this is a clear indication that wps has either been uninstalled or is no longer mapped to your server. To check this, do the following:
• Login to server1 or the DMGR
• Navigate to Applications -> Enterprise Applications
• Search for wps
• If do not find it, it has been uninstalled. If you do find it, click the link for it.
• For WAS v6.0.x, click 'Map modules to servers'
For WAS v6.1.x, click 'Manage Modules'
• Ensure that WebSphere_Portal if standalone or the ClusterName if clustered is mapped correctly for this application
4. Assuming you find the line in step 3, double check the context root. Several lines after this line, you should see a line like this:
SRVE0242I: [wps] [/wps] [portal]: Initialization successful.
This is your context root. In this example, it is:
/wps/portal
This can vary. For example:
SRVE0242I: [wps] [/contextRoot] [portal]: Initialization successful.
In this case, it is: /contextRoot/portal
This is what you should be typing to access Portal.
Subscribe to:
Posts (Atom)
