When you upgrade the application server to a newer version, be aware of the following settings that you might want to change.
- Configuring JavaServer Faces implementation
The Application
Server JSF engine determines if the Sun Reference Implementation (RI)
1.2 or Apache MyFaces 2.0 is used from the Application Server run
time. If either is used, the correct listener class is registered
with the web container. You do not need to add the com.sun.faces.ConfigureListener
or the org.apache.myfaces.StartupConfigureListener to your web.xml file.
- Core group administration considerations
Prior to Version 6.1.0.27,
every core group must contain at least one administrative process.
In this version of the product an administrative process is only required
if one of the following conditions exist:
- Your core group only contains members of one cluster.
- You are running in a mixed cell environment. In a mixed cell environment,
every core group that contains any Version 6.x members must also contain
an administrative process.
- Migration of JPA applications and bean validation
The
Bean Validation API and implementation are included in the Version
8.x product. If you want to deploy the feature pack applications on
Version 8.x, be aware of the following changes in configuration and
runtime behaviors:
- In Version 7.0, the system property, com.ibm.websphere.validation.api.jar.path,
is used to direct the feature pack run time to locate the Bean Validation
API JAR file. In Version 8.x, the Bean Validation API JAR file is
built into the product installation, therefore, this system property
is ignored. However, the bean validation provider can still be overridden
in Version 7 and Version 8.x when packaged in application or shared
libraries. The third bullet describes this usage scenario.
- The bean validation implementation in WebSphere® Application Server is automatically
the effective default bean validation provider.
- If standard bean validation features are used by the JPA application,
the com.ibm.websphere.validation.api.jar.path system property, and
user-supplied bean validation provider can be removed from application
deployment.
- If non-specification compliant or provider-specific features are
used by an application, the bean validation provider that supports
the required features must be packaged, configured, and deployed as
a typical, third-party service provider in the user application, the
application shared library, and the server associated shared library.
Read more about shared library usage in applications for more 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 the current version,
the scheme does not change. You can reverse the new behavior by changing
the application code. With a "sips" URI, the behavior remains the
same after upgrading from version 6.1 to 7.0 or above. See the information
center topic Premigration considerations for more information.
Web server plug-in connections
In Version 8.5.5.0 and
later, if the web server plug-in receives an HTTPS request but cannot
create an HTTPS transport to the application server, no connection
is made. If you want to enable the web server plug-in to create an
HTTP connection if an HTTPS connection cannot be made, specify the
UseInsecure custom property. Creating an HTTP connection if an HTTPS
connection cannot be made is less secure than creating no connection
because the user might be unaware that their connection is no longer
secure. By default in previous versions of WebSphere Application Server,
if the web server plug-in receives an HTTPS request but cannot create
an HTTPS transport to the application server, it creates an HTTP transport
if one is defined. If an HTTP transport is not defined, no connection
is made.