Reflections on Engage

Introduction

Last week I had the pleasure to attend Engage, the yearly event for the BeNeLux user-group around IBM’s collaboration portfolio. Indeed it was a pleasure, due to the efforts of Theo Heselmans and his team, the sponsors, the location and of course the participants. Much appreciated! No user-groups without users!

Before the event I read a tweet of someone wishing all attendees at Engage good luck with finding IBM’s roadmap for Domino. I took this tweet with me in mind to the event.

Sessions attended

Here is the list of ‘sessions’ that I attended:

  • Keynote/General opening session
  • Once you go graph
  • IBM Domino App. Next
  • The Lotus position: four degrees of freedom
  • Round table: IBM Domino Development
  • Speedsponsoring
  • Live on the edge of innovation with IBM bluemix
  • Creating mobile apps: an introduction to Ionic
  • Troubleshooting XPages
  • The xpages of things
  • Break your Domino Designer dependency

I will not review each individual session but just let my thoughts run around things heard from speakers, attendees and IBM-ers.

IBM

The new general manager for IBM Collaboration Solutions gave a fresh impression and her perspective on collaboration. I am not sure how good and bad this is for the products in her portfolio and time will tell.

All the brag about project Toscana, the interpretation of Slack by IBM for me is just a bit painful. It gives me the impression that the distance between IBM Labs and the product managers in ICS have just grown through the years and makes me wonder who is holding the prophetic views within ICS?

I also talked with an IBM salesperson and my frustration with IBM Connections and trying to integrate applications with it was down-played as ‘not knowing how to use the platform to it’s full potential’ and ‘is providing links to these applications not sufficient’? Why may I not use my collaboration tools in the way I would like to and not confirm to the limitations/restrictions the manufacturer tells me to?

Sometimes I wish that IBM would train their sales personnel with the help of Watson, or something. In the meantime is was directed to TimeToAct and their web content tool for Connections.

Graph

I like the concept of graph data modelling where you ‘on the fly’ bind objects together via relationships. In a recent project we established something similar, but than specifying these relations in Notes documents and load them whenever an object was loaded. The major problem is that there is just 1 level depth of relationships, so advanced computations like ‘related’, ‘mentions’, ‘similar or most in common objects’ were not possible.

Having digged through Oliver Busse’s example and Nathan’s presentation I see the potential of Graph with Notes data and I frankly do NOT understand why IBM is not assisting the OpenNTF Domino API team to get the Graph feature available in Extension Library as from TODAY.

Graph capabilities would be a good argument for customers to keep their data in Notes (for now) and in the meantime give them the opportunity to understand and explore the (new) opportunities Graph can bring to the platform. Perhaps these customers remain dedicated to the Notes platform!

But perhaps involvement of IBM would slow down the ODA team when hearing the comment on project Toscana “only IBM would brag for two days for a feature that requires 15 minutes of coding”.

Nevertheless it hurts to read tweets from IT managers how wonderful Microsoft’s Office Graph is while IBM has nothing to offer to us.

Bluemix

And then there was Bluemix, IBM’s hybrid cloud development platform where Xpages and Notes NoSQL database are recently available.

Recently I moved a Teamroom application to Bluemix which took me a bit more time than expected due to the architecture of the application. John Jardin demonstrated some entertaining examples of services on Bluemix that can bring new functionality to Xpages applications.

Definitely a cool area to explore new paradigms and technologies.

Mobile

Mark Leusink held a nice introduction to Ionic, a hybrid mobile app framework. For me mobile development never came from the ground, mainly because lack of demand. Delivering an XPages app with responsive behaviourcapturing touch gestures and more bells and whistles did not feel like mobile development. You simple need access to and use native services to capture a mobile application full potential.

I never took the time to look at IBM’s MobileFirst platform and I wonder how many Notes customers are interested lifting multiple application straight ahead to mobile instead of cherrypicking one or two applications. For me it is also not clear where data on Domino stands in this MobileFirst story😕

Reflecting back on the projects I have been working on, having to rewrite the java classes to some client-side javascript in order to work with Domino data, would be a nightmare in the Ionic paradigm.

XPages

Aah XPages, my comfort zone. Too bad no stories or demonstrations of highly complex or smart solutions build on XPages on the conference.

Node

Niklas Heidloff‘s to have the option to have a Node.js server on Domino with capabilities to access NSF’s via Domino Access Services would be a nice option to deliver full CSJS solutions and attract a different (new) audience of developers.

Being able to develop similar applications but then on Node instead of XPages and hereby following the trends in web application development would be something I would favour. Even if that would mean to be forced to cast away all that XPages knowledge.

During the days I have spoken with developers who were irritated by lack of roadmap for XPages. I have to admit hearing Peter Janzen talking about Domino App Dev futures were giving me flashbacks to his presentation in 2015 at IBMConnect. I am not sure how big encryption is for web development. Bootstrap we take for granted nowadays. How can we integrate Domino into Connections? And (again) when can we have Graph capabilities?

Roadmap

Coming back on the tweet mentioned in the introduction. So did I find the roadmap for Domino?

It was not said where the data for project Toscana, IBM’s late adaption of Slack, would reside. Verse is (partly I guess) on Domino.

During a round table discussion with Peter Janzen about Domino App dev concerns where made by developers to have a modern Designer, preferably as a plugin in Eclipse. Peter mentioned that the Forms and View (probably also the Agents) design elements hinders IBM to move in such direction. Having worked with now with Spring Tools Suite some parts of Domino Designer are a crime (source control, build automation).

Being able to develop inline with most other web development projects like Keith Strickland demonstrated is in the benefit of Domino developers and of the Domino platform.

So excuse me for not finding this roadmap.

Wrap up

The best thing about a user-group conference is being able to talk with users and share thoughts. And a have drink and go out for dinner. I like to thank everyone I met.

One comment that I may make to the Engage organisation is perhaps the type of sessions. I met a developer who said he had submitted an abstract on developing with React and Domino and got it rejected😦

 

So this brings me to the conclusion that after having attended the conference I probably have as much (different) questions as I had before. Nevertheless I had a nice time with my fellow “experts in the field”.

Questions and Answers from deploying a Teamroom application on Bluemix

Introduction

write once, run everywhere

Thise WORE slogan is used often in cross-platform solutions, also in IBM Domino. But what if you move your XPages application from an on premise Domino installation to the cloud, more specific IBM Bluemix?

Teamroom

To gain some experience in this area I decided to take a well known application, IBM’s Teamroom and deploy it on Bluemix. I will spare you the details of creating a Bluemix account, setting up Domino Designer, deploying the Design application and binding it to a XPages NoSQL Database service. I will focus on adapting/preparing the Design of the XPages application and some areas I have not found an answer for (yet).

First consideration – Choose your data-binding

bluemixContext

Bluemix requires the separation of design and data so if you haven’t use this principle your applications yet, you must apply it now. Second, Bluemix will allow you also to run your XPages application in a mixed environment (part cloud / part on-premise) so if your application will do so the bluemixContext object will let you identify where your application is running and point to the corresponding data NSF.

DAO Bean

In my case the Teamroom application would only run in Bluemix so instead of applying bluemixContext.getDataService().findDatabaseName() I prefer to use Oliver Busse’s daobean which I have been using in other applications as well. This allows me to use the shorter dao.getDbpath() for xp:dominoDocument and xp:dominoView data-binding.

Remember: in the Teamroom design you need to set this property for every Document and View binding!

<xp:this.databaseName><![CDATA[#{javascript://bluemixContext.getDataService().findDatabaseName()
dao.getDbpath()}]]></xp:this.databaseName>

Use the search function in DDE to locate where these bindings are used.

Valuepickers

Value pickers are used throughout the Teamroom application and for the dataProvider property you need to calculate the location of the database.

Search after dataProvider and you will get the list of design elements where they are used. Look for the once who use the xe:dominoViewValuePicker since they are using a View as data-source. Again make the database location computed.

Addressbook

Some dataProviders use xe:dominoNABNamePicker and the location of the server is set via the Teamroom Setup function, which asks for the web server address. Default the web server address where the design resides is filled in. I tried to fill in the ip address of the server where the data resides (gathered via dao.getServer()) but this still did not allow me to open an NAB.

@dbcolumn @dblookup

What is an XPages application without the @dbcolumn and @dblookup functions? Use DDE to allocate in which design elements there are used and exchange the @DbName() function with bluemixContext.isRunningOnBluemix()? bluemixContext.getDataService().atDbName():@DbName or dao.getServer()+”!!”+dao.getDatabase()

database object

With the database object is you can make a quick reference to the NotesDatabse class, and so it is used throughout the Teamroom application. Mind a database.isFTIndexed() to check if the search bar will be displayed or not? Again do your search in DDE.

You can apply method chaining e.g. dao.getDatabase().isFTIndexed()

Run form validation

I noticed that I had to disable the option to validate the saving of documents using form validation (on document save option). Otherwise the operation failed silently.

Changing form name

Adding a team member via the browser resulted in a document created with the form reference of Team Member Profile   –   ParticipantProfile. If you add a member via the Notes client the form reference will be ParticipantProfile. This explains why newly created members did not appear in the list at first.

So I modified the form name as:
<xp:dominoDocument formName=”ParticipantProfile” …

I also set this alias as first in the Notes form. Not sure if that is necessary.

Wrap-up

So far so good. So how “Bluemix ready” is my Teamroom and what are my first thoughts?

Except the lookup to the name and address book I pressume my Teamroom is working as normal. I guess you can call this is major issue.

The tag cloud is not working, but that is due to the fact that the  xp:tagCoud control does not provide a database property (yet). Again I would call this a major issue.

Looking at the design of the Teamroom and counting the number of design elements I would think the development team has made the application design too complicated. I think the power of custom controls and property definitions is that you can re-use them in complete other ways and so reduce the amount of design elements.

I also notified almost no Java code in the design. Perhaps adding some classes for the objects can also reduce the amount of design elements dramatically. Also the application might get less spaghetti coded with logic stored in a central place.

Going through the code resulted in some new “discoveries” and was therefor fun to do. I will write another post about the things I haven’t used before.

Happy development and looking forward to next week’s Engage =)

 

 

Certified Application Developer Notes 9

Today I passed the second exam for my certification for IBM Application Developer Notes and Domino 9. My last certification dated from the Notes 7 era so I was forced to take the two core exams as explained in the image below:

vlcsnap-2014-10-01-20h45m37s40

 

This second exam was much more focused on development with XPages, using the Extension Library and the Mobile controls. I guess according what you would expect in modern Domino development. There were the ooccasional LotusScript and @Formula questions, but the majority of the questions were XPages related. Personally I find the setup a bit odd. I Hardly use @Formula or LotusScript in new projects. I wonder why IBM is not defining exams within each technical area seperately e.g. XPages, @Formula & Functions, LotusScript, Java and Extension Library if you wish.

Overall I liked the second exam better, no odd questions about Notes client installation, parameters in the client, more practical development questions. But also expect questions on JSF, XSP configuration etcetera.

A tip I could give is to take a look at the API documentation:

XPages configuration file format

I have not considered to upgrade my certification to the ‘Advanced’ level since I have not worked with administration so intensively lately. I expect though that the XPages mobile advanced topics would be a “piece of cake”. What are your experiences? After all it is also a financial question because the exams are not free. Maybe there will be the option to take an exam on IBM ConnectED 2015?

 

New app in town: Rooms & Connections

This post is for all you IBM Notes users:

I assume you all have experienced the problem of finding an available room when you register a new entry in your calendar. Especially with spontaneous meetings it is frustrating not be able to find a room, and if you check at the physical location the room seems to be empty.

You have then the option to start/open your laptop, open one or more the resource reservation applications and find out who has booked the room, contact the person and ask if he/she really needs the room at the moment OR dive in the room and sit uncomfortable because people could appear later and you have to find another room and start the meeting from scratch.

Those days are over! 

The Rooms and Connections app is an indispensable tool to find room information via your smartphone or tablet or book a room.

 

 

 

Engage – signed up

Funny, but a motive when moving to Sweden was to combine work with a bit of holiday. Recently I signed up for the Engage event and will do it the other way around in the Netherlands: combine holiday with a bit of work.

I am looking forward to the event because of it’s great line-up. I am curious how the ‘collaboration market’ nowadays looks like in the Netherlands and Belgium and what the opportunities are.

 

Domino Blog support tip: do not use/allow apostrophes in the Page Name field

I experienced a bit of blaming and naming today. A customer “announced” that commenting in the IBM(?) Domino Blog Template had stopped working and the counters were not correct.

It appeared that the Page Name field (shows when you select the Show Advanced link in the Notes client) had inherited the apostrophe(s) used in the Subject field. Normally these apostrophes are removed by the following input translation formula:

@ReplaceSubstring(@ReplaceSubstring(@ReplaceSubstring(pagename;”?”:”&”:”@”:”£”:”$”:”%”:”^”:”<“:”>”:”*”:”/”:”‘”:”#”:”~”:”(“:”)”:”+”:”=”:”!”:”;”:”\””:”:”:”,”:”|”:”\\”;””);”–“:” – “:” “;”-“);” – “:”–“:”—“;”-“)

pagename

For some reason this function has stopped working in the application concerned.

The Page Name field is used on the comment form in the action property:

commentform

 

Comment documents are still being created, but the relation ($REF) to the parent article/blog post can not be computed.

I hope this will help you in supporting the Domino blog.

Good news is that rumors say that IBM will soon replace this dated “traditional” template with a brand new XPages based version ;-) 

 

 

 

Comparison between Extension Library (OpenNTF) and Upgrade Pack 1 (IBM) – You’re help is appreciated

Some days ago I posted a question on the XPages development forum: Comparison of functionality between Extension Library (OpenNTF) and Upgrade Pack 1 (IBM).

I work in a hosted environment and having a change applied (continue to work with extension libraries from OpenNTF via Update site instead of Upgrade Packs) is a complicated issue. Therefor I have wrote down some use cases where new functionality in the Extension Library which are not available in the Upgrade Pack can bring value to the organisation.

To save time I only did the comparison on paper, which means I have only looked in the “readme” files distributed which each new release and compared them the “What’s new in Domino Designer 8.5.3 Upgrade Pack 1” online document. I admit this is probably not the best research but it helps you to get started.

Below you will find the comparison. Please respond in case I have missed something or understood incorrect. The use cases are too sensitive so I will leave them out of this document. Thank you in advance for your assistance!

Package name

Extension Library

Upgrade Pack 1

 

Release date

2013 April

2011 December

 

Distributed by

OpenNTF

IBM

 

Controls

 

 

 

Area: Data Access

 

 

Expose data access services.


Document

þ

þ

 


View

þ

þ

 


Relational
Database Support

 

þ

 

Area: Dojo Form

 

 

Mimic components from the Dojo toolkit.


Dojo
Button

þ

þ

 


Dojo
Check Box

þ

þ

 


Dojo
Combo Box

þ

þ

 


Dojo
Currency Text Box

þ

þ

 


Dojo
Date Text Box

þ

þ

 


Dojo
Filtering Select

þ

þ

 


Dojo
Horizontal Slider

þ

þ

 


Dojo
Slider Rule

þ

þ

 


Dojo
Slider Rule Labels

þ

þ

 


Image
Select

þ

þ

 


Select
Link Select

þ

þ

 


Select
List Text Box

þ

þ

 


ListTextBox
Name Text Box

þ

þ

 


Dojo
Number Text Box

þ

þ

 


Dojo
Radio Button

þ

þ

 


Dojo
Simple Text Area

þ

þ

 


Dojo
Number Spinner

þ

þ

 


Dojo
Text Area

þ

þ

 


Dojo
Text Box

þ

þ

 


Dojo
Time Text Box

þ

þ

 

Area: Dojo Layout

 

 

Mimic components from the Dojo toolkit.


Accordion
Container

þ

þ

 


Accordion
Pane

þ

þ

 


Border
Container

þ

þ

 


Border
Pane

þ

þ

 


Dojo
Content Pane

þ

þ

 


Dojo
Data Grid

þ

þ

 


Dojo
Data Grid Column

þ

þ

 


Dojo
Data Grid Row

þ

þ

 


Stack
Container

þ

þ

 


Stack
Pane

þ

þ

 


Tab
Container

þ

þ

 


Tab
Pane

þ

þ

 

Area: Extension Library

 

 

Extend the capabilities of the Designer Core Controls.


Accordion

þ

þ

 


Application
Layout

þ

þ

 


Bread
Crumbs

þ

þ

 


Widget
Container

þ

þ

 


Data
View

þ

þ

 


Dialog

þ

þ

 


Dialog
Button Bar

þ

þ

 


DropDown Button

þ

þ

 


Dump
Object

þ

þ

 


Dynamic
View Panel

þ

þ

 


Dynamic
Content

þ

þ

 


Firebug
Lite

þ

þ

 


Form
Layout Column

þ

þ

 


Form
Layout Row

þ

þ

 


Forum
Post

þ

þ

 


Forum
View

þ

þ

 


Form
Table

þ

þ

 


Outline

þ

þ

 


Inline
List Container

þ

þ

 


In
Place Form

þ

þ

 


Keep
Session Alive

þ

þ

 


List
Container

þ

þ

 


List
of Links

þ

þ

 


List
Separator

þ

þ

 


Multi-image
Output

þ

þ

 


Name
Picker

þ

þ

 


Navigator

þ

þ

 


Pager
Add Rows

þ

þ

 


Pager
Expand/Collapse

þ

þ

 


Pager
Save State

þ

þ

 


Pager
Show/Hide Details

þ

þ

 


Pager
Sizes

þ

þ

 


PopupMenu

þ

þ

 


Redirect
control

 

þ

 


Sort
Links

þ

þ

 


Switch

þ

þ

 


Tag
Cloud

þ

þ

 


Toolbar

þ

þ

 


Tooltip

þ

þ

 


Tooltip
Dialog

þ

þ

 


Value
Picker

þ

þ

 

Area: iNotes

 

 

Support certain views, lists, and stores.


iCal
Store

þ

þ

 


iNotes
Calendar

þ

þ

 


iNotes ListView

þ

þ

 


ListView Column

þ

þ

 


Notes
Calendar Store

þ

þ

 


Notes
List View Design

þ

þ

 


Notes
List View Store

þ

þ

 

Area: Mobile

 

 

Support mobile applications.


Mobile
Page

þ

þ

 


Mobile
Switch

þ

þ

 


Page
Heading

þ

þ

 


Rounded
List

þ

þ

 


Single
Page Application

þ

þ

 


Static
line item

þ

þ

 


Tab
Bar

þ

þ

 


Tab
Bar Button

þ

þ

 

Domino Access Services

 

 

REST API that accesses databases on Domino servers.


Remote
Services

þ

þ

 


REST
Service

þ

þ

 


Domino
Mail service

 

þ

 

Updated templates

 

 

Skeleton that contains design elements, but no documents. You
use a template to create an application.


TeamRoom

þ

þ

 


Discussion

þ

þ

 


Document
Library

 

þ

 

Social Business Toolkit

 

 

Single source for developing integrations and leveraging IBM
Connections and IBM SmartCloud for Social Business.


Activity
Stream

 

þ

 

Social Enabler

 

 

Tools and controls for XPages to access information from other
social applications such as Facebook, Twitter, Dropbox, LotusLive, or IBM
Connections.


File
service

 

þ

 


Twitter

 

þ

 


Connections

 

þ

 


Sametime controls

 

þ

 


Facebook
controls

 

þ

 


Web
Security Store

 

þ

Storage of user credentials

when an application needs to connect to third party

servers.

Distribution of the extension library

I have written a document on the distribution of the extension library. I have compared Upgrade Pack installation option with using an Update Site. You may guess who has become the winner. If there is anything incorrect stated in the document please let me know.

PDF: Distribution Extension Library

Contents

  • Introduction. 2
    • Description. 2
    • Upgrade Pack. 2
    • Update Site database. 2
  • Discussion. 3
    • Physical installation versus runtime installation. 3
    • Administration overhead. 3
    • IBM support. 3
    • Speed in delivery of new functionality. 4
    • Proven technology versus Experimental phase. 4
  • Comparison. 4
    • Winner. 4
  • References. 5
    • XPages Extensibility API Developers Guide. 5
    • Installing and administering the XPages Extension Library. 5
    • XPages Extension Library Deployment in Domino 8.5.3. 5

Introduction

This document discusses the (recommended) way the extension library is distributed within Organization X.

Description

Based on the XPages Extensibility API, the Extension Library provides a set of new artifacts, including controls, which introduces extended capabilities to supplement XPages.

At the moment we see the library distributed in 2 ways:

  • Upgrade Pack.
  • Update Site database.

Upgrade Pack

The Upgrade Pack is an installation package that contains new features and improvements in Domino Designer.

The main functionality highlights of this upgrade pack include the following:

  • XPages Extension Library.
  • Domino Designer tooling plug-in.
  • Domino Data Services.
  • Updated TeamRoom and Discussion templates.

The XPages Extension Library provides additional controls that are ready to use.

The Upgrade Pack is restricted to a specific release of Domino. Currently there is 1 version released which is dedicated to Domino 8.5.3.

The Upgrade Pack 1 is supported by IBM.

Update Site database

An Eclipse update site is a repository for features and plug-ins and it follows a standard format. In IBM Notes the update site is an NSF application where OSGi bundles are dynamically contributed to the OSGi runtime of the Domino server.

The Extension Library will be uploaded to the Update Site application from where it is made available.

A great advantage of this approach is that plugins are not physically installed on the server but started up on HTTP startup of the Domino server.

The Domino OSGi launcher will automatically detect which version of a plugin it should use. Multiple versions of the Extension Library can be hosted by an update site. This increases the delivery of new functionality.

The Extension Library for an Update Site is distributed via OpenNTF at http://extlib.openntf.org/.

Discussion

There should be a discussion what the preferred way to distribute the extension library is. Each method has its advantages and disadvantages:

  • Physical installation versus runtime installation.
  • Administration overhead.
  • IBM support.
  • Speed in delivery of new functionality.
  • Proven technology vs. Experimental phase.

Physical installation versus runtime installation

The installation (and de-installation) via an Upgrade Pack is a physical installation and demands that a server must be shut down. The installation via an Update Site is not a physical installation and the server does not have to be shut down, only the HTTP task has to be restarted on the server.

The Update Site can be installed on multiple servers via replication and hereby the installation of the Extension Library on multiple servers can be accelerated.

There is a downside to the runtime installation. A Notes server has to have defined in the Notes.INI settings that dynamic bundles can be installed in OSGI via HTTP reset:

http://www-10.lotus.com/ldd/ddwiki.nsf/dx/XPages_Extension_Library_Deployment#Set+the+Notes.INI+variable+-+OSGI_HTTP_DYNAMIC_BUNDLES

In order to have this Notes.INI setting in place the server has to be restarted once.

Administration overhead

The Extension Library provided via OpenNTF has continuous new releases. Most of these releases are bug fixes and the others provide new functionality.

It is likely that developers demand after the installation of latest release via an Update Site, in order to have access to the new functionality. This will create extra requests and administration overhead.

On the other side the physical downtime of a server has a very high impact also on the administration side (announcements, change requests, fall back servers, incident reports sent by ignorant users).

IBM support

Upgrade Pack is “supported” by IBM. You can discuss what that means. For certain you can make a PMR (problem management record) but it is not known if IBM is providing hotfixes for bug fixes for the Upgrade Pack.

Experiences in other PMR’s on Notes software (NTF templates for Notes) have not been positive always.

On the other hand one cannot really say that distribution of the Extension Library from OpenNTF via an Update Site is “not supported” by IBM. Since the release of the Extension Library there have been multiple releases (over 30) of the Extension Library. Most of these releases are bug fixes assumed.

There is a lively discussion on the Extension Library on OpenNTF http://www.openntf.org/internal/home.nsf/discussions.xsp?action=openDocument&name=XPages%20Extension%20Library&documentId=523C4281B0889F12862577910060E232 which makes the necessity of support from IBM less.

Speed in delivery of new functionality

In Today’s world software suppliers provide more often software updates silently on the background to boost security or to provide new functionality. In the browser world this seems almost to have become a standard.

Being able to deliver new functionality more quickly can bring extra value to the business.

An Upgrade Pack has only been released once until now. The announced Upgrade Pack 2 seems only to be focused on Notes Traveller. In the meantime more than 30 releases are available for the Extension Library on OpenNTF.

Proven technology versus Experimental phase

Upgrade Pack 1 contains only a stable version of the Extension Library.  The Extension Library on OpenNTF contains also experimental features (e.g. Social, RDBMS support). These features will someday reside in the ‘ordinary’ Extension Library.

The features are collected in an Extended Components library. This Extended Components library must be installed via an Update Site. From discussions on the internet it seems to be possible to install this library on top of an Upgrade Pack via and Update Site. But why use 2 methods to distribute functionality when you can combine them via one (via Update Site)?

Comparison

Based upon the previous discussion we will compare the two methods.

Upgrade Pack Update Site
Installation Physical Runtime
Administration 1 version Multiple versions
Support IBM (PMR) OpenNTF (defect, discussion)
New functionality New Upgrade (once 2 years?) New Release (each 2 months)
Proven vs Experimental Proven Proven + Experimental

Winner

The overall ‘winner’ in this comparison is the distribution via an Update Site. A runtime installation offers a lot of benefits above a physical installation:

  • Quick installation.
  • Availability server.
  • Replication option installation software.
  • New functionality.

There are some drawbacks:

  • A server needs to have the OSGI_HTTP_DYNAMIC_BUNDLES Notes.INI property which requires a restart of the server.
  • Installed versions of the Upgrade Pack should be removed first.

References

XPages Extensibility API Developers Guide

http://www-10.lotus.com/ldd/ddwiki.nsf/dx/Master_Table_of_Contents_for_XPages_Extensibility_APIs_Developer_Guide

Installing and administering the XPages Extension Library

http://www-10.lotus.com/ldd/ddwiki.nsf/xpDocViewer.xsp?lookupName=Domino+Designer+XPages+Extension+Library#action=openDocument&res_title=Installing_and_administering_the_XPages_Extension_Library_ddxl853&content=pdcontent

XPages Extension Library Deployment in Domino 8.5.3

http://www-10.lotus.com/ldd/ddwiki.nsf/dx/XPages_Extension_Library_Deployment

If alignment of a row in a view requires an upgrade of your server… (XPages Documentation Wiki)

I reported a defect on the XPages Documentation wiki. As you can see in the screen shot the alignment of information in the view is broken:

Here it is in an instance on an IBM address:

 

I was surprised I got contacted shortly after that by IBM (mostly they don’t seem to respond on reported defects on IBM projects on OpenNTF)

Here the conversation:

Michael Stewart
8:07 PM (15 hours ago)

to me, Jennifer
Hi,

Your server level may be the cause of some or all of the problems you’re
seeing. The 2.8.2 template requires IBM Domino 9.0 Social Edition. My
apologies for not making that clear on OpenNTF or in the 2.8.2 template
documentation. Jennifer Heins has added text to that effect in both places.

If you are able to upgrade, you can get the beta here:

http://www-10.lotus.com/ldd/ndsebetaforum.nsf/topicThread.xsp?action=openDocument&documentId=2F8AD78A70015CC485257AD3004AF0EE

and I would appreciate it if you could let us know at that point whether
you still see the problems you have reported.

Again, sorry for the inconvenience–but I’m also glad that you made the
initial attempt, since it exposed the need for this clarification.

Mike

From:   Patrick Kwinten
To:     Michael Stewart
Cc:     Jennifer Heins
Date:   01/24/2013 01:17 PM
Subject:        Re: Re view alignment defect

Hi Mike,

no I did not make any modifications to the views or styling.

As theme have I set idctheme, since our server is on 8.5.2. it extends
oneui2.1

KR Patrick

On Thu, Jan 24, 2013 at 6:52 PM, Michael Stewart wrote:
Hi,

Regarding this defect:

http://www.openntf.org/internal/home.nsf/defect.xsp?action=openDocument&documentId=226AFB4BE255565486257AFD003A0914

I don’t recognize the styling in the top image. It isn’t just the view
entry alignment that is off, but also the highlighting of the navigation
entries in the lefthand column. Have you made any modifications to the
styles in this wiki?

Thanks,

Mike

Well excuse me? Do I need to upgrade my server so a broken line for a row are fixed? FAIL!