The timeout.resume.session parameter is not included in the /shared/app/config/services/ by default, which equates to the parameter being set to "false." Therefore, if an idle session timeout is experienced, a user will see the ErrorSessionTimeout screen and be forced to re-login. The login causes a new session to be created. This session is separate from the LTPA security token which allows for Single Sign-On.

The timeout.resume.session parameter should be set to "true" in cases where you do not wish for users to see the ErrorSessionTimeout screen and have to re-login to WebSphere Portal once the inactivity timeout for the WebSphere Portal application is exceeded. An example scenario would be if you were using an External Security Manager (ESM) and Trust Association Interceptor (TAI) to handle authentication for WebSphere Portal. You could take advantage of the security invalidation and timeout features of the ESM and TAI to control when the session gets invalidated (and thus when the user gets redirected to ESM's login page to re-login).

To illustrate further, review the behaviors in the following use cases. Note that the following environment was used for testing these use cases:

WebSphere Portal v5.1.0.2 with PK09525 installed

WebSphere Application Server v5.1.1.7 (includes PK03711)

WebSphere Business Integration Server Foundation v5.1.1.3 set to:

persistent.session.level = 2 (return to last visited page before session was destroyed)
persistent.session.option =0 (user can't choose whether to resume session on login)

Session Inactivity timeout set to 5 minutes in WebSphere Administration console for WebSphere Portal application.

Filed in:

This article shows how content architects can coordinate the publishing or transfer of all portal content artifacts from a staging or development environment to a production server. Portal content artifacts include those stored in IBM® Workplace® Web Content Management, Portal Document Manager and WebSphere Portal Personalization.

The scenario assumes you are publishing content that references personalization rules which, when executed, return documents from a known folder in a document library. You see how to publish all content stored in the portal content repository.

Filed in:

As per the release..

Lotus Notes on a Stick is a feature of IBM Lotus Notes V7.0.2 and later that allows you to download your Lotus Notes client, including data, applications, mail, and more, to a Universal Serial Bus (USB) device (also known as a memory stick) that you can then plug into any Microsoft Windows workstation with a USB port. You use a simple command to install Lotus Notes on the USB device. Once that is done, you can work with Lotus Notes from any location without your laptop.

Lotus Notes on a Stick automatically recreates your Lotus Notes environment on any workstation. No configuration is necessary for set up on the host machine. With one click, you can launch Lotus Notes from the USB device, which automatically adds an icon to your host machine's desktop. When you remove the USB device, Lotus Notes on a Stick uninstalls Lotus Notes, removing the desktop icon, all files, and registry keys. Nothing is left behind.

Roaming users can take advantage of Lotus Notes on a Stick to download their roaming files to a USB device for even greater mobility.

Lotus Notes is not required any on machine into which you plug the USB device. Lotus Notes on a Stick has no effect on any existing installations of Lotus Notes.

This piece left me wondering if, I can, ever take my MS Outlook Client on a stick and use it on any OS, any device anywhere

Filed in: