203 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
Domino – Often Still the Best
Thu, Nov 9th 2017 18
IBM Announcement – HCL to take over Notes and Domino Development
Tue, Oct 31st 2017 9
Moving to Microsoft – Sharing Notes Apps from the O365 Portal
Tue, Oct 31st 2017 5
MWLUG 2017 – We Believe!
Thu, Sep 7th 2017 9
Why we DO migrate code.
Tue, Jun 27th 2017 4
Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas
Thu, May 25th 2017 4
Migrate Notes to DOCOVA Blog Series Part 16: Form events
Tue, May 23rd 2017 5
Top 10
Is 2017 The Year IBM Announces the End of Life of Notes?
Tue, May 24th 2016 20
Domino – Often Still the Best
Thu, Nov 9th 2017 18
ICAA – Did IBM Release a Free Version of the Notes Client?
Sun, Oct 30th 2016 12
DOCOVA V4.5 – Feature Quick Tour
Sun, Sep 27th 2015 11
@DbLookup in Javascript? You Bet!
Mon, Nov 7th 2016 10
DOCOVA SE General Release Announcement!
Wed, May 27th 2015 9
DIY – Migrating from IBM Quickr with DOCOVA Migration Tools
Tue, Apr 21st 2015 9
MWLUG 2017 – We Believe!
Thu, Sep 7th 2017 9
IBM Announcement – HCL to take over Notes and Domino Development
Tue, Oct 31st 2017 9
SharePoint – A Partner and Customer Perspective
Sat, Apr 2nd 2016 8


Why we DO migrate code.
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
John Ryan    

I decided to write a blog entry on the issue of migrating Notes application code when migrating Notes applications to DOCOVA.  When I say “code”, I mean the LotusScript and @formula language that is contained in Notes applications.

Now, I’ve seen some blogs and vendor web pages that espouse how you should NOT attempt to migrate the code.  These vendors typically want to convince you that you should re-develop your Notes applications on their platforms.  I get it.  That represents a lot in terms of billable services.  The bottom line, really, is that they simply lack the tools capable of migrating the code, so they try to convince you that you shouldn’t do it.

Part of the DOCOVA Migration Methodology includes the task of migrating Notes applications, including the code, to the DOCOVA platform.  Developing the tools to convert LotusScript and @formula language to other languages like JavaScript and PHP is not easy.  But, we’ve done the work.

In our research of business partners and organizations that still consult in or have Lotus Notes and Domino environments, we’ve found that they are looking for viable platforms to move their Notes applications to.  In companies that are still using Notes and Domino, the overwhelming consensus is that THE number one activity they DO NOT want to engage in is process re-engineering their Notes applications.  They want an efficient, cost effective way to convert their Notes applications to a new platform with as little interruption to their business as possible.  Once migrated, they want to be able to continue enhancing these applications while building new ones when they can properly plan the time, cost and resources to do so.

We have found that across the board, the vast majority of companies still on Notes and Domino have staff with skills that encompass the most popular browser application development languages in use today, that being JavaScript, Java, PHP and Python.  They all need their applications to be browser based and cross-device.  Also, the majority of these organizations already have and use Microsoft SQL Server, MySQL, Oracle or PostgreSQL as database management solutions somewhere in their organization.  This market reality is exactly what we have catered to in developing DOCOVA.

The companies we talk to often have hundreds or sometimes into the thousands of Notes applications that they need to migrate.  To sit down with staff, dig through, revisit, re-engineer and re-develop these applications is a nightmare in terms of time and money.  The VPs, CIOs and Directors of these organizations understand that fact.

The vendors that don’t have code conversion solutions will argue that you can’t convert “old” LotusScript code to a new modern development language, like JavaScript or PHP, because you’d miss out on “new capabilities”, syntax and patterns.  Well two things.  First off, I agree, and of course this is why when LotusScript and @formula code is converted from your Notes application to DOCOVA, it is transformed into DOCOVA’s modern JavaScript/PHP object oriented API which leverages modern language constructs.  Secondly,  the last time I looked, LotusScript declared variables, used functions, conditional statements, looping constructs and class structures.  This hasn’t gone away in any language…and yes, DOCOVA converts all of this.  Moving forward, DOCOVA’s development environment is flexible enough to allow developers to implement whatever “modern” programming approaches they deem fit to leverage for their applications.

Vendors will also argue that companies shouldn’t try to convert their old, tired, bug-ridden applications to a new platform.  I kind of resent these pejorative assumptions. Although the Notes client interface for applications is dated, most of our customers take the workflow and business logic, “the code” of their Notes applications very seriously.  They use their applications on a daily basis to run their businesses.  To treat them as if they were “throw-away” is misguided.  That said though, it is true that sometimes, for some applications, companies would rather re-develop them.  This too is perfect for DOCOVA as it offers a comprehensive drag and drop, WYSIWYM (what-you-see-is-what-you-mean) browser integrated application design environment for building applications super fast.

With DOCOVA and our migration methodology, it’s NOT about keeping the old stuff old.  The import is about modernizing your legacy Notes apps into a new modern platform in an automated fashion.  Notes UI elements are transformed into new modern browser based UI elements and LotusScript and @formula language are converted to JavaScript/PHP and DOCOVA’s modern object oriented API.

So yes, if you’re looking to move off of Notes and Domino and are wondering what to do with your applications, we of course encourage you to seek out and review all of the Notes and Domino “migration” solutions you can find.  Then come and see DOCOVA.  Using this approach will help you truly appreciate what it has to offer!

Let us give you a demonstration.  Our experience in Notes application migrations will quickly become evident and you will gain an understanding as to why we boast the most complete end-to-end migration solution for your Notes applications.



---------------------
http://www.docova.com/why-we-do-migrate-code/
Jun 27, 2017
5 hits



Recent Blog Posts
18
Domino – Often Still the Best
Thu, Nov 9th 2017 6:23p   Gary Walsh
In many cases, from a technical and financial standpoint, Domino is still hands down the best choice in terms of a platform.  The Domino server, with the database, messaging, web server and application server all tightly integrated makes it affordable and easy to work with. Its replication capabilities simply cannot be found in other platforms.  If you have any level of technical knowledge you can see why it is so hard to replace as an application platform. It drives me nuts when I read articl
9
IBM Announcement – HCL to take over Notes and Domino Development
Tue, Oct 31st 2017 5:22p   Gary Walsh
Last week IBM made this announcement. The gist of it is that they are using an Indian company, HCL, to do future development on Notes and Domino and a few other collaboration products. This news appeared on several blogs after it was announced by HCL.  IBM delivered the news to IBM partners October 26.  There were rumors floating around Social Connections 2017 that IBM was preparing to sell off Notes and Domino.  This seems to be the basis of those rumors. Frankly, I do no think it really mat
5
Moving to Microsoft – Sharing Notes Apps from the O365 Portal
Tue, Oct 31st 2017 3:31p   Gary Walsh
If you have many complex Notes applications, and you have an understanding of both Notes and Microsoft development, you know you cannot move them to SharePoint without some serious business process re-engineering.  SharePoint and Notes are too different. The applications are going to have to change and in many cases it is not even doable. DOCOVA will allow you to migrate those custom Notes apps to SQL, and provide the same level of functionality you had in the Notes and Domino environment.  Fo
9
MWLUG 2017 – We Believe!
Thu, Sep 7th 2017 5:22p   Gary Walsh
They call Toronto “Leaf Nation”, because so many of the population are passionate about the hockey team, the “Toronto Maple Leafs”.  No matter where the team sits in the standings, they “believe”.   The Notes and Domino community has been like that too over the last decade or so.  Regardless of how the technology is trending, they believe it is the best. MWLUG 2017 in Virginia this past August, like most of the Lotus User Group type events, was a gathering
5
Why we DO migrate code.
Tue, Jun 27th 2017 1:28p   John Ryan
I decided to write a blog entry on the issue of migrating Notes application code when migrating Notes applications to DOCOVA.  When I say “code”, I mean the LotusScript and @formula language that is contained in Notes applications. Now, I’ve seen some blogs and vendor web pages that espouse how you should NOT attempt to migrate the code.  These vendors typically want to convince you that you should re-develop your Notes applications on their platforms.  I get it.  That repr
4
Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas
Thu, May 25th 2017 1:51p   John Ryan
Welcome to blog series part 17 of 17 on migrating Notes apps to DOCOVA.  The subject of this blog is Input translation and input validation formulas (formulae if you prefer). Right.  So, one day I hear this argument coming from down the hall here at DOCOVA.  The dev team embroiled in some discussion.  Oh the controversy.  Fisticuffs? Naw.  Heated?  Maybe that would be a bit of a stretch.  The debate?  How should input translation and input validation formulas be handled in DOCOVA? In a
5
Migrate Notes to DOCOVA Blog Series Part 16: Form events
Tue, May 23rd 2017 1:24p   John Ryan
Welcome to blog series part 16 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to talk about form events. Okay, so the talk about form events usually starts of with the question: Does DOCOVA have document events like onLoad, onUnload, QueryOpen, QuerySave and WebQueryOpen? Yes.  DOCOVA supports both typical browser events like onLoad and onUnload but has also been extended to handle similar events that were found in Notes forms like QueryOpen, QuerySave, PostSave and so
3
Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders
Thu, May 18th 2017 1:38p   John Ryan
Welcome to blog series part 15 of 17 on migrating Notes apps to DOCOVA..  In this entry I’m going to talk about good ‘ol Private on first use folders. This is another one of those “interesting” Notes application design constructs.  In my journeys I don’t think I’ve ever come across this same sort of construct in any other application environment.  Anywhere.  Ever.  Sure, a private folder, but “…on first use” is the kicker.  Interestingl
5
Migrate Notes to DOCOVA Blog Series Part 14: Column sorting and categorizing
Tue, May 16th 2017 12:18p   John Ryan
Welcome to blog series part 14 of 17 on migrating Notes apps to DOCOVA..  In this entry I’m going to talk about view column sorting and categorizing. All view sorting and categorizing functionality is supported in DOCOVA.  Additionally, other properties like “Show multiple values as separate entries” and showing response docs in a hierarchy are also supported. I mean, as you get more in depth with DOCOVA, you’ll learn the breadth of the view object model and all the cool stuff
2
Migrate Notes to DOCOVA Blog Series Part 13: Shared columns and fields
Thu, May 11th 2017 1:52p   John Ryan
Welcome to blog series part 13 of 17 on migrating Notes apps to DOCOVA.  This entry is dedicated to shared columns and fields.  It’s short and sweet. DOCOVA does not support the concept of shared columns and fields between applications at this time. Say what?  I know, right?  DOCOVA is so over the top, so chalk full of functionality…it’s crazy, alas at the time of writing this blog entry, it doesn’t support shared columns and fields.  Well, that’s the reason ri




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition