Lessons Learned by WebSphere Application Server Support about Version 5.0
 White paper
 
Abstract
The following are observations and suggestions made by the team that supports IBM® WebSphere® Application Server. This includes beta tests, technical support and consultants.
 
 
Content
  1. Are you migrating to WebSphere Application Server V5.0?
    Redbook: Migrating to WebSphere V5.0: An End-to-End Migration Guide
    [ HTML | PDF ]
    Document Number - SG24-6910
    Link to Redbook site http://www.redbooks.ibm.com/
    Documentation on migrating in WebSphere Application Server V5.0 Information Center.

  2. New terminology in WebSphere Application Server V5.0
    1. Important new definitions:

      Managed Process - individual server or process like Application Server or Java™ Message Service (JMS) Server.
      Node
      - Consists of a set of Managed processes, managed through a Node Agent.
      Cell - Aggregation of Nodes.

    2. For more on new terminology, look under the Getting Started section of the WebSphere Application Server V5.0 Information Center for Network Deployment.

  3. WSCP scripts need to be changed as WebSphere Application Server V5.0 has more new objects than V4.0
    Documentation on migrating to wsadmin.

  4. IBM® HTTP Server V2.0 is not available from WebSphere Application Server V5.0 CDs
    You can go to the trials and betas site for IBM HTTP Server and search on "2.0" to find downloads for the released product.

  5. You should back up your configuration right after installing WebSphere Application Server V5.0
    The backupConfig command allows you to save your current configuration. It is recommended that you backup your configuration after initial installation so that you can restore to the default configuration should the repository become corrupt. You can also run backupConfig whenever you make significant administrative changes to your configuration.

    In WebSphere Application Server V4.0, if the database gets corrupted, you could drop the database and recreate it. In Version 5.0, you can use the backupConfig command, and then use the restoreConfig command to restore the configuration.
    Documentation on backupConfig command.

  6. The WebSphere Administrative Repository in Version 5.0 is XML based
    There is no need to install a relational database prior to installing and configuring WebSphere Application Server V5.0.

  7. Classloader default values have changed to Parent First (It was Parent Last in WebSphere Application Server V4.0)
    Documentation on classloading.

  8. Relational Resource Adapter comes pre-installed with WebSphere Application Server V5.0
    Do not modify or delete Resource Adapter, as it is needed for Java™ database connectivity (JDBC™) connections.
    Documentation on relational resource adapter.

  9. Isolation Levels is part of IBM Extension to the Enterprise JavaBeans™ (EJB™) 2.0 Specification
    Isolation Levels are not part of the Java 2 Platform, Enterprise Edition (J2EE™), like in WebSphere Application Server V4.0.
    Documentation on isolation levels.

  10. Name space no longer has single root for entire domain
    When performing lookups in the name space, fully qualified names might be needed (see Information Center). Name space is segmented into transient and persistent areas. Scenarios that include user bindings into the name space need to consider this when determining where that binding should go (see Information Center). When looking up resources in the name space from a client, the .jar files required to instantiate the resource must be in the classpath (Recommendation: Use the Java client setup).
    Documentation on name spaces.

  11. Use command line tools to start and stop servers in a WebSphere Application Server deployment
    Servers that have been created in the base WebSphere Application Server deployment must be started or stopped using the command line tools (for example: startServer, stopServer) until they are added to a Network Deployment Cell using the addNode command.

  12. Server status is unavailable
    If the server status is unavailable, make sure that the node agent is started on the node where the server is located.


Related Resources
Recommended updates for WebSphere Application Server
Cumulative Fix Strategy for WebSphere Application Server V5.0 and V5.1
Java SDK upgrade policy for WebSphere Application Server
 
 
Original publication date
2002/12/12
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 7002412
IBM Group: Software Group
Modified date: Sep 8, 2004