Notes / Domino by Sven Hasselbach 

node node.js, domino-db & Docker (12): DominoDB and a big NO-NO?  

By Sven Hasselbach | 11/15/18, 6:17 PM | Infrastructure - Notes / Domino | Added by Oliver Busse

Disclaimer: This is a response on Heiko’s post about his security considerations with the domino-db module. It is good to have such a discussion, and hopefully this discussion will go on. This is my personal view on this topic. If you have another opinion, feel free to add a comment.

node.js, domino-db & Docker (5): memcached  

By Sven Hasselbach | 11/5/18, 2:04 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

To use memcached in our Docker container, we have to modify the existing Dockerfile a little bit. First it is required to install memcached in the container itself, and then it is required to change the CMD command to start the service and our express application.

node.js, domino-db & Docker (4): Error Handling  

By Sven Hasselbach | 11/1/18, 10:03 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

When we started our express application and accessed it in the browser, an error raised on the console and no response was sent back to the browser. The reason for this behaviour is that the database connection is not correctly configured, and the request from our application fails.

node.js, domino-db & Docker (3): Adding domino-db  

By Sven Hasselbach | 11/1/18, 2:46 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

The express application is still the boilerplate created by express generator. Now let’s look into the existing code and use the domino-db package. First we have to understand express a little bit better. I won’t go deeply into details, because there are many tutorials available, and the documentation is really awesome.

node.js, domino-db & Docker (2): Dev Environment  

By Sven Hasselbach | 11/1/18, 2:45 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

Before we can start to create a new app we first have to setup a development environment. While there are multiple IDE’s around, I have made most of my node.js development with Atom instead of an IDE like Eclipse or Visual Studio. Maybe this will change in the future, but for a better understanding, let’s start with Atom and do the required steps manually.

node.js, domino-db & Docker  

By Sven Hasselbach | 11/1/18, 2:45 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

Here is an example to create a express application with the new domino-db npm module and run it in a docker container. Requirements are that node.js & Docker is installed. Everything is done in the command line and a text editor.

Domino & Spring Boot: ScheduledTasks  

By Sven Hasselbach | 5/2/18, 7:55 AM | Infrastructure - Notes / Domino | Added by John Oldenburger

When developing Spring Boot applications running on Domino, there is a feature which runs out of the box and makes developers happy: ScheduledTasks. These are the equivalent for agents, but they are running directly in the HTTP task (which allows to access the complete Spring Application at runtime).

Domin & REST: Debug your Plugin  

By Sven Hasselbach | 3/7/17, 10:05 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

When developing OSGi Plugins, you should have your own development server running on your local machine. Not only because of the faster deployment of changes (a new version of a plugin must always deployed with a HTTP restart), but because of the Java debugging posibilities: Only one Eclipse instance can connect to the JVM, and every request processed by the server will start the debugger.

REST & Security: Why HTTP GET is insecure (and the other methods too)  

By Sven Hasselbach | 2/26/15, 6:43 AM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

Yesterday René commented that submitting username and password with HTTP GET is insecure, because they are submitted in clear text over the wire as part of the URI. At the first moment, I did not give some thought about it, because it is known fact that data added to an URI are less secure. They are added to the browser history, are logged in the requests on servers, and every proxy.

Rest & Security: More about the DominoStatelessTokenServlet  

By Sven Hasselbach | 2/25/15, 8:09 AM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

During the last days I have refined the DominoStatelessTokenServlet a little bit. It is now a pre-beta release, and I think it is time to explain some details about it. While it is still a proof-of-concept, it demonstrates how a stateless authentication can easily be implemented. A lot of testing is still required until it is ready for production use, but I think it provides really cool things for the domino environment.

REST & Security: Same-Origin Policy / CORS  

By Sven Hasselbach | 2/2/15, 8:16 AM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

The “Same-orginin policy“ is an important concept for protecting web applications. In short, only resources from the same domain are allowed, everything else is permitted. To allow access other domains in your application, you have to enable “CORS“, a tutorial how to enable this on a Domino server was written by Mark Barton a while ago.

HowTo: Vaadin on Domino (4)  

By Sven Hasselbach | 1/26/15, 2:18 PM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

Now, let’s access some Domino resources. I have created a database named “VaadinResources.nsf“, containing a normal image resource, and an image added via package explorer to the “WEB-INF” folder. Vaadin provides stream resources, which allows creating of dynamic resources. These resources handle “InputStream” objects, which we can grab from Domino via Java NAPI.

HowTo: Vaadin on Domino (3)  

By Sven Hasselbach | 1/25/15, 4:19 PM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

HowTo: Vaadin on Domino (3). Let’s create another application, based on Vaadin’s AddressBook example. You can download the source code directly or grab the code from the repository; it is a single class file named “AddressbookUI” only. After importing (or manually creating) the class in the HelloVaadin plug-in, the servlet configuration in “web.xml” must be updated.

HowTo: Vaadin on Domino (2)  

By Sven Hasselbach | 1/25/15, 4:16 PM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

HowTo: Vaadin on Domino (2). When running your own servlet, you eventually want to access the Domino environment. To do this, some changes has to be made to the HelloVaadin plug-in. Open the “MANFIFEST.MF” and open the “Dependencies” tab. Add the plug-in “com.ibm.osgi.domino.core” to the list of required plug-ins.

HowTo: Vaadin on Domino  

By Sven Hasselbach | 1/25/15, 4:13 PM | Infrastructure - Notes / Domino | Added by Johnny Oldenburger

HowTo: Vaadin on Domino. This example requires a valid XPages Plugin Development Environment. The execution environment used is the XPages Domino JRE. The <init-param> tag inside <servlet> defines our UI class of our application. We will create this class later. The <servlet-mapping> defines a mapping inside the webapplication path.

Security: Usefull HTTP Response Headers  

By Sven Hasselbach | 1/15/15, 10:45 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

Here is a list of usefull HTTP headers for responses you should know about