This section provides information about how to troubleshoot a problem with your IBM® software.
You can also search live, Web-based support resources by using the customized query fields in the "Web search" page. To find this page, expand Searching knowledge bases in the information center table of contents and select the Web search page for your product. Additional topics include the Troubleshooting Guide, getting fixes, and contacting IBM® support.
Follow these shortcuts to get started quickly with popular tasks.
To debug your application, you must use a development environment like the IBM® Rational® Application Developer for WebSphere® to create a Java project. You must then import the program that you want to debug into the project.
You can add logging and tracing to applications to help analyze performance and diagnose problems in WebSphere Application Server.
Various diagnosis tools are provided to help you determine the source and impact of problems occurring in your application serving environment.
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. This topic describes the conventions in use for WebSphere Application Server.
This page provides a starting point for finding information about ActivitySessions, a WebSphere extension for reducing the complexity of commitment rules and limitations that are associated with one-phase commit resources.
This page provides a starting point for finding information about application profiling, a WebSphere extension for defining strategies to dynamically control concurrency, prefetch, and read-ahead.
This page provides a starting point for finding information about application clients and client applications. Application clients provide a framework on which application code runs, so that your client applications can access information on the application server.
This page provides a starting point for finding information about data access. Various enterprise information systems (EIS) use different methods for storing data. These backend data stores might be relational databases, procedural transaction programs, or object-oriented databases.
This page provides a starting point for finding information about the dynamic cache service, which improves performance by caching the output of servlets, commands, web services, and JavaServer Pages (JSP) files.
This page provides a starting point for finding information about enterprise beans.
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere® Application Server.
This page provides a starting point for finding information about naming support. Naming includes both server-side and client-side components. The server-side component is a Common Object Request Broker Architecture (CORBA) naming service (CosNaming). The client-side component is a Java™ Naming and Directory Interface (JNDI) service provider. JNDI is a core component in the Java Platform, Enterprise Edition (Java EE) programming model.
This page provides a starting point for finding information about the Object Request Broker (ORB). The product uses an ORB to manage communication between client applications and server applications as well as among product components. These Java Platform, Enterprise Edition (Java EE) standard services are relevant to the ORB: Remote Method Invocation/Internet Inter-ORB Protocol (RMI/IIOP) and Java Interface Definition Language (Java IDL).
Find starting points pertaining to security.
This page provides a starting point for finding information about service integration.
This page provides a starting point for finding information about SIP applications, which are Java programs that use at least one Session Initiation Protocol (SIP) servlet written to the JSR 116 specification.
This page provides a starting point for finding information about Java Transaction API (JTA) support. Applications running on the server can use transactions to coordinate multiple updates to resources as one unit of work, such that all or none of the updates are made permanent.
This page provides a starting point for finding information about web applications, which are comprised of one or more related files that you can manage as a unit, including:
This page provides a starting point for finding information about web services.