WebSphere Network Deployment
Planning and installation

 

+

Search Tips   |   Advanced Search

 

Overview

1. Gather information

2. Collect and install interim fixes and fix packs using the update installer application. Also known as the updateInstaller or the update installation wizard.

3. To the base WAS package, the WAS Network Deployment package adds:
   • Clustering
   • Workload management (weighted bind policy)
   • Failover
   • Distributed security
   • Distributed naming
   • Distributed systems administration
   • Single-system image
   • Cluster creation and management
   • Application distribution
   • Monitoring

4. Multiple node environments are created by federating multiple WAS installations into cells, each of which is managed by a deployment manager provided by a Network Deployment installation.

5. Use the addNode command to federate the configuration of a stand-alone WAS installation into a cell-wide configuration store for distributed management.

   When you migrate to V5, the configuration from the previous version is split between configuration information relative to the Network Deployment node (specifically, the deployment manager on that node) and the other nodes it manages. In particular, the following objects are migrated on a deployment manager configuration:

   • Clusters
   • Security
   • Virtual hosts

   Indeed, the WASPostUpgrade migration tool cannot be used on an WAS node that already belongs to a cell managed by a deployment manager. To be able to use the migration tool again, remove the node from the cell, use the tool, and then federate the node into the cell again.

6. Migration tools help you migrate existing configurations from certain previous versions during the installation process. They include both pre-upgrade and post-upgrade activities. The WASPreUpgrade and the WASPostUpgrade migration tools are updated for each release. To migrate the configuration from another version of WAS, use the WASPreUpgrade tool from the migration/bin directory on the product CD-ROM. The tool from the previous release is not sufficient for migrating to a new one.

   There are several scripts that the installer program copies to the V5.0.x migration/bin directory when you use the installation wizard to migrate a V5.0.x release to V5.1.

   • The pre_uninst50ws and the post_uninst50ws tools prevent removing the configuration of a migrated node from the deployment manager when you uninstall.

   • The pre_uninst502mq and the post_uninst502mq tools prevent deleting a messaging queue manager when you uninstall after migrating a configuration of V5.0.2 to V5.1.

   For more information, see Migrating and coexisting.

7. Use the migration tools to migrate your WAS Express configuration and applications to IBM WAS using instructions in the base product information center.

8. Multiple server instances and multiple product installations on one machine are now supported.

9. Multiple configuration instances are also available.

   Configuration instances appear to be separate installation instances on a single machine but actually share product binaries and have unique configurations and data only. You can create a configuration instance when the original installation location is read-only.

10. The servlet redirector and remote OSE mechanisms are no longer supported.

    Instead, HTTP forwards Web requests from your Web server to an HTTP server or an HTTP internal transport running inside the appropriate appserver.

11. WebSphere Edge Server functionality has been integrated into IBM WAS, including a Demilitarized Zone (DMZ) CD containing software for load-balancing and content caching. The edge of the DMZ includes:
    1. HTTP routers
    2. HTTP server
    3. Caching proxy
    4. Deployment manager

12. The Assembly Toolkit replaces the Application Assembly Tool.

    The Assembly Toolkit is available on the IBM WAS Toolkit (ASTK) CD-ROM. The Assembly Toolkit consists of the J2EE Perspective of the WSAD product, including code generation capabilities.

13. The base WAS product includes a new level of the IBM HTTP Server powered by Apache 1.3, which is V1.3.28.

    WAS also includes a plug-in option for IBM HTTP Server powered by Apache 2.0. The installer can configure either Web server.

    The installer program requires you to install IBM HTTP Server into a new directory.

14. The release level of the embedded messaging feature, which is based on WebSphere MQ technology, is CSD04.

    Because installation instances on one machine share embedded messaging code, coexistence is affected by the presence of the embedded messaging feature. V5.0.2 or V5.1 with embedded messaging does not install on a V5.0.0 or V5.0.1 machine with embedded messaging at an earlier level. Stop the installation and upgrade the V5.0.x level to V5.0.2, which can coexist with another installation of V5.0.2 or with an installation of V5.1. Or clear the selection of the embedded messaging feature and install V5.0.2 or V5.1 without embedded messaging.

15. There is a new level of GSKit. The new level of GSKit support is 7.0.1.10.

16. The installer program configures the Sun ONE Web Server on AIX for WAS support when you select the Sun ONE plug-in when installing on an AIX machine. Other platforms are still supported.

 

New and improved WebSphere Samples Gallery

1. Technology centered Samples, including EJB, J2EE client, JMS, JSP, and Servlet Samples.

2. The Plants by WebSphere "super Sample," demonstrating multiple technologies used to build realistic applications.

3. Java Petstore Sample

4. ANT-based build scripts enabling you to run, modify, rebuild, and run the Samples again.

5. Use of Cloudscape rather than DB2 for the Samples requiring a database. Cloudscape has a smaller footprint.

 

Servers

• WAS now has a single JVM run time, including containers, naming, security, administration, resources, ORB, and HTTP engine

• The new, flexible packaging structure means there is just one Application Server code base, with add-ons available for scale and function. The Application Server now runs with the high performing:

  • IBM Developer Kit, Java Technology Edition, Version 1.4.1 used on AIX, Windows, Linux, and z/OS operating systems.

  • Java 2 SDK from Sun on the Solaris Operating Environment

  • Java 2 SDK from HP-UX on the HP-UX operating system

  For more information, see Using the JVM.

  To confirm that you have the latest version of the IBM SDK for z/OS, you can use a java -version command. For more information about build dates and included fixes, see Service summary - IBM SDK for z/OS, Java 2 Technology Edition

• The Generic Servers feature that was previously available in WAS V4 for distributed platforms is now available in V5.1.1 This feature allows you define a generic server within the WebSphere administration. You can then use the WAS product to start, stop, and monitor the non-WebSphere program associated with that generic server.

• Workload management and clustering has improved.

  • Clusters now can be managed with browser based, scripting, and JMX administrative clients.

    In V4, clusters were known as server groups or models and clones.

  • The ability to configure member weights provides the administrator more control in tuning the system.

  • A new load balancing algorithm has been incorporated to better optimize the distribution of client requests across cluster members.

  • Enhanced failover support provides quicker failover in the case of network outages and other problems.

  • You can now use workload management (WLM) across multiple cells. This means that you can divide your servers into separate cells, and have them communicate (load balance and failover) with one another through WLM. As a result, you have more flexibility in designing your syste and keeping it manageable.

  For more information, see Balancing workloads with clusters.

• Support of Enterprise Workload Manager (eWLM) and Application Response Measurement (ARM). For more information, see Enabling Application Response Measurement

• In V3.5.x and V4, the default bootstrap setting was 900. Now the default is 2809. This does not cause problems in applications unless there is a direct reference to port 900. You can reconfigure the port setting to 900 if you migrate your previous configuration.

  For more information, see Port number settings in WAS versions.

• The system name space structure provided by the name server has changed significantly since the last release, including:

  • The V5 name space is distributed, meaning that objects are not all bound under a single context root as with previous versions.

  • The name space consists of partitions. Some partitions in the name space contain transient bindings and some partitions contain persistent bindings.

  These features and other new naming features are summarized in V5 features for name space support.

 

Applications > EJB modules

• EJB persistence manager has been re-architected to support EJB 2.0 CMP scheme, which differs greatly from the EJB 1.1 scheme

• EJB persistence manager has improved in modularity, maintainability, and performance. Maintenance focuses on configuration of server components, with less need to regenerate deployed artifacts

• EJB 2.0 specification support, including:

  • Local and remote beans
  • Message-driven beans
  • Container-managed relationships
  • A portable finder query language
  • All other aspects of the specification
  • Programming model
  • Abstract and concrete entity beans
  • Local home and local entity interfaces
  • Container-managed association relationships
  • Dependent values
  • EJB query language

• Plus these features that add high performance persistence beyond EJB 2.0:

  • Changing semantic behavior
  • Entity bean inheritance
  • Optimistic concurrency control
  • Read-ahead
  • Intent mechanism support
  • Support for different types of backend access mechanisms
  • Procedural access
  • SQLJ
  • Data caching

  EJB specification extensions are described in WebSphere extensions to the Enterprise JavaBeans specification.

• Powerful new features enhance container-managed persistence (CMP) entity bean performance, including:

  • Caching of bean data at several levels

  • Long lifetime caching, for beans that change only infrequently and thus remain read-only across many transactions

  • Read-ahead, which pre-loads groups and working-sets of beans in a single datastore operation by following selected bean relationships

  • Optimistic concurrency control, which minimizes the amount of time data is actually locked during updates and thus increases overall throughput in heavily-used applications

• CMP beans and bean-managed persistence (BMP) beans can share datastore connections, allowing access to related data by both kinds of beans when in the same transaction.

• CMP beans may inherit from one another (in other words, they may subclass one another). The Application Server will recognize this during bean deployment and at run time will -- for example -- allow finders to return beans of that class or any subclass. Inheritance may be expressed in relational datastores in either "single-table" or "root-leaf" arrangements.

 

Applications > Web modules

• WAS now allows you to create HTTP session database tables using the Binary Large Object (BLOB) data type for the medium column, which increases performance of persistent session when Oracle database are used.

  For more information, see Web container custom properties.

• Servlet 2.3 with Filters and Events

• JSP 1.2 with XML Syntax

• Changes in autoRequestEncoding and autoResponseEncoding

  The web container no longer automatically sets request and response encodings and response content types. The programmer is expected to set these values using the methods available in the Servlet 2.3 API. If you want the Application Server to attempt to automatically set these values, set autoRequestEncoding=true in order to have the request encoding value set and set autoResponseEncoding=true in order to have the response encoding and content type set. These values can be found in the ibm-web-ext.xmi file for each web application.

  For more information, see autoRequestEncoding and autoResponseEncoding.

• Filters are Java classes that can be configured to operate on (filter) the request and response data of a requested resource.

  The resource to filter, and filter precedence is specified in the deployment descriptor information found in the web.xml file of a Web application. Initialization parameters for filters can also be specified in the web.xml. Filters can be chained and can be configured to work on a single resource or a group of resources. Typical usages for filters include logging filters, image conversion filters, encryption filters, and MIME-type filters (functionally equivalent to the old style servlet chaining).

  For more information, see Servlet filtering.

• Application lifecycle events give the application developer greater control over interactions with ServletContext and HttpSession objects.

  Application event objects consist of application events and application listeners. Servlet context listeners are used to manage resources at an application level. Session listeners manage resources associated with a series of request from a single client. Listeners are available for lifecycle events and for attribute modification events. The listener developer creates a class that implements the javax listener interface corresponding to the desired listener functionality.

  For more information, see Application lifecycle listeners and events.

• The HttpUtils class is deprecated in 2.3 and its methods are replaced by new methods in the request object. The HttpUtils class will still be available for use by servlet writers until a future servlet specification directs its complete removal.

• WAS no longer requires the JSP-enabling servlet

  The file serving enabled check box in the IBM extensions tab of the Web module properties in the Application Assembly Tool controls this function for V5, V5.0.1, and V5.0.2. (It is selected by default.)

  The Assembly Toolkit (on the Application Server Toolkit CD) controls the function beginning with V5.1.

  Adding JSP files to the WAR file in the Assembly Toolkit or to the appropriate application_name.war directory of the installed enterprise application causes the JSP files to be served.

  Adding HTML files to the Web archive (WAR) file in the Assembly Toolkit or to the appropriate application_name.war directory of the installed enterprise application causes the HTML files to be served.

• New and improved features pertaining to HTTP session support include:

  • Multiple mechanisms for HTTP session state management, plus configuration options based on scalability and failover requirements from simple, single server environments to large, high-load clusters:

    • In memory

    • Persistent to database

    • Memory-to-memory

  • Replacement of the Session Manager object, which resided underneath each servlet engine in the WAS V4 topology. Its properties are now part of each Application Server.

  • Enhanced support for HTTP Session State failover, as described in Managing HTTP sessions.

  • With V5, a new option exists for saving HttpSession information for failure recovery purposes. In addition to a database, IBM WAS can save a HttpSession in more than one Application Server instance. Called in-memory session replication, this feature leverages the replication domain and replicator entry services provided in Network Deployment.

  • Session support for Wireless Application Protocol devices, as described in Configuring session tracking for Wireless Application Protocol (WAP) devices.

• Global settings for internal servlets for Web applications can now be set at the Web container level. For more information, see Web container custom properties.

• WAS V5.1, introduces support for UTF-8 encoded Unifor Resource Locators (URLs) to include double byte characters in URLs. The UTF-8 encoded URL feature is enabled by default but can be disable as described in Web container custom properties.

 

Applications > Web services

WAS V5.02 introduces support for Web services for J2EE (JSR-109).

WAS V5.1.1 continues support for Web services for J2EE (JSR-109). The Web services standards are developed for the Java language under the Java Community Process (JCP). These standards include the Java API for XML-based remote procedure call, JAX-RPC (JSR-101), and Web services for J2EE.

The new Web services standards are developed for the Java language under the Java Community Process (JCP). These standards include the Java API for XML-based remote procedure call, JAX-RPC (JSR-101), and Web services for J2EE.

The JAX-RPC standard covers the programming model and bindings for using Web Services Description Language (WSDL) for Web services in the Java language. The Web services standard for J2EE covers the use of JAX-RPC in a J2EE environment, as well as the deployment of Web services implementations in a J2EE server. Both standards are part of the J2EE 1.4 release.

• Web services development tools have been enhanced and are now based on the Java API for XML-based remote procedure call (JAX-RPC) 1.0 and on the Web services for J2EE, V1.0 (JSR-109) specifications. See Implementing Web services for an introduction to the new documentation based on these specifications.

• Web services development tools have been enhanced and are now based on the Java API for XML-based remote procedure call (JAX-RPC) 1.1 and on the Web services for J2EE, V1.0 (JSR-109) specifications. See Implementing Web services for an introduction to the new documentation based on these specifications.

• Invoking RMI-IIOP using JAX-RPC (Multiprotocol JAX-RPC)

  Two programming models, WSIF and JAX-RPC have merged. The merging of JAX-RPC and WSIF creates a programming model with support for non-SOAP protocol bindings and tools to produce WSDL documents with extended bindings.

  See Invoking RMI-IIOP using JAX-RPC for details.

• Web services enable businesses to connect applications to other business applications, to deliver business functions to a broader set of customers and partners, to interact with marketplaces more efficiently, and to create new business models dynamically. To that extent, the product provides four protocols that support Web services:

  • Web Services Description Language (WSDL), an XML-based description language that provides a way to catalog and describe services

  • Universal Discovery Description and Integration (UDDI), a global, platform-independent, open framework to enable businesses to discover each other, define their interaction, and share information in a global registry

  • SOAP, a lightweight protocol for exchange of information in a decentralized, distributed environment

  • eXtensible Markup Language (XML), which provides a common language for exchanging information.

• Enhanced Web Services, including WSIF and Web Services Security. New and improved features in Web services support include:

  • An open source implementation of a Web Services Invocation Framework (WSIF), new in this release. It includes protocol isolation and dynamic invocation (no stubs)

  • The following new features added by WAS Network Deployment and WAS for z/OS:

    • A private Universal Description, Discovery and Integration (UDDI) Registry, implementing V2.0 of the UDDI specification. The UDDI feature also requires installation of the base WAS product in the cell, to host the enterprise applications. See Migrating from a previous version of IBM WebSphere UDDI Registry about migrating from the IBM WebSphere UDDI Registry PRPQ that ran in the previous product version.

    • A Web Services Gateway for providing gateway access to existing Web services. The Web Services Gateway feature also requires installation of the base WAS product in the cell, to host the enterprise applications. See Web services gateway - What is new in this release for a description of the main differences between this version of the gateway and the Technical Preview version of the gateway that ran in the previous product version.

    • AXIS has improved performance and flexible architecture.

  • Newly-enhanced Web services capabilities of WebSphere Studio (sold separately) for developing Web services and Web services gateway filters.

  • Web services security functionality that is based on standards included in the Web services security (WS-Security) specification. Web services security is a message-level standard, based on securing SOAP messages through XML digital signature, confidentiality through XML encryption, and credential propagation through security tokens. See Securing Web services based on WS-Security for information on securing Web services.

 

Applications > Application services

• Changes and improvements in naming support are described in V5 features for name space support. They include:

  • The way that the system binds objects into the name space has changed significantly.

    Before WAS V5.0, all objects were bound relative to a single root context. Now they are bound to a context that is specific to the server associated with the object. This context is referred to as the server root context. Each server has its own server root context. An initial context can be any server root context. This means that jndiName values in deployment descriptors and lookup names in thin clients must be qualified when the object associated with the name is bound under a server root context different from the initial context.

    For more information, see Name space logical view and Lookup names support in deployment descriptors and thin clients.

  • In V3.5.x and V4.x, the Name Server runs in the same process as the administrative server. An administrative server is no longer running on every V5 installation. The Name Server configuration is included in the same configuration files as Application Servers. The Name Server runs in its own process.

• Changes and improvements in dynamic caching include:

  • V4 supported the configuration of dynamic servlet caching through the use of a servletcache.xml file. For migration purposes, this file is still supported by this release. In order to utilize the new and improved functionality of the dynamic cache service in this release, configure your cache policy using the new cachespec.xml format. For more information, see Configuring cacheable objects with the cachespec.xml file.

  • Sophisticated dynamic network caching follows these directives, meaning explicit cache APIs are not needed:

    • Cache within the J2EE context (such as Servlet, JSP, and EJB patterns)

    • Describe caching behavior in the form of XML cache policy files, providing a more flexible cache policy deployment descriptor
    The dynamic caching engine features:

    • Disk overflow of cached objects through Java Object store/access (put and get)

    • Least Recently Used (LRU) management

    • XML cache policy management (such as the use of ID generation)

    • Invalidation management

    • Replication from one dynamic cache to another, using Replication Domains and their associated Replicator Entries

    • External cache support for caches such as:

      • IBM WebSphere Edge caching using Akamai ESI

      • IBM HTTP Server Fast Response Cache Accelerator (FRCA)
    Caching support includes:

    • Servlet and JSP results caching (same as V4)

    • Command caching

    • Pattern caching

    • Web services caching

    • Results caching of Web services requests. For more information, see Configuring the Web services client cache.

    For more information, see Configuring the dynamic cache service to improve performance.

• Internationalization support enables applications to become global by determining the client locale and changing supported attributes, such as currency, character sets, and so on. For information about the localizable-text API, see Internationalizing applications.

• Class loaders are new and improved as of V5.0. For more information, see Class loading.

• User profile support is deprecated. For more information, see Using user profiles.

 

Resources > Messaging

• Java Message Service (JMS) through embedded provider

  • Supports point-to-point and publish/subscribe styles of messaging

  • Used for message-driven bean support

  • Integrated with transaction manager (JMS with XA)

  • Used for messaging within a cluster or cell

• Support for plugging in other JMS providers, including MQ Series

• Messaging and e-mail interfaces through JavaBeans Activation Framework (JAF), Remote Method Invocation over Internet InterORB Protocol (RMI/IIOP), the JavaMail API, and Java Messaging Service (JMS) with the help of IBM MQ Series

• Integrated JMS, as described in Using asynchronous messaging

 

Resources > Data access

• The administrative console pages for configuring data sources now contain options for testing the data source connections. See Test connection.

• All connector access is through J2C.

  • JDBC access managed via J2 relational resource connector

  • Legacy JDBC support is provided

• Data access support provides a complete implementation of the JCA 1.0 specification, including support for:

  • Connection sharing

    This version fully supports the res-sharing-scope tag within the resource reference (resource-ref) element, so the product supports both shareable and unshareable connections.

  • Get/use/close and get/use/cache programming models for connection handles

    The product supports the Web container. Both EJB and Web components can utilize the J2EE Connector Architecture.

  • XA, local, and No transaction models of resource adapters, including XA recovery

  • Security options A and C per the specification

• Res-auth settings of either application or container.

  In V4, the res-auth setting was disregarded. That is, it was treated as if the value of res-auth was set to application. If your existing applications had res-auth set to container, you might get different behavior if you install them into the new environment without any changes.

Applications must be packaged as J2EE 1.3 applications. For more information, see Migrating a version 4.0 data access application to version 5.1.

• Subpools were eliminated to provide better performance. You can no longer specify pool and subpool names. The pool name is based on the data source or JNDI name of the connection factory.

• J2EE Connector Architecture or J2C is part of the J2EE specification beginning with J2EE V1.3.

  J2C is similar to the Common Connector Framework (CCF) but is implemented for the Java platform. It provides specialized access to Enterprise Resource Planning (ERP) and mainframe systems such as CICS and IMS from IBM. As part of J2C, the product provides these components:

  • Common Client Interface API, which simplifies access to diverse back-end Enterprise Information Systems (EIS)

  • Connection Factory, which connects an application to the Resource Adapter

  • J2C Adapters, which enable the product to communicate with a number of back-end EIS resources, can be obtained. Adapters are available for:

    • Host On-Demand

    • CICS

    • IMS

    • SAP

    • J.D. Edwards

    • PeopleSoft

    • Oracle Financial
  You can find more information on the available adapters and adapter suppliers at    J2EE Connector Architecture Product Information
  http://java.sun.com/j2ee/connector/products.html .

 

Security

• The z\OS SecureWay LDAP server is now supported, using the same configuration as that of IBM SecureWay LDAP. The z\OS SecureWay LDAP server functions just like any other LDAP server currently supported by IBM WAS.

• Four administrative roles are now available for securing the administrative console.

  For more information, see Administrative console and naming service authorization.

• Enhanced security features include:

  • JAAS

  • CSIv2 interoperability

  • Java2 security

  • Support for third party Security Providers
  For more information, see Welcome to Security.

• Distributed systems management, security, and directory support

• J2EE security support, including JAAS programming model and CSIv2 for CORBA interoperability

• Web services security includes signatures and credential propagation

• Support for third party security providers (prior to JSR 115)

• A new UserRegistry interface, to which V4 users should consider migrating from the deprecated CustomRegistry interface that was introduced in V4.

• The Trust Association Interceptor interface remains backward compatible with that of V4.

• The application login helper functions provided in V4 and prior releases are deprecated, but still supported.

• The login helper functions are replaced by the JAAS LoginContext and subject-based programming model in V5.

• WAS, V5.0.2 includes Federal Information Processing Standards (FIPS) cryptographic modules including Java Secure Socket Extension (JSSE) and Java Cryptography Extension (JCE). These IBMJSSEFIPS and IBMJCEFIPS modules are undergoing 140-2 certification.

• APAR PQ87788 corrected the instructions for encoding plain text passwords. For more information, see Protecting plain text passwords.

• WAS, V5.1 includes the IBM Developer Kit, Java Technology Edition V1.4.x.

• Java 2 Security is enabled by default. WAS will rethrow Java 2 Security exceptions (java.security.AccessControlException) when the security manager prevents unauthorized access to protected resources. Previously, WAS logged the exceptions in the SystemOut.log file, but did not rethrow them.

• Java 2 Platform, Enterprise Edition (J2EE) Version 1.4 requires that the Java run time install a security manager for all J2EE containers.

• A tutorial for enabling security is available at the following location: WebSphere education on demand: Enabling security best practice tutorials

• WAS propagates security attributes to downstream servers. For more information, see Security attribute propagation.

• The Chrysalis Luna SA cryptographic token device is supported on the Solaris operating system only.

  For more information, see Configuring to use cryptographic tokens.

 

Environment

• Configurable plug-ins for popular Web servers.

  The Web server (or HTTP Server) plug-in enables communication between the HTTP server and the Application Server. It uses the industry-standard HTTP transport protocol for non-secure transports and HTTPS for secure transports.

• The plugin-cfg.xml file location has changed to...

  install_root/config/cells/plugin-cfg.xml

  For more information, see Configuring Web server plug-ins.

• HTTP server capabilities embedded within the base product.

• New variable support. Variables are configuration properties that can be used to provide a parameter for any value in the system.

• New shared library support.

 

System administration

• Terminology for distributed systems management:

  • A cell is a collection of machines that you are managing together.

  • A node is a machine on which you are running an Application Server.

  • A server is the Java virtual machine running the Application Server containing your applications.

• New, scalable XML-based administrative infrastructure:

  • All configuration data is stored in XML for standard deployment descriptors, and XMI format for product-specific configuration documents. These documents are stored on each node. No relational database is required. See Working with server configuration files.

  • The Server configuration API is provided for manipulating product configuration files. See WebSphere configuration documentation (Javadoc) .

  • Servers load directly from configurations in XML documents.

  • Application binaries are managed as part of the configuration repository.

  • In clusters, the product manages synchronization of documents across machines. This feature is configurable, as described in File synchronization service settings.

• JMX support:

  • Multiple protocol support (SOAP by default, but also RMI/IIOP)

  • Support for alerts

  • Message routing between machines, providing cell-level view

  • Support for MBeans that you define and register

  • Run-time attributes and access to run-time operations, configurations, and performance data

  For more information, see Deploying and managing using programming.

• Scripting support:

  • Based on Bean Scripting Framework (BSF), supports multiple scripting languages;

  • Parallel capability between scripting and Web-based administrative console

  • Interactive and script modes

  • Multiple connection styles (SOAP, RMI)

  • Remote administration support

  • Ability to access any MBean registered in any server in the cell

  • Run-time attributes and access to run-time operations, configurations, and performance data

  For more information, see Deploying and managing using scripting.

• WebSphere administrative console:

  • Accesses configuration data and the run-time state of ongoing operations.

  • Supports multiple users, providing the ability to customize preferences for each user.

  • Provides coarse-grain administrative security control and filtering for roles such as administrator, monitor, configurator, and operator.

    See Administrative console and naming service authorization.

  • Filters and search capabilities for collections.

  • Exists in all product packages. The V4.0 Java-based console is no longer available.

  • Scales to provide additional features as additional product packages are installed.

  • Supports struts and tiles.

  • Displays run-time and configuration exceptions, with a toggle function to switch the view.

  For more information, see Using the administrative console.

• Many command line tools are now available for specific tasks. For more information, see Managing using command line tools.

 

Monitoring and tuning performance

• The Runtime Performance Advisor and the Performance Advisor in Tivoli Performance Viewer are new tools that suggest configuration changes to help administrators optimize performance on WAS. For more information, see Welcome to Performance

• Tuning information has been enhanced to include the handy:

  • Parameter hotlist, key parameters you can tune for a high impact on performance

  • Parameter index, the comprehensive list of tuning parameters

  • Troubleshooting tips, a concise guide that traces various problems to their possible origins in poor tuning

• The Performance Monitoring Infrastructure (PMI):

  • Is now integrated with Java Management eXtensions (JMX), as shown in Performance Monitoring Infrastructure .

  • Has new counters including those for:

    • Dynamic caching

    • Workload management

    • Object Request Broker (ORB)

    • HTTP session size

    • JDBC time

    • Web Services

    • CPU utilization
    For more information about data, see Performance data organization.

  • Supports both the PmiClient interface and the JMX interface. The latter is supported through the AdminClient class described in Developing an administrative client program.

  • Continues to support the V4-style APIs, but the data hierarchy has been updated to match the V5 product structure.

• The Resource Analyzer has been rebranded as the Tivoli Performance Viewer and bundled with WAS. New features include logging and replay in XML format, and CPU utilization. For more information, see Monitoring performance with Tivoli Performance Viewer (formerly Resource Analyzer).

• Request metrics instrumentation tracks the time spent by selected requests in each WAS component in the system. The data can be written to a log file or sent to an ARM agent. For more information, see Measuring data requests (Performance Monitoring Infrastructure Request Metrics).

• Performance features include:

  • Dynamic, multi tier caching, which is set up per node or Application Server using XML files. Such caching is most effective for non-user-specific output, such as mutual fund prices.

  • Dynamic reloading of enterprise beans.

  • JNDI caching, which improves performance by caching expensive lookups.

    See JNDI caching.

  • Caching of dynamic content, such as servlets and JSP files, to improve throughput.

• WAS can be tuned from the WebSphere administrative console.

 

Troubleshoot

1. First failure data capture (FFDC):

   • Collects data based on the first failure in the system

   • Filters out expected or recurring exceptions to reduce overhead in collecting data

   • Passes data to an analysis engine that searches a knowledge base of information about common errors, including their possible causes and solutions

RAS collector tool

Gathers information to send to IBM Service personnel.

RAS collector summary

Lightweight version of the RAS collector tool. Useful for initial problem reporting to IBM Service personnel.

 

New in V5.1.1

WebSphere Business Integration Server Foundation (WBISF V5.1)

Used for building service-oriented applications (SOAs). Supports Business Process Execution Language for Web Services (BPEL4WS) and a technology preview of the Common Event Infrastructure feature.

Previously known as IBM WAS Enterprise. V5.1 continues to support all WAS Enterprise V5.0 function.

WBISF V5.1 is also available for the z/OS platform.

Future releases will focus on process choreography and business rule features.

 

WebSphere Studio Application Developer Integration Edition V5.1 (WSAD IE v5.1)

Eclipse-based composite application development environment used for building SOAs. Optimized for building apps that deploy to IBM WBISF V5.1.

Full J2EE specification support (Servlet 2.3, JSP 1.2, EJB 2.0, etc...).

 

---