Application deployment troubleshooting tips
When you first test or run a deployed application, you might encounter problems.
Select the problem you are having with testing or the first run
of deployed code for WebSphere® Application Server:
![[AIX Solaris HP-UX Linux Windows]](../images/ngdist.svg)
Application Server start or restart problems.- Application startup problems.
- Web resource is not displayed.
- Data access problems.
- Enterprise bean cannot be accessed from a servlet, a JSP file, a stand-alone program, or another client.
- Application access problems.
- Access problems after enabling security.
- Security enablement followed by errors.
- SSL errors for security.
- Application client SOAP request troubleshooting tips.
- A client program does not work.
You can use the following administrative console pages to inspect
the configuration of your applications and JMS resources:
- For a view of the JMS resources for a given application, see the following page: Messaging resources for this application.
- For a view of the applications and JMS resources for a given default messaging provider destination, see the following page: Application resources for this destination.
If you do not see a problem that resembles
yours, or if the information provided does not solve your problem,
see Troubleshooting help from IBM.
For current information available from IBM Support on known problems and their resolution, see the IBM Support webpage.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the Must gather documents page for information to gather to send to IBM Support page.