Chapter 8. Portal server troubleshooting
Review the Tivoli Enterprise Portal Servertroubleshooting topics for help with
solving problems you encounter with the portal server.
If you do not find the resolution to your problem, review the topics in Chapter 6,
“Connectivity troubleshooting,” on page 115.
Performance impacts of the HTTP and HTTPS protocols
Connection protocol options between the Tivoli Enterprise Portal client and the
Tivoli Enterprise Portal Server include the default protocol, IIOP, as well as the
HTTP and HTTPS protocols. Note, however, that you might encounter a response
time impact when you use the HTTP and HTTPS protocols. Affected workspaces
include the Linux Process workspace, Linux PAS workspace, and UNIX Process
workspace. These workspace have longer response times when you use the HTTP
Tivoli Enterprise Portal client instead of the CORBA/IIOP Tivoli Enterprise Portal
client. In addition to the response time impact, you might encounter increased
CPU consumption for the HTTP and HTTPS protocols.
Users who run the IBM HTTP Server do not have permission to the
content directory
During configuration and startup of the Tivoli Enterprise Portal Server, the system
attempts to confirm that the user running the IBM HTTP Server has permission to
access the IBM HTTP Server content directory. If not, one of the following
messages are displayed:
KCIIN2723W User who runs IHS (IBM HTTP Server) does not have proper
permissions to IHS content directory. Do you want to continue?
or
KCIIN2724W User who runs IHS (IBM HTTP Server) does not have proper
permissions to IHS content directory.
This error occurs when the IBM HTTP Server is running under a user that does
not match the user specified in the CANDLE_HOME/ARCH/iu/ihs/httpd.conf file. For
the portal server to run correctly, the user who is running the IBM HTTP Server
must have access to the IBM HTTP Server content directory.
tacmd exportWorkspaces or importWorkspaces receives an out of
memory error
If you get an OutOfMemory Error when running this command, you can increase
the maximum Java heap size for the tacmd java JVM by using the
TACMD_JVM_MAX_MEMORY environment variable. This variable specifies the
maximum java heap size (in megabytes) for the tacmd Java virtual system.
Memory for tacmd is freed when the tacmd invocation finishes. Valid values are
256 through to 2048, inclusive.
© Copyright IBM Corp. 2005, 2012 147
To Next Page
Loading...
Need help?
General
