A client program does not work

What kind of problem are you seeing?

 

ActiveX client fails to display ASP files, or WAS resources (JSPs, 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 WAS (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 admin 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 standalone server into a Deployment Manager cell, the bootstrap port number of the appserver 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:

1. Install a standalone WAS.

2. Run the Plants by WebSphere example.

3. Create a Deployment Manager (DMGR) using the Profile Management tool or by using manageprofiles command.

4. Federate the standalone WAS into a Deployment Manager cell using addNode command.

5. 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.

1. Go to was_server_root\profiles\my_server_name\config\cells\my_cell\nodes\my_node.

   1. Open the serverindex.xml file.

   2. Locate the BOOTSTRAP_ADDRESS port number of the appserver, for example 9810.

2. Assign this port number to the client to communicate with the newly-federated appserver. Go to was_client_root\bin and edit the setupClient.bat file.

3. Locate the line 'SET SERVERPORTNUMBER' and set the value for it to 9810.

   If we have security enabled, verify the bus security is also enabled and that a user is defined to the bus connector role before running pbwsCatalogMgr.

4. Restart the node agent and the appserver.

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.

---

 

Related tasks

Troubleshooting deployment

 

Related

Application deployment troubleshooting tips