Special Cases of Attachments in Oracle Calendar Migrations to Microsoft Exchange

Secure signed attachments in Oracle Communication Convergence Calendar, that is anything named “smime.p7m” or with a “.p7m” extension.  These are signed, secured attachments in in Oracle Communication Convergence Calendar so the Sumatra process takes them as the secured, signed (therefore encrypted) attachments they are.

Please make sure your security-tasked admins know this and are prepared to deal with it in a post-migration Microsoft Exchange environment and have their certificates and security arranged appropriately.

Otherwise we are migrating data that cannot be read in your Office 365 / Microsoft Exchange environment.

Inline attachments in Oracle Communication Convergence Calendar

OCC identifies inline attachments by excluding the file name and the format type.  Since Sumatra doesn’t know the file name or file type, we name the attachment “att_” + <>, without extension, and attach as a FILE (not inline.) 

Oftentimes users can leverage their browsers to view each attachment.  In the calendar event select the attachment and Right-Click-Open, selecting the appropriate application if you know what it is or Microsoft Explorer if you do not.  If the attachment does not display correctly please contact the meeting organizer.

Attachments in Oracle Communication Convergence Calendar Migration to Exchange Version 2

Okay okay....

Remember this article?

We changed our minds.

Our test site did not want just the URL.

SO we needed to actually attach the damned binary file(s).

Sure.  We're getting a paycheck somewhere in here, right?

The insertion team (kudos to Russ!) put this together.

Export using fetchattach=1 in WCAP.

Select this option in your configuration:

Notes:

Attachments will slow down the process!

Attachments are not supported in historical archive mode.  

Attachments in Oracle Communication Convergence Calendar Migration to Exchange

Attachments.

The bane of full-state calendar migration, largely because it slows down the entire process and really grinds every gear we have.

So in the Oracle Communication Convergence Calendar server migration where you can extract URLs to attachments -- we insert URLs to the attachment.

We've given it to one site to try out.  If anyone else out there is looking for Oracle Communication / nee Sun Java Calendar, let us know.

The configuration looks like this:

Speeding your Oracle to Exchange calendar migration

Migrations are time-consuming and resource-intensive.

If you did not know this before, welcome to being woke.

The way we do them is of course even MORE time-consuming and resource-intensive because we re-create connections to attendees in meetings.  Because of the way EWS works this means more time and effort.

UNLESS... you consider that historical events do not really need to be fully-recreated.

Oh... please tell me more!

YES!  If you (say) do a full-state migration take data from (say) a month back and into the future as full-state.  

The key is the Calendar Selection Dates in your Configuration.

Your usual insertion settings for live meetings is this:  Do that for say (Today-30 days) into the Future at 2039.

For an archive / historical insertion:  Do this for (Whenever your earliest necessary date is) to (Today-30) Date.

Big warnings:
Make sure you use a different  in the _Config.xml for the historical insertion and the current insertion.  Reason: If your historical needs to be rolled back you do not want it to also remove your current data.  That's what we call a resume-generating process.

Oracle Communications Calendar Server to Microsoft Exchange Migration

We've been doing Oracle Calendar Server and Oracle Beehive for a while now.  The old Sun Java calendar was something we experimented with a while ago but didn't see much market for.

Then a 3000 seat migration came in for Oracle Communications Convergence Calendar Server (née iPlanet, then Sun Java calendar, etc.).

So we wrote it and added it to the regular Oracle Calendar Server migration code, running to migrate server-side into Microsoft Exchange.

As usual, we have a couple of advantages over client-side methods:

• Meetings are meetings with guest lists and responses.
• Recurrence patterns come over
• Room and resource bookings are recreated
• To-dos come over
• We have an UNDO capability to selectively remove only the data we inserted if necessary.
• Users and resources can be mapped to new IDs

Of course for email use imapsync.  Look through our blog for more info on how to use it and why it is the optimal solution for pretty much every situation you could be in migrating email.