Date Created: Wed 15-Dec-2010

Related Document Categories:

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/



WebSphere 8 What has changed?

Below is my summary of the information found in this URL:
http://publib.boulder.ibm.com/infocenter/wasinfo/beta/topic/com.ibm.websphere.base.doc/info/aes/ae/welc_transition.html

Over the coming months of 2011 I will be producing fully working example of how each of these new features aids administrator and developers and architects.

What has changed for administrators.
When you upgrade the application server to a newer version, be aware of the following settings that you might want to change.

Application Server property settings for a web server plug-in

The Use read/write timeout setting on the administrative console corresponds to the ServerIOTimeout attribute in the plugin-cfg.xml file. The default for the setting and the attribute for Version 8 is 900 seconds. For Version 7, the default is 60 seconds. Before Version 7, the default is 0.

Creating application-specific and trust service-specific bindings using the wsadmin tool

In WebSphere Application Server Version 7.0 and later, the security model was enhanced to a domain-centric security model instead of a server-based security model. The configuration of the default global security (cell) level and default server level bindings has also changed in this version of the product. In the WebSphere Application Server Version 6.1 Feature Pack for Web Services, you can configure one set of default bindings for the cell and optionally configure one set of default bindings for each server. In Version 7.0 and later, you can configure one or more general service provider bindings and one or more general service client bindings. After you have configured general bindings, you can specify which of these bindings is the global default binding. You can also optionally specify general binding that are used as the default for an application server or a security domain.

Enabling DB2 Performance Expert Extended Insight

The enableEndToEndMonitoringFeature custom property is deprecated in the WebSphere® Application Server V7.0.0.1 environment, because PEEI feature is enabled by default. PEEI can be controlled by the disableEndToEndClientMonitoringFeature custom property, which has a default of false. If you use the enableEndToEndMonitoringFeature custom property, Application Server will issue an OBSOLETE_PROPERTY_SPECIFIED warning.

Implementing web services applications with JAX-WS

Starting with WebSphere Application Server Version 7.0 and later, Java EE 5 application modules (web application modules version 2.5 or above, or EJB modules version 3.0 or above) are scanned for annotations to identify JAX-WS services and clients. However, pre-Java EE 5 application modules (web application modules version 2.4 or before, or EJB modules version 2.1 or before) are not scanned for JAX-WS annotations, by default, for performance considerations. In the Version 6.1 Feature Pack for Web Services, the default behavior is to scan pre-Java EE 5 web application modules to identify JAX-WS services and to scan pre-Java EE 5 web application modules and EJB modules for service clients during application installation. Because the default behavior for WebSphere Application Server Version 7.0 and later is to not scan pre-Java EE 5 modules for annotations during application installation or server startup, to preserve backward compatability with the feature pack from previous releases, you must configure either the UseWSFEP61ScanPolicy property in the META-INF/MANIFEST.MF of a web application archive (WAR) file or EJB module or define the Java™ virtual machine custom property, com.ibm.websphere.webservices.UseWSFEP61ScanPolicy, on servers to request scanning during application installation and server startup. To learn more about annotations scanning, see the JAX-WS annotations information.

Java virtual machine settings

Version 7.0 and previous versions use the optthruput garbage collection algorithm. In Version 8.0, the default is set to the generational garbage collector. This garbage collection algorithm can increase performance. The following JVM option is added to the WebSphere Application Server startup command: -Xgcpolicy:gencon. If you prefer to use the optthruput garbage collection alogorithm, you can remove -Xgcpolicy:gencon and the default optthruput garbage collection algorithm is used.

JCA life cycle management

When an application attempts a connection to a paused data source, the connection manager raises an SQLException with an error code of com.ibm.websphere.rsadapter.WSDataSource.ERROR_CONNECTION_POOL_IS_PAUSED.

Managing policy set attachments using the wsadmin tool

The application and system/trust values for the -attachmentType parameter are deprecated. Specify the provider value in place of the application value. For system policy set attachments, specify the provider value for the attachmentType parameter. For a trust client attachment, or a WSNClient attachment, specify the client value for the attachmentType parameter.

Migration scenario for the getHeaderNames method

To ensure the most successful migration, the return type of the StoredResponse getHeaderNames method was changed to com.ibm.websphere.servlet.response.CollectionEnumerationHybrid<String>. This type implements both Collection<String> and Enumeration.

Object Request Broker custom properties

The default for the com.ibm.CORBA.ConnectTimeout property for Version 8 is 10. Before Version 8, the default is 0.

Securing web services using Security Markup Assertion Language (SAML)

In WebSphere Application Server Version 7.0.0.7 and later, to use the SAML default policy sets, sample SAML general bindings, and JAAS login configuration settings for SAML, you were required to set up the SAML configuration, which is stored in a profile. In WebSphere Application Server Version 8.0, the SAML feature is available in all profiles by default.

Web server plug-in request and response optimization properties

The Accept content for all requests setting on the administrative console corresponds to the AcceptAllContent attribute in the plugin-cfg.xml file. For Version 8, the default for the setting is checked and for the attribute is true. Before Version 8, the default for the setting is not checked and for the attribute is false.

Web services migration best practices

Existing JAX-RPC applications wanting to use JAX-WS features must be rewritten using the JAX-WS programming model.

What has changed for developers.
When you upgrade the application server to a newer version, be aware of the following settings that you might want to change.

Developing JAX-WS web services with annotations

In WebSphere® Application Server Version 7.0 and later, if a Provider implementation returned a null value, there was a response message that consisted of a SOAPEnvelope that contained an empty SOAPBody. In the current version of this product, if the Provider implementation returns a null value, no response is returned. You can set the JVM property, jaxws.provider.interpretNullAsOneway, to false if you want a response message returned whenever a Provider implementation returns a null value.

EJB 3.0 and EJB 3.1 application bindings overview

To specify user-defined bindings information for EJB 3.x modules, place the file ibm-ejb-jar-bnd.xml, in the META-INF directory for the EJB Java™ archive (JAR) file. The suffix on this file is XML, not XMI, as in prior versions of product.

Enabling DB2 Performance Expert Extended Insight

The enableEndToEndMonitoringFeature custom property is deprecated in the WebSphere Application Server V7.0.0.1 environment, because PEEI feature is enabled by default. PEEI can be controlled by the disableEndToEndClientMonitoringFeature custom property, which has a default of false. If you use the enableEndToEndMonitoringFeature custom property, Application Server will issue an OBSOLETE_PROPERTY_SPECIFIED warning.

Implementing web services applications with JAX-WS

Starting with WebSphere Application Server Version 7.0 and later, Java EE 5 application modules (web application modules version 2.5 or above, or EJB modules version 3.0 or above) are scanned for annotations to identify JAX-WS services and clients. However, pre-Java EE 5 application modules (web application modules version 2.4 or before, or EJB modules version 2.1 or before) are not scanned for JAX-WS annotations, by default, for performance considerations. In the Version 6.1 Feature Pack for Web Services, the default behavior is to scan pre-Java EE 5 web application modules to identify JAX-WS services and to scan pre-Java EE 5 web application modules and EJB modules for service clients during application installation. Because the default behavior for WebSphere Application Server Version 7.0 and later is to not scan pre-Java EE 5 modules for annotations during application installation or server startup, to preserve backward compatability with the feature pack from previous releases, you must configure either the UseWSFEP61ScanPolicy property in the META-INF/MANIFEST.MF of a web application archive (WAR) file or EJB module or define the Java virtual machine custom property, com.ibm.websphere.webservices.UseWSFEP61ScanPolicy, on servers to request scanning during application installation and server startup. To learn more about annotations scanning, see the JAX-WS annotations information.

Migration scenario for the getHeaderNames method

To ensure the most successful migration, the return type of the StoredResponse getHeaderNames method was changed to com.ibm.websphere.servlet.response.CollectionEnumerationHybrid<String>. This type implements both Collection<String> and Enumeration.

Runtime considerations for SIP application developers

When a SIP application sends a request to a SIP URI over Transport Layer Security (TLS) in version 6.1, the request URI scheme changes from "sip" to "sips." In version 7.0, the scheme does not change. You can reverse the new behavior in version 7.0 by changing the application code. With a "sips" URI, the behavior remains the same after upgrading from version 6.1 to 7.0. See the information center topic Premigration considerations for more information.

Securing JAX-RS applications within the web container

When using the BasicAuthSecurityHandler class, ensure that you target resources using the https scheme for your URLs, and that the target application is SSL-enabled. It is highly recommended to use SSL connections when sending user credentials. You may explicitly turn off the requirement for SSL in the BasicAuthSecurityHandler class by invoking the setSSLRequired method on the security handler with the false value. By default, this value is true.

secHandler.setSSLRequired(false);

Securing web services using Security Markup Assertion Language (SAML)

In WebSphere Application Server Version 7.0.0.7 and later, to use the SAML default policy sets, sample SAML general bindings, and JAAS login configuration settings for SAML, you were required to set up the SAML configuration, which is stored in a profile. In WebSphere Application Server Version 8.0, the SAML feature is available in all profiles by default.

Web services migration best practices

Existing JAX-RPC applications wanting to use JAX-WS features must be rewritten using the JAX-WS programming model.

What has changed for security specialists

Creating a CA certificate in SSL

Certificates can be created by a certificate authority (CA) when a CAClient object is configured to connect to the CA to create the certificate. Certificates created by a certificate authority (CA) with a CA client are tracked in the security configuration in an object called CACertificate. The certificate is stored in a keystore and a CACertificate object is added to the configuration to reference the certificate. CA certificates are personal certificates

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/

Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories