Runing Lotus Domino on a mainframe

Sean Burgess suggested that I blogged about running Lotus Domino on z/OS for a development server so here goes:

I am acting as an IT architect for a system called ePOS which acts as a frontend to a payment solution called IBM Payment Systems. This frontend solution is running on Lotus Domino R8 for z/OS – and was upgraded on August 26 from R7 in order to better consume web services on a backend system. The mainframes in question are two IBM z990 (eServer zSeries 990) running z/OS 1.9.

The system setup for the Domino solution is as follows:

  • development server: single Domino server on a single z/OS LPAR
  • combined test and pre-production server: two Domino servers in a cluster on two seperate z/OS LPARs
  • production server: two Domino servers in a cluster on two seperate z/OS LPARs

Please notice that the two mainframes are responsible for all of the 5 LPARs mentioned above.

Teamstudio CIAO! is used for configuration management of the databases on the development server.

The development server is accessible from the intranet only while the test and production servers are accessible from both intranet and internet. The common IBM LDAP (IBM Bluepages) is used for authentication for the intranet systems while a seperate LDAP server is used for the authentication of internet users. The ePOS application accesses backend systems using Java APIs and web services.

I have previously blogged about architectural patterns and Lotus Domino and in this case the architectural pattern used to access Domino from the internet is the “caching proxy and Domino” pattern combined with the high availability caching proxy pattern. This means that the Domino server cluster is located on the intranet while a redundant reverse proxy server (Tivoli Access Manager WebSEAL) is located in the DMZ.

As mentioned I have the role of being the IT architect for the solution running on these servers. I am not responsible for the actual installation of Domino on z/OS but besides doing architecture work I am also involved in the administration of the Domino servers.

Update August 26: The development server has been upgraded from Domino 7.0.2 to Domino 8.0.2.

DXL: Domino XML

I recently listened to the first episode of the YellowCast podcast and was reminded how powerful DXL is. I created this blog post to store my notes from listening to this podcast and to provide others with links to all the useful info that the YellowCast hosts Chris Toohey and Tim Tripcony shared during the podcast.

DXL is XML for Lotus Notes and Domino and is the XML representation of Notes/Domino data and design. DXL uses a Notes/Domino specific DTD located in the xmlschemas directory of the Notes client. Although powerful DXL is not entirely complete yet and has issues with roundtrip fidelity (export followed by import can lead to missing design elements).

So what can we do with DXL according to Chris and Tim:

  • You can actually write code for writing code! Chris gives an example of an agent that exports itself, rewrites the exported XML and then imports itself and thereby modifying it’s own code. It is not easy to imagine the usefulness of this but it sure shows how powerful DXL is.
  • You can add code from outside of your application in order to add new features. For example you can install OpenLog to an existing database using DXL. So you could skip error handling while developing and then install ipenlog before user acceptance test.
  • You can download image resources via DXL.
  • You can work with documents in a corrupted database by exporting the documents using DXL.
  • You can export design elements and process the XML outside of Lotus Notes in order to do e.g. search and replace across design elements (similar to what you can do with Teamstudio Configurator).

To get started with editing the exported XML you need a XML editor – and the hosts recommend Eclipse, Aptana, or the free Microsoft Visual Studio Express.

To get started with your first “Hello World” example in DXL create a simple agent in Domino Designer and view the agent as exported DXL using Tools – DXL Utilities – Viewer. Then try to do a real export, modify the exported XML and then try a real import of the XML. Check the Domino Designer Help for the NotesXMLProcessor Lotusscript class and its derived classes for information on how to do this.

Using the NotesXSLTransformer Lotusscript class you can use XSLT to convert the DXL into anything as the hosts phrase it.

Chris and Tim also mentions a lot of examples of using DXL that are available out there on the Internet:

Check out the show notes of YellowCast episode 1 for more links.

I’m the GONAD Worshipful Grand Dragon for Denmark

I have just been accepted as an official GONAD (Geeky Order of Notes Admins and Developers) member by – more precisely with a degree of Worshipful Grand Dragon for Denmark. I am so proud! 🙂

If you are interested in GONAD and in applying for membership you can read more here: