Lotus what? Nah mate, the world has moved on.

Friday, 19 February 2016

wissel.net :: Vert.x and Domino

wissel.net :: Vert.x and Domino:

'via Blog this'

An interesting article written by Stephan Wissel.


A while ago I shared how to use vert.x with a Notes client, which ultimately let me put an Angular face on my inbox and inspired the CrossWorlds project.
I revisited vert.x which is now 3.2.1 and no longer beta. On a Domino Linux server (I don't have Windows) and on a Mac Notes client the JVM is 64 Bit, which makes the configuration easier (no -w32 switch, no download of an additional JVM). The obligatoryHelloWorld verticle ran quite nicely with my manually. However it wouldn't run, when the Domino ran using a startup script.
The simple reason: to be able to access the Domino instance the vert.x verticle needs to run with the same user as the Domino server. su into the user doesn't do the trick - and of course you can't login into my server with the id that runs Domino. The solution was to turn to the expert and his outstanding Linux boot script. Using the /etc/sysconfig/rc_domino_config_* file you can simply define the behavior of your Domino startup and shutdown experience. Mine looks like this (I use "domino" as my standard user, not "notes"):



I have installed vert.x using npm using the full stack. With node.js installed, all you need is sudo npm install vertx3-full. Of course there are more conservative ways to install, vert.x, this may be an exercise left to the reader. I didn't use any of the environment variables exposed by the standard boot script to keep it independent. The script itself is just a few lines:


# Starts the vert.x tasks that talks to Domino
export JAVA_HOME=/usr/lib/jvm/java-8-oracle
export VERTX_HOME=/usr/lib/node_modules/vertx3-full/vertx
export CLASSPATH=.:$DOMINO_HOME/jvm/lib/ext/Notes.jar:$CLASSPATH
vertx start com.ibm.issc.verseu.VerseLauncher -cp /home/domino/scripts/verseu.jar --vertx-id domino

The shutdown script is short and sweet. Since I used an vertx-id, I can use that to shut down the verticle without knowing or caring for its startclass name:


# Stops the vert.x tasks that talks to Domino
export JAVA_HOME=/usr/lib/jvm/java-8-oracle
export VERTX_HOME=/usr/lib/node_modules/vertx3-full/vertx
vertx stop domino

Next step: write some actual code beyond "Hello World".
As usual YMMV

Tuesday, 5 January 2016

LDC Via: how does it work?



LDC Via offers a comprehensive programming model to make the most of your organisation’s data: a RESTful API provides secure access to everything you need, and you can build a new front-end to your data using whatever technology you wish—our own LDC Via Lens offering lets you build a simple interface with no code at all!

Whether migrated using our web application or a local installation of the Java utility, your data is safe and sound. All content is stored in a resilient, backed-up MongoDB instance, with our application layer (and its in-built security) on top.

There are many reasons why an organisation would want to take advantage of the possibilities offered by LDC Via. Here are some of the more common use-cases:

  • Speed up existing Domino applications by off-loading data to the LDC Via platform.
  • Move data from Domino into a document store more suited to an organisation’s defined IT architecture plans with minimal upheaval.
  • Manage the “push” of data from inside the firewall to the outside world (e.g. for suppliers and clients).
  • Use LDC Via as an alternative document store for data that would otherwise languish in an application or environment which has been retired.
  • A simple application archive solution: LDC Via’s document store coupled with its web-based data viewer and query engine make for an effective archive (especially combined with our standard application templates).


LDC Via: how does it work?:

Sunday, 6 December 2015

Bits or pieces?: Open source as weapon

Open source as weapon

I often talk about the use of an open play as weapon, a mechanism of changing the environment you exist in. Back in 2011, when I examined the phenotypic changes of companies (due to a particular cycle known as peace, war and wonder - more details here) there was a pronounced change in attitude in the next generation of companies from the use of open means for simply cost reduction to the provision of open means (source, APIs, data) to manipulate the market (see table 1).

Table 1 - Changes of phenotype from traditional to next generation.

In the following year, I examined the level of strategic play (based upon situational awareness) versus the use of open means to change a market and noticed a startling effect. Those who showed high levels of situational awareness and used open approaches to change a market showed positive market cap changes over a seven year period (see figure 1).

Figure 1 - Changes of market cap with Strategic Play vs Open approaches.

I've talked extensively about the use of Wardley mapping and how you can use this to identify where you might attack a market. I've also provided examples such as "Fool's mate" which is one of about 70+ different forms of repeatable gameplay that can be applied to a given context. In Fool's mate, you attack the underlying system with an open approach in order to gain a change in a higher order system. More details are provided here but figure 2 provides an outline.

Figure 2 - Fool's mate in business.

However, even if you do have reasonably high levels of situational awareness, you understand where to attack and how to manipulate a market through open approaches then this is not the end of the story. The use of open approaches is not a fire and forget system. You can't just declare this thing as "open" or create an "open consortium" and walk away.

Unfortunately, far too often in corporations I've seen people believe that "open" is synonymous with "free resources" and that somehow by opening up a system that the community will be so grateful for the gift that they'll just adopt it and success is assured. This is la la fantasy land. The majority of today's great tech corporations owe their success to the open source community, they are built on it and they do themselves no favours to disrespect the community in such a way.

If you decide to attack a market and you decide to use open as the means of changing it (what I like to call "open by thinking") then when you launch you'll going to have to put time, effort, money, resources and skill into making it happen. Hence the importance of "open by thinking" because going open should be seen as an investment decision which can pay handsomely if done right. There are numerous pitfalls to be avoid e.g. antagonising or not building a community, not listening to a community, not acting as a benevolent dictator for that community or failing to put its interests over your own, failing to steer a clear direction, failing to invest and worst of all establishing a collective prisoner dilemma.

You are the custodian, the gardener, the benevolent dictator of the community you hope to create. The act of throwing some code over the wall, creating an open source consortium and running a social media campaign on how "good" you are is a long way off from what you need to be doing. It is more akin to the self aggrandising but absentee landlord who claims the lack of tenants for their unsafe flats is purely because people renting properties are ungrateful.

Yes, you can use open approaches as a weapon to change the market in the battle between companies but it's a weapon that requires skill, dedication, investment and care.

BTW, I do love Chapter 12 - How to tell if a FLOSS [e.g. open source] project is doomed to FAIL. Hat tip to Jan Wildeboer for that one.

Bits or pieces?: Open source as weapon: I often talk about the use of an open play as weapon, a mechanism of changing the environment you exist in. Back in 2011, when I examined t...

Total Pageviews

Google+ Followers


Blog Archive

Popular Posts

Recent Comments

Rays Twitter feed


Web sites come and go and information is lost and therefore some pages are archived. @rayd123 . Powered by Blogger.