Search results

Overview of common DSAPI failures for Websphere integration on IBM i.

The "Minimum Timeout (minutes)" field on the Web SSO Configuration document does not work correctly for keys imported from WebSphere Application Server.

The purpose of this IBM Redbook is two-fold. First, it shows you how to configure and integrate several Domino servers on one iSeries server to provide a set of integrated collaborative services to Web browser users. These integrated collaborative services include Domino for iSeries 6.5.1 or later, IBM Lotus Instant Messaging and Web Conferencing (Sametime) for iSeries, IBM Lotus Team Workplace (QuickPlace) for iSeries, and Domino Web Access for iSeries Second, this redbook shows you how to take the previously configured integrated, collaborative environment of Domino, Sametime, QuickPlace, and Domino Web Access to enable collaboration within WebSphere Portal Express. This redbook is for system administrators who need to understand how to configure one or both of the following environments on an iSeries server: - How to configure an integrated, collaborative environment of Domino, Sametime, QuickPlace and Domino Web Access on an iSeries server. This redbook shows you how to configure a seamless environment using single sign-on between the Domino servers using a common Domino LDAP directory. It also shows you how to enable Sametime functions within QuickPlace and Domino Web Access. - How to use the previously configured Domino collaborative environment and integrate it within WebSphere Portal Express to enable collaboration.

Where to find documentation on what versions of WebSphere Application Server and Lotus Domino can be used together

When WebSphere Application Server attempts to make SSL DIIOP connections to a Lotus Domino server, it is refused with an error message from the DIIOP task: "SSL Handshake failed: Invalid Peer."

Within IBM, the Domino and WebSphere Application Server teams have coordinated efforts to develop and to deliver key integration points that customers have requested. Each of these elements stem from the need for positive user experience, easier administration, and overall infrastructure integration. While Java and J2EE standards make it possible to integrate disparate applications at a fairly broad level, Lotus and WebSphere have developed powerful integration points that are only available between Domino and WebSphere Application Server. Many customers have already chosen a strategic HTTP server for their environment. Lotus Domino has a built-in HTTP server that many customers use, but customers also want Lotus Domino to integrate better into their infrastructure. Lotus Domino 6 has the ability to use the iSeries IBM HTTP Server (powered by Apache) in front of Lotus Domino as the main point of entry for Web browser users. This functionality is provided by a set of HTTP plug-ins. For customers looking to standardize on a single user directory, Lotus Domino can serve the Domino Directory to other applications using Lightweight Directory Access Protocol (LDAP). LDAP is quickly becoming the standard for directory serving and is also used by WebSphere Application Server for authenticating users. Because Lotus Domino can serve as an LDAP server, WebSphere can utilize this directory, allowing customers to manage user identities for Lotus Domino and for WebSphere in one location, easing administration skills needed i

When integrating WebSphere and Domino on the iSeries server, there are three plug-ins to consider in this environment: WebSphere's Domino plug-in (LIBDOMINOH) Domino 6 for iSeries Apache plug-in (QZSRVIHSAH) WebSphere's Apache plug-in (QSVTIHSAH)

This document serves as a guide to troubleshoot issues that may arise when Domino is configured to be used with IBM's WebSphere Application Server for single sign-on (SSO) or LDAP authentication. This information can also be found in the Notes/Domino R5 Release Notes.