The Lotus Quickr product has been available for several years. Previously known as QuickPlace, Quickr has become recognized as a leader in web-based team collaboration, and it is used in many large corporations throughout the world.
The goal of the change from QuickPlace to Quickr is simplification. IBM wants the product to be so simple that an end user can, with a few clicks, generate productive services. There is also a focus on server deployment simplification.
One of the key components of Quickr is the connector technology that it introduces. These connectors will allow for direct and programmatic interaction with the data stored in the Quickr places. Connectors that will be shipping with Quickr 8.5.1 are as follows:
Quickr with services for Domino
The Domino-based edition of Quickr should be thought of as a significant upgrade to the existing QuickPlace product line. This product has been maturing over many years, and this new release provides many new capabilities. These include native support for wikis and blogs out of the box.
The basic installation process for Quickr with service for Domino is very simple. It involves installing a base Domino server version 8.5.1. The Quickr product components are then installed on top of this server. Based on this writing, the support for Quickr 8.5.1 will be supported on Domino 8.5.1 and Domino 8.5.3.
Currently, support for Quickr 8.5.1 installation support on Domino 8.5.2 is being skipped and will go straight to Domino 8.5.3. Quickr for Domino is installed in four basic steps that are listed as follows:
Installing and configuring Lotus Domino Server
Installing and configuring Lotus Domino Server is a standard Lotus Domino Server install. There are some additional Notes.ini variables that can be added, but overall this is just a standard Domino install. It is recommended to install Domino Offline Services (DOLS), if you would like to take your Quickr Places offline. Some of these Notes.ini variables could include the following:
Installing Lotus Quickr
It is very easy to install Lotus Quickr. The following screens show you how to get your Domino Quickr Server installed:
Configuring Multi-server Single Sign-on (MSSO) authentication
The next step is to set up the Multi-Server Single Sign-on (MSSO) authentication. In older releases of Lotus Domino, the MSSO was denoted as Server Single Sign-on (SSO). The features provide the ability for Web users to log in to a Domino or Websphere server once. A "token" will be provided to each user's Web client that will, in effect, authenticate that user for any server that is sharing the MSSO-based credentials. End users will only be prompted once for their credentials. The username and password will not be asked for again.
Base requirements for MSSO
The DNS domain that applies to the participating SSO servers is specified to each MSSO server configuration document. IP addresses cannot be used as part of the URL syntax. For example, http://126.96.36.199/ is not a legal entry for MSSO.
Also, it is critical for the DNS name to match the entry point into the server. For example, each MSSO configuration is setup based on a DNS name (example.com). As long as a server can resolve to an address, there is the possibility that HTTP can respond. But in the case of MSSO, the DNS name for the URL must match what was configured in the Domino server.
For example, DNS via NSLookup shows an IP address assigned to IBM.com as 188.8.131.52. Also, DNS via NSLookup shows an IP address assigned to example.com as 184.108.40.206.
If the DNS name is example.com, the IBM.com address will not accept the MSSO token. WebSphere cannot use Domino based authoritative LTPA tokens. To include Domino and WebSphere in the same LTPA group, you need to create the authoritative LTPA token first in WebSphere then you must export the LTPA token from WebSphere and import it into Domino.
Now, that you understand some of the basic rules, let's create a MSSO document and the associated security keys.
You can use the Domino Server document or a site document for the base Domino Web configuration settings. This is up to you and how you have configured your environment.
The following screenshot shows your final step. In the Domino Web Engine tab, select the Multiple Single Sign on option for the Session authentication field. This will then display a dialog box showing the LTPA tokens that you created. Select the one that matches your Internet domain name:
Now the server is configured for MSSO. Restart HTTP (or the Domino Server).
Configuring Quickr Domino Server settings
So far, you have set up Domino, Quickr, and MSSO. Now, it is time to configure the Quickr Settings. The following steps describe this process:
You will see the following screenshot:
As shown in the preceding screenshot, there are three important points on this screen. They are:
After you have installed Quickr, there is some additional configuration required, depending on the intended usage. They are:
The final integration component of Quickr with services for WebSphere Portal and Domino comes in the area of application development. As Quickr is built on top of a Domino foundation, it is possible to use traditional Domino development techniques to customize and extend it in many ways. Developers can use the standard Lotus Developer client to extend the use of Quickr places.
Quickr with services for WebSphere Portal
The WebSphere Portal-based edition of Quickr represents a significant application in the Web 2.0 space. It heavily leverages these technologies to bring an industry-leading collaboration experience. This product expands on the capabilities originally created from IBM Workplace Collaboration Services and IBM Workplace Services Express.
Installing Lotus Quickr services
The installation of Quickr services for the WebSphere Portal server has been optimized for ease of deployment. There are three installation types that are available in the setup program:
Integrating Sametime for Quickr WebSphere Portal
The use of awareness within Quickr services for WebSphere Portal is configured in the same way as any other WebSphere Portal installation:
Lotus Quickr Connectors
One of the key features of Quickr is the openness provided by the connector architecture. These connectors allow for direct interaction with the Quickr servers independently of the backend architecture (WebSphere Portal/Domino). To install the Lotus Quickr Connectors, you will need to complete the following steps:
The connector for Sametime allows access to Quickr content stores. It is implemented as a Lotus Expeditor plugin within the Sametime 8.5.1 client (and higher). The connector for Microsoft Office provides access to Quickr document management functions directly from within Office applications. As you can see, the Lotus Quickr connectors provide for tight integration into the content. This will give the end users a choice as to how they work and interact with their content.
IBM Lotus Notes Related Interview Questions
|IBM Lotus Notes Interview Questions||IBM Informix Interview Questions|
|IBM DB2 Interview Questions||DB2 Using SQL Interview Questions|
|IBM Mainframe Interview Questions||Active Directory Interview Questions|
|DB2 SQL Programming Interview Questions||IBM Integration Bus Interview Questions|
|IBM DataPower Interview Questions||Microsoft Exchange Server 2013 Interview Questions|
|Mainframe DB2 Interview Questions||Windows Server Support Interview Questions|
Ibm Lotus Notes Tutorial
Lotus Notes 8.5.3 And Soa
Overview Of New Lotus Notes 8.5.3 Client Features
Lotus Domino 8.5.3 Server Features
Deployment Enhancements In Notes/domino 8.5.3
Domino 8.5.3 Enhancements
Upgrading To Lotus Notes And Domino 8.5.3
Coexistence Between Notes/domino Releases
New Features In Notes/domino 8.5.3 Development
Integration With Other Lotus/ibm Products
Domino Configuration Tuner
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.