Problem:
The user interface is not displayed when starting the wizard.
Cause:
The JVM version may be not correct.
Resolution:
The wizard requires IBM
® JRE 1.5. Make sure that the Java version is correct.
Problem:
1) For primary node installation: A feature can still be selected if its cluster is already installed.
2) For secondary node installation: A cluster already has primary node, but the feature selection box is grayed out.
3) For uninstallation: A cluster is installed, but cannot be selected to uninstall.
Cause:
The installing primary node is not successful.
The uninstalling task is not successful for this node.
It failed to detect the existing clusters from DM.
Resolution:
Check whether it is successful to install primary node.
Check whether it is successful to uninstall this node.
Check the log file to see why it failed.
Problem:
SOAP RPC call time out during adding a node into cluster
Cause:
The SOAP connection timed out between the deployment manager and the application server.
Resolution:
Edit the soap.client.properties file to disable time out. Restart the servers and run the cluster wizard again. The property file is located in {WAS_HOME}/profiles/{Profile_Name}/properties.
Problem:
Fail to set shared folder.
Cause:
Failed to edit the WebSphere
® Application Server variables.
Failed to copy the data from the local directory to share folder.
Resolution:
After running the wizard, perform the following tasks again using instructions located in the information center:
- Edit the WebSphere Application Server variables on the administrative console.
- Copy the data from local to share folder.
Problem: There is a server port conflict on a subsequent node.
Cause:
More than one server process is using the same port.
Resolution:
Delete server processes that are not in the cluster on the WebSphere Application Server administrative console.
Double check whether there is another server process using the port and stop it, if possible.
On the WebSphere Application Server administrative console, change the conflict port for the WebSphere Application Server application server and the default ports in Virtual Host.
This completes Deployment Scenario 1 (S1). See the following link for additional deployment scenarios for Lotus Connections 2.5:
http://www-10.lotus.com/ldd/lcwiki.nsf/xpViewTags.xsp?categoryFilter=2.5_deployment&lookupName=Deployments
Table of Contents:
Lotus Connections 2.5 network deployment scenario