Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://feeds.feedburner.com/DocovaTechincalBlog

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
  3.  
  4. <channel>
  5. <title>Technical – DOCOVA.com</title>
  6. <link>http://www.docova.com</link>
  7. <description>DOCOVA.com Website</description>
  8. <lastBuildDate>Thu, 27 Apr 2017 16:28:44 +0000</lastBuildDate>
  9. <language>en-US</language>
  10. <sy:updatePeriod>hourly</sy:updatePeriod>
  11. <sy:updateFrequency>1</sy:updateFrequency>
  12. <generator>https://wordpress.org/?v=4.7.4</generator>
  13. <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/DocovaTechincalBlog" /><feedburner:info uri="docovatechincalblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
  14. <title>Migrate Notes to DOCOVA Blog Series Part 9: Response Documents</title>
  15. <link>http://www.docova.com/migrating-notes-to-docova-part-9-response-documents/</link>
  16. <comments>http://www.docova.com/migrating-notes-to-docova-part-9-response-documents/#respond</comments>
  17. <pubDate>Thu, 27 Apr 2017 09:00:24 +0000</pubDate>
  18. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  19. <category><![CDATA[Notes Migration]]></category>
  20. <category><![CDATA[Technical]]></category>
  21.  
  22. <guid isPermaLink="false">http://www.docova.com/?p=5345</guid>
  23. <description><![CDATA[Welcome to blog series part 9 of 17 on migrating Notes apps to DOCOVA..  In this entry I&#8217;m going to talk about how DOCOVA handles response or child documents. First let me take a second to praise response documents in IBM Notes.  You know, they seem like such a simple thing but I think it&#8217;s surprising how many systems don&#8217;t include this type of construct out of the box.  With their ability to inherit field info from their parent on creation and deep hierarchical depiction in views, they were great in my opinion.  Ya, sure, there were oddities here and there in views, but overall I think they were really useful and easy to implement. THAT SAID.  Yes, DOCOVA supports the design construct of response/child documents.  And, yes, column totals in a categorized view look correct in that the category total disappears when the category is expanded and shows up at the bottom as you&#8217;d expect.  Why they never got around to that, I&#8217;ll never know!  Also, in case you&#8217;re wondering about the obvious, yes, when creating response or child documents from a parent, you have the option to have fields automatically inherited from the parent onto the child just as Notes had done. I&#8217;m quite happy that we have this feature in DOCOVA, it&#8217;s really useful&#8230;and built right in. You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects. Comments below!  Ya&#8230;tell me how much you like response docs!]]></description>
  24. <content:encoded><![CDATA[<p>Welcome to blog series part 9 of 17 on migrating Notes apps to DOCOVA..  In this entry I&#8217;m going to talk about how DOCOVA handles response or child documents.</p>
  25. <p>First let me take a second to praise response documents in IBM Notes.  You know, they seem like such a simple thing but I think it&#8217;s surprising how many systems don&#8217;t include this type of construct out of the box.  With their ability to inherit field info from their parent on creation and deep hierarchical depiction in views, they were great in my opinion.  Ya, sure, there were oddities here and there in views, but overall I think they were really useful and easy to implement.</p>
  26. <p>THAT SAID.  Yes, DOCOVA supports the design construct of response/child documents.  And, yes, column totals in a categorized view look correct in that the category total disappears when the category is expanded and shows up at the bottom as you&#8217;d expect.  Why they never got around to that, I&#8217;ll never know!  Also, in case you&#8217;re wondering about the obvious, yes, when creating response or child documents from a parent, you have the option to have fields automatically inherited from the parent onto the child just as Notes had done.</p>
  27. <p>I&#8217;m quite happy that we have this feature in DOCOVA, it&#8217;s really useful&#8230;and built right in.</p>
  28. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  29. <p>Comments below!  Ya&#8230;tell me how much you like response docs!</p>
  30. ]]></content:encoded>
  31. <wfw:commentRss>http://www.docova.com/migrating-notes-to-docova-part-9-response-documents/feed/</wfw:commentRss>
  32. <slash:comments>0</slash:comments>
  33. </item>
  34. <item>
  35. <title>12 Apps in 18 Days – A Notes Migration Project</title>
  36. <link>http://www.docova.com/12-apps-in-18-days-a-notes-migration-project/</link>
  37. <comments>http://www.docova.com/12-apps-in-18-days-a-notes-migration-project/#respond</comments>
  38. <pubDate>Wed, 26 Apr 2017 16:09:27 +0000</pubDate>
  39. <dc:creator><![CDATA[David Wice]]></dc:creator>
  40. <category><![CDATA[Notes Migration]]></category>
  41. <category><![CDATA[Technical]]></category>
  42.  
  43. <guid isPermaLink="false">http://www.docova.com/?p=5853</guid>
  44. <description><![CDATA[Jamesway Incubator, located in Cambridge Ontario, manufactures and sells incubators worldwide.   For years they have used IBM Notes and Domino collaboration products to automate business processes and share information with a staff located all over the world.  However, like many in the Notes and Domino community, a corporate decision was recently made to switch to Microsoft based technologies. Replacing Notes based email is relatively easy, since the migration tools and processes are well defined.  Migrating Notes based applications is much more difficult.  Fortunately, Jamesway implemented DOCOVA as a document management system almost a decade ago to manage corporate documents, and the new version of DOCOVA (V5), has been specifically designed to migrate Notes based applications to SQL. DOCOVA V5 understands the design elements that were unique to Notes, and knows how to handle them when moving to SQL based technologies. Jamesway contracted DLI to perform the Notes application migration.  DOCOVA App Importer did the heavy lifting by automatically migrating the application design from Lotus Domino to DOCOVA, leaving the developer free to adjust and tweak the migrated applications. Without App Importer to take care of the grunt work it would have taken 6 months instead of 3 weeks to transform these applications. The DOCOVA migration methodology (Analyze, Plan, Migrate, Manage) has guided this project.  The initial analysis provided us with key information so that we could provide a quote for the migration and identify resource requirements. In discussions with Jamesway, the migration plan was developed, which in this case was to migrate off the Notes client first, keeping the Domino backend, then move the migrated applications and existing Document Management system to the DOCOVA SQL platform.   Since the DOCOVA UI is the same regardless of the [&#8230;]]]></description>
  45. <content:encoded><![CDATA[<p><strong><a href="http:///www.jamesway.com" target="_blank" rel="noopener noreferrer">Jamesway Incubator</a></strong>, located in Cambridge Ontario, manufactures and sells incubators worldwide.   For years they have used IBM Notes and Domino collaboration products to automate business processes and share information with a staff located all over the world.  However, like many in the Notes and Domino community, a corporate decision was recently made to switch to Microsoft based technologies.</p>
  46. <p>Replacing Notes based email is relatively easy, since the migration tools and processes are well defined.  Migrating Notes based applications is much more difficult.  Fortunately, Jamesway implemented <strong><a href="http://www.docova.com/is-docova-right-for-you/" target="_blank" rel="noopener noreferrer">DOCOVA</a></strong> as a document management system almost a decade ago to manage corporate documents, and the new version of <strong><a href="https://youtu.be/Bsm4t02k7ZI" target="_blank" rel="noopener noreferrer">DOCOVA (V5)</a></strong>, has been specifically designed to migrate Notes based applications to SQL. <strong><a href="https://youtu.be/Bsm4t02k7ZI" target="_blank" rel="noopener noreferrer">DOCOVA V5</a></strong> understands the design elements that were unique to Notes, and knows how to handle them when moving to SQL based technologies.</p>
  47. <p>Jamesway contracted DLI to perform the Notes application migration.  DOCOVA App Importer did the heavy lifting by automatically migrating the application design from Lotus Domino to DOCOVA, leaving the developer free to adjust and tweak the migrated applications. Without App Importer to take care of the grunt work it would have taken 6 months instead of 3 weeks to transform these applications.</p>
  48. <p><strong><a href="http://www.docova.com/migrationmethodology/" target="_blank" rel="noopener noreferrer">The DOCOVA migration methodology </a></strong>(Analyze, Plan, Migrate, Manage) has guided this project.  The initial analysis provided us with key information so that we could provide a quote for the migration and identify resource requirements. In discussions with Jamesway, the migration plan was developed, which in this case was to migrate off the Notes client first, keeping the Domino backend, then move the migrated applications and existing Document Management system to the DOCOVA SQL platform.   Since the DOCOVA UI is the same regardless of the backend platform, Jamesway could spread the migration out over time to be better able to handle the resource requirements on their end.</p>
  49. <p>The applications migrated included maintenance management, requisition systems (purchase order, cheque, etc), as well as reference/document repository applications.  Utilizing App Importer, the developer doing the migration didn&#8217;t need to know what the application did or the business logic behind it, as it was all migrated intact.</p>
  50. <p><img class="alignnone size-large wp-image-5856" src="http://www.docova.com/wp-content/uploads/2017/04/JWWorkspace-1024x563.png" alt="" width="1000" height="550" srcset="http://www.docova.com/wp-content/uploads/2017/04/JWWorkspace-1024x563.png 1024w, http://www.docova.com/wp-content/uploads/2017/04/JWWorkspace-300x165.png 300w, http://www.docova.com/wp-content/uploads/2017/04/JWWorkspace-768x422.png 768w, http://www.docova.com/wp-content/uploads/2017/04/JWWorkspace.png 1103w" sizes="(max-width: 1000px) 100vw, 1000px" /></p>
  51. <p>All aspects of the design were migrated (Layouts, Pages, Views, Calendar Views, Forms, Subforms, Agents, Script Libraries, Images, Folders) as well as the data, including profile documents.  What about security? Yes, that was migrated too, including document level security (authors/readers/controlled access sections). As for the LotusScript, that was automatically translated to Javascript.</p>
  52. <p>Being an early release of DOCOVA V5 there were hurdles to be crossed and issues to be addressed. In some cases application logic just doesn&#8217;t flow the same way in a browser as it does in a local Notes client (eg. dialogs, prompt boxes, etc), requiring some adjustments/tweaking by the developer post migration. Luckily the DOCOVA Application Analysis process flags these cases for us.  We are also constantly improving App Importer to address new scenarios, which means that if we were to repeat the project with the current version of <strong><a href="https://youtu.be/Bsm4t02k7ZI" target="_blank" rel="noopener noreferrer">DOCOVA V5</a></strong>, it could be completed in even less time.</p>
  53. <p>The Jamesway project has now moved into UAT. After we showed IT management the migrated applications and they saw how the business logic and UI have been maintained, they were quite comfortable taking on the UAT step, since there is little to no training required. Users just need to be shown how to access the new platform and add their applications to the workspace.</p>
  54. <p>While we still have some work to do to complete the <strong><a href="http://www.docova.com/migrationmethodology/" target="_blank" rel="noopener noreferrer">migration to the SQL platform</a></strong>, we&#8217;ve been able to take what could have been a very costly re-development project and deliver results in a short period of time, at a reasonable cost.</p>
  55. ]]></content:encoded>
  56. <wfw:commentRss>http://www.docova.com/12-apps-in-18-days-a-notes-migration-project/feed/</wfw:commentRss>
  57. <slash:comments>0</slash:comments>
  58. </item>
  59. <item>
  60. <title>Migrate Notes to DOCOVA Blog Series Part 8: Profile Docs</title>
  61. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-8-profile-docs/</link>
  62. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-8-profile-docs/#respond</comments>
  63. <pubDate>Wed, 26 Apr 2017 12:35:37 +0000</pubDate>
  64. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  65. <category><![CDATA[Notes Migration]]></category>
  66. <category><![CDATA[Technical]]></category>
  67.  
  68. <guid isPermaLink="false">http://www.docova.com/?p=5444</guid>
  69. <description><![CDATA[Welcome to blog series part 8 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to go over profile documents. In Notes apps, profile docs were convenient for, and typically used for, holding application settings type information.  The information on profile docs was easily gotten with @formula commands like @GetProfileField. The question is: Does DOCOVA support profile documents? Yes.  If a Notes application used profile documents then they will be supported in the migrated application in DOCOVA.  When migrating, of course the related profile document’s form will get migrated.  DOCOVA knows, based on how the form is edited, that the generated/updated document is to be treated as a profile document and saves it as such, similar to the way Domino handled profile docs. When the data of a Notes application is migrated, DOCOVA App Importer™ knows when a document is is a profile type document and will handle the conversion on the DOCOVA side. @Formula methods like @GetProfileField and @SetProfileField are supported in DOCOVAScript™ as $$GetProfileField and $$SetProfileField as well as $$Command([EditProfile]). If you&#8217;ve used profile documents in any of your Notes applications, when they are migrated over to DOCOVA, you can still use them in the same fashion as you did in Notes, and use them in any newly created DOCOVA apps too. You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects. Post comments and questions below!]]></description>
  70. <content:encoded><![CDATA[<p>Welcome to blog series part 8 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to go over profile documents.</p>
  71. <p>In Notes apps, profile docs were convenient for, and typically used for, holding application settings type information.  The information on profile docs was easily gotten with @formula commands like @GetProfileField.</p>
  72. <p>The question is: Does DOCOVA support profile documents?</p>
  73. <p>Yes.  If a Notes application used profile documents then they will be supported in the migrated application in DOCOVA.  When migrating, of course the related profile document’s form will get migrated.  DOCOVA knows, based on how the form is edited, that the generated/updated document is to be treated as a profile document and saves it as such, similar to the way Domino handled profile docs.</p>
  74. <p>When the data of a Notes application is migrated, DOCOVA App Importer™ knows when a document is is a profile type document and will handle the conversion on the DOCOVA side.</p>
  75. <p>@Formula methods like @GetProfileField and @SetProfileField are supported in DOCOVAScript™ as $$GetProfileField and $$SetProfileField as well as $$Command([EditProfile]).</p>
  76. <p>If you&#8217;ve used profile documents in any of your Notes applications, when they are migrated over to DOCOVA, you can still use them in the same fashion as you did in Notes, and use them in any newly created DOCOVA apps too.</p>
  77. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  78. <p>Post comments and questions below!</p>
  79. ]]></content:encoded>
  80. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-8-profile-docs/feed/</wfw:commentRss>
  81. <slash:comments>0</slash:comments>
  82. </item>
  83. <item>
  84. <title>Migrate Notes to DOCOVA Blog Series Part 7: XPages</title>
  85. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-7-xpages/</link>
  86. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-7-xpages/#respond</comments>
  87. <pubDate>Thu, 20 Apr 2017 14:17:28 +0000</pubDate>
  88. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  89. <category><![CDATA[Notes Migration]]></category>
  90. <category><![CDATA[Technical]]></category>
  91.  
  92. <guid isPermaLink="false">http://www.docova.com/?p=5442</guid>
  93. <description><![CDATA[Welcome to blog series part 7 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to discuss XPages. So, the simple question is: Does DOCOVA migrate and support XPages? Annnnd, the answer is: No. For DOCOVA’s development we pretty much stayed away from XPages for two reasons.  First, although we might have been able to leverage it on the Domino side, it wasn’t a good fit for the SQL edition of DOCOVA which caters to several different relational platforms.  Second, we never really got a good feeling about XPages.  We always felt it was a bit of an odd design construct slapped on a platform that IBM wasn&#8217;t giving much attention to anymore.  For those reasons, we did not invest any time in it except to use it for DOCOVA&#8217;s Public File Access (PFA) component for Domino installed instances. As it turns out, based on the comments coming out of IBM Connect 2017, it appears that IBM has all but abandoned XPages. The good news is that the DOCOVA App Builder is a powerful drag-and-drop, point-and-click IDE that enables businesses to quickly rebuild forms/pages that used XPages.  So, that might be helpful for some. Also, although it might be a bit of a stretch, if you still have the forms and such that you may have redeveloped in XPages then those can/will be migrated and modernized in DOCOVA. Aside from XPages, if you&#8217;ve built Notes applications that are web enabled through passthru HTML/inline JavaScript, DOCOVA does support the migration of all that and will be the topic of another blog post. You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this [&#8230;]]]></description>
  94. <content:encoded><![CDATA[<p>Welcome to blog series part 7 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to discuss XPages.</p>
  95. <p>So, the simple question is: Does DOCOVA migrate and support XPages?</p>
  96. <p>Annnnd, the answer is: No.</p>
  97. <p>For DOCOVA’s development we pretty much stayed away from XPages for two reasons.  First, although we might have been able to leverage it on the Domino side, it wasn’t a good fit for the SQL edition of DOCOVA which caters to several different relational platforms.  Second, we never really got a good feeling about XPages.  We always felt it was a bit of an odd design construct slapped on a platform that IBM wasn&#8217;t giving much attention to anymore.  For those reasons, we did not invest any time in it except to use it for DOCOVA&#8217;s Public File Access (PFA) component for Domino installed instances.</p>
  98. <p>As it turns out, based on the comments coming out of IBM Connect 2017, it appears that IBM has all but abandoned XPages.</p>
  99. <p>The good news is that the DOCOVA App Builder is a powerful drag-and-drop, point-and-click IDE that enables businesses to quickly rebuild forms/pages that used XPages.  So, that might be helpful for some.</p>
  100. <p>Also, although it might be a bit of a stretch, if you still have the forms and such that you may have redeveloped in XPages then those can/will be migrated and modernized in DOCOVA.</p>
  101. <p>Aside from XPages, if you&#8217;ve built Notes applications that are web enabled through passthru HTML/inline JavaScript, DOCOVA does support the migration of all that and will be the topic of another blog post.</p>
  102. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  103. <p>Post comments and questions below!</p>
  104. ]]></content:encoded>
  105. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-7-xpages/feed/</wfw:commentRss>
  106. <slash:comments>0</slash:comments>
  107. </item>
  108. <item>
  109. <title>Migrate Notes to DOCOVA Blog Series Part 6: Security</title>
  110. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-6-security/</link>
  111. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-6-security/#respond</comments>
  112. <pubDate>Wed, 19 Apr 2017 13:00:22 +0000</pubDate>
  113. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  114. <category><![CDATA[Notes Migration]]></category>
  115. <category><![CDATA[Technical]]></category>
  116.  
  117. <guid isPermaLink="false">http://www.docova.com/?p=5343</guid>
  118. <description><![CDATA[Welcome to blog series part 6 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to talk about three things. Security, security and security. We thought the security in Notes/Domino was pretty good.  It was clear, easy to manage and provided for a lot of variable implementation.  DOCOVA’s enhanced security capabilities were made so that it is flexible enough to support the Notes/Domino approach to security. DOCOVA application access control is handled similarly to Notes database ACLs.  They are managed through the UI of the DOCOVA App Builder integrated development environment (yes, all browser based) in the Properties of an application.  People, groups and roles can be added and created in the access control of an application and specific functionality can be assigned like the ability to delete documents/records and more. DOCOVA also supports Authors and Readers fields and yes, in conjunction with the access control of the application, similar to how Notes/Domino did.  Additionally, things like controlled access sections and document modes like read mode and edit mode are also supported. From a directory/address book perspective, DOCOVA connects to Address Books and Directories via  LDAP for things like authentication.  For DOCOVA instances that are on non-Domino platforms, DOCOVA allows for the creation of its own self-contained Directory which can be used to manage users and authentication services.  What&#8217;s cool is that both internal directories and the DOCOVA directory can be used simultaneously to do things like manage internal staff in your own internal directories like Active Directory while managing external users via DOCOVA&#8217;s directory. You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can [&#8230;]]]></description>
  119. <content:encoded><![CDATA[<p>Welcome to blog series part 6 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to talk about three things. Security, security and security.</p>
  120. <p>We thought the security in Notes/Domino was pretty good.  It was clear, easy to manage and provided for a lot of variable implementation.  DOCOVA’s enhanced security capabilities were made so that it is flexible enough to support the Notes/Domino approach to security.</p>
  121. <p>DOCOVA application access control is handled similarly to Notes database ACLs.  They are managed through the UI of the DOCOVA App Builder integrated development environment (yes, all browser based) in the Properties of an application.  People, groups and roles can be added and created in the access control of an application and specific functionality can be assigned like the ability to delete documents/records and more.</p>
  122. <p>DOCOVA also supports Authors and Readers fields and yes, in conjunction with the access control of the application, similar to how Notes/Domino did.  Additionally, things like controlled access sections and document modes like read mode and edit mode are also supported.</p>
  123. <p>From a directory/address book perspective, DOCOVA connects to Address Books and Directories via  LDAP for things like authentication.  For DOCOVA instances that are on non-Domino platforms, DOCOVA allows for the creation of its own self-contained Directory which can be used to manage users and authentication services.  What&#8217;s cool is that both internal directories and the DOCOVA directory can be used simultaneously to do things like manage internal staff in your own internal directories like Active Directory while managing external users via DOCOVA&#8217;s directory.</p>
  124. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  125. <p>If you have any questions or comments, post &#8217;em below.</p>
  126. ]]></content:encoded>
  127. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-6-security/feed/</wfw:commentRss>
  128. <slash:comments>0</slash:comments>
  129. </item>
  130. <item>
  131. <title>Migrate Notes to DOCOVA Blog Series Part 5: File attachments</title>
  132. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-5-file-attachments/</link>
  133. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-5-file-attachments/#respond</comments>
  134. <pubDate>Tue, 18 Apr 2017 15:33:01 +0000</pubDate>
  135. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  136. <category><![CDATA[Notes Migration]]></category>
  137. <category><![CDATA[Technical]]></category>
  138.  
  139. <guid isPermaLink="false">http://www.docova.com/?p=5341</guid>
  140. <description><![CDATA[Welcome to blog series part 5 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to talk about how file attachments are migrated over to DOCOVA. When it comes to the importing of data from a Notes application to a DOCOVA application, the DOCOVA App Importer initially scans and detects all file attachments in the source nsf and keeps track of what form design elements contain an attachment. As the import of form designs occurs, if a form had an attachment, not only will the App Importer import the form design element, but it will also add the DOCOVA file attachment element to that form.  The DOCOVA file attachment element is one of the most powerful file attachment handlers available for browser applications and allows for things like editing files in-place, renaming files and much more. If you&#8217;re using DOCOVA on Domino then attachments remain with their newly created associated document in DOCOVA.  In non-Domino DOCOVA instances the file attachments are moved and stored on the new server’s file system and associated to their parent document/record.  No matter what the backend platform is, Domino or SQL, from a user&#8217;s perspective the DOCOVA interface is always the same, showing the attachments on their documents via the DOCOVA file attachment element. All attachments in DOCOVA are full-text indexed regardless of platform so that all attachments are part of the full-text searching capabilities of DOCOVA. You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects. Comment below!]]></description>
  141. <content:encoded><![CDATA[<p>Welcome to blog series part 5 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to talk about how file attachments are migrated over to DOCOVA.</p>
  142. <p>When it comes to the importing of data from a Notes application to a DOCOVA application, the DOCOVA App Importer initially scans and detects all file attachments in the source nsf and keeps track of what form design elements contain an attachment.</p>
  143. <p>As the import of form designs occurs, if a form had an attachment, not only will the App Importer import the form design element, but it will also add the DOCOVA file attachment element to that form.  The DOCOVA file attachment element is one of the most powerful file attachment handlers available for browser applications and allows for things like editing files in-place, renaming files and much more.</p>
  144. <p><a href="http://www.docova.com/wp-content/uploads/2017/03/files.jpg"><img class="alignnone size-full wp-image-5404" src="http://www.docova.com/wp-content/uploads/2017/03/files.jpg" alt="files" width="1036" height="285" srcset="http://www.docova.com/wp-content/uploads/2017/03/files.jpg 1036w, http://www.docova.com/wp-content/uploads/2017/03/files-300x83.jpg 300w, http://www.docova.com/wp-content/uploads/2017/03/files-768x211.jpg 768w, http://www.docova.com/wp-content/uploads/2017/03/files-1024x282.jpg 1024w" sizes="(max-width: 1036px) 100vw, 1036px" /></a></p>
  145. <p>If you&#8217;re using DOCOVA on Domino then attachments remain with their newly created associated document in DOCOVA.  In non-Domino DOCOVA instances the file attachments are moved and stored on the new server’s file system and associated to their parent document/record.  No matter what the backend platform is, Domino or SQL, from a user&#8217;s perspective the DOCOVA interface is always the same, showing the attachments on their documents via the DOCOVA file attachment element.</p>
  146. <p>All attachments in DOCOVA are full-text indexed regardless of platform so that all attachments are part of the full-text searching capabilities of DOCOVA.</p>
  147. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  148. <p>Comment below!</p>
  149. ]]></content:encoded>
  150. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-5-file-attachments/feed/</wfw:commentRss>
  151. <slash:comments>0</slash:comments>
  152. </item>
  153. <item>
  154. <title>Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks</title>
  155. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-4-richtext-and-doclinks/</link>
  156. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-4-richtext-and-doclinks/#respond</comments>
  157. <pubDate>Wed, 12 Apr 2017 13:57:35 +0000</pubDate>
  158. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  159. <category><![CDATA[Notes Migration]]></category>
  160. <category><![CDATA[Technical]]></category>
  161.  
  162. <guid isPermaLink="false">http://www.docova.com/?p=5339</guid>
  163. <description><![CDATA[Welcome to blog series part 4 of 17 on migrating Notes apps to DOCOVA.  In this blog entry I&#8217;ll talk about richtext and how it gets migrated over. So, first off, there is  no such thing as a “richtext” field in a browser as compared to what a richtext field is in a Notes client.  If you are running DOCOVA on a Domino platform rather than one of the other SQL database platforms, DOCOVA RT remains RT and is rendered to HTML by the server when the page/form is first loaded.  From that point on it is treated and stored as HTML content.  On non-Domino SQL platforms as part of the migration and we convert the RT content to HTML and store it as HTML. With DOCOVA, when creating or editing a page/form in DOCOVA, a couple of HTML editor options are used to enable much of the functionality that a richtext field had in the Notes client.  One of the HTML editors is the TinyMCE plugin and the other is a custom DOCOVA HTML editor that we&#8217;ve built. One question that gets asked is what happens to the doclinks that were in richtext fields?  When migrating data from Notes documents that have richtext fields that contain doclinks, we track which documents have the doclinks and what those links are “hooked” to.  As we migrate the data we keep track of what documents have the doclinks and what the doclinks are connected to so that once the data lands in DOCOVA the links are reconnected. Additionally, DOCOVA’s API has a richtext navigator class that operates similarly to the NotesRichtextNavigator class to support any code that might leverage this class. You can fast-track and get all the [&#8230;]]]></description>
  164. <content:encoded><![CDATA[<p>Welcome to blog series part 4 of 17 on migrating Notes apps to DOCOVA.  In this blog entry I&#8217;ll talk about richtext and how it gets migrated over.</p>
  165. <p>So, first off, there is  no such thing as a “richtext” field in a browser as compared to what a richtext field is in a Notes client.  If you are running DOCOVA on a Domino platform rather than one of the other SQL database platforms, DOCOVA RT remains RT and is rendered to HTML by the server when the page/form is first loaded.  From that point on it is treated and stored as HTML content.  On non-Domino SQL platforms as part of the migration and we convert the RT content to HTML and store it as HTML.</p>
  166. <p>With DOCOVA, when creating or editing a page/form in DOCOVA, a couple of HTML editor options are used to enable much of the functionality that a richtext field had in the Notes client.  One of the HTML editors is the TinyMCE plugin and the other is a custom DOCOVA HTML editor that we&#8217;ve built.</p>
  167. <p>One question that gets asked is what happens to the doclinks that were in richtext fields?  When migrating data from Notes documents that have richtext fields that contain doclinks, we track which documents have the doclinks and what those links are “hooked” to.  As we migrate the data we keep track of what documents have the doclinks and what the doclinks are connected to so that once the data lands in DOCOVA the links are reconnected.</p>
  168. <p>Additionally, DOCOVA’s API has a richtext navigator class that operates similarly to the NotesRichtextNavigator class to support any code that might leverage this class.</p>
  169. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  170. <p>Please leave any comments/feedback below!</p>
  171. ]]></content:encoded>
  172. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-4-richtext-and-doclinks/feed/</wfw:commentRss>
  173. <slash:comments>0</slash:comments>
  174. </item>
  175. <item>
  176. <title>Migrate Notes to DOCOVA Blog Series Part 3: @formula language</title>
  177. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-3-formula-language/</link>
  178. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-3-formula-language/#respond</comments>
  179. <pubDate>Mon, 10 Apr 2017 14:59:34 +0000</pubDate>
  180. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  181. <category><![CDATA[Notes Migration]]></category>
  182. <category><![CDATA[Technical]]></category>
  183.  
  184. <guid isPermaLink="false">http://www.docova.com/?p=5337</guid>
  185. <description><![CDATA[Welcome to blog series part 3 of 17 on migrating Notes apps to DOCOVA. In this post I&#8217;m going to talk about @formula and @command language. Most Notes apps have the @formula and @command language strewn throughout them.  The @formula and @command languages were very useful in that they were an easy way to quickly accomplish simple tasks as well as tackle what were sometimes quite complex operations without being a master coder. In order to handle the conversion of @formula and @command languages, we dropped DOCOVAScript™ into DOCOVA.  DOCOVAScript is its own scripting language and can support the @[email protected] language conversion from Notes.  The big diff is that DOCOVA uses “$$” in front of its commands instead of the &#8220;@&#8221; sign.  For example, @DbColumn is supported with $$DBColumn.  @Username is $$Username and so on.  Pretty straightforward. I&#8217;m really pleased with how DOCOVAScript has turned out in DOCOVA.  It&#8217;s such a big part of what Notes apps were that I&#8217;m glad we can support it. The next question you should ask is&#8230;.what about @if, @do and @for statements?  And the answer is yes, those are converted too. When the DOCOVA App Importer encounters any @formula or @command functions it converts them to a corresponding $$ DOCOVAScript command that supports them.  There are some anomalies that are handled when converting this code due to some of the deep nesting capabilities of these functions in Notes not having the same context in a browser. As a result, some of the more complex nested @ code may need to be jigged slightly different (identified by DOCOVA Analyzer™), but for Notes developers making the transition to DOCOVA, the code is easy to identify and leverage&#8230;and of course the resulting capability [&#8230;]]]></description>
  186. <content:encoded><![CDATA[<p>Welcome to blog series part 3 of 17 on migrating Notes apps to DOCOVA. In this post I&#8217;m going to talk about @formula and @command language.</p>
  187. <p>Most Notes apps have the @formula and @command language strewn throughout them.  The @formula and @command languages were very useful in that they were an easy way to quickly accomplish simple tasks as well as tackle what were sometimes quite complex operations without being a master coder.</p>
  188. <p>In order to handle the conversion of @formula and @command languages, we dropped DOCOVAScript™ into DOCOVA.  DOCOVAScript is its own scripting language and can support the @[email protected] language conversion from Notes.  The big diff is that DOCOVA uses “$$” in front of its commands instead of the &#8220;@&#8221; sign.  For example, @DbColumn is supported with $$DBColumn.  @Username is $$Username and so on.  Pretty straightforward.</p>
  189. <p>I&#8217;m really pleased with how DOCOVAScript has turned out in DOCOVA.  It&#8217;s such a big part of what Notes apps were that I&#8217;m glad we can support it.</p>
  190. <p>The next question you should ask is&#8230;.what about @if, @do and @for statements?  And the answer is yes, those are converted too.</p>
  191. <p>When the DOCOVA App Importer encounters any @formula or @command functions it converts them to a corresponding $$ DOCOVAScript command that supports them.  There are some anomalies that are handled when converting this code due to some of the deep nesting capabilities of these functions in Notes not having the same context in a browser. As a result, some of the more complex nested @ code may need to be jigged slightly different (identified by DOCOVA Analyzer™), but for Notes developers making the transition to DOCOVA, the code is easy to identify and leverage&#8230;and of course the resulting capability is similar.</p>
  192. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  193. <p>Questions? Comments?  Enter them below.</p>
  194. ]]></content:encoded>
  195. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-3-formula-language/feed/</wfw:commentRss>
  196. <slash:comments>0</slash:comments>
  197. </item>
  198. <item>
  199. <title>Migrate Notes to DOCOVA Blog Series Part 2: LotusScript</title>
  200. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-2-lotusscript/</link>
  201. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-2-lotusscript/#respond</comments>
  202. <pubDate>Thu, 06 Apr 2017 13:30:38 +0000</pubDate>
  203. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  204. <category><![CDATA[Notes Migration]]></category>
  205. <category><![CDATA[Technical]]></category>
  206.  
  207. <guid isPermaLink="false">http://www.docova.com/?p=5335</guid>
  208. <description><![CDATA[Welcome to blog series part 2 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to go over LotusScript. In part 3 of this series I&#8217;ll talk about @formula and @command language. When we began to embark on the journey of providing a killer platform and migration strategy to bring Notes applications to DOCOVA, we knew that the conversion of LotusScript was going to be an important part of it. Converting LotusScript to JavaScript and PHP is complex.  If anyone out there has ever embarked on writing a grammar, lexer/parser for converting one programming language to another, you know what I mean. But it&#8217;s more than just the conversion of one programming language to another, it&#8217;s also about the object model and API that address that model. To facilitate migrations from Notes to DOCOVA and indeed provide similar powerful app building constructs, we dropped an object model into DOCOVA that, among other things, is supportive when converting Notes code. We also dropped in a JSON based API with front and back-end methods and properties in order to support the conversion of LotusScript methods and properties.  This support allows for a more direct conversion when migrating Notes applications to DOCOVA, and enables developers to hit the ground running. Example time!  To give you a bit of an idea of what some LotusScript converted to DOCOVA&#8217;s API looks like, here is an example of defining a workspace object and composing a new document by providing a form name. In LotusScript it would look something like this, Dim workspace As New NotesUIWorkspace Call workspace.ComposeDocument( &#8220;&#8221;, &#8220;&#8221;, &#8220;Main Topic&#8221; ) In DOCOVA&#8217;s API (Javascript in this particular case) it would look like this; var workspace [&#8230;]]]></description>
  209. <content:encoded><![CDATA[<p>Welcome to blog series part 2 of 17 on migrating Notes apps to DOCOVA.  In this entry I&#8217;m going to go over LotusScript. In part 3 of this series I&#8217;ll talk about @formula and @command language.</p>
  210. <p>When we began to embark on the journey of providing a killer platform and migration strategy to bring Notes applications to DOCOVA, we knew that the conversion of LotusScript was going to be an important part of it.</p>
  211. <p>Converting LotusScript to JavaScript and PHP is complex.  If anyone out there has ever embarked on writing a grammar, lexer/parser for converting one programming language to another, you know what I mean.</p>
  212. <p>But it&#8217;s more than just the conversion of one programming language to another, it&#8217;s also about the object model and API that address that model.</p>
  213. <p>To facilitate migrations from Notes to DOCOVA and indeed provide similar powerful app building constructs, we dropped an object model into DOCOVA that, among other things, is supportive when converting Notes code.</p>
  214. <p>We also dropped in a JSON based API with front and back-end methods and properties in order to support the conversion of LotusScript methods and properties.  This support allows for a more direct conversion when migrating Notes applications to DOCOVA, and enables developers to hit the ground running.</p>
  215. <p>Example time!  To give you a bit of an idea of what some LotusScript converted to DOCOVA&#8217;s API looks like, here is an example of defining a workspace object and composing a new document by providing a form name.</p>
  216. <p><strong>In LotusScript it would look something like this,</strong></p>
  217. <p><span style="color: #008000;">Dim workspace As New NotesUIWorkspace</span><br />
  218. <span style="color: #008000;">Call workspace.ComposeDocument( &#8220;&#8221;, &#8220;&#8221;, &#8220;Main Topic&#8221; )</span></p>
  219. <p><strong>In DOCOVA&#8217;s API (Javascript in this particular case) it would look like this;</strong></p>
  220. <p><span style="color: #008000;">var workspace = Docova.getUIWorkspace();</span><br />
  221. <span style="color: #008000;">workspace.compose({ </span><span style="color: #008000;">formname: &#8220;Main Topic&#8221; </span><span style="color: #008000;">});</span></p>
  222. <p>DOCOVA implements a front-end and back-end class structure with classes like DOCOVAUIDocument and DOCOVAView.</p>
  223. <p>With the class structure and API in hand, the DOCOVA App Importer does two things.  One it converts the Lotusscript programming language to JavaScript and/or PHP as needed and two, replaces Notes class and API references with DOCOVA class and API references.</p>
  224. <p>Also worth mentioning is that DOCOVA’s App Importer will handle anomalies such as case-sensitivity.  LotusScript didn’t care if you used a mix of case with variables.  For example, if a variable named “MyField” was initially declared, but then later in the code referenced as “myfield”, LotusScript was quite happy with that.  Other programming languages don’t allow this including JavaScript and PHP. DOCOVA’s importing process works to resolve these types of issues at import time.</p>
  225. <p>It all sounds pretty magical eh?  Well, it is, but now for a bit of a reality check.</p>
  226. <p>Although the DOCOVA conversion is impressive, DOCOVA does not support every class that is provided in the Notes/Domino environment.  This is mainly due to the fact that many Notes/Domino classes no longer make sense and have no context in browser land.</p>
  227. <p>Providing class and API similarities makes the transition for I.T staff and consultants much faster and easier while removing a significant amount of risk from these migration efforts.</p>
  228. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that will be discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology &#8211; MIGRATE whitepaper which goes over these technical aspects.</p>
  229. <p>Hit us up for a demonstration!  Comment below.</p>
  230. ]]></content:encoded>
  231. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-2-lotusscript/feed/</wfw:commentRss>
  232. <slash:comments>0</slash:comments>
  233. </item>
  234. <item>
  235. <title>Migrate Notes to DOCOVA Blog Series Part 1: What gets migrated?</title>
  236. <link>http://www.docova.com/migrate-notes-to-docova-blog-series-part-1-what-gets-migrated/</link>
  237. <comments>http://www.docova.com/migrate-notes-to-docova-blog-series-part-1-what-gets-migrated/#respond</comments>
  238. <pubDate>Tue, 04 Apr 2017 14:11:39 +0000</pubDate>
  239. <dc:creator><![CDATA[John Ryan]]></dc:creator>
  240. <category><![CDATA[Notes Migration]]></category>
  241. <category><![CDATA[Technical]]></category>
  242.  
  243. <guid isPermaLink="false">http://www.docova.com/?p=5333</guid>
  244. <description><![CDATA[Welcome to the first installment of the Migrate Notes to DOCOVA blog series.  This is a multi-part series touching on what gets migrated when moving Notes applications to the DOCOVA collaboration platform.  It doesn&#8217;t have to be Sharepoint.  I will publish entries on a regular basis, every couple of days or so, I&#8217;m shooting for Tuesdays and Thursdays right now. You can fast-track and get all the whitepapers on our migration methodology and everything that will be discussed in these blog posts. The &#8220;parts&#8221; of this series are based around questions we frequently get asked about what gets migrated to DOCOVA when migrating a Notes application, so, although there will be 17 parts, if I get asked about other things that emerge as important enough to blog about, then I might add more. If you have questions that you don&#8217;t want to drop into the comments section you can email me at [email protected] Who am I?  I&#8217;m John Ryan, I&#8217;ve been working with Notes and Domino since 1993.  I am a co-owner, with Gary Walsh, of DLI.tools Inc., the company behind DOCOVA.  I am the CTO here and chief architect of DOCOVA&#8230;although (tongue in cheek)&#8230;really, I&#8217;m just the guy who sets impossible goals for our exceptional development team&#8230;and somehow, they pull it off!  We&#8217;ve won many awards (11 of them) over the years for DOCOVA and other software products we&#8217;ve developed. I&#8217;m really jazzed about our new version of DOCOVA.  It is version 5.  In version 5 we&#8217;ve added a user workspace, a browser-based integrated development environment called App Builder and App Importer, an integrated tool you run in DOCOVA to import Notes applications into DOCOVA. When investigating Notes application migration solutions, Notes developers should [&#8230;]]]></description>
  245. <content:encoded><![CDATA[<p>Welcome to the first installment of the Migrate Notes to DOCOVA blog series.  This is a multi-part series touching on what gets migrated when moving Notes applications to the DOCOVA collaboration platform.  It doesn&#8217;t have to be Sharepoint.  I will publish entries on a regular basis, every couple of days or so, I&#8217;m shooting for Tuesdays and Thursdays right now.</p>
  246. <p>You can fast-track and get <strong><a href="http://www.docova.com/migrationmethodology/">all the whitepapers on our migration methodology</a> </strong>and everything that will be discussed in these blog posts.</p>
  247. <p>The &#8220;parts&#8221; of this series are based around questions we frequently get asked about what gets migrated to DOCOVA when migrating a Notes application, so, although there will be 17 parts, if I get asked about other things that emerge as important enough to blog about, then I might add more.</p>
  248. <p>If you have questions that you don&#8217;t want to drop into the comments section you can email me at [email protected]</p>
  249. <p>Who am I?  I&#8217;m John Ryan, I&#8217;ve been working with Notes and Domino since 1993.  I am a co-owner, with Gary Walsh, of DLI.tools Inc., the company behind DOCOVA.  I am the CTO here and chief architect of DOCOVA&#8230;although (tongue in cheek)&#8230;really, I&#8217;m just the guy who sets impossible goals for our exceptional development team&#8230;and somehow, they pull it off!  We&#8217;ve won many awards (11 of them) over the years for DOCOVA and other software products we&#8217;ve developed.</p>
  250. <p>I&#8217;m really jazzed about our new version of DOCOVA.  It is version 5.  In version 5 we&#8217;ve added a user workspace, a browser-based integrated development environment called App Builder and App Importer, an integrated tool you run in DOCOVA to import Notes applications into DOCOVA.</p>
  251. <p>When investigating Notes application migration solutions, Notes developers should be asking the tough questions about what exactly gets migrated to the target platform and that&#8217;s what this series is about.</p>
  252. <p>Lots of solutions out there talk about archiving and retiring Notes applications, or switching them over to off-the-shelf (cloud and on premises) solutions.  Dig deeper and you&#8217;ll see their plan is to get your applications down to the bare minimum&#8230;and then redevelop them on the new platform, or use and modify them in some separate interface from the intended target interface.</p>
  253. <p>So, why doesn&#8217;t anybody out there have a true end-to-end migration solution for Notes applications like DOCOVA?  Two reasons, first, because it&#8217;s difficult.  Second, because it&#8217;s difficult.</p>
  254. <p>Companies don&#8217;t want to process re-engineer their Notes applications on a &#8220;new&#8221; software platform because it can&#8217;t do what Notes did.  They need better.  That&#8217;s why we stepped into this arena.</p>
  255. <p>DOCOVA V5 was made to be very flexible and can support many of the design elements coming from Notes applications, helping to make migrations more of an &#8220;apples to apples&#8221; modernizing of your Notes applications.  Trying to migrate to something like Sharepoint and Office 365 is like trying to hammer a square peg into a round hole.</p>
  256. <p>Also, just for the record, I want to point out a couple of things about DOCOVA because we have had developers assume certain things about DOCOVA in the past.  First of all, DOCOVA does not use XPages.  Second, although you can run DOCOVA on Domino as one of the database platforms, the applications are still migrated. This means Notes applications are converted to DOCOVA applications.  DOCOVA does NOT serve as a &#8220;front-end&#8221; to existing NSFs.  Got it?  Let&#8217;s move on.</p>
  257. <p>Okay&#8230;all that said, in this first entry of the blog series, at a high level, let&#8217;s talk about what gets migrated?  Subsequent blog entries will go into more detail about specific elements that get converted.</p>
  258. <p>DOCOVA&#8217;s migration tool is called the App Importer and it will import the user interface (UI), business logic, security, database schema and data.  Each of these is explained in more detail below.</p>
  259. <p><a href="http://www.docova.com/whatgetsmigrated/" target="_blank"><img class="alignnone wp-image-5365 size-full" src="http://www.docova.com/wp-content/uploads/2017/02/WhatGetsMigrated-e1487702173761.jpg" alt="WhatGetsMigrated" width="868" height="565" /></a></p>
  260. <p><strong>User Interface (UI):</strong></p>
  261. <p>Most of the design elements that make up the Notes application interface like forms, views, subforms, framesets, outlines, pages and image resources are converted to the new migrated application.</p>
  262. <p>Additionally, within these design elements their attributes are maintained.  For example, within forms and subforms, items like fields, tables, controlled access sections and embedded views are brought over.  In views, column properties like “Show multiple values as separate entries” are supported as well as sorting, categorization and totaling (except with totaling&#8230;DOCOVA views don&#8217;t have that extraneous category total.  You know what I mean?  Ya, that&#8217;s a good thing).</p>
  263. <p><strong>Business Logic:</strong></p>
  264. <p>Yep, the code.  When a Notes application is imported into DOCOVA, all of the @[email protected] language and LotusScript is converted to JavaScript and/or PHP.  If you know about parsers and lexers and grammars&#8230;ya&#8230;that stuff.</p>
  265. <p>No need to re-engineer your business processes and logic.  Unless you want to.</p>
  266. <p>Alright, wait a second!  It&#8217;s true that there are significant differences between a Notes client and a browser client.  So, yes, there are anomalies that can happen, however in our DOCOVA Analyzer tool, we identify certain things that need to be reviewed in the code to make sure it was translated properly.  This speeds the QA process significantly.  Best thing to do is get a demo with us.  The conversion is stunning really.</p>
  267. <p><strong>Security:</strong></p>
  268. <p>Security in DOCOVA is very flexible and hence can handle the security aspects found with Notes applications.  Access control lists, access types and fields like authors and readers and controlled access sections are all supported.  DOCOVA can also maintain its own User Directory, but can also integrate with LDAP directory sources like Active Directory and others.  Pretty convenient.</p>
  269. <p><strong>Database Schema:</strong></p>
  270. <p>So this is pretty killer.  When importing a Notes application over to DOCOVA, you don’t have to first create the database layout like tables and table relationships or anything like that.  DOCOVA will automatically create everything for you.</p>
  271. <p><strong>Data:</strong></p>
  272. <p>This one goes without saying, right?  Of course the data has to be migrated too.  All Notes document data is copied over to the new migrated application.  Additionally, all attachments are brought over and things like richtext and doclinks are maintained in the new environment.</p>
  273. <p>Okay&#8230;that&#8217;s enough for this installment.  Stay tuned for Part 2 in this blog series where I will delve deeper into LotusScript, what gets migrated, and how we do it.</p>
  274. <p>Comment below!</p>
  275. ]]></content:encoded>
  276. <wfw:commentRss>http://www.docova.com/migrate-notes-to-docova-blog-series-part-1-what-gets-migrated/feed/</wfw:commentRss>
  277. <slash:comments>0</slash:comments>
  278. </item>
  279. <item>
  280. <title>How Complex are Your Custom Notes Applications?</title>
  281. <link>http://www.docova.com/how-complex-are-your-custom-notes-applications/</link>
  282. <pubDate>Tue, 07 Feb 2017 16:00:40 +0000</pubDate>
  283. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  284. <category><![CDATA[Technical]]></category>
  285.  
  286. <guid isPermaLink="false">http://www.docova.com/?p=5251</guid>
  287. <description><![CDATA[When it comes to Notes application migration projects, the first thing that needs to be done is an analysis of the Notes environment. There are a lot of analysis tools on the market, and to determine application complexity many count and compare the number of design elements that make up each of the applications.  That is really not a very good indicator as there is specific code that is problematic when you migrate from a Notes client based application to a browser based application. At a high level, you need to look at any calls that: (1) stop the code and wait for user input (dialogbox, messagebox, picklist, prompt) JavaScript does not support modal windows, where further code execution is stopped pending user action. Therefore, that code has to be re-visited.  In LotusScript, for example, there may be one function that calls a dialog which passes values to the remaining code. In Javascript, that needs to be split into two functions. Function 1 calls the dialog. When &#8216;OK&#8217; is clicked, the second function is then called and passed the applicable values. (2) affect document state (editmode, save, refresh) The Notes client can track the state of the document, that is, whether it is in read mode or edit mode, and it can recompute individual values without having to reload the entire screen. A web browser, on the other hand, is stateless. It does not track whether a document is editable or not, and in order to refresh specific values, supporting code has to be provided (eg: dynamic HTML, Ajax) to do the updates. If a LotusScript function changes a document into edit mode, moving that function to the web requires an assessment to see if [&#8230;]]]></description>
  288. <content:encoded><![CDATA[<p>When it comes to Notes application migration projects, the first thing that needs to be done is an analysis of the Notes environment. There are a lot of analysis tools on the market, and to determine application complexity many count and compare the number of design elements that make up each of the applications.  That is really not a very good indicator as there is specific code that is problematic when you migrate from a Notes client based application to a browser based application.</p>
  289. <p>At a high level, you need to look at any calls that:</p>
  290. <p><strong>(1) stop the code and wait for user input (dialogbox, messagebox, picklist, prompt)</strong></p>
  291. <p>JavaScript does not support modal windows, where further code execution is stopped pending user action. Therefore, that code has to be re-visited.  In LotusScript, for example, there may be one function that calls a dialog which passes values to the remaining code. In Javascript, that needs to be split into two functions. Function 1 calls the dialog. When &#8216;OK&#8217; is clicked, the second function is then called and passed the applicable values.</p>
  292. <p><strong>(2) affect document state (editmode, save, refresh)</strong></p>
  293. <p>The Notes client can track the state of the document, that is, whether it is in read mode or edit mode, and it can recompute individual values without having to reload the entire screen. A web browser, on the other hand, is stateless. It does not track whether a document is editable or not, and in order to refresh specific values, supporting code has to be provided (eg: dynamic HTML, Ajax) to do the updates.</p>
  294. <p>If a LotusScript function changes a document into edit mode, moving that function to the web requires an assessment to see if the document needs to be reloaded in edit mode, or if updates can be done by sending an update to the server only. Similarly, a save or refresh type of call in a browser requires a trip to the server and either a full or partial document refresh. These calls must each be evaluated to assess the impact. A save or refresh call at the end of a function is likely to be fine and easily migrated, but will require work to be done when these calls occur mid-function.</p>
  295. <p><strong>(3) are not supported in JavaScript (goto, on error, viewnavigator, richtextnavigator)</strong></p>
  296. <p>Javascript does not support goto and on error commands. These have to be replaced by try{} catch{} or some similar type of error handling. ViewNavigator and RichTextNavigator are specific to Notes constructs and don&#8217;t have a direct migration path in Javascript. These calls need to be assessed and converted to lookups, or DOM document search type actions.</p>
  297. <p>Here is sample output from the<strong> DOCOVA Notes Application Analysis tool, </strong>showing a listing of problematic code elements for a particular application:</p>
  298. <p><a href="http://www.docova.com/wp-content/uploads/2017/01/Challenges1.jpg"><img class="alignnone size-full wp-image-5269" src="http://www.docova.com/wp-content/uploads/2017/01/Challenges1.jpg" alt="Challenges1" width="202" height="216" /></a></p>
  299. <p>The DOCOVA Analyzer looks through the individual applications for these various elements, and the number of occurrences, to come up with a complexity ranking. We call this the complex code number, or CC#.</p>
  300. <p>Most customers have many applications, and the complexity can vary considerably from one to the next.  Here is an example of several Notes applications and their associated C#.</p>
  301. <p><a href="http://www.docova.com/wp-content/uploads/2017/01/CC.jpg"><img class="alignnone size-full wp-image-5255" src="http://www.docova.com/wp-content/uploads/2017/01/CC.jpg" alt="CC#" width="894" height="499" srcset="http://www.docova.com/wp-content/uploads/2017/01/CC.jpg 894w, http://www.docova.com/wp-content/uploads/2017/01/CC-300x167.jpg 300w, http://www.docova.com/wp-content/uploads/2017/01/CC-768x429.jpg 768w" sizes="(max-width: 894px) 100vw, 894px" /></a></p>
  302. <p>Go to our DOCOVA Migration page to register to receive a copy of our DOCOVA Notes Application Analysis tool.  There is more info available regarding DOCOVA V5, which you can use to migrate or modernize your custom Notes applications or migrate them to the SQL platform.  Access the page<a href="http://www.docova.com/migrations-ibm-notesdomino-to-docova/" target="_blank"><span style="text-decoration: underline;"> here.</span></a></p>
  303. <p>&nbsp;</p>
  304. ]]></content:encoded>
  305. </item>
  306. <item>
  307. <title>Are You Attending IBM Connect 2017?</title>
  308. <link>http://www.docova.com/are-you-attending-ibm-connect-2017/</link>
  309. <pubDate>Thu, 15 Dec 2016 15:28:09 +0000</pubDate>
  310. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  311. <category><![CDATA[Technical]]></category>
  312.  
  313. <guid isPermaLink="false">http://www.docova.com/?p=5206</guid>
  314. <description><![CDATA[The IBM Connect Conference,  which used to be Lotusphere until it was re-branded several years back, is to be held in San Francisco February 20-23 2017.  As you are probably aware, for more than two decades this event was held at the Disney complex in Orlando.  This is the first time the event is to be held on the West Coast of the USA. It has also been pushed back a month on the calendar. I personally have been to 18 of these events, starting out back in the day when you continuously cycled your browser refresh button, around the time the registration page live time hit, hoping to get a spot before the conference was full. That usually happened in less than an hour. A lot has changed in the Notes and Domino community over the past two decades. For the past four years we have passed on taking a booth on the Showcase floor, instead holding a DOCOVA event on the boardwalk or some other venue close to the action. This year we wanted to try and get a gauge from customers and business partners on their thoughts regarding the conference, find out if they were planning to attend, or not, and why. Here is the link to the conference web site.  If you have not been there take a minute and have a look.  There are a lot of different options compared to previous years that help you to control your costs from a registration point of view.  Sessions have yet to be posted, but should be up soon. Have a look if you have not already, then leave a comment on this page to let us know what your feelings are.]]></description>
  315. <content:encoded><![CDATA[<p><img class="alignnone wp-image-5207 size-full" src="http://www.docova.com/wp-content/uploads/2016/12/Connect2017.jpg" alt="connect2017" width="930" height="284" srcset="http://www.docova.com/wp-content/uploads/2016/12/Connect2017.jpg 930w, http://www.docova.com/wp-content/uploads/2016/12/Connect2017-300x92.jpg 300w, http://www.docova.com/wp-content/uploads/2016/12/Connect2017-768x235.jpg 768w" sizes="(max-width: 930px) 100vw, 930px" /></p>
  316. <p>The IBM Connect Conference,  which used to be Lotusphere until it was re-branded several years back, is to be held in San Francisco February 20-23 2017.  As you are probably aware, for more than two decades this event was held at the Disney complex in Orlando.  This is the first time the event is to be held on the West Coast of the USA. It has also been pushed back a month on the calendar.</p>
  317. <p>I personally have been to 18 of these events, starting out back in the day when you continuously cycled your browser refresh button, around the time the registration page live time hit, hoping to get a spot before the conference was full. That usually happened in less than an hour.</p>
  318. <p>A lot has changed in the Notes and Domino community over the past two decades. For the past four years we have passed on taking a booth on the Showcase floor, instead holding a <a href="https://youtu.be/850JFXO2YZ8" target="_blank"><span style="text-decoration: underline;">DOCOVA</span></a> event on the boardwalk or some other venue close to the action.</p>
  319. <p>This year we wanted to try and get a gauge from customers and business partners on their thoughts regarding the conference, find out if they were planning to attend, or not, and why.</p>
  320. <p>Here is the link to<span style="text-decoration: underline;"> <a href="http://www-01.ibm.com/software/collaboration/events/connect/" target="_blank">the conference web site</a>.</span>  If you have not been there take a minute and have a look.  There are a lot of different options compared to previous years that help you to control your costs from a registration point of view.  Sessions have yet to be posted, but should be up soon.</p>
  321. <p>Have a look if you have not already, then leave a comment on this page to let us know what your feelings are.</p>
  322. ]]></content:encoded>
  323. </item>
  324. <item>
  325. <title>@DbLookup in Javascript? You Bet!</title>
  326. <link>http://www.docova.com/dblookup-in-javascript-you-bet/</link>
  327. <pubDate>Mon, 07 Nov 2016 15:46:54 +0000</pubDate>
  328. <dc:creator><![CDATA[David Wice]]></dc:creator>
  329. <category><![CDATA[Technical]]></category>
  330.  
  331. <guid isPermaLink="false">http://www.docova.com/?p=5071</guid>
  332. <description><![CDATA[When moving Notes applications from a Notes client to a web client, there are a number of design approaches that need to be changed.   While Domino will support many @Functions on the web, often they come with the unwanted side effect of a refresh of the form.  One example of this is drop down selection fields that present available values based on a lookup, where the lookup key comes from another field on the form. This article presents a way to achieve this functionality using Javascript and jQuery. The examples shown are within the DOCOVA framework, however the concepts can be applied to any Domino web application, or actually, any web application. Let me setup the scenario.  First, I have some configured lists setup, in this case, a list of countries, where each country has a list of cities. In my form, I have Country and City fields setup, with drop down like icons for selecting the respective values.  The concept is straightforward, after a Country is selected, the City list shows only those cities that are listed for that Country. Here’s the selection dialog in action, first picking a Country Then a City Selected values, shown in the form Now let’s have a look at how this is done.   In my example, I’m working on a Domino server, but as mentioned, the concepts can be applied to any platform. Here are my fields in Domino Designer Arguably, the Country field could be a standard drop down field with a @DBLookup formula that retrieves the Country list, however I’ve opted for full client side Javascript for this example so it can be applied to any platform. The selectCountry() function calls dbLookup, which we have created [&#8230;]]]></description>
  333. <content:encoded><![CDATA[<p>When moving Notes applications from a Notes client to a web client, there are a number of design approaches that need to be changed.   While Domino will support many @Functions on the web, often they come with the unwanted side effect of a refresh of the form.  One example of this is drop down selection fields that present available values based on a lookup, where the lookup key comes from another field on the form.</p>
  334. <p>This article presents a way to achieve this functionality using Javascript and jQuery.</p>
  335. <p>The examples shown are within the DOCOVA framework, however the concepts can be applied to any Domino web application, or actually, any web application.</p>
  336. <p>Let me setup the scenario.  First, I have some configured lists setup, in this case, a list of countries, where each country has a list of cities.</p>
  337. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig1.png"><img class="alignnone size-full wp-image-5072" src="http://www.docova.com/wp-content/uploads/2016/11/fig1.png" alt="fig1" width="555" height="282" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig1.png 555w, http://www.docova.com/wp-content/uploads/2016/11/fig1-300x152.png 300w" sizes="(max-width: 555px) 100vw, 555px" /></a></p>
  338. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig2.png"><img class="alignnone size-full wp-image-5073" src="http://www.docova.com/wp-content/uploads/2016/11/fig2.png" alt="fig2" width="515" height="284" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig2.png 515w, http://www.docova.com/wp-content/uploads/2016/11/fig2-300x165.png 300w" sizes="(max-width: 515px) 100vw, 515px" /></a></p>
  339. <p>In my form, I have Country and City fields setup, with drop down like icons for selecting the respective values.  The concept is straightforward, after a Country is selected, the City list shows only those cities that are listed for that Country.</p>
  340. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig3.png"><img class="alignnone size-full wp-image-5074" src="http://www.docova.com/wp-content/uploads/2016/11/fig3.png" alt="fig3" width="619" height="255" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig3.png 619w, http://www.docova.com/wp-content/uploads/2016/11/fig3-300x124.png 300w" sizes="(max-width: 619px) 100vw, 619px" /></a></p>
  341. <p>Here’s the selection dialog in action, first picking a Country</p>
  342. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig4.png"><img class="alignnone size-full wp-image-5075" src="http://www.docova.com/wp-content/uploads/2016/11/fig4.png" alt="fig4" width="351" height="366" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig4.png 351w, http://www.docova.com/wp-content/uploads/2016/11/fig4-288x300.png 288w" sizes="(max-width: 351px) 100vw, 351px" /></a></p>
  343. <p>Then a City</p>
  344. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig5.png"><img class="alignnone size-full wp-image-5076" src="http://www.docova.com/wp-content/uploads/2016/11/fig5.png" alt="fig5" width="335" height="356" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig5.png 335w, http://www.docova.com/wp-content/uploads/2016/11/fig5-282x300.png 282w" sizes="(max-width: 335px) 100vw, 335px" /></a></p>
  345. <p>Selected values, shown in the form</p>
  346. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig6.png"><img class="alignnone size-full wp-image-5077" src="http://www.docova.com/wp-content/uploads/2016/11/fig6.png" alt="fig6" width="537" height="78" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig6.png 537w, http://www.docova.com/wp-content/uploads/2016/11/fig6-300x44.png 300w" sizes="(max-width: 537px) 100vw, 537px" /></a></p>
  347. <p>Now let’s have a look at how this is done.   In my example, I’m working on a Domino server, but as mentioned, the concepts can be applied to any platform.</p>
  348. <p>Here are my fields in Domino Designer</p>
  349. <p><a href="http://www.docova.com/wp-content/uploads/2016/11/fig7.png"><img class="alignnone size-full wp-image-5078" src="http://www.docova.com/wp-content/uploads/2016/11/fig7.png" alt="fig7" width="694" height="77" srcset="http://www.docova.com/wp-content/uploads/2016/11/fig7.png 694w, http://www.docova.com/wp-content/uploads/2016/11/fig7-300x33.png 300w" sizes="(max-width: 694px) 100vw, 694px" /></a></p>
  350. <p>Arguably, the Country field could be a standard drop down field with a @DBLookup formula that retrieves the Country list, however I’ve opted for full client side Javascript for this example so it can be applied to any platform.</p>
  351. <p>The selectCountry() function calls dbLookup, which we have created as a direct replacement for the formula language @DBLookup function, and is part of our Docova.Utils JS class that contains a number of such methods.   The syntax for our dbLookup function and corresponding code is included in the attached code.  We use a JSON value pair array to pass the options so that the order doesn’t matter, and we can easily add options to the functions in the future without having to revisit all existing code. (Note the selectKeyword function is not included with this article)</p>
  352. <p>selectCity() is very similar to selectCountry(), the difference being we pass the Country as part of the lookup key, allowing us to return the correct list of cities.</p>
  353. <p>The JS header code is available <strong><a href="http://www.docova.com/wp-content/uploads/2016/11/dbLookup-Example-JSHeader.js" target="_blank">here</a></strong>, and the dblookup function is <strong><a href="http://www.docova.com/wp-content/uploads/2016/11/dbLookup.js" target="_blank">here</a></strong>.</p>
  354. <p>For more information on DOCOVA and how we’re migrating Notes applications to the web, visit <a href="http://www.docova.com" target="_blank">www.docova.com</a>.</p>
  355. <p>&nbsp;</p>
  356. ]]></content:encoded>
  357. </item>
  358. <item>
  359. <title>ICAA – Did IBM Release a Free Version of the Notes Client?</title>
  360. <link>http://www.docova.com/icaa-version-of-the-notes-client/</link>
  361. <pubDate>Sun, 30 Oct 2016 12:05:19 +0000</pubDate>
  362. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  363. <category><![CDATA[Technical]]></category>
  364.  
  365. <guid isPermaLink="false">http://www.docova.com/?p=5026</guid>
  366. <description><![CDATA[ICAA stands for IBM Client Application Access.  This is a standalone client, available for Mac and Windows, that is a stripped down version of the R9 Notes Basic client.   It has been around for awhile, June of 2015 I believe is when it was first released, however it seems to have come in under the radar of most customers and business partners.   Many thought it was simply a re-branding of the Notes browser plugin, which has been around for years now, and is installed by default when you install Notes R9. &#160; If you have not seen ICAA, check out this 1.5 minute video clip. This IBM announcement letter says that &#8220;the IBM® Client Application Access delivers a lightweight solution, enabling you to move to a browser-based interface for email (IBMiNotes®, IBM SmartCloud® Notes® web, or IBM Verse™), while continuing to work with existing Notes and Domino® applications.&#8221; Based on the above ICAA may lend support to the theory that IBM is perhaps looking to retire the Notes client.  If they were to stop selling the Notes client, Verse could provide IBM customers still using Notes for email with an alternative, and ICAA would provide a way of accessing existing applications.  By making Smartcloud a requirement to run ICAA it would encourage customers to move their Notes based applications to the IBM Cloud.   Or maybe it is in fact the Notes Browser Plugin repackaged, and not a key part of the Notes and Domino road map after all. This 80 ish mb  client is very much a Notes client.  It has a similar look and feel to the R9 Notes client. It even has the traditional Notes Workspace where your applications appear on tabs.  In [&#8230;]]]></description>
  367. <content:encoded><![CDATA[<p>ICAA stands for <strong>IBM Client Application Access</strong>.  This is a standalone client, available for Mac and Windows, that is<strong> a stripped down version of the R9 Notes Basic client</strong>.   It has been around for awhile, June of 2015 I believe is when it was first released, however it seems to have come in under the radar of most customers and business partners.   Many thought it was simply a re-branding of the Notes browser plugin, which has been around for years now, and is installed by default when you install Notes R9.</p>
  368. <p>&nbsp;</p>
  369. <div style="max-width:600px;max-height:350px;"><div class="video-shortcode"><iframe title="YouTube video player" width="600" height="350" src="http://www.youtube.com/embed/C4P8SkC5dDA" frameborder="0" allowfullscreen></iframe></div></div>
  370. <p>If you have not seen ICAA, check out this <a href="https://youtu.be/C4P8SkC5dDA" target="_blank">1.5 minute video clip</a>.</p>
  371. <p>This <a href="http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&amp;subtype=CA&amp;htmlfid=897/ENUS216-201" target="_blank">IBM announcement letter says</a> that &#8220;the IBM® Client Application Access delivers a lightweight solution, enabling you to move to a browser-based interface for email (IBMiNotes®, IBM SmartCloud® Notes® web, or IBM Verse™), while continuing to work with existing Notes and Domino® applications.&#8221;</p>
  372. <p>Based on the above ICAA may lend support to the theory that IBM is perhaps looking to retire the Notes client.  If they were to stop selling the Notes client, Verse could provide IBM customers still using Notes for email with an alternative, and ICAA would provide a way of accessing existing applications.  By making Smartcloud a requirement to run ICAA it would encourage customers to move their Notes based applications to the IBM Cloud.   Or maybe it is in fact the Notes Browser Plugin repackaged, and not a key part of the Notes and Domino road map after all.</p>
  373. <p>This 80 ish mb  client is very much a Notes client.  It has a similar look and feel to the R9 Notes client. It even has the traditional Notes Workspace where your applications appear on tabs.  In fact, if you make a copy of your Notes/Data directory, delete Notes, then install ICAA you can have the Workplace appear with your applications similar to what you see with the Notes client, standard or basic varieties.</p>
  374. <p><a href="http://www.docova.com/wp-content/uploads/2016/10/ICAAWorkspace.jpg"><img class="alignnone wp-image-5031" src="http://www.docova.com/wp-content/uploads/2016/10/ICAAWorkspace.jpg" alt="icaaworkspace" width="539" height="330" srcset="http://www.docova.com/wp-content/uploads/2016/10/ICAAWorkspace.jpg 656w, http://www.docova.com/wp-content/uploads/2016/10/ICAAWorkspace-300x184.jpg 300w" sizes="(max-width: 539px) 100vw, 539px" /></a></p>
  375. <p>I have accessed a wide variety of Notes applications with ICAA, from simple to complex, and except for not supporting attachment viewing and providing for spellcheck in rich text fields, the applications seem to behave the same as they do when you use the full Notes client.</p>
  376. <p>Below is one of our older commercial DLI applications that has since been retired, the DLI HelpDesk, viewed using ICAA.</p>
  377. <p><a href="http://www.docova.com/wp-content/uploads/2016/10/ICAAHelpDesk.jpg"><img class="alignnone wp-image-5032" src="http://www.docova.com/wp-content/uploads/2016/10/ICAAHelpDesk.jpg" alt="icaahelpdesk" width="886" height="427" srcset="http://www.docova.com/wp-content/uploads/2016/10/ICAAHelpDesk.jpg 1918w, http://www.docova.com/wp-content/uploads/2016/10/ICAAHelpDesk-300x145.jpg 300w, http://www.docova.com/wp-content/uploads/2016/10/ICAAHelpDesk-768x370.jpg 768w, http://www.docova.com/wp-content/uploads/2016/10/ICAAHelpDesk-1024x493.jpg 1024w" sizes="(max-width: 886px) 100vw, 886px" /></a></p>
  378. <p>What are the license requirements for ICAA? <strong>Is ICAA free?</strong>  I called the IBM Passport Advantage folks who dug into it more and I was forwarded an email from the Offering Manager for IBM Collaborative Solutions saying that indeed<strong> ICAA is a replacement for the Notes Browser Plugin</strong>.  It comes free with the Utility servers.</p>
  379. <p>Digging through available documentation I was able to find the following documents to support that:<!--Notes ACF
  380. <meta http-equiv="Content-Type" content="text/html charset=utf-8">--></p>
  381. <div>
  382. <div>
  383. <div><a href="http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/0/897/ENUS215-350/index.html&amp;lang=en&amp;request_locale=en">http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/0/897/ENUS215-350/index.html&amp;lang=en&amp;request_locale=en</a></div>
  384. <div><a href="http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&amp;subtype=CA&amp;htmlfid=897/ENUS216-201">http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&amp;subtype=CA&amp;htmlfid=897/ENUS216-201</a></div>
  385. <div><a href="http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&amp;subtype=CA&amp;htmlfid=897/ENUS215-213&amp;appname=USN">http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&amp;subtype=CA&amp;htmlfid=897/ENUS215-213&amp;appname=USN</a></div>
  386. </div>
  387. </div>
  388. <div></div>
  389. <div>The Domino Server License agreement, however, is the document that defines what is allowed and what is not in terms of client access.  It would be better to have ICAA mentioned specifically in that document as it does not fit the definition of a browser client. It is a client application.</div>
  390. <p>Although interesting, I do not feel ICAA will impact the downward trajectory of Notes. Even if ICAA provides customers with a free client, <strong>Domino is already one of the most affordable application development environments on the market</strong>.  Customers are leaving the platform for other reasons. With the Standard Notes Client, The Basic Notes Client,  I think ICAA adds more confusion to the mix.</p>
  391. <p>Keep in mind <a href="http://www.docova.com" target="_blank">DOCOVA</a> provides a migration alternative for customers looking to migrate their Notes apps to browser based apps on Domino, or on SQL.  Some will say I am simply feeding the fires to promote self interests when I raise questions about product announcements like ICAA and IBM&#8217;s inconsistent messages regarding the road map for Notes and Domino.  The reality is that I feel<strong> Domino is a very solid platform</strong>, and I would like nothing better for it to be at the heart of every DOCOVA deal we do.  The reality is that the majority of customers are opting for our DOCOVA SQL Edition vs DOCOVA on Domino.   We have been drawn into the <a href="http://www.docova.com/migrations-ibm-notesdomino-to-docova/" target="_blank">migration market</a> due to market conditions, not by choice.</p>
  392. ]]></content:encoded>
  393. </item>
  394. <item>
  395. <title>IBM Extends Support for Notes V9.0.1 to 2021</title>
  396. <link>http://www.docova.com/ibm-extends-support-for-notes-v9-0-1-to-2021/</link>
  397. <pubDate>Fri, 23 Sep 2016 16:06:44 +0000</pubDate>
  398. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  399. <category><![CDATA[Technical]]></category>
  400. <category><![CDATA[uncategorized]]></category>
  401.  
  402. <guid isPermaLink="false">http://www.docova.com/?p=4984</guid>
  403. <description><![CDATA[The announcement IBM indicated was coming in September came.   It confirms that IBM will be extending support for the current version of Notes until &#8220;at least&#8221; 2021.  It also mentions that new features will be delivered as fix packs rather than new versions.  Some blogs have suggested that IBM is embarking on a continuous delivery model for features, which in my opinion is a good thing.  It would have been nice for them to include that in their announcement, so customers and partners are not reading between the lines and filling in their own opinions. Although this announcement is positive on the surface, Notes &#38; Domino have been supported for the last three years, since 9.01 was released, and customers and partners have pretty vocal that a voice on the end of the phone is not enough. If you want to come up to speed on the reaction to the announcement I suggest you find your way to Planet Lotus.  That is a blog aggregate that focuses on the Notes &#38; Domino community. A partner perspective I liked can be found at Red Pill Now&#8217;s Blog.  A customer/developer perspective I found interesting came from David Leedy.  If you are looking for a more positive spin on things I suggest you check out Bill Malchiski&#8217;s blog. The general feel I get is that IBM is serious about fixing the barn door but they do not articulate very well how they are going to do that.  In my opinion the real problem has to do with the horses. &#160; IBM Notes and Domino V9 Extends Support &#160;]]></description>
  404. <content:encoded><![CDATA[<p>The announcement IBM indicated was coming in September came.   It confirms that IBM will be <strong>extending support for the current version of Notes until &#8220;at least&#8221; 2021</strong>.  It also mentions that new features will be delivered as fix packs rather than new versions.  Some blogs have suggested that IBM is embarking on a<strong> continuous delivery model</strong> for features, which in my opinion is a good thing.  It would have been nice for them to include that in their announcement, so customers and partners are not reading between the lines and filling in their own opinions.</p>
  405. <p>Although this announcement is positive on the surface, Notes &amp; Domino have been supported for the last three years, since 9.01 was released, and customers and partners have pretty vocal that a voice on the end of the phone is not enough.</p>
  406. <p>If you want to come up to speed on the reaction to the announcement I suggest you find your way to <a href="http://planetlotus.org/blogs/" target="_blank">Planet Lotus</a>.  That is a blog aggregate that focuses on the <strong>Notes &amp; Domino community</strong>. A partner perspective I liked can be found at <a href="http://redpillnow.com/was-that-it/" target="_blank">Red Pill Now&#8217;s Blog</a>.  A customer/developer perspective I found interesting came from <a href="http://www.notesin9.com/2016/09/13/no-more/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+NotesIn9+%28Notes+In+9+-+Wordpress%29" target="_blank">David Leedy</a>.  If you are looking for a more positive spin on things I suggest you check out <a href="http://www.billmal.com/billmal/billmal.nsf/dx/barry-rosen-part-1.htm" target="_blank">Bill Malchiski&#8217;s</a> blog.</p>
  407. <p>The general feel I get is that IBM is serious about fixing the barn door but they do not articulate very well how they are going to do that.  In my opinion the real problem has to do with the horses.</p>
  408. <p>&nbsp;</p>
  409. <blockquote data-secret="Mgq5TWzqqb" class="wp-embedded-content"><p><a href="https://www.ibm.com/blogs/social-business/2016/09/12/ibm-notes-domino-v9-extends-support/">IBM Notes and Domino V9 Extends Support</a></p></blockquote>
  410. <p><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted" src="https://www.ibm.com/blogs/social-business/2016/09/12/ibm-notes-domino-v9-extends-support/embed/#?secret=Mgq5TWzqqb" data-secret="Mgq5TWzqqb" width="600" height="338" title="&#8220;IBM Notes and Domino V9 Extends Support&#8221; &#8212; Social Business Spotlight Blog" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe></p>
  411. <p>&nbsp;</p>
  412. ]]></content:encoded>
  413. </item>
  414. <item>
  415. <title>Mobile App Dev for Dummies</title>
  416. <link>http://www.docova.com/mobile-app-dev-for-dummies/</link>
  417. <comments>http://www.docova.com/mobile-app-dev-for-dummies/#comments</comments>
  418. <pubDate>Fri, 23 Sep 2016 15:13:26 +0000</pubDate>
  419. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  420. <category><![CDATA[Technical]]></category>
  421.  
  422. <guid isPermaLink="false">http://www.docova.com/?p=4977</guid>
  423. <description><![CDATA[I fly a little home built airplane as a hobby.  I am lucky in that it burns car gas instead of the much higher priced aviation fuel.  In Canada, in the province of Ontario, because a portion of gasoline tax goes to road improvements and an airplane does not use roads, you can get the tax back.  Its not hard to do. You take the information from your gas receipt, the quantity purchased, the price per liter, the total cost&#8230;that kind of thing, and you put into a log.  At the end of the year you total it all up, do a simple calculation and submit a claim to the Ontario Ministry of Finance.  They send you a rebate that represents the road tax.  You have to keep the receipts and the log for seven years, in case they decide to audit you.                                                                So why can I never seem to do it?  The reason is that I wait till the end of the year.  Its not one receipt but dozens, if I can find where I put them. They all have to be entered into the log, which takes time, and I never seem to have the time. What I needed was an app for my phone.  An app that allowed me to capture all the meta data, along with an image of the receipt, while I was at the gas pump. An app that put everything into a summary report. An app that did all the work for me.  Most important, it had to be easy to create. I am not a developer. I can hack something together with IBM Notes, but XPAGES or Rest Services, not happening. &#160; &#160;                                                        I do, however, [&#8230;]]]></description>
  424. <content:encoded><![CDATA[<p>I fly a little home built airplane as a hobby.  I am lucky in that it burns car gas instead of the much higher priced aviation fuel.  In Canada, in the province of Ontario, because a portion of gasoline tax goes to road improvements and an airplane does not use roads, you can get the tax back.  Its not hard to do. You take the information from your gas receipt, the quantity purchased, the price per liter, the total cost&#8230;that kind of thing, and you put into a log.  At the end of the year you total it all up, do a simple calculation and submit a claim to the Ontario Ministry of Finance.  They send you a rebate that represents the road tax.  You have to keep the receipts and the log for seven years, in case they decide to audit you.</p>
  425. <p style="text-align: justify;"><a href="http://www.docova.com/wp-content/uploads/2016/09/TEU3.jpg">                                                               <img class="alignnone wp-image-4991" src="http://www.docova.com/wp-content/uploads/2016/09/TEU3.jpg" alt="teu3" width="272" height="153" srcset="http://www.docova.com/wp-content/uploads/2016/09/TEU3.jpg 534w, http://www.docova.com/wp-content/uploads/2016/09/TEU3-300x169.jpg 300w" sizes="(max-width: 272px) 100vw, 272px" /></a></p>
  426. <p>So why can I never seem to do it?  The reason is that I wait till the end of the year.  Its not one receipt but dozens, if I can find where I put them. They all have to be entered into the log, which takes time, and I never seem to have the time.</p>
  427. <p>What I needed was an app for my phone.  An app that allowed me to capture all the meta data, along with an image of the receipt, while I was at the gas pump. An app that put everything into a summary report. An app that did all the work for me.  Most important, it had to be easy to create. <strong>I am not a developer. </strong>I can hack something together with IBM Notes, but XPAGES or Rest Services, not happening.</p>
  428. <p>&nbsp;</p>
  429. <p>&nbsp;</p>
  430. <p><a href="http://www.docova.com/wp-content/uploads/2016/09/GasApp.jpg">                                                       </a><a href="http://www.docova.com/wp-content/uploads/2016/09/GasApp.jpg"><img class="alignnone wp-image-4988" src="http://www.docova.com/wp-content/uploads/2016/09/GasApp.jpg" alt="gasapp" width="221" height="375" srcset="http://www.docova.com/wp-content/uploads/2016/09/GasApp.jpg 350w, http://www.docova.com/wp-content/uploads/2016/09/GasApp-177x300.jpg 177w" sizes="(max-width: 221px) 100vw, 221px" /></a></p>
  431. <p>I do, however, have access to a <strong>DOCOVA</strong> environment.  <strong>One hour after starting on it, I was done</strong>.  Here is what I created, and how I did it ( 3 min 40 sec).</p>
  432. <div style="max-width:600px;max-height:340px;"><div class="video-shortcode"><iframe title="YouTube video player" width="600" height="340" src="http://www.youtube.com/embed/uEfPWEqqXiY" frameborder="0" allowfullscreen></iframe></div></div>
  433. <p>&nbsp;</p>
  434. <p>&nbsp;</p>
  435. <p>&nbsp;</p>
  436. <p>&nbsp;</p>
  437. <p>&nbsp;</p>
  438. ]]></content:encoded>
  439. <wfw:commentRss>http://www.docova.com/mobile-app-dev-for-dummies/feed/</wfw:commentRss>
  440. <slash:comments>1</slash:comments>
  441. </item>
  442. <item>
  443. <title>MWLUG 2016 Recap</title>
  444. <link>http://www.docova.com/mwlug-2016-recap/</link>
  445. <pubDate>Sat, 20 Aug 2016 22:31:04 +0000</pubDate>
  446. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  447. <category><![CDATA[Technical]]></category>
  448.  
  449. <guid isPermaLink="false">http://www.docova.com/?p=4774</guid>
  450. <description><![CDATA[Overall the attendance was about the same as last year.  Somewhere around 200.  MWLUG, like many of the  Lotus User Groups, continues to fan the embers of the Notes and Domino community, keeping the flame burning.  Unlike the IBM Connect Event, formerly called Lotusphere, the sessions were Notes &#38; Domino heavy, with a variety of seasoned speakers distributing valuable technical advice. The MWLUG venue was the Four Seasons in downtown Austin Texas.  Service was off the charts. A bit creepy in some respects, such as when you find a bookmark in your book where a dogear used to reside.  Weather was not typical as it rained during most of the event, making treks out to see the live music and other amenities the city has to offer a soggy affair. The event  kicked off on the Wednesday with a tour of the IBM Design Labs.  Austin is the home to several tech companies, including IBM.   It was interesting to see the sometime unusual aspects of a workspace designed to foster creativity.  Movable walls.  Stand up desks. Rooms filled with balloons and boxes filled with ducks.                                                Although the sessions started up Wednesday afternoon,  the Opening General Session began on Thursday.  IBM, as a Diamond sponsor, had the floor first.   Although the focus was more on Watson and the whole concept of cognitive computing, I was pleasantly surprised to see a slide appear that mentioned Notes &#38; Domino. Katrina Troughton, IBM GM, Social and Smarter Workplace Client Success, used a slide to illustrate that IBM was still committed to Notes &#38; Domino.  Most of [&#8230;]]]></description>
  451. <content:encoded><![CDATA[<p>Overall the attendance was about the same as last year.  Somewhere around 200.  MWLUG, like many of the  Lotus User Groups, continues to fan the embers of the Notes and Domino community, keeping the flame burning.  Unlike the IBM Connect Event, formerly called Lotusphere, the sessions were Notes &amp; Domino heavy, with a variety of seasoned speakers distributing valuable technical advice.</p>
  452. <p>The MWLUG venue was the Four Seasons in downtown Austin Texas.  Service was off the charts. A bit creepy in some respects, such as when you find a bookmark in your book where a dogear used to reside.  Weather was not typical as it rained during most of the event, making treks out to see the live music and other amenities the city has to offer a soggy affair.</p>
  453. <p>The event  kicked off on the Wednesday with a tour of the IBM Design Labs.  Austin is the home to several tech companies, including IBM.   It was interesting to see the sometime unusual aspects of a workspace designed to foster creativity.  Movable walls.  Stand up desks. Rooms filled with balloons and boxes filled with ducks.</p>
  454. <p><a href="http://www.docova.com/wp-content/uploads/2016/08/balloons.jpg"><img class="alignnone wp-image-4782 " src="http://www.docova.com/wp-content/uploads/2016/08/balloons-e1471633449764-169x300.jpg" alt="balloons" width="220" height="391" srcset="http://www.docova.com/wp-content/uploads/2016/08/balloons-e1471633449764-169x300.jpg 169w, http://www.docova.com/wp-content/uploads/2016/08/balloons-e1471633449764-768x1365.jpg 768w, http://www.docova.com/wp-content/uploads/2016/08/balloons-e1471633449764-576x1024.jpg 576w" sizes="(max-width: 220px) 100vw, 220px" />                                                </a><a href="http://www.docova.com/wp-content/uploads/2016/08/BoxDucks.jpg"><img class="alignnone wp-image-4783 " src="http://www.docova.com/wp-content/uploads/2016/08/BoxDucks-e1471633557813-169x300.jpg" alt="BoxDucks" width="187" height="332" srcset="http://www.docova.com/wp-content/uploads/2016/08/BoxDucks-e1471633557813-169x300.jpg 169w, http://www.docova.com/wp-content/uploads/2016/08/BoxDucks-e1471633557813-768x1365.jpg 768w, http://www.docova.com/wp-content/uploads/2016/08/BoxDucks-e1471633557813-576x1024.jpg 576w" sizes="(max-width: 187px) 100vw, 187px" /></a></p>
  455. <p>Although the sessions started up Wednesday afternoon,  the Opening General Session began on Thursday.  IBM, as a Diamond sponsor, had the floor first.   Although the focus was more on Watson and the whole concept of cognitive computing, I was pleasantly surprised to see a slide appear that mentioned Notes &amp; Domino.</p>
  456. <p><a href="http://www.docova.com/wp-content/uploads/2016/08/IBMSlide.jpg"><img class="alignnone wp-image-4781 " src="http://www.docova.com/wp-content/uploads/2016/08/IBMSlide-1024x576.jpg" alt="IBMSlide" width="475" height="267" srcset="http://www.docova.com/wp-content/uploads/2016/08/IBMSlide-1024x576.jpg 1024w, http://www.docova.com/wp-content/uploads/2016/08/IBMSlide-300x169.jpg 300w, http://www.docova.com/wp-content/uploads/2016/08/IBMSlide-768x432.jpg 768w" sizes="(max-width: 475px) 100vw, 475px" /></a></p>
  457. <p>Katrina Troughton, IBM GM, Social and Smarter Workplace Client Success, used a slide to illustrate that IBM was still committed to Notes &amp; Domino.  Most of the dialog was about Verse and she did not address the unanswered question regarding the long awaited (almost three years and counting) release of Notes 9.02.  Katrina said FixPack 7 includes several new features, so it is really more than a Fix Pack.  Blue Mix was also mentioned, and she asked for a show of hands of how many people used BlueMix for development.  I counted  a total of three hands.  If she had asked who used Notes &amp; Domino it would have been dozens.</p>
  458. <p>The Keynote speaker was local singer/songwriter and studio owner Christine Albert.  She is also the Founder and CEO of Swan Songs, a non-profit that fulfills musical last wishes for the terminally ill.   The irony of Swan Songs at a conference for Notes &amp; Domino professionals hung in the air.</p>
  459. <p><a href="http://www.docova.com/wp-content/uploads/2016/08/SwanSong-1.jpg"><img class="alignnone wp-image-4805" src="http://www.docova.com/wp-content/uploads/2016/08/SwanSong-1.jpg" alt="SwanSong" width="654" height="368" srcset="http://www.docova.com/wp-content/uploads/2016/08/SwanSong-1.jpg 5312w, http://www.docova.com/wp-content/uploads/2016/08/SwanSong-1-300x169.jpg 300w, http://www.docova.com/wp-content/uploads/2016/08/SwanSong-1-768x432.jpg 768w, http://www.docova.com/wp-content/uploads/2016/08/SwanSong-1-1024x576.jpg 1024w" sizes="(max-width: 654px) 100vw, 654px" /></a></p>
  460. <p>Several of the sessions focused on security, which included SSL/TLS/and SHA1 certificates and the fact that they would not be supported by Microsoft or Google after Jan 1, 2017.   That should be a <a href="http://www.docova.com/quickr-alert-ssl/">RED ALERT</a> for Quickr customers who have Quickr sites that are exposed to the internet.  Basically it means that if customers do nothing content will not be available to users in the new year. Of course they could front end the Domino server with a proxy, but it represents a clear call to action.</p>
  461. <p>For me MWLUG confirmed that the Notes client is pretty much reached the end of its life.  This was openly discussed in several sessions by many of the speakers who in the past have only spoken openly about it behind closed doors.   That has never been an issue for Darren Duke, whose final session around security was vocal to say the least.   He made the comment that version 9.02 has been complete for almost 2.5 years now, but IBM has not released it. Duke says the most recent fix pack, due out in September, could be pushing 1 GB in size and will represent the majority of what was intended to be 9.02.  This supports what Katrina had said in the OGS.  He suggests that the September announcement IBM has planned around the <a href="http://www.docova.com/ibm-announces-a-change-to-the-notes-domino-life-cycle-policy/" target="_blank">Notes &amp; Domino LifeCycle Policy </a> could potentially be a change in the nomenclature regarding releases and fix packs.  I think they will extend the life of 9.0x to something like 2020 or later since there is no intention to do a version 9.1, let alone a 10.</p>
  462. <p>For me MWLUG has re-enforced our DOCOVA strategy.  The Notes client is no longer a target for investment within IBM.  DOCOVA is an opportunity for companies who want to minimize their risk to transition off the Notes client sooner rather than later.  If the Notes client were to disappear, and IBM does not have a solid offering beyond email that will address the future of Notes applications, <a href="http://www.docova.com/migrations-ibm-notesdomino-to-docova/" target="_blank">DOCOVA represents the best migration alternative</a>.  It is a browser and mobile based replacement for the Notes client, with platform independence that provides a migration path if customers decide they are leaving the Notes &amp; Domino platform. For more information check out our 2.5 minute migration video or visit our <a href="http://www.docova.com/migrations-ibm-notesdomino-to-docova/" target="_blank">migration page</a>.</p>
  463. <p>The MWLUG torch was passed to Washington DC during the closing session.   That will be the location for the event next year.  We will be there.</p>
  464. ]]></content:encoded>
  465. </item>
  466. <item>
  467. <title>Quickr Alert – SSL Certs Expire Jan 1, 2017</title>
  468. <link>http://www.docova.com/quickr-alert-ssl/</link>
  469. <pubDate>Fri, 19 Aug 2016 12:39:00 +0000</pubDate>
  470. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  471. <category><![CDATA[Technical]]></category>
  472.  
  473. <guid isPermaLink="false">http://www.docova.com/?p=4757</guid>
  474. <description><![CDATA[I went to a session yesterday at MWLUG regarding SSL Certificates.  I had heard there were issues around SSL certs and it could impact Quickr customers.  What I learned is that Microsoft and Google are phasing out support for SHA-1 style certs, in favor of the more secure SHA-2 format.   As of Jan 1, 2017 Microsoft and Google will stop supporting these older SHA-1 certs. Since Domino 8.5 does not support SHA-2 certificates, customers need to upgrade to Domino 9.0.1 FP3 or higher. Quickr is not supported on Domino V9, which means after Jan 1, 2017 users could lose access to data stored in Quickr.  There are some workarounds available, such as standing up a proxy server in front of the Quickr server, but some form of action is required. Many Quickr customers have demonstrated a reluctance to migrate off Quickr even though the end of support date of September 2016 is almost here.   The issue around SSL Certs is definitely a call to action. DOCOVA is an excellent migration alternative for Quickr customers.   It has functional similarities to Quickr and will run on both Domino and SQL platforms.  We have created a migration tool that customers can use to migrate their Quickr Places to DOCOVA themselves on a timeline they can manage.   For more information check out the Quickr Migration Toolkit.]]></description>
  475. <content:encoded><![CDATA[<p>I went to a session yesterday at MWLUG regarding SSL Certificates.  I had heard there were issues around SSL certs and it could impact Quickr customers.  What I learned is that <a href="https://blogs.windows.com/msedgedev/2016/04/29/sha1-deprecation-roadmap/#ITRoj0hGUeIWP1Hr.97" target="_blank">Microsoft</a> and <a href="https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html" target="_blank">Google</a> are phasing out support for SHA-1 style certs, in favor of the more secure SHA-2 format.   As of Jan 1, 2017 Microsoft and Google will stop supporting these older SHA-1 certs.</p>
  476. <p>Since Domino 8.5 does not support SHA-2 certificates, customers need to upgrade to Domino 9.0.1 FP3 or higher. Quickr is not supported on Domino V9, which means after Jan 1, 2017 users could lose access to data stored in Quickr.  There are some workarounds available, such as standing up a proxy server in front of the Quickr server, but some form of action is required.</p>
  477. <p>Many Quickr customers have demonstrated a reluctance to migrate off Quickr even though the end of support date of September 2016 is almost here.   The issue around SSL Certs is definitely a call to action.</p>
  478. <p>DOCOVA is an excellent migration alternative for Quickr customers.   It has functional similarities to Quickr and will run on both Domino and SQL platforms.  We have created a migration tool that customers can use to migrate their Quickr Places to DOCOVA themselves on a timeline they can manage.   For more information check out the <a href="http://www.docova.com/quickr-migration-tool/" target="_blank">Quickr Migration Toolkit</a>.</p>
  479. ]]></content:encoded>
  480. </item>
  481. <item>
  482. <title>IBM Announces a Change is Coming to the Notes &amp; Domino Life Cycle Policy</title>
  483. <link>http://www.docova.com/ibm-announces-a-change-to-the-notes-domino-life-cycle-policy/</link>
  484. <comments>http://www.docova.com/ibm-announces-a-change-to-the-notes-domino-life-cycle-policy/#comments</comments>
  485. <pubDate>Fri, 12 Aug 2016 18:06:33 +0000</pubDate>
  486. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  487. <category><![CDATA[Technical]]></category>
  488. <category><![CDATA[uncategorized]]></category>
  489.  
  490. <guid isPermaLink="false">http://www.docova.com/?p=4709</guid>
  491. <description><![CDATA[IBM recently posted this announcement. This is really an announcement that there will be an announcement.  Lets take a guess at what could be coming. The lifecycle policy defines the length of time that a product is supported following its release.  For IBM Notes it is classified as Enhanced, or 5 + 3.  The product will be supported for 5 years since the date it was released, with 3 more years  optional if a customer pays for support.   Notes 9.01 was released in April of 2013, so the end of support would be in April of 2018. Initially my prediction was that in September IBM will change that policy to extend the time that Notes is supported from 5 to something like 7 years or more.   I thought that the reason 9.0.2 was not released was because it would require that IBM support it for at least another 5 years, and they did not want to do that. After attending MWLUG, and talking to others in the community, I am not sure that is the case.  The lifecycle policy does not kick in for a point release, something like a 9.0.2.  It would for a major new release, like version 10, but not for a point release.  That being said, apparently there is a QA and documentation process that is part of a point release, and that costs money.  It appears to me and others I talked to that IBM is putting features into the fix packs to avoid having to absorb the costs related to a point release. In the per-announcement above they talk about their continued commitment to Notes &#38; Domino, referencing to new features and the release of Verse on-premises.   Verse uses [&#8230;]]]></description>
  492. <content:encoded><![CDATA[<p>IBM recently posted this announcement.</p>
  493. <p><a href="http://www.docova.com/wp-content/uploads/2016/08/Announce1.jpg"><img class="alignnone size-full wp-image-4836" src="http://www.docova.com/wp-content/uploads/2016/08/Announce1.jpg" alt="Announce1" width="816" height="317" srcset="http://www.docova.com/wp-content/uploads/2016/08/Announce1.jpg 816w, http://www.docova.com/wp-content/uploads/2016/08/Announce1-300x117.jpg 300w, http://www.docova.com/wp-content/uploads/2016/08/Announce1-768x298.jpg 768w" sizes="(max-width: 816px) 100vw, 816px" /></a></p>
  494. <p>This is really an announcement that there will be an announcement.  Lets take a guess at what could be coming.</p>
  495. <p>The lifecycle policy defines the length of time that a product is supported following its release.  For IBM Notes it is classified as <a href="https://www-01.ibm.com/software/support/lifecycle/cd-faq.html" target="_blank">Enhanced</a>, or 5 + 3.  The product will be supported for 5 years since the date it was released, with 3 more years  optional if a customer pays for support.   Notes 9.01 was released in April of 2013, so the end of support would be in April of 2018.</p>
  496. <p>Initially my prediction was that in September IBM will change that policy to extend the time that Notes is supported from 5 to something like 7 years or more.   I thought that the reason 9.0.2 was not released was because it would require that IBM support it for at least another 5 years, and they did not want to do that.</p>
  497. <p>After attending MWLUG, and talking to others in the community, I am not sure that is the case.  The lifecycle policy does not kick in for a point release, something like a 9.0.2.  It would for a major new release, like version 10, but not for a point release.  That being said, apparently there is a QA and documentation process that is part of a point release, and that costs money.  It appears to me and others I talked to that IBM is putting features into the fix packs to avoid having to absorb the costs related to a point release.</p>
  498. <p>In the per-announcement above they talk about their continued commitment to Notes &amp; Domino, referencing to new features and the release of Verse on-premises.   Verse uses the Domino server, and in my opinion is a replacement for iNotes, their Domino web based mail client.   If IBM sees the need to provide an alternative for Notes email it suggests to me that the intent is to retire the Notes client in the near future.</p>
  499. <p>It could be they extend the lifecycle for Notes beyond the Enhanced 5 &amp; 3 model to calm customers who are currently running 9.0.1, or that they change the nomenclature around releases and Fix Packs to be more in line with the cloud, or they take it a step further and announce that Notes is withdrawn as a SKU.</p>
  500. <p>Our <a href="http://www.docova.com" target="_blank">DOCOVA</a> product can be looked at as <a href="http://www.docova.com/migrations-ibm-notesdomino-to-docova/" target="_blank">a replacement for the Notes client</a> when it comes to applications, so I expect to be criticized as stirring the pot.  Please keep in mind that at DLI our roots are in Notes &amp; Domino.  We only created a SQL version because we were forced to because of a decaying market.  I think the Domino technology is still heads and shoulders above many of the alternatives.  I would like nothing more than to be part of a vibrant community selling Notes &amp; Domino solutions.</p>
  501. <p>September is just around the corner, so we will not have long to wait.</p>
  502. <p>&nbsp;</p>
  503. <p>&nbsp;</p>
  504. ]]></content:encoded>
  505. <wfw:commentRss>http://www.docova.com/ibm-announces-a-change-to-the-notes-domino-life-cycle-policy/feed/</wfw:commentRss>
  506. <slash:comments>2</slash:comments>
  507. </item>
  508. <item>
  509. <title>Is 2017 The Year IBM Announces the End of Life of Notes?</title>
  510. <link>http://www.docova.com/is-2017-the-year-ibm-announces-the-end-of-life-of-notes/</link>
  511. <pubDate>Tue, 24 May 2016 12:16:58 +0000</pubDate>
  512. <dc:creator><![CDATA[Gary Walsh]]></dc:creator>
  513. <category><![CDATA[Technical]]></category>
  514.  
  515. <guid isPermaLink="false">http://www.docova.com/?p=4468</guid>
  516. <description><![CDATA[In 2016, following the MWLUG event in Austin, blogs from individuals in the Notes community became very critical of IBM&#8217;s lack of attention to the product.  Version 9.01 was released in April of 2013, and despite promises by IBM, no new release had appeared.  That is a span of over 3 years.  Our DOCOVA product was initially based on Domino.  Due to all the uncertainty we now have a version that runs on SQL. Prior to IBM Connect 2017, the conference that used to be known as Lotusphere, IBM responded with a redefined roadmap for Notes and Domino.  At the conference we got to hear about that in detail. Let me start with Ed Brill&#8217;s recent posting recapping Connect 2017.  In his posting he says that IBM made it &#8220;a priority to emphasize our commitment to IBM Domino as an application and mail platform.&#8221; He said that they have &#8220;announced a number of initiatives to provide clear examples of the value both IBM and our clients place on having a confident direction for the product and its roadmap&#8221;.  These included: Extended Support Feature Packs Verse On-Premises Application Analysis API&#8217;s Application Refresh (aka Modernization) Lets look at each of these.  Extended support refers to support for Notes and Domino to at least 2021. Notes 9.01 was released in April of 2013, and as it was categorized in their life cycle policy as &#8220;enhanced&#8221; meant that it had a commitment of 5 years of support, with additional support available for a cost over the annual support fee.  That would take it to 2018.  IBM announced in September of 2016 that support has been extended to 2021, with additional support, for a fee, to 2024.  There was nothing new announced at Connect [&#8230;]]]></description>
  517. <content:encoded><![CDATA[<p>In 2016, following the MWLUG event in Austin, blogs from individuals in the Notes community became very critical of IBM&#8217;s lack of attention to the product.  Version 9.01 was released in April of 2013, and despite promises by IBM, no new release had appeared.  That is a span of over 3 years.  Our <span style="text-decoration: underline;"><strong><a href="http://www.docova.com/migrationmethodology/" target="_blank">DOCOVA product</a> </strong></span>was initially based on Domino.  Due to all the uncertainty we now have a version that runs on SQL.</p>
  518. <p>Prior to IBM Connect 2017, the conference that used to be known as Lotusphere, IBM responded with a redefined roadmap for Notes and Domino.  At the conference we got to hear about that in detail.</p>
  519. <p>Let me start with <a href="https://www.ibm.com/blogs/social-business/2017/03/09/ibm-notes-domino-product-update-connect-2017/" target="_blank">Ed Brill&#8217;s recent posting recapping Connect 2017.</a>  In his posting he says that IBM made it &#8220;a priority to emphasize our commitment to IBM Domino as an application and mail platform.&#8221; He said that they have &#8220;announced a number of initiatives to provide clear examples of the value both IBM and our clients place on having a confident direction for the product and its roadmap&#8221;.  These included:</p>
  520. <ul>
  521. <li>Extended Support</li>
  522. <li>Feature Packs</li>
  523. <li>Verse On-Premises</li>
  524. <li>Application Analysis</li>
  525. <li>API&#8217;s</li>
  526. <li>Application Refresh (aka Modernization)</li>
  527. </ul>
  528. <p>Lets look at each of these.  <strong>Extended support</strong> refers to support for Notes and Domino to at least 2021. Notes 9.01 was released in April of 2013, and as it was categorized in their life cycle policy as &#8220;enhanced&#8221; meant that it had a commitment of 5 years of support, with additional support available for a cost over the annual support fee.  That would take it to 2018.  IBM announced in September of 2016 that support has been extended to 2021, with additional support, for a fee, to 2024.  There was nothing new announced at Connect in this regard.</p>
  529. <p>It could be argued that this is perhaps less of a commitment than more. Lets take a look at the math.  If in 2013 IBM was committing to support Notes and Domino ver 9.01 for 5 years, that would mean it was supported up to April of 2018.  If, when that end date was near, they extended it another 5 years the product would be supported into 2023.  By extending the support in September of 2016, they committed to support until at least 2021.  Are they actually committing to a shorter window of time than if they renewed support closer to the end date of the previous period? It depends on how the process typically works.  I tried to find out what was normal in terms of when IBM renewed their support commitment for a product and I could not.  The reason is that it has never really been an issue before. Nobody really paid attention to the date for renewal of support in the past.  This time around was unique and created by the concern in the community about the future of Notes.</p>
  530. <p>Ed then addressed the new<strong> feature packs</strong>, which is a continuous delivery model that he explains is &#8220;more modern&#8221; than the older method of releasing a new version. I still think that IBM is cutting costs when it comes to Notes and Domino, using the spin of &#8220;more modern&#8221; feature packs so they do not have to go to the expense related to the process required to release a new version.  There was a lot of talk at Connect 2017 about IBM Connections version 6.  It seems Connections, a more modern technology, is not using the more modern continuous delivery approach.</p>
  531. <p><strong>Verse on premises</strong> shipped in December of 2016 and was once again highlighted at Connect 2017.  I think the announcement of a new browser based mail offering, coupled with the release of a new Notes client offering (ICAA) that allows customers to access Notes client based applications, suggests that perhaps the future of the Notes client is uncertain. I would not be surprised to see an announcement prior to 2018 that the Notes client will not be available for purchase.  That is just an opinion.  There has been no press released from IBM to support that.</p>
  532. <p>The Rest<strong> API&#8217;s</strong> being available to Notes and Domino is definitely a good thing. Most other platforms have it, and have had it for some time now. This will allow better integration between Notes applications and other systems.  I heard some feedback that there is a feeling XPAGES is not going to see a lot of attention moving forward.  That has a lot of technical folks, especially those who invested a lot of time learning the technology, concerned. It really depends on whose report from Connect 2017 you read.  Some argue XPAGES is alive and well, others do not.</p>
  533. <p>Prior to the event Ed indicated there would be a significant announcement around <strong>modernization</strong> of Notes and Domino based applications.  The big announcement seemed to be &#8220;contact a partner&#8221;.  IBM had Sopho do a demo of their application, and how it could surface Domino data.  He mentioned other product offerings, but not all of the ones available.  Sopho was a bit of a surprise, but in retrospect maybe it should not be considering IBM&#8217;s focus on social.  Sapho is not modernizing applications as much as scraping data and packaging it in a social media stream.  I personally thought IBM had something significant up their sleeve.  Notes and Domino is often classed as legacy, and could have really used a modernization face lift. I am not sure Sopho is going to help much. Here is an article that shares that<a href="https://www.theregister.co.uk/2017/02/23/sapho_domino/" target="_blank"> opinion</a>.</p>
  534. <p>In addition Ed said for Notes and Domino <strong>application analysis</strong> customers with active M&amp;S could obtain a free copy of the tool created by Panagenda. I cannot recall in the past where IBM showcased one partner product over another to such a degree. There are several loyal Notes and Domino vendors with similar offerings in terms of analysis tools, and to encourage one over another in my opinion is an unusual move for IBM.</p>
  535. <p>In my opinion, the debate about Notes and Domino being a priority for IBM is old news.  Anyone who has been involved in the &#8220;Lotus&#8221; community over the years knows what is going on.  The LUGS, formerly known as the Lotus User Groups, are now all sponsored by IBM.  They use these as a forum to market new products and technology to the Notes community. There is a lot of focus on new products, specifically Watson, Cloud and Analytics.  I think IBM will continue to sell these products to the Notes and Domino clients and continue to tell their customers that Notes and Domino are alive an well.</p>
  536. <p>Is Notes going away in the next couple of years?  It would not surprise me in the least to hear the full client has been pulled from sales. Same for Domino Designer.  In my opinion, Domino, the server component, is not likely to disappear anytime soon.</p>
  537. <p>Like most vendors who had a commercial product based on Notes and Domino we have ported it to other technologies.  Based on that experience, and our two decades of experience with Notes and Domino application development,  we have found ourselves in the migration game.  At this time we feel we have the best solution on the market for migrating custom Notes applications to another platform.  Check out our <span style="text-decoration: underline;"><strong><a href="http://www.docova.com/migrationmethodology/" target="_blank">Migration Methodology </a></strong></span>page for more info.</p>
  538. ]]></content:encoded>
  539. </item>
  540. </channel>
  541. </rss>
  542.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//feeds.feedburner.com/DocovaTechincalBlog

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda