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://dominothoughts.com/DomThoughts/domthoughts.nsf/feed.rss

  1. <?xml version="1.0" encoding="iso-8859-1"?>
  2. <rss version="2.0"
  3. xmlns:dc="http://purl.org/dc/elements/1.1/"
  4. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  5. xmlns:admin="http://webns.net/mvcb/"
  6. xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  7. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  8. xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  9. <channel>
  10. <title>Domino Thoughts</title>
  11. <description>Just my rambling thoughts on Domino and life</description>
  12. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/</link>
  13. <language>en-us</language>
  14. <lastBuildDate>Thu, 27 Apr 2017 09:58:56 -0700</lastBuildDate>
  15. <item>
  16. <title>IBM Docs 2.0 CR2 IF1 Available</title>
  17. <pubDate>Thu, 27 Apr 2017 09:58:56 -0700</pubDate>
  18. <description>
  19. <![CDATA[
  20. No sooner after I publish my post about the Security Updates in CR2, do I see that there's CR2 IF1 available now as well. IBM Connections Docs 2.0 CR2 iFix 001 Release Notes This includes support fo ...
  21. ]]>
  22. </description>
  23. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-if1-available.htm</link>
  24. <category></category>
  25. <dc:creator>Ted Hardenburgh</dc:creator>
  26. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-if1-available.htm?opendocument&amp;comments</comments>
  27. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-if1-available.htm</guid>
  28. <content:encoded><![CDATA[ No sooner after I publish my post about the Security Updates in CR2, do I see that there's CR2 IF1 available now as well. <br /> <br /><a href="http://www-01.ibm.com/support/docview.wss?uid=swg22002672">IBM Connections Docs 2.0 CR2 iFix 001 Release Notes</a> <br /> <br />This includes support for TLS v1.2, so if that' important to you - I'm looking at you externally facing servers - then you'll want to check this out. <br /> <br />Enjoy!  ]]></content:encoded>
  29. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-docs-2.0-cr2-if1-available.htm</wfw:commentRss>
  30. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-if1-available.htm?opendocument&amp;comments</wfw:comment>
  31. </item>
  32. <item>
  33. <title>IBM Docs 2.0 - CR2 Includes Fixes For Security Vulnerabilities</title>
  34. <pubDate>Thu, 27 Apr 2017 03:08:34 -0700</pubDate>
  35. <description>
  36. <![CDATA[
  37. If you're looking for another reason to install CR2 for IBM Docs 2.0 beyond "just getting the latest", here's one: this CR includes fixes for three different security vulnerabilities. If you've got a ...
  38. ]]>
  39. </description>
  40. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-includes-fixes-for-security-vulnerabilities.htm</link>
  41. <category>IBM Connections Docs</category>
  42. <dc:creator>Ted Hardenburgh</dc:creator>
  43. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-includes-fixes-for-security-vulnerabilities.htm?opendocument&amp;comments</comments>
  44. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-includes-fixes-for-security-vulnerabilities.htm</guid>
  45. <content:encoded><![CDATA[ If you're looking for another reason to install CR2 for IBM Docs 2.0 beyond "just getting the latest", here's one: this CR includes fixes for three different security vulnerabilities. &nbsp;If you've got an externally facing Connections environment, I would recommend getting the update scheduled sooner rather than later. <br /> <span style="text-decoration:underline"><br /> </span><a href="http://www.ibm.com/support/docview.wss?uid=swg22001687&amp;myns=swglotus&amp;mynp=OCSSFHJY&amp;mync=E&amp;cm_sp=swglotus-_-OCSSFHJY-_-E" target=_blank><strong><span style="text-decoration:underline">Security Bulletin: IBM Connections Docs is Vulnerable to a Denial of Service (CVE-2015-8806)</span></strong></a> <br /> <span style="text-decoration:underline"><br /> </span><a href="http://www.ibm.com/support/docview.wss?uid=swg22001688&amp;myns=swglotus&amp;mynp=OCSSFHJY&amp;mync=E&amp;cm_sp=swglotus-_-OCSSFHJY-_-E" target=_blank><strong><span style="text-decoration:underline">Security Bulletin: IBM Connections Docs is Vulnerable to a Heap-based Buffer Overflow (CVE-2016-2073)</span></strong></a>  <br /> <br /><a href="http://www.ibm.com/support/docview.wss?uid=swg22001685&amp;myns=swglotus&amp;mynp=OCSSFHJY&amp;mync=E&amp;cm_sp=swglotus-_-OCSSFHJY-_-E" target=_blank><strong>Security Bulletin: IBM Connections Docs is Vulnerable to a Stack-based Buffer Overflow (CVE-2016-3705)</strong></a> <br /><br /> <br /> Happy upgrading!   ]]></content:encoded>
  46. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-docs-2.0-cr2-includes-fixes-for-security-vulnerabilities.htm</wfw:commentRss>
  47. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-2.0-cr2-includes-fixes-for-security-vulnerabilities.htm?opendocument&amp;comments</wfw:comment>
  48. </item>
  49. <item>
  50. <title>IBM Traveler 9.0.1.16 - A Note On Upgrading</title>
  51. <pubDate>Fri, 17 Feb 2017 09:34:50 -0700</pubDate>
  52. <description>
  53. <![CDATA[
  54. So IBM Traveler 9.0.1.16 is now available. We've been waiting on it to upgrade our internal server that was on an older version, mostly due to the issue that Detlev posted about in December. That is ...
  55. ]]>
  56. </description>
  57. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-traveler-9.0.1.16-a-note-on-upgrading.htm</link>
  58. <category>IBM Verse</category>
  59. <dc:creator>Ted Hardenburgh</dc:creator>
  60. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-traveler-9.0.1.16-a-note-on-upgrading.htm?opendocument&amp;comments</comments>
  61. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-traveler-9.0.1.16-a-note-on-upgrading.htm</guid>
  62. <content:encoded><![CDATA[ So IBM Traveler 9.0.1.16 is now available. &nbsp;We've been waiting on it to upgrade our internal server that was on an older version, mostly due to the issue that <a href="http://www.netzgoetter.net/internet/blogs/netzgoetter.nsf/dx/hotfix-via-pmr-available-for-traveler-9.0.1.15-standalone-issue.htm">Detlev posted about in December</a>. &nbsp;That is "fixed" in this release, however my experience upgrading revealed that it wasn't so much fixed as the command that you need to issue to resolve the error was enabled for use.  <br /> <br />So, after upgrading Traveler from the .12 release, the server started up and watched as the Traveler db had its design updated and also saw updates to the Derby database used by Traveler getting logged: <br /> <br />02/16/2017 05:19:42 PM Traveler: Server starting... <br />02/16/2017 05:19:56 PM Traveler: GUIDMAP has no records violating the constraint. <br />02/16/2017 05:19:56 PM Traveler: Primary key PK_GUIDMAP successfully created. <br />02/16/2017 05:19:56 PM Traveler: GUIDMAP table is repaired. <br />02/16/2017 05:19:56 PM Traveler: TS_FILTERS has no violating records. <br />02/16/2017 05:19:56 PM Traveler: Primary key PK_TSFILTERS successfully created. <br />02/16/2017 05:19:56 PM Traveler: TS_FILTERS table is repaired. <br />02/16/2017 05:19:56 PM Traveler: PUSH has no violating records. <br />02/16/2017 05:19:56 PM Traveler: Primary key PK_PUSH successfully created. <br />02/16/2017 05:19:56 PM Traveler: PUSH table is repaired. <br />02/16/2017 05:19:56 PM Traveler: REPLICAS has no violating records. <br />02/16/2017 05:19:56 PM Traveler: Primary key PK_REPLICAS successfully created. <br />02/16/2017 05:19:56 PM Traveler: REPLICAS table is repaired. <br /> <br />However, after that was done, I saw the message Detlev wrote about: <br /> <br />02/16/2017 05:20:00 PM Traveler: WARNING *system Exception caught trying to create constraint PK_INVMAP on Table INV_MAP. Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: 'DEVUID' cannot be a column of a primary key because it can contain null values.  <br /> <br />I wasn't expecting this, but figured I could try the command IBM gave out with the Hotfix: <br /> <br />tell traveler sql ALTER TABLE inv_map ALTER COLUMN devuid NOT NULL  <br /> <br />After restarting HTTP, the error did not appear again, so it looks like running this command may be necessary if you are upgrading your standalone Traveler install from an older release. <br /> <br />Of course, as always, YMMV. <br /> <br />I'll be at the IBM Connect conference next week - hope to see some of you there! <br /> <br />  ]]></content:encoded>
  63. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-traveler-9.0.1.16-a-note-on-upgrading.htm</wfw:commentRss>
  64. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-traveler-9.0.1.16-a-note-on-upgrading.htm?opendocument&amp;comments</wfw:comment>
  65. </item>
  66. <item>
  67. <title>IBM Verse On-Premises - some thoughts after using for two weeks</title>
  68. <pubDate>Tue, 17 Jan 2017 12:07:00 -0700</pubDate>
  69. <description>
  70. <![CDATA[
  71. We installed IBM Verse On-Premises (VOP) the day it was released. See my previous post about the installation (simple). This post will cover my impressions after having used it for two weeks as my main access point to my company email. Basic Usage: Overall, I'm pretty pleased with the VOP 1.0 release. Reading and composing emails are easy and straightforward. When new mail arrives, the browser tab adds a red dot to the Verse icon to let me know there's something new. Messages render as expected and give me the option to show images if desired - just like Notes or iNotes do. The options to work with a message are available in the icon bar and are a mix of text button (Reply, Reply All, Forward) or images (Mark Needs Action, Mark read/unread, delete, move to folder, print or schedule a meeting). There's also an indicator of which folder(s) the message is found in. This is very nice. The Mark Read/Unread button was a topic of conversation in that it wasn't immediately apparent from the icon what it's for - and was missed entirely by someone else. The hover text does point it out, but I'm chalking up missing it due to me not paying attention. ...
  72. ]]>
  73. </description>
  74. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm</link>
  75. <category>Verse</category>
  76. <dc:creator>Ted Hardenburgh</dc:creator>
  77. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm?opendocument&amp;comments</comments>
  78. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm</guid>
  79. <content:encoded><![CDATA[ We installed IBM Verse On-Premises (VOP) the day it was released. &nbsp;See my <a href="http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/../../dx/initial-impressions-on-ibm-verse-on-premises-1.0.htm">previous post about the installation</a> (simple). &nbsp;This post will cover my impressions after having used it for two weeks as my main access point to my company email. <strong><br /> <br /> Basic Usage:</strong> <br /> Overall, I'm pretty pleased with the VOP 1.0 release. &nbsp;Reading and composing emails are easy and straightforward. When new mail arrives, the browser tab adds a red dot to the Verse icon to let me know there's something new. Messages render as expected and give me the option to show images if desired - just like Notes or iNotes do. The options to work with a message are available in the icon bar and are a mix of text button (Reply, Reply All, Forward) or images (Mark Needs Action, Mark read/unread, delete, move to folder, print or schedule a meeting). &nbsp;There's also an indicator of which folder(s) the message is found in. This is very nice. &nbsp; The Mark Read/Unread button was a topic of conversation in that it wasn't immediately apparent from the icon what it's for - and was missed entirely by someone else. &nbsp;The hover text does point it out, but I'm chalking up missing it due to me not paying attention. <br /> <br /> <br /> <br /> I can see where the Important People ribbon at the top can be very useful to drill down on the messages from those people I'm the most active with. <br /> <br /> Working with multiple messages collects them in a list in the "content" panel on the right. From there I can work on them and choose the Read/Unread, delete, or move all to folder options. Easy to work with. <br /> <br /> Clicking on a name in the Folder views or message will show a business card for the user. If they are in my Connections environment, the Connections biz card data is displayed, otherwise it's just the person's email address. <br /> <br /> Browser alerts in Chrome, Firefox and Safari are OK - I seem to have some issues with the alerts popping up from time to time. I'm trying to narrow it to a browser issue or something with the app itself. <br /> <br /> The down side is the Connections Files integration. I have it working in iNotes, but Verse uses a different set of API calls from what iNotes uses. Still working on this one. <strong><br /> <br /> Search:</strong> <br /> The search works very well from my experience. You can select your Important People and clicking their icon will show all messages from them no matter which folder they are in. That's the nice bit of displaying the folder location in the message. It gives you an additional context to work with. &nbsp; <br /> <br /> You can additionally refine the result set to a timeline and folders to drill down further. <br /> <img  alt="Image:IBM Verse On-Premises - some thoughts after using for two weeks" border="0" src="http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm/content/M2?OpenElement" /><br /> <br /> If you need to search on a sender that isn't in your Important People collection, you can type their name/address in the search bar and te results are returned the same way. <br /> <br /> Kudos to the team that managed to build this as an OSGi plugin and not requiring and entire SOLR install. HT to Stephan for <a href="http://www.notessensei.com/blog/2016/12/the-totally-inofficial-guide-to-verse-on-premises.html">his post on the backstory of VOP</a><strong> </strong>- just in case someone missed it when it was originally published. That and his other posts around this are interesting reads.<strong><br /> <br /> "GTD" Features:</strong> <br /> One of the important features in VOP is the "GTD" actions it adds - Marking messages as Needing Action or Waiting For. &nbsp;i've been waiting for this since I first noticed it in the Verse Mobile app last year. &nbsp;It allows you to track my own work on whether I have something owed someone or someone owes me something. &nbsp;This is not a way to "assign" work to others like you can in a To Do. &nbsp;Iniitally that's what I was expecting, but I didn't read the documentation until after trying that with a colleague. &nbsp;When you mark an email as Waiting For, it only adds it to a view in your mail. &nbsp;There's nothing that would add the message to the recipient's Needs Action view. &nbsp;Perhaps that is coming in a future release - I think it would be nice to have. <br />  <br /><img  alt="Image:IBM Verse On-Premises - some thoughts after using for two weeks" border="0" src="http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm/content/M3?OpenElement" />&nbsp;<br /> <br /> Aside from that misunderstanding - it works as advertised. &nbsp;I can mark an email I've received as needs action with a reminder for today, tomorrow, anytime or choose a date. You can also add comments/notes. For Sent message, I can mark them as Waiting For with the same options. &nbsp;Once marked, the messages show up in the appropriate view and the icon in the display changes. <strong><br /> <br /> Calendar:</strong> <br /> At the bottom of the page is the Calendar Bar. It provides a timeline of the day that shows me what and when I've got on my calendar for the day. It's very nice. &nbsp;I can click on an item and it will give me the name and time of the meeting. &nbsp;I can click on the link and get the meeting details. The details are displayed in a Verse designed page. I can also click a button to create a new meetings in a Verse designed form. Those are all nice and work for me. &nbsp;I can also pull up a separate calendar page by clicking on the Calendar button that shows Day/Week/Month views. <br /> <br /> However, if I click the Calendar option in the navigation bar at the top, it opens up the iNotes calendar. &nbsp;Since IBM appear to have designed a Verse Calendar view, I'm not sure why that isn't what I'm directed to. &nbsp;Hopefully this gets fixed soon as it doesn't give a consistent user experience. The People link is the same, it opens iNotes, though I haven't found a Verse version of Contacts yet. &nbsp; <strong><br /> <br /> Connections integration:</strong><br /> The integration with Verse and Connections is, at first, simple to enable based on the documentation. The biz card and user photos are a nice integration point and work as designed. As I mentioned, the Files integration is not working completely. It appears to be with the OPTIONS method and not getting the response it should. &nbsp;I'm working on that and will post more once I figure that out.<strong><br /> <br /> Things I'd Like to See:</strong> <br /> I think I've seen others mention some of these, but here's my list:  <ul> <li>Complete the Calendar (and Contacts) move to Verse UI  </li><li>Add workflow to the Needs Action/Waiting For  </li><li>Documentation on custominzing UI. Would be nice to be able to have Connections customizations in the Verse UI  </li><li>Ability to add more links to the "Apps" drop-down (part of customization)  </li><li>Development API. I know there's something for the Verse cloud, but on-premises would be great  </li><li>Calendar overlay/aggregation (e.g. Google calendar and other iCal feeds) - would be great to have that data show in the calendar bar!  </li><li>Watson integration as an option</li></ul><br /> Overall, I'm impressed with the 1.0 release and look forward to watching Verse grow and improve. <br /> <br /> As I'm drafting this article, I saw <a href=https://youtu.be/LBgJFugihhc><span style="text-decoration:underline">Alan Lepofsky's interview with Ed Brill </span></a>and it looks like some of my requests are in the pipeline.   ]]></content:encoded>
  80. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm</wfw:commentRss>
  81. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-verse-on-premises-some-thoughts-after-using-for-two-weeks.htm?opendocument&amp;comments</wfw:comment>
  82. </item>
  83. <item>
  84. <title>IBM Docs - Technote on Understanding the Save, Publish and Copy options</title>
  85. <pubDate>Fri, 13 Jan 2017 10:29:55 -0700</pubDate>
  86. <description>
  87. <![CDATA[
  88. This came across my feed this morning and I think it's a useful piece of information to share with users of IBM Docs. They often ask the difference between the save, auto-save, publish, auto-publish ...
  89. ]]>
  90. </description>
  91. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-technote-on-understanding-the-save-publish-and-copy-options.htm</link>
  92. <category>ibm connections</category>
  93. <dc:creator>Ted Hardenburgh</dc:creator>
  94. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-technote-on-understanding-the-save-publish-and-copy-options.htm?opendocument&amp;comments</comments>
  95. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-technote-on-understanding-the-save-publish-and-copy-options.htm</guid>
  96. <content:encoded><![CDATA[ This came across my feed this morning and I think it's a useful piece of information to share with users of IBM Docs. &nbsp;They often ask the difference between the save, auto-save, publish, auto-publish and the copy options when working on documents. &nbsp;This technote from IBM gives a fairly succinct explanation of what the differences are. <br /> <span style="text-decoration:underline"><br /> </span><a href="http://www-01.ibm.com/support/docview.wss?uid=swg21997113"><span style="text-decoration:underline">Understanding Save, Auto-save, Publish, Auto-publish, and Copy</span></a> <br />   ]]></content:encoded>
  97. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-docs-technote-on-understanding-the-save-publish-and-copy-options.htm</wfw:commentRss>
  98. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-technote-on-understanding-the-save-publish-and-copy-options.htm?opendocument&amp;comments</wfw:comment>
  99. </item>
  100. <item>
  101. <title>IBM Connections Files Integration with iNotes</title>
  102. <pubDate>Fri, 6 Jan 2017 08:39:43 -0700</pubDate>
  103. <description>
  104. <![CDATA[
  105. Now that Verse On-Premises 1.0 is out, I was taking a look at the integration with Connections Files. I've run into an issue with that that I'm still looking at, but as part of the diagnosis, I went ...
  106. ]]>
  107. </description>
  108. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-files-integration-with-inotes.htm</link>
  109. <category>Domino</category>
  110. <dc:creator>Ted Hardenburgh</dc:creator>
  111. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-files-integration-with-inotes.htm?opendocument&amp;comments</comments>
  112. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-files-integration-with-inotes.htm</guid>
  113. <content:encoded><![CDATA[ Now that Verse On-Premises 1.0 is out, I was taking a look at the integration with Connections Files. &nbsp;I've run into an issue with that that I'm still looking at, but as part of the diagnosis, I went back to look at the Connections Files integration with iNotes to try and get some better logging. &nbsp;During that inspection, I came across a different issue after we've upgraded our Connections instance to 5.5 and narrowed the TLS settings. <br /> <br /> The issue in iNotes was that the client was failing wth a SSL handshake error in the iNotes console (nice to have that in iNotes). &nbsp;Further review in the IHS log on the Connections side indicated a cipher mismatch. <br /> <br /> First off, on the Domino side I enabled SSL_DEBUG_ALL=1 to get more information and the interesting thing is that Domino as the client was attempting to connect using the ECDHE_RSA_WITH_AES_256_GCM_SHA384 cipher. On Domino this is the <a href="https://www-10.lotus.com/ldd/dominowiki.nsf/dx/TLS_Cipher_Configuration"><span style="text-decoration:underline">top cipher used when TLS 1.2 is enabled</span></a>. &nbsp;However, this cipher isn't enabled by default in IHS <a href=https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.ihs.doc/ihs/rihs_ciphspec.html><span style="text-decoration:underline">according to the docs</span></a>, so I updated the httpd.conf to add the additional ciphers for TLS 1.2 and all TLS versions. <br /> <br /> # SSL Cipher settings <br /> SSLCipherSpec ALL NONE <br /> SSLCipherSpec TLSv12 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 <br /> SSLCipherSpec TLSv12 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 <br /> SSLCipherSpec TLSv12 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 <br /> SSLCipherSpec TLSv12 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 <br /> SSLCipherSpec ALL TLS_RSA_WITH_AES_128_GCM_SHA256 <br /> SSLCipherSpec ALL TLS_RSA_WITH_AES_256_GCM_SHA384 <br /> SSLCipherSpec ALL TLS_RSA_WITH_AES_128_CBC_SHA256 <br /> SSLCipherSpec ALL TLS_RSA_WITH_AES_256_CBC_SHA256 <br /> <br /> After making that change and restarting HTTP, I still saw the handshake errors. &nbsp;Going back into the httpd.conf, I changed the settings from only supporting TLSv12 to all TLS versions: <br /> <br /> SSLProtocolEnable TLS <br /> SSLProtocolDisable SSLv3 SSLv2 <br /> <br /> Saving and restarting HTTP, this got Connections Files with iNotes working. &nbsp; <br /> <br /> Unfortunately, that didn't get the Connections Files with VOP working, so I'm back to looking at that. &nbsp;More to come... <br />   ]]></content:encoded>
  114. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-connections-files-integration-with-inotes.htm</wfw:commentRss>
  115. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-files-integration-with-inotes.htm?opendocument&amp;comments</wfw:comment>
  116. </item>
  117. <item>
  118. <title>Initial impressions on IBM Verse On-Premises 1.0</title>
  119. <pubDate>Fri, 30 Dec 2016 14:23:44 -0700</pubDate>
  120. <description>
  121. <![CDATA[
  122. NOTE: This is a "first impression" post after working with VOP for a few hours. I didn't participate in the betas, so this is a fresh experience. So, as has been announced on the interwebs today, ...
  123. ]]>
  124. </description>
  125. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/initial-impressions-on-ibm-verse-on-premises-1.0.htm</link>
  126. <category>Domino</category>
  127. <dc:creator>Ted Hardenburgh</dc:creator>
  128. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/initial-impressions-on-ibm-verse-on-premises-1.0.htm?opendocument&amp;comments</comments>
  129. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/initial-impressions-on-ibm-verse-on-premises-1.0.htm</guid>
  130. <content:encoded><![CDATA[ NOTE: &nbsp;This is a "first impression" post after working with VOP for a few hours. &nbsp;I didn't participate in the betas, so this is a fresh experience. <br /> <br /> So, as has been announced on the interwebs today, IBM Verse On-Premises 1.0 (VOP) was made available for download today. &nbsp;Part number: CNDG8ML &nbsp; <br /> <br /> We had some time today, so Chris Whisonant and I installed it and setup the integration with Connections. &nbsp;So Chris did the Domino side and I handled the Connections side. &nbsp;Here are my brief comments on my couple of hours in. <br /> <br /> INSTALL: &nbsp;Went very smoothly on Windows, no issues. &nbsp;Install the Hotfix that enables Verse, copy some JARs to the OSGI folder, set some notes.ini parameters, update the redirect db design, mail design and that's it. One note is that while the documentation only advises to make sure mail files are indexed, it looks like if you already have an indexed file, you'll want to rebuild the indexes. &nbsp;We ran into that on my mail file on the server. &nbsp;The server will initiate a rebuild, but it looks like it may cause some errors in the Inbox until the index is re-done. &nbsp;At least that was my experience. <br /> <br /> Also, there is one URL https://server.domain.com/verse for all users. &nbsp;So if you want to make verse the default, you'll want to update your server configuration. <br /> <br /> INTERFACE: &nbsp;If you've seen any slidedeck from this year, you'll know what to expect for the most part. &nbsp;It's an interface that you'll recognize. When you login, you'll be prompted to allow browse notifications in Chrome, Safari and Firefox. <br /> <br /> You get links to Mail, Calendar, People and Apps (links to iNotes, Notebook and ToDo). &nbsp;Interesting note - Calendar takes you to the iNotes calendar, so it has not been "versefied" yet. &nbsp; <br /> <br /> The next "row" is icons for Inbox/Unread, Needs Action, Waiting For and then your Important People. &nbsp;The Needs Action and Waiting for look to have lots of potential, I'll be playing around with that more. &nbsp;Our initial test of trying to send an action to another didn't result in the message getting flagged in the recipient's mail. We'll look at this further. <br /> <br /> SEARCH: &nbsp;The "big" thing is the faceted search. &nbsp;So far - working great. &nbsp;You can drill down based on important people or perform a search and then you can refine the search based on time or folders. It is really nice - a big reason to check it out. <br /> <br /> CALENDAR BAR: At the bottom is the calendar bar that shows your day in "blocks" where you have something scheduled and click on the block and get the details. &nbsp;I like it, you can scroll through the day or from day to day. We'll see how much "use" I'll get out of it, but I like it so far. <br /> <br /> CONNECTIONS INTEGRATION: &nbsp;Integration was easy and simple to setup. Nothing installed on the Connections side, just some changes to the httpd.conf on the HTTP Server and a notes.ini change on the servers. Integration gives you photos and business card data. &nbsp;Nicely done. If you have iNotes files integration, it will be available when composing a message as well. <br /> <br /> So - in summary, for a 1.0 release it's looking pretty good. &nbsp;Deeper testing will be done as I use the browser to access my mail primarily. <br /> <br /> UPDATE: &nbsp;Here's the link to the <a href=https://www.ibm.com/support/knowledgecenter/SS4RQV_1.0.0/welcome/vop_welcome.html><span style="text-decoration:underline">VOP Knowledge Center</span></a> - it has the details on confguring VOP and integrating with Connections and Box.<br /> <br /> Happy New Year everyone!   ]]></content:encoded>
  131. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/initial-impressions-on-ibm-verse-on-premises-1.0.htm</wfw:commentRss>
  132. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/initial-impressions-on-ibm-verse-on-premises-1.0.htm?opendocument&amp;comments</wfw:comment>
  133. </item>
  134. <item>
  135. <title>IBM Connections 5.5 - Errors in SystemOut.log cleaning up HOMEPAGE database</title>
  136. <pubDate>Thu, 22 Dec 2016 07:30:00 -0700</pubDate>
  137. <description>
  138. <![CDATA[
  139. Working with a client on IBM Connections 5.5 CR1, they were noticing errors in the SystemOut.log of the InfraCluster around 11pm regularly. Lately, the errors were filling up 1GB of logs for a minute ...
  140. ]]>
  141. </description>
  142. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-errors-in-systemout.log-cleaning-up-homepage-database.htm</link>
  143. <category>connections</category>
  144. <dc:creator>Ted Hardenburgh</dc:creator>
  145. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-errors-in-systemout.log-cleaning-up-homepage-database.htm?opendocument&amp;comments</comments>
  146. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-errors-in-systemout.log-cleaning-up-homepage-database.htm</guid>
  147. <content:encoded><![CDATA[ Working with a client on IBM Connections 5.5 CR1, they were noticing errors in the SystemOut.log of the InfraCluster around 11pm regularly. &nbsp;Lately, the errors were filling up 1GB of logs for a minute when it occurred. <br /> <br /> The "critical" piece of information was the line below: <tt><br /> Error for batch element #1: A parent row cannot be deleted Page 10 of 67 because the relationship "HOMEPAGE.NR_READ_STATUS.FK_READ_STATUS_STR" restricts the deletion.. SQLCODE=-532, SQLSTATE=23504, DRIVER=4.19.49</tt> <br /> <br /> We looked through the logs to find which entry it was, but couldn't find anything specific in the logs or the DB2DIAG log. It looked like it was trying to delete newsletter stories, but that's as close as we could get. <br /> <br /> A PMR was opened with IBM and after reviewing the logs, we were told it was a known issue and there was a fix planned for CR3, but one is available for CR1 now. I'm guessing that a version for CR2 is available as well. <br /> <br /> If that error is popping up in your logs, open a PMR and request the fix LO90678. <br /> <br /> As I was searching on the fix, I happened across a <a href="https://www-304.ibm.com/support/entdocview.wss?uid=swg1LO90678"><span style="text-decoration:underline">link to a IBM technote</span></a> (login required for this one) regarding this entry. Not much info beyond that this appears to be an issue in 5.5 and later CRs, but has the full stack of the error if you're interested.   ]]></content:encoded>
  148. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-connections-5.5-errors-in-systemout.log-cleaning-up-homepage-database.htm</wfw:commentRss>
  149. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-errors-in-systemout.log-cleaning-up-homepage-database.htm?opendocument&amp;comments</wfw:comment>
  150. </item>
  151. <item>
  152. <title>IBM Connections Mail - destined for end of support</title>
  153. <pubDate>Mon, 21 Nov 2016 09:56:38 -0700</pubDate>
  154. <description>
  155. <![CDATA[
  156. Over the weekend, I noticed a blog entry in my feed reader from the IBM Collaboration Solutions Support blog - End of Support Plans for the Connections Mail Plug-in - which starts of detailing that t ...
  157. ]]>
  158. </description>
  159. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-mail-destined-for-end-of-support.htm</link>
  160. <category>connections</category>
  161. <dc:creator>Ted Hardenburgh</dc:creator>
  162. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-mail-destined-for-end-of-support.htm?opendocument&amp;comments</comments>
  163. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-mail-destined-for-end-of-support.htm</guid>
  164. <content:encoded><![CDATA[ Over the weekend, I noticed a blog entry in my feed reader from the IBM Collaboration Solutions Support blog - &nbsp;<a href="https://www.ibm.com/developerworks/community/blogs/LotusSupport/entry/End_of_Support_Plans_for_Connections_Mail_Plug_in?lang=en">End of Support Plans for the Connections Mail Plug-in</a> - which starts of detailing that the IC Mail plugin for Connections 4.0 and 4.5 entered end of support this month. It also indicated EOS dates for the plugins for 5.0 <br /> <br />The interesting/disturbing piece is related to future plans for IC Mail and Connections. &nbsp;The statement is that there are no plans for a version of the Mail plugin to work with Connections 6.0. &nbsp;And there is no mention of what a replacement might be. <br /> <br />Most of our clients that use Connections use the Mail plugin as well, so this would be a significant loss of functionality if there is actually nothing to replace the plugin. &nbsp;Is it going to be part of the main suite now? Will Verse (cloud and on-prem) replace it? &nbsp;Who knows, but apparently IBM is happy to let speculation play out until it makes a complete announcement.  <br /> <br />Once again - we need IBM to fully explain what's going on. &nbsp; <br /> <br />  ]]></content:encoded>
  165. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-connections-mail-destined-for-end-of-support.htm</wfw:commentRss>
  166. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-mail-destined-for-end-of-support.htm?opendocument&amp;comments</wfw:comment>
  167. </item>
  168. <item>
  169. <title>File Downloads from Connections using SPNEGO</title>
  170. <pubDate>Thu, 3 Nov 2016 10:48:47 -0700</pubDate>
  171. <description>
  172. <![CDATA[
  173. With IBM Connections, there are options to utilize different SSO options. One of the eaiser is using Windows Integrated Authentication, better known as SPNEGO. This uses the AD domain and the user's W ...
  174. ]]>
  175. </description>
  176. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/file-downloads-from-connections-using-spnego.htm</link>
  177. <category>ibm connections</category>
  178. <dc:creator>Ted Hardenburgh</dc:creator>
  179. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/file-downloads-from-connections-using-spnego.htm?opendocument&amp;comments</comments>
  180. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/file-downloads-from-connections-using-spnego.htm</guid>
  181. <content:encoded><![CDATA[ With IBM Connections, there are options to utilize different SSO options. One of the eaiser is using Windows Integrated Authentication, better known as SPNEGO. This uses the AD domain and the user's Windows credentials to issue a ticket that can be used to authenticate users against other resources, such as an IBM Connections site. <br /> <br /> In some cases, this doesn't work like it should. &nbsp;One example is if the user gets an email with a link to download a file stored in Connections, but hasn't yet authenticated with the site. &nbsp;By default, the Files download isn't configured to support this, it relies on getting the LTPA token after authentication to serve requests. &nbsp;The user gets a login page (or just the basic auth pop-up) before getting to the download page. For users that are used to never "logging in" to Connections, this can cause some anxiety and unnecessary Service Desk calls. <br /> <br /> Here's what you can change in IBM Connections 5.5 to get File downloads to "work" as expected. &nbsp;You'll need to remove the spaces between the < symbol and the following character for the XML to work. That's just so its readable here.<br /> <br /> 1 - Backup the web.xml from the <WASRoot>\profiles\dmgr01\config\cells\<cellname>\applications\Files.ear\deployments\Files\files.web.war\WEB-INF folder <br /> 2 - Locate the <security-contraints> nodes in the web.xml file and add the following: <br /> <pre> <br /> <code> <br /> < security-constraint><br /> < display-name>Forms< /display-name> <br /> < web-resource-collection> <br /> < web-resource-name>Form< /web-resource-name> <br /> < url-pattern>/form/*< /url-pattern> <br /> < http-method>GET< /http-method> <br /> < http-method>PUT< /http-method> <br /> < http-method>POST< /http-method> <br /> < http-method>DELETE< /http-method> <br /> < /web-resource-collection> <br /> < auth-constraint> <br /> < description>Form< /description> <br /> < role-name>reader< /role-name> <br /> < /auth-constraint> <br /> < /security-constraint> <br /> </code> <br /> </pre><br /> <br /> 3 - Perform a full resynch of all nodes <br /> 4 - Restart all clusters <br /> <br /> Also check the SPNEGO config to make sure the &nbsp;url /form/anonymous/* isn&#8217;t included in the filter criteria. If it&#8217;s there, remove it, save the change and resent the nodes. SPNEGO config should be dynamic, so a restart won&#8217;t be needed. <br /> <br /> We opened a PMR for this and we're waiting to hear if IBM is going to make this change permanent in a future release .   ]]></content:encoded>
  182. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/file-downloads-from-connections-using-spnego.htm</wfw:commentRss>
  183. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/file-downloads-from-connections-using-spnego.htm?opendocument&amp;comments</wfw:comment>
  184. </item>
  185. <item>
  186. <title>Startup Beans and adding additional nodes in Connections</title>
  187. <pubDate>Tue, 5 Jul 2016 11:34:22 -0700</pubDate>
  188. <description>
  189. <![CDATA[
  190. Last week, working with a customer that had setup a two-node install of Connections 5.5. Getting ready to go live and we noticed an issue in the SystemOut log of the InfraCluster when the server would ...
  191. ]]>
  192. </description>
  193. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/startup-beans-and-adding-additional-nodes-in-connections.htm</link>
  194. <category>Connections</category>
  195. <dc:creator>Ted Hardenburgh</dc:creator>
  196. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/startup-beans-and-adding-additional-nodes-in-connections.htm?opendocument&amp;comments</comments>
  197. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/startup-beans-and-adding-additional-nodes-in-connections.htm</guid>
  198. <content:encoded><![CDATA[ Last week, working with a customer that had setup a two-node install of Connections 5.5. Getting ready to go live and we noticed an issue in the SystemOut log of the InfraCluster when the server would start or when the search index task would run. <br /> <br />CLFRW0454E: Unable to get indexing information about the current server, the index will not be built for this server. <br /> <br />We had followed the instructions for adding the new node, and couldn't determine why we were seeing this issue. Opened a PMR and we got back, after the initial MustGather request, some information to try. Basically, the internal technote indicated that the Startup Beans Service wasn't enabled in the newly added App Server. &nbsp;Going to the app server's Container Settings > Container Services > Startup Beans service page and enabling that option followed by a sync and restart solved the issue. <br /> <br /> ]]></content:encoded>
  199. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/startup-beans-and-adding-additional-nodes-in-connections.htm</wfw:commentRss>
  200. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/startup-beans-and-adding-additional-nodes-in-connections.htm?opendocument&amp;comments</wfw:comment>
  201. </item>
  202. <item>
  203. <title>IBM Connections 5.5 CR1 and Connections Mail - issue with calendar picker</title>
  204. <pubDate>Mon, 20 Jun 2016 15:44:31 -0700</pubDate>
  205. <description>
  206. <![CDATA[
  207. After updating a test server with Connections 5.5 CR1, a customer noticed that the calendar picker in Activities would stay open after selecting a Due Date for an activity. This didn't happen in 5.5 o ...
  208. ]]>
  209. </description>
  210. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-cr1-and-connections-mail-issue-with-calendar-picker.htm</link>
  211. <category>Connections</category>
  212. <dc:creator>Ted Hardenburgh</dc:creator>
  213. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-cr1-and-connections-mail-issue-with-calendar-picker.htm?opendocument&amp;comments</comments>
  214. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-cr1-and-connections-mail-issue-with-calendar-picker.htm</guid>
  215. <content:encoded><![CDATA[ After updating a test server with Connections 5.5 CR1, a customer noticed that the calendar picker in Activities would stay open after selecting a Due Date for an activity. This didn't happen in 5.5 or earlier versions. We opened a PMR with IBM and after some back and forth, according to IBM the issue is related to Connections Mail being enabled on the server. &nbsp;If you don't have Connections Mail enabled, there's no issue. <br /> <br /> A fix is in the works. &nbsp;I'm hoping that it will be an update available from FIx Central and not just a fix, but we'll see.  <br /> <br />UPDATE July 1: My client received a fix and installed it and it has resolved the issue. LO89462 is the APAR number, so open a PMR with that info if you need the fix.<br />   ]]></content:encoded>
  216. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-connections-5.5-cr1-and-connections-mail-issue-with-calendar-picker.htm</wfw:commentRss>
  217. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-5.5-cr1-and-connections-mail-issue-with-calendar-picker.htm?opendocument&amp;comments</wfw:comment>
  218. </item>
  219. <item>
  220. <title>IBM Cnx 5.5 CR1 and WAS 8.5.5.8 update - something to remember</title>
  221. <pubDate>Fri, 10 Jun 2016 15:01:37 -0700</pubDate>
  222. <description>
  223. <![CDATA[
  224. I was updating a Connections 5.5 environment to CR1 today and part of the process is updating WebSphere to 8.5.5.8. The installs all went very smoothly untill we went to verify the updates by launchi ...
  225. ]]>
  226. </description>
  227. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-cnx-5.5-cr1-and-was-8.5.5.8-update-something-to-remember.htm</link>
  228. <category>Connections</category>
  229. <dc:creator>Ted Hardenburgh</dc:creator>
  230. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-cnx-5.5-cr1-and-was-8.5.5.8-update-something-to-remember.htm?opendocument&amp;comments</comments>
  231. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-cnx-5.5-cr1-and-was-8.5.5.8-update-something-to-remember.htm</guid>
  232. <content:encoded><![CDATA[ I was updating a Connections 5.5 environment to CR1 today and part of the process is updating WebSphere to 8.5.5.8. &nbsp;The installs all went very smoothly untill we went to verify the updates by launching the site. &nbsp;We saw the always generic "We are unable to process your request" message hitting the homepage. &nbsp;Off to the SystemOut.log! <br /> <br /> Looking at the logs, I saw a series of SSL Handshake errors and then it hit me - the Java policy files to handle the large SSL key size must have been overwritten. &nbsp;I need to remember that they will be overwritten during an update like this. <br /> <br /> Checking the <WAS_install_location>\java\jre\lib\security folder verified that the files had been replaced. &nbsp;Once we replaced them with the correct version and restarted WebSphere we were able to login successfully. <br /> <br /> Now to finish the testing! <br /> <br /> UPDATE: Rainer asked where the updated policy files were downloaded from. &nbsp;I used this <a href="https://www-01.ibm.com/marketing/iwm/iwm/web/reg/pick.do?source=jcesdk&amp;lang=en_US"><span style="text-decoration:underline">IBM link</span></a> to download them (login required) and chose the first option that included the j9 VM2.6 version. &nbsp;Use the "java -version" command in the WAS Java folder to confirm that the JVM matches the versions listed there.   ]]></content:encoded>
  233. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-cnx-5.5-cr1-and-was-8.5.5.8-update-something-to-remember.htm</wfw:commentRss>
  234. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-cnx-5.5-cr1-and-was-8.5.5.8-update-something-to-remember.htm?opendocument&amp;comments</wfw:comment>
  235. </item>
  236. <item>
  237. <title>IBM Docs - Mapping CIFS drives</title>
  238. <pubDate>Fri, 3 Jun 2016 09:22:52 -0700</pubDate>
  239. <description>
  240. <![CDATA[
  241. Working on a Docs 2.0 install and came across some strange issues when setting up the servers to map drives to the Windows file share. On some servers, the drives mapped as expected, while others did ...
  242. ]]>
  243. </description>
  244. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-mapping-cifs-drives.htm</link>
  245. <category>Connections</category>
  246. <dc:creator>Ted Hardenburgh</dc:creator>
  247. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-mapping-cifs-drives.htm?opendocument&amp;comments</comments>
  248. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-mapping-cifs-drives.htm</guid>
  249. <content:encoded><![CDATA[  Working on a Docs 2.0 install and came across some strange issues when setting up the servers to map drives to the Windows file share. On some servers, the drives mapped as expected, while others didn't. &nbsp;No errors were logged in the Windows Event Viewer. <br /> <br /> For reference, the documentation from IBM we followed is <a href=http://www.ibm.com/support/knowledgecenter/SSFHJY_2.0.0/deploy/mount_cifs_share_on_windows.html><span style="text-decoration:underline">here</span></a>. <br /> <br /> To determine what was going on, I edited the cifsmount.bat to include some "logging" output to see if anything was happening we couldn't see when the task ran. &nbsp;Oddly enough, I found messages like this: <br /> <br /> <blockquote>X: has a remembered connection to \\fileserver\CnxData. Do you want to overwrite the remembered connection? (Y/N) &#91;Y}: </blockquote> <br /> <br /> So, WIndows was trying to do what we asked, it just had a mapping in its memory and needed a response. <br /> <br /> To fix this I altered the cifsmount.bat file to 1- delete any mappings for the drives I'm using, and 2 - added a "/y" to the net use line so that it would default to Yes for any prompts. <br /> <br /> <blockquote> net use /y X: \\fileserver\DocsData >>d:\logs\mountX.log</blockquote> <br /> <br /> I kept the logging in so we can check if there are issues in the future. <br /> <br /> Hope this helps someone else.   ]]></content:encoded>
  250. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-docs-mapping-cifs-drives.htm</wfw:commentRss>
  251. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-docs-mapping-cifs-drives.htm?opendocument&amp;comments</wfw:comment>
  252. </item>
  253. <item>
  254. <title>Known Issues after upgrading to Verse 9.4 for Android and Something That Worked For Me</title>
  255. <pubDate>Wed, 25 May 2016 21:02:34 -0700</pubDate>
  256. <description>
  257. <![CDATA[
  258. This evening the following technote was published by IBM: Overview of known issues affecting users after upgrading to Verse 9.4 for Android After I upgraded I was having issues syncing. One thing ...
  259. ]]>
  260. </description>
  261. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/known-issues-with-verse-for-android-9.4-and-something-that-worked-for-me.htm</link>
  262. <category>Domino</category>
  263. <dc:creator>Ted Hardenburgh</dc:creator>
  264. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/known-issues-with-verse-for-android-9.4-and-something-that-worked-for-me.htm?opendocument&amp;comments</comments>
  265. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/known-issues-with-verse-for-android-9.4-and-something-that-worked-for-me.htm</guid>
  266. <content:encoded><![CDATA[ This evening the following technote was published by IBM: <span style="text-decoration:underline"><br /> <br /> </span><a href="http://www.ibm.com/support/docview.wss?uid=swg21984118&amp;myns=swglotus&amp;mynp=OCSSMTU9&amp;mynp=OCSSYRPW&amp;mync=E&amp;cm_sp=swglotus-_-OCSSMTU9-OCSSYRPW-_-E" target=_blank><span style="text-decoration:underline">Overview of known issues affecting users after upgrading to Verse 9.4 for Android</span></a> <br /> <br /> After I upgraded I was having issues syncing. One thing I noticed was that if I went into the main Verse app the prompt to force a new sync would appear, but the sync never finished. Each time I opened the Verse app, I saw the same prompt. <br /> <br /> This morning I finally thought about deleting the local data and trying again. After doing this, I was prompted to login to my Traveler server and it performed a full sync and I've been working as expected since. <br /> <br /> Hope this helps and sorry for the very long, IBM-like title.   ]]></content:encoded>
  267. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/known-issues-with-verse-for-android-9.4-and-something-that-worked-for-me.htm</wfw:commentRss>
  268. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/known-issues-with-verse-for-android-9.4-and-something-that-worked-for-me.htm?opendocument&amp;comments</wfw:comment>
  269. </item>
  270. <item>
  271. <title>DB2 HADR configuration reminder</title>
  272. <pubDate>Wed, 25 May 2016 10:55:43 -0700</pubDate>
  273. <description>
  274. <![CDATA[
  275. This one is a reminder for me more than anything: When setting up DB2 HADR, for IBM Connections, IBM Sametime, or anything, don't forget to make sure you've set the logging for the database before t ...
  276. ]]>
  277. </description>
  278. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/db2-hadr-configuration-reminder.htm</link>
  279. <category>Connections</category>
  280. <dc:creator>Ted Hardenburgh</dc:creator>
  281. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/db2-hadr-configuration-reminder.htm?opendocument&amp;comments</comments>
  282. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/db2-hadr-configuration-reminder.htm</guid>
  283. <content:encoded><![CDATA[ This one is a reminder for me more than anything: <br /> <br /> When setting up DB2 HADR, for IBM Connections, IBM Sametime, or anything, don't forget to make sure you've set the logging for the database before trying to configure the standby database. <br /> <br /> It's easy to do when you're working with the number of databases that Connections involves and that's what happened here. We somehow skipped over one of them, even though we were using the DB2 directory as a guide. We were trying to start the database as a standby - one of the final steps - and got the SQL1767N error, reason code=1. &nbsp;This indicates that the database wasn't in a roll-forward pending state which is what we want for setting up the standby. <br /> <br /> After looking around I decided to check the log folder on the primary server and found that there weren't any folders for this database in the archive log folder. &nbsp;So this meant that since the database wasn't configured for logging, it wouldn't be in the state we wanted after a restore. <br /> <br /> This was a quick fix of just running the commands we needed to setup the database for logging on the primary side and then taking a new offline backup and restore it on the standby server and run the commands. &nbsp;Lo and behold - it did what we expected - started as the HADR standby. <br /> <br /> I should probably work on scripting this out to avoid this in the future.<br /> <br /> Hope this helps someone else!   ]]></content:encoded>
  284. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/db2-hadr-configuration-reminder.htm</wfw:commentRss>
  285. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/db2-hadr-configuration-reminder.htm?opendocument&amp;comments</wfw:comment>
  286. </item>
  287. <item>
  288. <title>IBM Connections dbWizard issue - it&#8217;s all about the bits</title>
  289. <pubDate>Tue, 12 Jan 2016 07:58:48 -0700</pubDate>
  290. <description>
  291. <![CDATA[
  292. Started a Connections 5.5 deployment for a customer last week. Things are going well, but when we got to the database Wizard, the wizard wan't cooperating. We couldn't choose the DB2 instance - which ...
  293. ]]>
  294. </description>
  295. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-dbwizard-issue-its-all-about-the-bits.htm</link>
  296. <category>Connections</category>
  297. <dc:creator>Ted Hardenburgh</dc:creator>
  298. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-dbwizard-issue-its-all-about-the-bits.htm?opendocument&amp;comments</comments>
  299. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-dbwizard-issue-its-all-about-the-bits.htm</guid>
  300. <content:encoded><![CDATA[ Started a Connections 5.5 deployment for a customer last week. Things are going well, but when we got to the database Wizard, the wizard wan't cooperating. We couldn't choose the DB2 instance - which normally auto-populated anyway. We basically could bounce back between the Create/Update/Delete menu and the Database type and couldn't move forward. <br /> <br />We were able to create databases manually, but with other deployments coming up we wanted to make sure it was working. <br /> <br />After looking around the systems, I noticed some memory errors and discovered that the 32-bit version of DB2 was installed. Upgrading the version to 64-bit version resolved the dbWizard issue. <br /> <br />Just to be safe - and since we had only populated some test users - we dropped the original databases and created a new set using the Wizard. &nbsp; <br /> <br />Moving on!  ]]></content:encoded>
  301. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/ibm-connections-dbwizard-issue-its-all-about-the-bits.htm</wfw:commentRss>
  302. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/ibm-connections-dbwizard-issue-its-all-about-the-bits.htm?opendocument&amp;comments</wfw:comment>
  303. </item>
  304. <item>
  305. <title>Notes 9.0.1 FP3 IF1 - Updated Support for Google Calendar</title>
  306. <pubDate>Tue, 17 Feb 2015 08:57:07 -0700</pubDate>
  307. <description>
  308. <![CDATA[
  309. Recently, the focus of the Domino community has been on the Interim Fixes and Fix Packs for the Domino server around the POODLE issues. Yesterday I noticed a TechNote about an Interim Fix and reading ...
  310. ]]>
  311. </description>
  312. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/notes-9.0.1-fp3-if1-updated-support-for-google-calendar.htm</link>
  313. <category>Lotus Notes</category>
  314. <dc:creator>Ted Hardenburgh</dc:creator>
  315. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/notes-9.0.1-fp3-if1-updated-support-for-google-calendar.htm?opendocument&amp;comments</comments>
  316. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/notes-9.0.1-fp3-if1-updated-support-for-google-calendar.htm</guid>
  317. <content:encoded><![CDATA[ <br>Recently, the focus of the Domino community has been on the Interim Fixes and Fix Packs for the Domino server around the POODLE issues. &nbsp;Yesterday I noticed a TechNote about an Interim Fix and reading through the Fix List for it, I can upon a fix for an issue we had noticed previously with a client. &nbsp;That is that the federated calendar with Google was throwing an error. &nbsp;The error was pretty generic, but it was something with authentication. <br /> <br /> The Fix List yesterday referenced that they were updating the version of the Google Calendar API. &nbsp;It appears that the API version that was in use was deprecated back in November 2014. &nbsp;The new version prompts you to login to Google and accept that Notes will manage your calendar. &nbsp;If you've used any other 3rd party product with Google, it will look familiar. &nbsp;AND...it supports two-factor authentication as you'd expect. <br /> <br /> Create the calendar as normal and you'll get a prompt like one above.<br /> <br /> Federate away! <span style="text-decoration:underline"><br /> <br /> </span><a href="http://www-01.ibm.com/support/docview.wss?uid=swg21657963#Notes"><span style="text-decoration:underline">Interim Fixes for Notes 9.0.1.x</span></a>   ]]></content:encoded>
  318. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/notes-9.0.1-fp3-if1-updated-support-for-google-calendar.htm</wfw:commentRss>
  319. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/notes-9.0.1-fp3-if1-updated-support-for-google-calendar.htm?opendocument&amp;comments</wfw:comment>
  320. </item>
  321. <item>
  322. <title>Sametime Policy Naming - One character to not use in a name</title>
  323. <pubDate>Sun, 18 Aug 2013 21:10:05 -0700</pubDate>
  324. <description>
  325. <![CDATA[
  326. Working with a client last week, they had reported an issue getting a policy setting from Sametime to apply properly. The Chat History setting wasn't getting set as expected. Looking at the issue, ...
  327. ]]>
  328. </description>
  329. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/sametime-policy-naming-one-more-character-to-not-use.htm</link>
  330. <category>Sametime</category>
  331. <dc:creator>Ted Hardenburgh</dc:creator>
  332. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/sametime-policy-naming-one-more-character-to-not-use.htm?opendocument&amp;comments</comments>
  333. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/sametime-policy-naming-one-more-character-to-not-use.htm</guid>
  334. <content:encoded><![CDATA[ Working with a client last week, they had reported an issue getting a policy setting from Sametime to apply properly. &nbsp;The Chat History setting wasn't getting set as expected. <br /> <br /> Looking at the issue, we determined that the policy file - policies.user.xml - wasn't getting updated. In fact, it had been a few days since it was updated. Looking at the trace output on the community server, everything looked OK. We could see the policy that was updated on the SSC getting read by the community server, and even see that the setting was what the client wanted. The XML wasn't getting updated. <br /> <br /> Looking at it later in the week, I noticed a meeting policy had a date in it and that date coincided with the last date the policy XML file was updated. The date had a slash in it and I thought that was odd. Checking the documentation, it isn't listed as a prohibited characted, but I changed how the date was entered and waited to see if the policy XML file was updated. Lo and behold it was. Checking with a couple of users, they reported that the policy that was set incorrectly was now showing up as expected. <br /> <br /> Two takeaways:  <ul> <li>Do NOT use anything but alphanumerics in the policy name. Stay away from special characters.  </li><li>Don't use dates in the policy name. </li></ul>It would be good to have a comment field in the policy document that would allow some kind of tracking of changes, but that might need to be retained elsewhere for now. Also, I believe that changing the name of the policy whenever a change is made would potentially cause some issue with updating clients since they have to pick up what is essentially a "new" policy and then apply the "new" settings. <br /> <br /> Coming this week - SPNEGO. Fun times ahead!   ]]></content:encoded>
  335. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/sametime-policy-naming-one-more-character-to-not-use.htm</wfw:commentRss>
  336. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/sametime-policy-naming-one-more-character-to-not-use.htm?opendocument&amp;comments</wfw:comment>
  337. </item>
  338. <item>
  339. <title>Due by Thursday, July 18 - Update your Sametime Proxy certificates</title>
  340. <pubDate>Mon, 15 Jul 2013 09:44:55 -0700</pubDate>
  341. <description>
  342. <![CDATA[
  343. The current set of security certificates used to send push notifications to Apple iOS devices expire this week. So by the 18th, you'll want to download and install the "fix" for Sametime Proxy server ...
  344. ]]>
  345. </description>
  346. <link>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/due-by-thursday-july-18-update-your-sametime-proxy-certificates.htm</link>
  347. <category>Sametime</category>
  348. <dc:creator>Ted Hardenburgh</dc:creator>
  349. <comments>http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/due-by-thursday-july-18-update-your-sametime-proxy-certificates.htm?opendocument&amp;comments</comments>
  350. <guid isPermaLink="true">http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/due-by-thursday-july-18-update-your-sametime-proxy-certificates.htm</guid>
  351. <content:encoded><![CDATA[ The current set of security certificates used to send push notifications to Apple iOS devices expire this week. &nbsp;So by the 18th, you'll want to download and install the "fix" for Sametime Proxy server that updates the certs. <br /> <br /> See <a href="http://www-01.ibm.com/support/docview.wss?uid=swg21641787"><span style="text-decoration:underline">IBM Technote 1641787 </span></a>for more info including instructions on installing the update.   ]]></content:encoded>
  352. <wfw:commentRss> http://dominothoughts.com/domthoughts/domthoughts.nsf/dxcomments/due-by-thursday-july-18-update-your-sametime-proxy-certificates.htm</wfw:commentRss>
  353. <wfw:comment> http://dominothoughts.com/domthoughts/domthoughts.nsf/dx/due-by-thursday-july-18-update-your-sametime-proxy-certificates.htm?opendocument&amp;comments</wfw:comment>
  354. </item>
  355. </channel></rss>
  356.  

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//dominothoughts.com/DomThoughts/domthoughts.nsf/feed.rss

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