In this blog I will lay out some new Administration Tips and Tricks around Digital Experience, WebSphere Portal and Web Content Manager:
IBM JDK 7.1 was shipped and can be used with version 8.5
With version 8.5 of Digital Experience during install WebSphere Application Server 8.5.5.x and JDK 7.0.0.x are deployed as prerequisites for Digital Experience.
Starting with WebSphere Application Server 184.108.40.206 Java 7.1.0.x was provided with the Application Server fix pack.
We have functionally tested 7.1.0.x and also performance tested it and saw a very slight improvement.
Version 7.1.0.x can be installed via the Installation Manager. After installing the JDK the command managesdk can be leveraged to switch the JDK used with the Digital Experience profile to 7.1.
Should multiple Digital Experience Clusters per cell be used or rather Multiple Cells be defined?
My recommendation is to not use multiple Digital Experience clusters in a single cell. While the main saving is to have a single Deployment Manager for all clusters in the cell the disadvantages far outweigh this single advantage in my eyes:
- cell wide configuration settings like for instance security configuration limit flexibility
- dynacache replication in the cell can impact performance
- challenge to administer since even scoped setting changes need to be done in the right scope
- All portal clusters must be at the same maintenance levels
Health Management with Digital Experience on WebSphere Application Server 8.5.5.x
Starting with WebSphere Application Server 8.5 new Health Monitoring features were introduced - the health monitor and health policies.
The health monitor uses health policies. A health policy is a combination of health conditions and actions. Health conditions define triggers from which the system can protect itself, for example, a memory leak. Health actions are the specific steps that the system takes when a health condition is triggered. For example, with a memory leak condition, the health action can be to restart the associated servers . A number of predefined health conditions are installed with the product. You can use the predefined health conditions to create default health policies. In addition to these broad default health policies, you can define specific policies that apply for your environment.
The health monitoring happens at the Java Virtual Machine level and can be used with Digital Experience JVMs as well.
For more details pertaining to Health Management see:
Starting with WebSphere Application Server 8.5 in addition to the classic web server plugin and the On Demand Router a new feature was introduced - Intelligent Routing.
In the WebSphere Console you can turn on the Intelligent Routing feature for the web server plugin and from then on the Intelligent features will be enabled.
Among others the Intelligent Routing provides:
- Routing information based on events in WebSphere like stopping a server or starting an application
- Weighted Least Outstanding Requests (WLOR) load balancing
- Honoring health management features like not routing requests to a server that is in maintenance mode
For more details pertaining to Intelligent Routing see:
The SessionTimeoutFilter in Portal is only called for authenticated users. When using anonymous sessions and requiring cleanup code a J2EE session listener needs to be implemented.
For information regarding SessionTimeoutFilters see: http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/admin-system/adauthflt.dita?lang=en