Ben Langhinrichs

Photograph of Ben Langhinrichs
E-mail address - Ben Langhinrichs






May, 2017
SMTWTFS
 01 02 03 04 05 06
07 08 09 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31

Search the weblog





























Genii Weblog


Civility in critiquing the ideas of others is no vice. Rudeness in defending your own ideas is no virtue.


Tue 23 May 2017, 12:31 PM
"After a migration, it is essential that the original content, context and intent are clear, as there is usually little recourse to checking the original source. In our experience, approximately 5‒10% of emails suffer from some form of fidelity issues, while 1‒2% suffer serious data loss or corruption due to rendering issues. These numbers may range much higher for organizations who have a long history of integrating Notes mail with their applications." - Mitigating Risk of Data Loss – Migrating Notes Emails
 
Click on the link to read about ten problem areas, and how we help mitigate your risk.
 
CoexLinks Migrate - Whether you are converting, archiving or migrating, we ensure the integrity of your company's email. (Application data migrations also available.)
 
 
If the data matters, you want it preserved. If the data doesn't matter, why are you migrating it?
 
Inline JPEG image
 
 
 

Copyright © 2017 Genii Software Ltd.

Wed 3 May 2017, 01:17 PM
If you work with customer/client companies who currently use or are moving away from IBM Domino, and you might be interested in reselling any of our CoexLinks products, don't hesitate to contact me. Opportunities available in most regions of the world. If you work for an email vault or data warehouse company which might be interested in expanding to ingest Domino emails, either archived or live, from client companies, I'd be interested in talking with you as well.
 
CoexLinks Fidelity is for outbound/mobile/web email fidelity. All three products use out proprietary rendering engine for the best fidelity available. (Applies to Notes/Domino/Traveler/iNotes.)
 
CoexLinks Migrate is for either converting mail in place (for Verse) or migrating it out to disk or elsewhere for use in archival systems or new email systems where all email is desired in a single place.  (Applies to Notes/Domino/Verse)
 
CoexLinks Journal is for journaling email into a secure vault or data warehouse for compliance, surveillance or analysis.  (Applies to Notes/Domino/Verse)
 
Below is an example of the importance of the high fidelity rendering. Whether you are sending email to clients, journaling or archiving it for later retrieval, or migrating it to another email system, you should expect at a minimum that it contain all the information in your email and that it look roughly similar. If you sell a CoexLinks solution to a client, you can have confidence that the fidelity will be top notch, and the data will be retained.
 
 
 

Copyright © 2017 Genii Software Ltd.

Wed 3 May 2017, 11:54 AM
I posted this over on Facebook, but though I'd share it here as well. We've been doing some performance tuning on CoexLinks Migrate, which let's you export your email, both MIME and rich text, to high fidelity standardized formats including MBOX and EML and Exchange Mail Journal Envelope format (basically a wrapped up EML file with all the recipients and such in an envelope.
 
Performance tuning is fun, but it isn't sexy. You take Software A which creates End Product B, work incredibly hard to make sure it still creates the exact same damn End Product B, but faster. Same input, same output, less time. Not sexy.
 
But it can be satisfying. Here are the results from my test this morning (run on an old PC, so your mileage may vary, but it is likely to be better).
 
Inline JPEG image
 
Performance tuning seems to be helping. This is exporting to MBOX format, which is much faster than individual EML files, but 6000/minute means averaging 1/100 of a second per document. Wow. This generated an MBOX file with size 0.93GB from a mail db of 1.62GB, for what it is worth. When I ran the same test on the same database generating EML files,  it did about 2600/minute and generated 1.8GB in total EML files. That's overhead for you. 
 
In case you wonder the practical needs for this kind of speed, we have a client with 5TB of archived email. Using a very rough approximation based on my own mailbox, that would take about 96 hours (approximately 4 days) generated to MBOX. It would take roughly 220 hours for EML format (approximately. 9 days). 
 
When we started tuning, it averaged 950/minute for EML (we didn't measure for MBOX then). At that rate, it would have have taken 602 hours (approximately 25 days). Now, because these are separate databases, you would either run it on multiple processors or multiple machines, but even dividing these numbers by 10 machines/processors would take 9.6 hours, 22 hours and 60 hours respectively. The longer it takes, the more chance of something going wrong and having to start that part over. In short, speed matters. Fast enough, and you can even re-do the whole thing if some assumption turns out to be wrong. Slow enough, and a mistake can make you miss deadlines.
 
But as thay say on Reading Rainbow, you don't have to take my word for it. Request an evaluation license today and give it a spin.

Copyright © 2017 Genii Software Ltd.

Fri 28 Apr 2017, 10:59 AM
A new CoexLinks Migrate customer had an interesting observation about why they signed on. For several years, their users have forwarded documents from different databases as snapshots to be saved by their manager. No embedded form or anything, just a standard Notes feature, Actions - Forward. Since the manager had a Notes client, they thought nothing of it. But when they went to migrate all this mail out of Notes (meeting requirements for retention), they discovered that critical data was missing from these snapshots.
 
While I can't share their data, Below is a simple example using the Notes database I use to track orders and maintenance. It has some of the same elements they identified. Note that this same engine with some variants is used for CoexLinks FidelityCoexLinks Journal and CoexLinks Migrate.
 
But what the customer said last really stuck with me. I'm paraphrasing here, but he said that it was one thing to have something go out badly when it was a current email, but with a migration, it was your last chance. If the data was missing, it was gone forever. Or, as I put it, your one chance to make a good last impression.
 
 
1) Notes form open in Notes client
 
Inline JPEG image
 
 
2) The form forwarded via email, still in the Notes client
 
Inline JPEG image
 
 
3) The email received by Gmail, using the native Notes rendering
 
Inline JPEG image
 
 
4) The form received by Gmail, using CoexLinks rendering
 
Inline JPEG image
 

Copyright © 2017 Genii Software Ltd.

Thu 6 Apr 2017, 11:27 AM
There is an old saying that imitation is the sincerest form of flattery. But a corollary i9n the tech world might be imitation is the surest form of interoperability.
 
A long-standing complaint among Notes users has been that many solutions build integrations for Microsoft Outlook/Exchange, but not for IBM Notes/Domino. While there are myriad reasons, it leaves an ISV supporting Notes/Domino with a challenge. Do we only support those solutions with native Notes/Domino integrations, or do we build out own solution/integration? Both choices are limiting. 
 
When we built CoexLinks Journal and CoexLinks Migrate, we faced this challenge again. Did we want to restrict our output to third-party platforms that support Notes/Domino, or did we want to build our own archival solution which would distract from our core business? We needed a third choice, which is where imitation comes in. If we could deliver emails in a format that sufficiently mimics Microsoft Exchange Journals, the data warehouses and email vaults that support Microsoft Exchange would automatically support IBM Notes/Domino (and IBM Verse, as a bonus).
 
So we did that. We render the emails with our exclusive high fidelity rendering engine, package them as EML files and wrap them in an envelope that looks just like a Microsoft Exchange Journal. Now, for our customers who need journaling for compliance, surveillance and analysis or legacy archiving for similar purposes, we can integrate with any of the myriad email vaults or data warehouses that accept Microsoft Exchange. Because the MIME format is standardized, even if the journal envelope isn't, those emails are preserved in a standards-based format that does not require a dedicated Domino storage. Of course, the envelope is just an option, as a customer can also archive or migrate using EML or MBOX format. Regardless of the specific goal, migration or coexistence or archiving or data warehousing, a standards-based solution is more likely to be readable and usablein the future, no matter what happens to the different email platforms.
 
Why not try CoexLinks Journal or CoexLinks Migrate for your company? Or contact us for further information.
 
 
 

Copyright © 2017 Genii Software Ltd.

Technorati tags:

Tue 4 Apr 2017, 04:13 PM
Our newest product, CoexLinks Migrate is available and out there in the wild.. But since you haven't tried it yet (ok, a few of you might have), here is a very brief demo. Like, a minute long. Seriously, it's a back end product, so there's not a lot to see. Soon, I'll have some demos about the results, and why you should care, but if you've been paying attention to CoexLinks Fidelity, those won't come as much of a surprise. High fidelity email rendering to EML and MBOX. If that doesn't quicken the pulse...
 
 
Unlike the results of CoexLinks Migrate, this video is low fidelity. Sorry.

Copyright © 2017 Genii Software Ltd.