WebSphere Application Server Network Deployment server problems

These problems and resolutions are related to the services tier and IBM® WebSphere® Application Server Network Deployment.

Resolving IBM WebSphere Application Server installation problems
Use this troubleshooting information when you install IBM WebSphere Application Server with IBM InfoSphere® Information Server.
Installation fails when the IBM WebSphere Application Server Network Deployment port is changed after installation
After you install IBM InfoSphere Information Server, if you change the WebSphere Application Server HTTPS port (WC_defaulthost_secure) by using the IBM WebSphere Application Server administrative console, future installations, product additions, and updates fail.
Errors when you try to add a DataStage connection
An error occurred while adding a DataStage connection to SIEBEL using SIEBEL EIM stage.
Errors when you re-install the IBM WebSphere Application Server after an installation failure
An error occurred while reinstalling the same version of IBM WebSphere Application Server.
Resolving connection problems
An installation might fail because the Domain Name System (DNS) server is unable to resolve system names or because the application server is not running.
Unable to start IBM WebSphere Application Server after the user name changes or expires
If the user name or password that you created for WebSphere Application Server or for the metadata repository changes or expires, the application server does not start.
Adding an IBM WebSphere Application Server administrator user to an internal user registry
If you do not know the WebSphere Application Server administrator user and password, you can create a user in the internal user registry.
Repairing the WebSphere Application Server Network Deployment registry after switching to LDAP
If you have switched from an internal registry to a Lightweight Directory Access Protocol (LDAP) user registry without using the documented procedure, "Switching to an LDAP user registry," you might be unable to stop IBM WebSphere Application Server processes.
Services tier performance
If the services tier is slow, ensure that you have not turned on IBM WebSphere Application Server tracing.