Latest available updates for IBM WebSphere Portal and IBM Web Content Manager
IBM recommends to update Portal with the latest cumulative fixes (CF) on a regular basis to benefit from product fixes as soon as they become available. Staying on the latest CF level will also help you in making sure that interim fixes for potential security vulnerabilities will become available to you as quickly as possible. For more information follow the link to PSIRT Blog to see the latest IBM Security Bulletins by product.
Article Title: "Administering IBM WebSphere Portal 8.5: A comprehensive workshop" Authors: Thomas Hurek and Chet Tuttle - Portal + WCM Development Link: https://developer.ibm.com/digexp/docs/docs/customization-administration/administering-ibm-websphere-portal-8-5/ Summary: The goal of this white paper is to explain the various administration and configuration tools offered by IBM WebSphere Portal 8.5. Learn about which tool to use for which task and about the new capabilities of WebSphere Portal 8.5, and understand differences from previous versions of WebSphere Portal. [The whitepaper] will take you through exercises for each tool so you can learn hands-on how to use them.
Article Title: "IBM WebSphere Portal V 8.5 Performance Tuning Guide" Authors: Multiple Portal Testers and Developers Link: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/IBM_WebSphere_Portal_V_8.5_Performance_Tuning_Guide Summary: This white paper provides a basis for parameter and application tuning for IBM WebSphere Portal for Multiplatform and for Linux on System Z V8.5.0. Remember that both tuning and capacity are affected by many factors, including the workload scenario and the performance measurement environment. For tuning, the objective of this paper is not to recommend that you use the values we used when measuring our scenarios, but to make you aware of those parameters used in our configuration. When tuning your individual systems, it is important to begin with a baseline, monitor the performance metrics to determine if any parameters should be changed and, when a change is made, monitor the performance metrics to determine the effectiveness of the change.
Article Title: "Security Hardening Guide for IBM WebSphere Portal" Author: Jason Wicker - Portal Support Link: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Security_Hardening_Guide_for_IBM_WebSphere_Portal Summary: Security is a fundamental requirement for most web applications. Organizations commonly demand detailed accounting of web application security, especially after mainstream media coverage of high-profile vulnerabilities or exploits. This guide instructs architects and administrators on evaluating and improving the security of applications based on IBM WebSphere Portal.
Article Title: "Theme updates in IBM WebSphere Portal 8.5" Posted 31-Mar-2015 Author: Stephan Hesmer - Portal Theme Development Link:https://developer.ibm.com/digexp/blog/2015/03/24/theme-updates-ibm-websphere-portal-8-5/ Summary: [The author] wanted to give an update on all the improvements around themes that happened the last couple of months as part of the IBM WebSphere Portal 8.5 Cumulative Fixpacks. Several new features were introduced to themes in cumulative fix 03 and cumulative fix 05, which the author describes in detail.
Article Title: "Creating an Ajax autocomplete field using the WCM REST API" Posted 31-Mar-2015 Author: Mark Taylor - IBM Services Link:http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Creating_an_Ajax_autocomplete_field_using_the_WCM_REST_API Summary: The WCM REST API offers remote access to WCM data. Requests can be used to perform the standard CRUD (create, read, update and delete) operations on WCM data. The API can handle data in both JSON and XML format. [The article provides] one implementation of an autocomplete field where a user can type into a text field some part of a name and any entries that match the partial text are offered to the user. The user can then select one of the suggestions. In the example, the autocomplete code is included in a WCM HTML Component. This component is self-contained and can be included in a Presentation Template or nested within another component. The example uses the jQuery library to handle the autocomplete action. jQuery not only allows the end user to enter partial text and make a selection, but it generates results code in the page.
Article Title: "Java Class Cache Sizing for WebSphere Portal" Posted 24-Mar-2015 Author: Alex Lang - Portal Development Link:https://www.ibm.com/developerworks/community/blogs/portalops/entry/java_class_cache_sizing_for_websphere_portal?lang=en Summary: Recently [the blog author] came across a performance problem at a client which likely affects multiple other Portal installations; particularly those using JSF (JavaServer Faces). The client reported that a newly migrated Portal had significantly worse performance than it's predecessor. I initially suspected a problem in the SAN or the VIO servers on AIX due to latency. But when the Javacores only showed waiting on the file attributes but not the file reads and writes themselves, I realized that Unix/Linux stores the file and attributes in memory buffers. The Java JVM was only checking the attributes to make sure that something had not updated on the SAN. Realizing that files were not changing but that Java was blocking on the attribute lookups, I quickly came to the conclusion that we have frequent class reloading since the cache was full. [The author continues the blog entry with details of how to modify the class cache size to resolve the issue, further techniques to troubleshoot and isolate root cause, etc.]
Article Title: "WebSphere Portal Migration from V6.1 to V8.5" Posted 10-Mar-2015 Author: Joseph John - Portal Development Link:https://developer.ibm.com/digexp/docs/docs/customization-administration/websphere-portal-migration-from-6-1-to-8-5/ Summary: You can migrate from version 6.1 to version 8.5 through a two-step automated migration path or a manual migration path. The automated vs manual migration section below provides various considerations to help you choose between automated and manual migration. For details on the automated migration process see the IBM Knowledge Center under WebSphere Portal 8.0.0 (previously referred to as the Information Center). Additional details on the manual migration process is provided [in this article]. *Editor's Note: The manual migration process requires a significant skillset with the WebSphere Portal to execute successfully. There are also some significant limitations with the process - including the extent to which L2 support can assist with manual migrations. However, for customers with the available skillset and willing to accept the limitations it can be advantageous vs. the two-step automated process - and yes, it has been proven in the field to work.
Article Title: "Step by step guide to implement SAML 2.0 for Portal 8.5" Posted 10-Mar-2015 Author: Paolo Della Rocca - IBM Services Link:https://developer.ibm.com/digexp/docs/docs/customization-administration/step-step-guide-implement-saml-2-0-portal-8-5/ Summary: WebSphere Portal is often included in architectures where multiple components are involved and integrated, and SAML SSO is often considered as an option to provide a good user experience for authenticated requests. Because WebSphere Portal is based on WebSphere Application Server (WAS) middleware technology and leverages WAS security layer, SAML SSO is available on Portal as provided by WAS. In this document we will describe the SAML 2.0 standards, what WAS provides for SAML SSO, and the steps to implement it for WebSphere Portal with a generic Identity Provider.
Article Title: "Flexible JSPs in WCM using parameters" Posted 10-Mar-2015 Author: Maarten Pol - Non-IBM Services Link:http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Flexible_JSPs_in_WCM_using_parameters Summary: JSPs offer loads of flexibility. But sometimes you end up creating several copies with minor changes just to accommodate slightly different purposes. Avoid this by making the JSPs respond to parameters. The parameters are set from the invoking JSP component, or passed in through the query string. Use this ability to limit maintenance and the need for deployments.