WebSphere Entitlement FAQ Arthur Fontaine 2.Oct.02 11:06 AM a Web browser General 6.0All Platforms
FAQ -- Domino 6/WebSphere Entitlement
Q. What are you announcing today?
A. We are announcing that customers who purchase Domino 6 will also be entitled to use IBM WebSphere Application Server (WAS) 5.0, licensed for use with Domino applications. As WAS 5 is announced but not yet available, the initial entitlement will be for WebSphere Application Server 4.03 Advanced Edition (AE), with an evolution to WAS 5 as it becomes available and is tested against Domino.
Q. Why is this important?
A. Lotus and IBM are committed to a strategy that exploits the Java 2 Platform, Enterprise Edition (J2EE) development model, a set of specifications and practices for building multi-tier Web applications. The WAS license enables Domino developers to extend their applications with J2EE elements such as Java Server Pages (JSPs) and servlets -- at no incremental cost.
Q. When will this entitlement become effective, and for whom?
A. This entitlement will become effective with the release of Domino 6 on September 30, 2002. It is intended for purchasers of Domino 6 Enterprise Server or Utility Server (not Messaging Server). For Domino R5 users, the existing WebSphere Application Server 3.5, Standard Edition entitlement remains in place. Note that, for purposes of entitlement, a maintenance agreement that gives the customer the right to install Domino 6 also will entitle the new WAS software, but we urge only Domino 6 users to install the new WAS; Lotus will focus on testing interoperability between Domino 6 and WebSphere 5, so users of this combination can expect the best results.
Q. What are the specifics of the entitlement?
A. Domino 6 will include an entitlement to download the WAS software from the IBM Lotus Passport Advantage site. This is the same WAS AE code as IBM sells to its other customers, but the Domino entitlement contains a limited terms and conditions (Ts & Cs) license designed to restrict its use to applications based on Domino. In a future update, WebSphere 5 will replace this entitlement, with the same restrictions.
Q. How will customers benefit?
A. Domino 6 contains several new features that support the J2EE model, including a JSP tag library, hardened Java APIs, and the ability to call Java classes from LotusScript, the BASIC compatible scripting model in Domino. Customers benefit from exclusive Domino-WebSphere integration features such as single sign-on (SSO), and the extensive testing conducted between the products. The combination makes it easy to extend Domino applications with J2EE elements for new levels of scalability, granularity and flexibility.
Q. What would these applications look like?
A. Some typical uses would be:
* Increasing scalability by using JSPs for high-volume pages, such as index or home pages, while Domino stores and presents specific documents such as knowledge base entries or architectural drawings. JSPs also offer "pixel level" control in presenting the same content and objects, in ways that can be challenging to duplicate in native Domino forms and documents.
* Mixing servlets in with agents in Domino applications and workflows. The performance advantage for servlets over agents is that servlets are instantiated once and remain resident in memory. Agents retain advantages specific to the Domino object model, including more granular security, but intelligent use of servlets can extend a Domino application's functionality while improving its performance.
* Exposing Domino application functionality as Web services, which can be accessed remotely by other servers and applications. WebSphere can provide the Java and Web services engines that makes this possible.
Q. Is this something I can’t do today?
A. No, this is actually a pretty common model for enhancing Domino with j2EE elements. In fact developers have done these things for a while, using separately purchased J2EE servers or the previous WAS 3.5 Standard Edition (SE) entitlement. It's fair to say that the Domino community has been as zealous in pursuing ways to extend Domino via J2EE as have our own developers, who have been focused on Java since Domino 4.6.
This announcement enhances capabilities in this area. Newer versions of WAS are fully J2EE certified and have made huge strides in important areas such as administration and programmability. Domino 6 includes many new enhancements to make it compatible with the J2EE development model, including a JSP tag library, hardened Java APIs, and the ability to call Java classes from LotusScript, the BASIC compatible scripting model in Domino.
Q. Do I get single sign-on (SSO) with this entitlement?
A. Yes. The capability to support SSO (through lightweight third party authentication [LTPA]) is available in both Domino 6 and WebSphere AE 4.x. We plan to also deliver SSO in the WAS 5 entitlement. Note that this discusses using the entitled servers together, but any combination of WebSphere (AE and above) and Domino gives you the SSO capability. Many customers use SSO today between Domino and their separately licensed WebSphere servers.
Q. What do the license restrictions mean?
A. It’s important to understand the goals of this entitlement. The license restrictions are a way to promote the use of J2EE elements such as servlets and JSPs in Domino applications. This entitlement does not permit the use of WAS as enterprise middleware infrastructure. For example, no connections to data sources other than Domino are permitted – unless Domino is making the connection, not WebSphere. Essentially, for Domino-centric applications this entitlement enables developers to easily add servlet and JSP elements without a separate J2EE server cost.
Note that the J2EE-centric capabilities of Domino are not limited to what’s entitled by the bundled version of WAS. For customers who have already deployed a WAS J2EE infrastructure, the Domino 6 JSP and Java enhancements will be of tremendous use in distributed multi-tier applications.
Q. Are there any technical limitations with this entitlement?
A. Domino 6 and WebSphere 4.03 are the currently available versions. There is a current Java incompatibility between WAS and Domino on Unix machines only (not affecting Windows). This imposes a restriction that WAS access Domino via CORBA/IIOP, not the local Java classes. Everything still works but there is an extra layer of abstraction required. Again, this is planned to be fixed when the bundle revs to WAS 5.x.
Q. You previously endorsed Tomcat (at least implicitly) by making it part of the proposed “Garnet” elements of Domino 6. Why can’t I just use that?
A. You certainly can use Tomcat, or any other J2EE server. The entitlement for WebSphere is offered as a way to achieve a single vendor solution and as a way to get a top-quality, market-leading offering for your J2EE development needs.
Q. So this replaces Garnet?
A. No, although the functionality in Garnet had a lot of the same design goals, in terms of making it easier to extend Domino applications with J2EE. Garnet was a project to embed J2EE capabilities within Domino, including rudimentary servlet and JSP editing capabilities in Designer. The decision was made to discontinue the Garnet work primarily because it did not meet the prescribed standards (or conventions) of J2EE. The WebSphere entitlement meets the need to add J2EE elements to Domino, but does so in a way that is standards compliant (J2EE certified), and helps Domino developers gain skills that are valid in the fast-growing J2EE marketplace.
Q. Do I get upgrade rights from this entitlement?
A. Upgrades will be posted to the Passport site as they become available and are tested. Lotus will make its best efforts to minmimize any lag between generally available (GA) WebSphere products and the entitled software, but quality and testing take precedence to ensure the best possible customer experience. There are no upgrade rights to any retail version of WebSphere.
Q. Will you still also include a native servlet engine in Domino, as you did for R5?
A. Yes, the servlet engine in Domino has been updated for Domino 6, so any applications previously created for it should run fine. This servlet engine is not J2EE certified, however, and may not be revised as often as a product like WAS, for which the servlet engine is a key component. For this reason, we found that many R5 customers took advantage of the WAS 3.5 SE entitlement and the ability to "swap in" its servlet engine in Domino.
Q. Is this part of the Lotus "nextgen" strategy?
A. It is consistent with the nextgen strategy. Lotus has stated it commitment to enhancing its entire product line with J2EE elements, wherever possible, and this is part of that. Separately, Lotus has announced a parallel initiative to exploit its unmatched expertise in collaboration technology in creating a new set of components that deliver many of the same benefits as current Lotus products (e.g., awareness, instant messaging, document workflows, expertise location), in a new form designed to be used in a J2EE environment.
Q. Other IBM Lotus products include Domino (e.g., Sametime and QuickPlace) -- Do I get this WebSphere entitlement with them as well?
A. No. The possible exception is if the product license you are purchasing (e.g., Sametime and QuickPlace) expressly requires WebSphere -- but in that scenario the license for the purchased product takes precedence.