Blog
Assorted articles, maxims, aphorisms and pearls of wisdom from the Teamstudio team.
Here at Teamstudio, we do our best to make Teamstudio Export as easy to configure as possible and we attempt to support as many Lotus Notes application design aspects that we come across, but there will be times things just don't seem to want to work. This article explore some of the most common problems that users encounter, and how to deal with them.
Our previous DevOps for Domino article explained the basic concepts and mechanisms used by Teamstudio Build Manager to help facilitate modern deployment and DevOps practices within the Domino application release cycle. In this article we aim to take this a step further and look at a few of the specific steps and approaches we can use to deploy an example application into an on-demand provisioned test stack on Amazon Web Services (AWS).
Previously, we have explored the topic of migrating Teamstudio Export HTML-based application archives to SharePoint sites using Microsoft based tools which have seen a few changes over the past couple of years. The approaches we’ve previously described are using SharePoint Designer and the Microsoft SharePoint Migration Tool (SPMT). There have been a couple of changes to those tools that mean we need to update our recommendations for the process of importing your Exported databases into SharePoint.
The release of HCL Domino v12, combined with Teamstudio Build Manager v9.0, opens up some interesting possibilities for using new features in both products to integrate HCL Domino apps into DevOps strategies using modern platforms and tools. This is the second in a series of articles that describes some options for how to do that.
