HCL Domino AppDev Pack 1.0.2 – Documentation Released

The documentation for the new version of Domino AppDev Pack 1.0.2 is available.

So if you are evaluating to deploy the Domino AppDev Pack, make sure to take a look at the release notes of the 1.0.2 version.

What’s New in Release 1.0.2

Release 1.0.2 includes the following new features:

  • (Preview) A domino-db application may now request the ability to make Proton requests on behalf of a user. The feature, collectively named Act as User is implemented across multiple components from the AppDev pack. For details, see:
  • IAM service
    • Efficiently leverage multiple CPU cores on the server.
    • The ability to configure token expiration. See Configure Token Expiration.
    • Support 3rd party statistics server integration through ‘StatsD’ protocol. See IAM statistics.
  • The ability to create and read Names, Readers and Authors items.
  • The ability to create, read and delete attachments. See Attachments for details.
  • The ability for Proton to update the Domino directory with an application’s certificate. See details here.

HCL Connections – Replacing Textbox.io with TinyMCE

We have the possibility now to replace Textbox.io editor with TinyMCE. I like this new addition to the product and I did not have any issues with.

Replacing the old editor is really easy, basically you use the same process as updating Textbox.io.

But do take care, some formatting, in Wikis for example, will get lost after you switch the editors. So make sure to fill your test environment with some articles from the production and check with your users if this poses a problem for them.

HCL Connections – Survey Export Issue

Recently I came across a problem when exporting the Survey results to an Excel file, export to Open Document Spreadsheet didn’t work also, though export to an XML File worked without any issues.

The error in the GUI I was getting was:

We are unable to process your request. If this error persists, report the problem to your administrator and provide error reference.

The errors I have seen in the Surveys Application Server log:

StandardExcep E com.ibm.form.nitro.platform.StandardExceptionMapper toResponse c29d32cb-eaf7-4c42-a9c3-eaf05d272f69
com.ibm.form.platform.service.framework.exception.ServicesPlatformException: java.lang.NoClassDefFoundError: org.odftoolkit.odfdom.pkg.OdfFileDom

AbstractFrame E com.ibm.form.platform.service.framework.AbstractFramework frameworkEvent Framework error:
java.io.IOException: Exception in opening zip file: /tmp/ibm.fsp.temp.1559308546569/configuration/org.eclipse.osgi/bundles/33/1/bundlefile

The environment I was getting this error, was a Connection 6 CR4 environment, thankfully after I updated to WebSphere and Connections 6 CR5 this error was gone. So If you get this error, make sure to update to the latest Version of WebSphere and Connections prior to contacting HCL and opening a case.

HCL Verse on-Premises 1.0.8 is around the corner!

Today I came across “Verse on-Premises 1.0.8” section in IBM Knowledge Base, there it is mentioned that the Version 1.0.8 is coming in Q3 of this year.

In the “What´s New” Article, I found a few interesting features like the possibility to manage your Notes ID Password from Verse. We know that HCL wants to get rid of “Internet Passwords”, this might be first step of many to be made.

Being able to see your Archive is also a nice touch. We missed this for quite some time.

It looks like you will need Domino 10.0.1 FP2 running under Verse to be able to activate the new features, there are also a few new Notes.ini Settings you will need to set and a few options in the Notes Policy so that the users are actually able to change their Passwords. So you might want to prepare for that.

HCL Connections – The Future is Bright

Yesterday I took part of the Webcast, “HCL Connections: The Future is Bright”, it was hosted by “DNUG” (a big thumbs up for that). In this Webcast Danille Baptiste showed us the future plans for HCL Connections. And indeed I do think that the future of the product is bright. The HCL is planing integrations with Microsoft Products, Salesforce and SAP just to name a few, and finally, a proper Integration with Domino! 🙂

I always thought that I knew about all the “Connections Assets”, add-ons developed by “IBM Services”, well I was wrong, Danielle mentioned at least ten of them of which I never heard about. And guess what, HCL will make them all generally available, they will also be installed as a part of the Connections installation.

The thing I like the most is, being able to see all the information you need on single screen/browser tab, things like that blow me away and I hope this will come rather soon:

Danielle also presented a Roadmap for Connections, at the end of the Q3 we should get the next CR, and towards the end of the year we will get Connections 6.5. From there on HCL plans to deliver a major release every year.

Here are a few more slides presented.

I like the way the product is heading, the HCL recognizes the products strengths and weakness and you can clearly see that in their vision. We will hear more of that and in greater detail at Social Connections 15 in Munich.

Notes Shared Login/Notes Federated Login and Smart Card Support

One of our customers wants to implement Single-Sign-On for Notes Clients on Windows Operating Systems and in the future they plan to implement Smart Cards as a Login mechanism on Windows PCs.

Due to some misleading official articles, I was not sure if Smart Cards are supported with NSL or NFL. After a check with IBM Support, it turns out that Smart Cards are supported with Notes Shared Login and Notes Federated Login, as long as you do not use “Smart Card Protected ID” Feature.

So, as long you use Smart Cards solely for OS access/login you are good to go to use NSL or NFL for Notes SSO.

IBM Connections – Restricting the Community Types Users can create

A while ago we had a requirement to restrict the Community types users can create, in the following I will describe how you can do that. First of these settings are primarily managed in “communities-policy.xml”, you must do the following steps to check the file out and be able to edit it.

  • Start the “wsadmin” command tool and give yourself the administration rights.

./wsadmin.sh -lang jython -username wasadmin -password <password>


  • Check out the “communities-policy.xml” configuration file.


  • Navigate to the folder where you have extracted the community configuration files and open “communities-policy.xml” file in your preferred editor.

Going through the Configuration file you will get the idea what you can do. But simply editing the file won´t get the job done, we also need to make use of the “Security role to user/group mapping” in Websphere console. We will get to that towards the end. Being the case that we cannot create additional user roles in WAS, we must make use of what we have offered, so in the example bellow we will make use of the “Reader” Role in Community application.

    The plan was to allow all users to create only Restricted Communities and grant the “Power Users” the ability to create Restricted and Moderated Communities, “Global” Community Administrators will still have the right to create all types of Communities, including Public Communities. In order to do that you have to take the following steps.

  • Add the following lines under <comm:policy>, Reader section:

<comm:permission class=“com.ibm.tango.auth.permission.CommunityManagementPermission”communityType=“private”action=“create”/>

  • And comment out the following lines in the Community Creator Role section (using “<!–” and “–>”):

<!– <comm:permission class=”com.ibm.tango.auth.permission.CommunityManagementPermission” communityType=”public” action=”create” /> –>

Screenshot of the Configuration file: 

  • Save the changes and check the configuration files back in.


  • After that, make sure that the WebSphere Nodes are Synchronized.
  • Change the Security role to user/group mapping.

By using the following settings all Users will be allowed to create Restricted and Moderated Type of Communities.

By mapping the “Special Subjects” to “None” and setting a desired User Group for “community-creator” role, we can achieve the desired settings.

After clicking the “OK” button, the application should be restarted automatically, so you do not have to restart it manually, but keep that in mind, because your users will not be able to access Communities during restart. After doing so, we should have the following result, all users can create Restricted Communities:

Power Users have additionally the ability to create Moderated Communities:

This is just one of the possibilities you have, you could for example also manipulate the configuration file to take away the ability for all users to create Restricted Communities.