If you experience problems with the Configuration Console,
before calling IBM Software Support, review this list of the most
common problems encountered while using the Configuration Console:
- I cannot see the Configuration Console Login screen.
- Do you see the message "The page cannot be displayed"?
- The Configuration Console URL is probably incorrect. Retype the
URL. If you are unsure of the correct URL, contact your system administrator
or internal technical support for assistance.
- Other potential reasons: The port that connects your machine to
the embedded WebSphere Application Server might be blocked, or the
embedded WebSphere Application Server might not be started. Contact
your system administrator or internal technical support for assistance.
- Is the screen blank?
- Contact your system administrator or internal technical support.
The port that connects your machine to the embedded WebSphere Application
Server might not be started, or the Configuration Console database
password might have changed.
- If none of these solutions resolves the problem, contact your
system administrator or internal technical support for assistance.
- I cannot log in to the Configuration Console.
- Make sure that you are entering the correct user name and password.
The Configuration Console does not lock user accounts, regardless
of the number of incorrect login attempts, so try entering your user
name and password again.
- If you have forgotten your user name and password, contact your
system administrator or internal technical support for assistance.
You might need to have your password reset.
- A report opens in the Web browser, but nothing displays
on the report.
- If you see the wait cursor (HourGlass), wait a minute or two more,
because the report might still be generating. As the system is generating
a report, it starts by displaying a blank screen in the browser. Once
the report has generated and is ready for display, the system displays
the report.
- If you see an About: screen, but the screen
is blank, review your Microsoft Internet Explorer browser settings.
You might need to adjust these Web browser settings before Configuration
Console reports display.
- Make sure that your Configuration Console HTTP address is included
on the list of trusted Internet Web sites. (This setting is located
under the security settings for trusted Internet sites.) If the Configuration
Console is not on the list of trusted Web sites, add it.
- Make sure that all download options are enabled for your trusted
Internet Web sites. (This setting is located under the custom level
security settings for trusted Internet sites.) If you need to, enable
any of the download options that are currently disabled.
- If the Internet Explorer pop-up blocker is enabled, make sure
that the HTTP address for the Configuration Console instance is on
the list of Web sites that allow pop-ups. (This setting is located
under the popup blocker settings.) If the Configuration Console is
not on the list of Web sites to allow pop-ups, add it.
- Make sure that you have Adobe Acrobat Reader version 7.0 or higher
installed on your local machine. If not, you can download the latest
Adobe Acrobat Reader for free from the Adobe Web site.
- I cannot see the status of a pipeline on the Pipeline
Status tab.
- Do any of the pipelines running on the same pipeline node display
status on the Pipeline Status tab?
- If not, make sure that the pipeline node is running.
- If not, make sure that the SNMP agent is started on the pipeline
node, and that the SNMP agent is using the correct port number. The
default port number value is 13516, but look at the server.xml file
to find the configured SNMP port number.
- Is the pipeline registered on the Pipelines tab?
- If not, register the pipeline. Only pipelines registered on this
tab display in the Pipeline Status tab.
- Does the name of the pipeline on the Pipeline Status tab
match the pipeline name specified as part of the pipeline command
when the pipeline was started?
- On the pipeline node from a command line, enter the pipeline command
to see the status of all pipelines running on that node.
- Configuration changes made in the Configuration Console
are not being honored by the pipeline.
- Before pipelines apply configuration changes, they must be stopped
and restarted. When the pipelines restart, the configuration changes
are applied as part of the pipeline initialization process.
- For data-integrity purposes, stop and restart all running pipelines
after a configuration change.