Since it's not possible to identify encryption status and level using native LotusScript/Java classes here is a way to do that. The solution is based on Notes CAPI (within LotusScript) but it works for both Linux/Windows environment.

In my last blog post I talked about challenges we had to overcome as a team with regard to caching of constants. But a bigger challenge we hit was caching of design elements. Part of the solution we built required copying design elements from one database to another. Part of the beauty of Domino is that everything is a Note - including design elements. Design elements are just Notes with a special flag. So just as you can copy a document from one database to another by getting a handle on the note, you can also copy a design element from one database to another by getting a handle on the design note.

Though Domino's HTTP stack infamously doesn't support WebSocket, WebSocket isn't the only game in town when it comes to getting push-type information to HTTP clients. HTML5 also brought with it the less-famous Server-Sent Events standard, which is basically half of WebSocket: it allows the server to push events to the client, but it's still a one-way communication channel.

A while ago I started my journey into testing applications. Like most people I started with Selenium IDE since it’s free, easy to install and setup. The idea was to record the workflow in an application and play it back after the development of every new feauture.

In some previous posts, I've started talking about some steps one can take to make a complicated XPages app more platform-independent. There's a lot to be done there, refactoring code to bridge differences between runtime environments and to lessen dependencies on XPages-specifics things, but there's a huge elephant in the room: all that XSP markup.

Recently I’ve been involved in a project with a lot of LotusScript. As a team our approach has been to structure the code according to best practices and leveraging what we’ve learned from other languages. Standards are always good, but there are always peculiarities that impact what you do. The crucial skill is to be able to work out what is happening when the standard ways don’t produce expected results. And most importantly, work out how to work around them.

Many of us Notes developers know the problem. You have developed a Java agent that contains methods from imported .jar files in addition to the actual code. When the agent is executed on a HCL Domino server, it works for a while ( sometimes longer, sometimes shorter ), but then causes problems due to memory leaks. The problem lies in the architecture of Domino. The imported .jar files are reloaded every time the agent is started and over time they use more and more RAM.

In my last post and its predecessor, I talked about my tinkering at the XspCmdManager level of Domino's HTTP stack and then more specifically about the com.ibm.designer.runtime.domino.adapter.HttpService class. Now, HttpService is about as generic a name as you can get for this sort of thing, and it doesn't really tell you what it represents. You can think of Domino's HTTP stack since at least the 8.5 era as having two cooperating parts: the core native portion that handles HTTP requests in basically the same way as Domino always did, plus the Java layer as organized by XspCmdManager. The Java layer gets "right of first refusal" for any incoming request that wasn't handled by a DSAPI plugin: before routing the request to the legacy HTTP code, Domino asks XspCmdManager if it'd like to handle it, and only takes care of it at the native layer if Java says no.

In my last post, I described the new auto-configuring reverse proxy I added. This gives you a unified layout that points to your configured webapps first and then, for all other URLs, points to Domino. After that, though, I realized that there'd be some convenience value in doing that kind of thing in Domino's HTTP stack itself.

This has bugged me for a while. I may have just been a bit lazy as well. But that's what friends are for, and Ted Hardenburgh came to my rescue in our Openntf slack channel. You can join the slack channel here: https://openntf.slack.com if you have FOMO or just want to ask us your crazy questions. Anyway, back to Ted's help with my situation. We have a client running a task that is not a native Domino task, and I wanted to monitor it from the Admin client's Server-Monitoring tab that acts as a Dashboard. You did know you have a dashboard built into the Admin client, right?