IBM Domino and Java problem with old applets

All the old Java applets that is YES in some old apps not yet converted used got another problem today on Domino 9 and 9.01. They are now blocked by Oracle because the code signing certificate is outdated, it seams like when they where updated to work with Java 1.7 45 the person who resigned them did that with an old certificate and now that cert is outdated and has been so for 1 month. If IBM or you want to keep track on when your code or SSL certs expires QNova Systems contract management system works really great for this purpose and many more things, contact me if you want to know more. An interesting thing will also to see if the new code cert created with SHA-2, because I don’t think you can get one with SHA-1 anymore and this will make Java 1.6 outdated because it doesn’t have support for SHA-2.

I’ll keep you updated on this matter.screen392

Moving on with Excel Export part 6 : But now we Import

The previous 5 steps in this series (part 1 part 2 part 3 part 4 part 5) has been getting data out to excel in different ways this part will show you how to get data back into Domino again thru your XPage, this will give you the possibility to roundtrip data handling. Export all customers mark the rows you have changed and re import the data. Because Apache POI is installed on the server as an OSGI we have access to these classes in all java code on the server and that is what I’m going to show you today and how to upload an Excel file and read some data from a cell.

In the example database for POI4XPages there is a class you really need and that is the ImportAction this is needed to open up a workbook of a xlsx file you don’t need it if you are only using xls. This class is used for changing the classpath of the jvm and some security stuff so you don’t need to modify the java.policy file on your server (Thanks Christian for pointing this out)

We start with some OpenNTF data in Excel


We create an java class

public String getData( file,Integer row,Integer cell){

try {

 String inputFile = file.getPath();

 String CellVal=””;

 ImportAction ioAction = new ImportAction();

 HashMap<String, String> hsCurrent = new HashMap<String, String>();

 hsCurrent.put(“FILE”, inputFile);

 workbook =, hsCurrent);

 if (ioAction.hasError()) {

   Exception exLst = ioAction.getLastException();



 Sheet worksheet=workbook.getSheetAt(0); 

 Row rowdata = worksheet.getRow(row);

 Cell celldata = rowdata.getCell(cell);

 CellVal= celldata.getStringCellValue();


return CellVal;

}catch(Exception e){

return “”;


lets look at the parts of this class

 ImportAction ioAction = new ImportAction();

 HashMap<String, String> hsCurrent = new HashMap<String, String>();

 hsCurrent.put(“FILE”, inputFile);

 workbook =, hsCurrent);

 if (ioAction.hasError()) {

   Exception exLst = ioAction.getLastException();


This is the magic call the the ImportAction class that will create a Excel POI workbook Object.

The following rows will get the first sheet in the excel file get the first row and the first cell and return the string

Sheet worksheet=workbook.getSheetAt(0); 

 Row rowdata = worksheet.getRow(row);

 Cell celldata = rowdata.getCell(cell);

 CellVal= celldata.getStringCellValue();

Now we need to create the XPage to enable the upload of the Excel file


The interesting part is behind the read button onclick event


var con = facesContext.getExternalContext();

var request:com.sun.faces.context.MyHttpServletRequestWrapper = con.getRequest();

var map:java.util.Map = request.getParameterMap();

var fileDataName = getClientId(“fileUpload1″) ;

var = map.get( fileDataName );

if( fileData == null ){



var = fileData.getServerFile();

var Excel=new com.xpagedeveloper.ExcelData(),0,0)

We get the uploaded file in fileData and retrieve the actual file using fileData.getServerFile() remember that this file is a server based temp file and with that I mean that you will not get the same same on the file as it was when the user uploaded it. And next I create an object of my class and call the getData function with the java io file object the row and the cell number remember that this has a zero based index so 0,0 is actual row 1 and cell 1, this is the result I get when running the code against the Excel sheet


If you are going to loop thru a full excel sheet you probably need to rewrite the code but this will give you a hint where to begin.

Moving on with Excel Export part 5 : XPages Export

In the previous parts (Part 1 Part 2 Part 3 Part 4) we covered plain export, styling your exports and doing selective exports. Today I want to show you how to create more advanced and flexible way to get your data using a java object that we use for the export.

We start by creating 2 java classes one for the export and one of the Export Data


Then in each class add implements Serializable and the private variable on the row below. This is so the java VM can swap the data out disk if needed.







We will start by creating our data class, very simple. Check what type of data you want to export in each column, in my case I want to export


And then we use the generate setters/getters function in DDE by right clicking in the source window


And select all variables you want to autogenerate setter and getters for an click on OK


Time to create the getData function in the Export class the important thing here is that we return a a java object of the type List.


I also create the function as static because I will only run this function and return the data once. This is the code for the export class. The important thing to point out is

The I create the Exportdata object on each row and store it in the RowData variable

And when I have populated it I add it to the Data ArrayList Object the is returned from the function at the end.

package com.xpagedeveloper;
import java.util.ArrayList;
import java.util.List;
import lotus.domino.NotesException;
import lotus.domino.Session;
import lotus.domino.Database;
import lotus.domino.View;
import lotus.domino.ViewNavigator;
import lotus.domino.ViewEntry;
import java.util.Vector;
public class Export implements Serializable 
	private static final long serialVersionUID = 1L;
	public static List<Exportdata> getData(Session session){
		Exportdata RowData;
		List<Exportdata> Data = new ArrayList<Exportdata>();
		try {
			View v=session.getCurrentDatabase().getView("City");
			ViewNavigator Nav=v.createViewNav();
			ViewEntry VE=Nav.getFirst();
			ViewEntry VE2;
			Vector Col;
				RowData=new Exportdata();
;				VE.recycle();
		} catch (NotesException e) {
			// TODO Auto-generated catch block
		return Data;


In my Excel export component in All properties datarowexport and I select to create a wgpoi:ListObjectDataSource.screen194

And click on the buildValues property to add some source


And we add this simple code to get the data from the Java objects returned you can expand you getData class and sending in filter parameters from the XPage as we did in Part 4 of this series but in this case the filtering will be done in java.


But wait, you might say how do we populate the column data. That’s the great part of the implementation. You write the name of you variable in you data class and the getter will do the rest. so in this case it will call getName from your row class that is returned.


With this new way of exporting you can combine the data from different sources not only one as I’ve shown in the past parts of this series of posts and giving even better exports to you users.

Integrating a better export into your application will make your users happier

Moving on with Excel Export part 4 : XPages Export

The recent parts of this series has shown you how to create excel exports from a view and also changing the layout of the reports with headers and logos. This post will show you how to filter the data in your excel reports both using keys and fulltext searches. Let’s get started.

To get some filtered export we add an combobox into our XPage and in this case to show both a Export with a key and search we have two buttons for the different export options.








The code behind the combobox is a standard lookup fro the value data







And storing the information within a viewScope variable ExportData










The setup behind the buttons is the same as we done in the previous posts but we add a scriptblock before doing the actual export









If we look at the simple formula for a key based export.














We clear the ExportSearch viewScope var I’ll explain this later and assign the ExportData var into the ExportKey var. The view we are working against is an ordinary view with a categorized first column.








What you need is assigning the key param with the viewScope.ExportKey. In this case I’ve also assigned the search param. But in an ordinary case you would probably assign only one of them. Depending on if you want to get all documents by category or by Fulltext search.








The code behind the search export button is this

screen230We place a standard FT search formula inside the ExportSearch viewScope variable. Selecting all documents that the field Region has the value stored in the ExportData viewScope variable.

So exporting to excel with user customized data has never been easier. 

Apache POI for XPages has more options up it sleave so this series will continue so stay tuned in.

Moving on with Excel Export part 3 : XPages Export

Making you report look a bit nicer with some formatting.

Excel reporting from views can be so dull and boring the XPages for POI can give you more options in this matter and help you create some design to your report.

1. Customizing your template

Because POI is using a copy of you template you can customize your temple with logos and predefined information.







We need to import this new template and change the startRow and template name


In this case we start at row 12 below the logo and we assign the new template with the logo that we created. Note that the data will be placed on the row below the one you specified, don’t know why but good to know.











And the Export will be a combined with the logo from the template and the data from the Domino view.

But we want more

2. Setting up a header for you data

This can be done in two ways 1 directly in your template but that isn’t good in if you want to add a column that you need to change the template or if you want to use the template for multiple exports.

So what we do is that we add columns to our Export above the data, we need 4 columns for this example.


We click on add on cellValues and add 4 items of cellValue and as you can see we could also add data to Excel bookmarks. Could be handy if you have a multi sheet excel file.


We specify the columnNumber, rowNumber and because we know the header value we write it but we could actually compute the value also. But a header in plain text is quite dull so we click on cellStyle, scroll down and set the property to get bold on the font and a bigger size.


Your Excel export with a custom logo and a styled header is now ready. There is lots of stuff to cover with POI and application integration so this series will continue, the more I dig into POI for XPages the more I love it.











Part 1:

Part 2:

Moving on with Excel Export part 2 : XPages Export

In my last post I wrote about how to in some simple steps generate an automated export of an view to excel. In this post I will show you how to fine grain this using the excel component instead.

Start by creating a blank excel file note what the sheet you want to place data on is called usually Sheet1 if you have an english version of Excel. Save and import it as a file resource in the database, name it export.xlsx

Now create a new XPage add a button and the Excel component POI Workbook






This is how the result should look







Now add a simple action to the Export button













Select the Excel Component and go to all properties and create a new resource template


In the resource template specify the name of your excel template





The template is now ready to be used and we can now move over to setup the actual data that should be added to the spreadsheet. create a new dominoViewSource


Specify your view name in my case Images


Look at your view and note down the column headers, I have 4 columns with the names Topics, Size, Created and last a calculated column called Ext


Add four columns in your component





On each column add the Column number in the Excel sheet where the data should be placed and the name of the column.






In my case I ended up with this

screen200And now to we need to add the name of the exportfile and the easiest thing to forget the sheet name where you want to place the export data, Sheet1 in my case.


Now you view export is a bit more advance and you can specify what to export and in what column.

I will continue the series and show you more about the power of POI for XPages, stay tuned.

If your user want reports in Excel you should read this

XPages did get a great addon more than a year ago to be more exact 13:th of September 2013. It was when Christian Güdemann uploaded the first version of POI for XPages. Apache POI is a rather old apache project, 13 years to be exact. And there have even been a Notes in 9 show by Paul Calhoun on how to use the standalone version of Apache POI.

But Christians version makes everything that much simpler to get the Excel file out to the end user, start by going to or if you want lots of more great XPage addons. Download the latest version of one of the project.

Now you need to install the OSGI plugins into your designer and to the server, and David Leedy as recently created a notes in 9 video on how to install plugins into the designer and the server.

And when you have installed POI for XPages in both places you are good to try it out.

It’s very simple, Add the poi library to the database you want to use it in you do this in in the  Page Generation tab







Now you are ready to create a new XPage, when you have created the XPage.






Drag the simple View Export into you new Export XPage also create a button on your XPage







Click on the button and create a simple action














Select the sveId, you should find the ID of your simple Export control in the list.

Select you export component and select “All properties”


Fill out the downloadFileName with a name of you choice i.e export.xlxs


also select if you want if the view headers should be exported includeHeader and write the name of the view you want to export view.

Open up the XPage and click on the button and you export will be sent to you client.

News from IBM ConnectED15

Some of the news from IBM Connect

IBM releases early access to IBM Verse.

IBM Verse will come an an Domino solution for on premise deployment later this year

The Domino HTTP engine will get more updates that the previous released updates with SHA2 and TLS 1.0

It will get new HTTP security options as TLS 1.2, PFS and AEAD



the IBM HTTP server addon released with Domino 9 will be deprecated

screen105The NSF Datastore will get updates that we have all wanted for a long time.

View Indexes outside of the database and with this and DAOS we are breaking the 64GB nsf database maximum finally.

Live view updates is a server task that will pull and update view indexes with a interval of your choice this update is already in 9.0.1 FP3


XPages will receive support for encryption and signatures

New backend classes for XPages, Lotuscript and Java agents

There are plans for future upgrades to update java in Domino to 1.7 or 1.8



XPages support in Bluemix, see Niclas article 

Availability for this great new functionality is Q2 2015, price has not been announced yet.

This is the news I have captured, if I missed something please comment

Part 2 of Partial Refresh in Notes Forms

I couldn’t actually accept myself defeated in the battle to get partial refresh into old school Notes applications. And after a second look at my code I found a way, so I rewrote the javascript library to be a javascript object class so all calls are made inside the class. So now partial refresh of the entire form tag is the standard way of refresh but you can also narrow the refresh to everything inside a div or a table sell if you want to. And Serverside refreshes from a QuerySave agent also works.

So what you need to do is to add the AjaxCall scriptlibrary to your database.

Call the function PartialDomino.onloadAjax() in your onload event

Now all refresh events on the form will be handles as partial refresh.

If you want to also add clicks from a button, give the button a id and add that id using PartialDomino.addPartialRefreshId(“refresh”,””)

The next time the button is clicked a partial refresh is done.

If you would have added a second id to the function, only the element with that id will be replaced after the refresh.

Download the database and see the working example


2014 a year of change

Looking back at 2014, I see the year that XPages really got accepted as the primary language for Domino.
IBM Bluemix got launched and the response was no XPage support in Bluemix, but in the last 2 months we saw that IBM had changed their minds and now there are talking of some kind of support for xPages apps in Bluemix. Great IBM that will get the community to start using the service even more if you can deploy your apps in a real scalable App Engine. The Domino OpenNTF API, evolved and have lot’s of great features like the graph database implementation.

My 2014 has been almost only XPages Development both internal with our application suite, custom applications for different companies and adding more customers to QNova:s application cloud  that has been a real success for the company I work for. My board work with OpenNTF has just started, lots of things to understand and I hope to be able to contribute even more in 2015.

Hope you all out there have a great holiday and come back in 2015 with new contribution power because we all can do more if we do it together.