Browse Component: WebSphere Application Server

Product documentation


Abstract

This document provides a list of components regarding IBM® WebSphere® Application Server, explains the type of material covered in technotes grouped by that component, and points you to the collection of those documents.

Content

By clicking a component below, a list of the current technotes categorized under that component will be generated. Your search results will generally contain information regarding tasks, problems, defects and workarounds.

Note:
The results obtained through the Browse Component search will change frequently as new technotes are added and old ones removed.

If there is a particular topic you would like to see added to one of the components or any feedback about the existing content, please submit your comments using the Rate this page section below.


Component Description
100% CPU Usage Includes multiple product categories. 100% CPU usage due to a WebSphere Application Server process.
Administrative Console (all non-scripting) Any problems associated with using the Administrative Console, not including scripting (wsadmin). Does not include problems that occur after changing a setting that causes a change in behavior.
Administrative Scripting Tools (for example, wsadmin or ANT) Problems experienced performing Administration tasks using command line tools
Application Client Problems related to any number of Java™ 2 Platform, Enterprise Edition (J2EE™) supported stand-alone applications that communicate directly with the Application Server.
Application Server Toolkit (AST) A tool for making Enterprise Applications (EARs) deployable in WebSphere Application Server.
Classloader Programming errors or configuration issues that result in programs or classes not being found. Typically you see an error message in the stack track trace or in the browser indicating "class not found".
Crash Process dies (usually generates a core file on UNIX® or a user.dmp on Windows®).
Data Replication Service (DRS) Problems with sharing and replicating cached contents using JMS message broker.
DB Connections/ Connection Pooling Problem with connectivity to the supported relational databases (i.e. DB2®, Oracle, Sybase, etc) using WebSphere Connection Manager.
Deploy
(for example, AAT or ANT or EAR/WAR/JAR)
Problems that occur during the deployment of J2EE application.
Double Byte Character Set (DBCS) Language-specific issues where the character set requires two bytes to store a letter (for example, Kanji).
Dynamic Cache Problems that occur when dynamic cache is enabled, but do not occur if dynamic cache is disable.
Edge Component Problems that occur with Load Balancer or Caching Proxy. Beginning with WebSphere Application Server V5.0, Edge is a component of the Application Server product.
Enterprise JavaBeans Container Problems with Enterprise JavaBeans™.
EJBDeploy (WebSphere Studio Application Developer) Problems with the EJBDeploy tool. Problem determination is handled by the WebSphere Studio Application Developer support group. This is available for alternate reference.
Embedded/Express This should be transparent to a user; however, there are cases when the core WebSphere product that is embedded (such as WebSphere Express) displays problems that can be corrected by WebSphere.
Enterprise Edition (EE) Problems with collections of tools and packages that enable integration to existing Enterprise Infrastructure (for example, IMS and MQ workflow).
General These are process-related issues. Only a few problems fall into this category.
Hangs/Performance Degradation Any problems reporting a hang or degradation in performance in a WebSphere Java™ virtual machine (JVM™). This can include performance problems that occur after upgrading to a newer version of WebSphere Application Server; however, this should not contain performance issues that occur after deploying a new version of a customer application. These types of problems are handled by the IBM Services group.
High Availability (HA) High Availability Manager is a new component for V6.0, providing enabling features like failover, session replication and stateful session bean failover for large cells. Also included is hot failover for Service Integration Technology and transaction logs, replication services and WLM routing.
HTTP Transport Any problems that occur during communication directly to the Application Server (bypassing the plug-in).
IBM HTTP Server Any Web server related problem. IBM HTTP Server is delivered as a WebSphere Application Server component.
Install Problems that might be encountered installing the product, Fix Packs or Interim Fixes. Do not put configuration problems in this category.
Java 2 Connectivity (J2C) Problems using J2C resource adapters within WebSphere (for example, CICS, IMS, SAP).
Java Management Extensions (JMX) or JMX client API Errors with Java Code that uses WebSphere Application Server JMX APIs.
Java Message Service (JMS) Problems with back-end connectivity to Messaging Servers (for example, WebSphere MQ®). See also Service Integration Technology.
Java SDK Problems specific to the JVM (for example, JVM crashes and JIT failures).
Java Security (JSSE/JCE) Problems with implementing Java security with applications using Java Secure Socket Extension (JSSE) defined interfaces.
Java Transaction Service (JTS) JTS provides the internal facilities needed by WebSphere components to coordinate resources that are involved in transactional work. Any specific JTS problems are reported here.
JNDI/Naming Problems with the lookup facility for objects like enterprise beans (Enterprise JavaBeans), data sources.
JSP Problems with JavaServer Pages™ (JSP™) (for example, JSP compilation failures, JSP BatchCompiler problems, and JSP runtime exceptions).
Migration Problems associated with migrating to a new release.
Object Level Trace/ Distributed Debugger (OLT/DD) Problems running this graphical user interface tool.
Object Request Broker (ORB) Problems encountered when managing distributed objects (for example, Enterprise JavaBeans).
Out of Memory Out of memory issues.
PD tools (for example: Log Analyzer) Problems running problem determination stand-alone tools.
Plug-in Any plug-in problem, with the exception of remote installations.
Plug-in (remote) Install Problems related to the installation or configuration of a Web server on system other than WebSphere Application Server.
PMI/Performance Tools Problems with Performance Monitoring Tools, Performance Advisors or with the Interface.
Portlet Container Problems with runtime environment for portlets using JSR 168 Portlet Specification.
Program Model Extensions (PME) A collection of application programming interfaces (APIs) that enables business process solutions, such as Application Profiling, Asynchronous Beans and Object Pools. Scheduler is listed as a separate component.
Proxy server Problems that occur with WebSphere proxy server. Beginning with WebSphere Application Server V6.0.2, WebSphere proxy server is a component of the Application Server Network Deployment and z/OS® editions.
Samples Problems with any of the sample applications that ship with WebSphere Application Server.
Scheduler A programming extension responsible for starting actions at specific times or intervals.
Security Problems that occur only when security is enabled. This includes authentication issues (for example, RACF and LDAP).
Service Data Objects (SDO) Problems with the data-centric, disconnected, XML-integrated, data access mechanism that provides a source-independent result set.
Service Integration Technology A Java-based messaging facility that integrates well into the J2EE environment. This is independent of WebSphere MQ. This component is also the default JMS messaging provider in WebSphere Application Server V6.0.
Servlet Engine/Web Container Problems experienced running servlets.
Sessions and Session Management Problems or errors maintaining HttpSessions (for example: loss of session data or problems with HttpSession failover).
System Management/ Repository Problems starting Network Deployment Edition or Base Application Server, or errors in related Application Server logs.
Trial Any problems related to the Trial (Beta) version of WebSphere Application Server. Currently, beta versions of code are not supported through the normal PMR submission process.
Web Services
(for example: SOAP or UDDI, or WSGW or WSIF)
Problems with technology that invokes services or applications using Internet standards and protocols.
Web Services Security Problems that occur only when security is enabled for Web Services.
Workload Management (WLM) Problems specific to WLM using service classes, application environments or WLM problems that occur in runtime.

Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express General AIX, HP-UX, i5/OS, Linux, Solaris, Windows 7.0, 6.1, 6.0, 5.1

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
General

Software version:

5.1, 6.0, 6.1, 7.0

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows

Software edition:

Base, Express, Network Deployment

Reference #:

7010073

Modified date:

2008-08-14

Translate my page

Machine Translation

Content navigation