What kind of problem are you seeing?
ActiveX client fails to display ASP files,
or WebSphere Application Server resources
(JSP files, servlet, or HTML pages) or both
A possible
cause of this problem is that both IIS for serving Active Server Pages
(ASP) files and an HTTP server that supports WebSphere Application Server (such as IBM® HTTP
Server) are deployed on the same host. This deployment leads to misdirected
HTTP traffic if both servers are listening on the same port (such
as the default port 80).
To resolve this problem, either:
- Open the IIS administrative panel, and edit the properties of
the default web server to change the port number to a value other
than 80
- Install IIS and the HTTP server on separate servers.
For current information available from IBM Support
on known problems and their resolution, see the IBM Support page.
Plants by WebSphere Catalog Manager
(pbwsCatalogMgr) exceptions
When you federate a stand-alone
server into a Deployment Manager cell, the bootstrap port number of
the application server may change. This will cause the client to not
be able to communicate with the server, thus causing an exception.
The following scenario may cause an exception when you start Plants
by WebSphere:
- Install a stand-alone WebSphere Application Server.
- Run the Plants by WebSphere example.
- Create a Deployment Manager (DMGR) using
the Profile Management tool or by using the manageprofiles command.
- Federate the stand-alone WebSphere Application Server into a Deployment
Manager cell using the addNode command.
- Start pbwsCatalogMgr.
To
avoid the exception, locate the new (changed) port number on the server
and modify the client configuration to match the port number on the
server.
- Go to was_server_root\profiles\your_server_name\config\cells\your_cell\nodes\your_node.
- Open the serverindex.xml file.
- Locate the BOOTSTRAP_ADDRESS port number of the application server,
for example 9810.
- Assign this port number to the client to communicate with your
newly-federated application server. Go to was_client_root\bin and
edit the setupClient.bat file.
- Locate the line 'SET SERVERPORTNUMBER' and set the value for it
to 9810.
If you have security enabled, ensure that the bus security
is also enabled and that a user is defined to the bus connector role
before running pbwsCatalogMgr.
- Restart the node agent and the application server.
The client is now properly set up to start pbwsCatalogMgr.
IBM Support has documents that can save you time
gathering information needed to resolve this problem. Before opening
a PMR, see the IBM Support page.