Migrating Enterprise Content & Data into the Cloud

Organizations that have implemented large enterprise content and business process management solutions understand the burden of data and content storage. From server and storage costs to ongoing support and monitoring, managing large amounts of content and data on-premises or through your virtual environments is time and resource consuming.

Find out how you can migrate your enterprise content and data, including your Perceptive Content OSM and INOW database, into the cloud. Cloud-based storage saves time and resources by off-loading time consuming tasks, monitoring, and issue management, while maintaining performance and system availability.

Download PDF
Transcript

John Marney:

Hi everyone. Thanks for joining us for another RPI Consultants webinar Wednesday. This is Michael and John part two.

Mike Madsen:

We’re back.

John Marney:

Today, this afternoon, we’re discussing how to migrate your data and your content into the cloud. This is going to cover a wide variety of cloud topics and expect this webinar to run a little longer than most of ours do, probably just over half an hour. So, buckle in, but I think we’ve got some really good material ready for you.

As far as other upcoming webinars: Next month on Wednesday, November 6th, we have a Kofax themed webinar series, What’s New in Kofax TotalAgility, 7.6? Subtitle: The Elimination of Silverlight. And then in the afternoon we have what’s new in Kofax ReadSoft Online. If you haven’t joined us for our office hours, that’s a different kind of webinar where we take a deep dive into a technical topic with hands on demonstrations, taking questions, and demo requests from attendees. So, we have one of those a month.

The October one is over perceptive content application plans and then the November office hours is over perceptive experience. Most of you know me. My name is John Marney, manager of the Content and Process Automation practice here at RPI. That’s us here in Kansas City. I have been doing this for around a decade now, as Michael reminded me just a few minutes ago, and that made me feel really good, and I do consider myself an AP automation guru.

Mike Madsen:

And hello, I’m Mike Madsen. I’m a lead consultant here primarily working with Perceptive Content Brainware programs and I work a lot with back office and higher education. As the office Dungeon Master, we’re hoping for a net 20 on this webinar.

John Marney:

Oh, yes. All right, so our agenda today, first we’re going to cover what is cloud? Once we know what it is, probably all of you know what it is, but we’re going to cover what it is in context for this discussion and we’re going to discuss how the cloud applies to your actual content and business process applications.

We’re going to cover a case study of something we’ve actually done. In this case, it’s Perceptive OSMs with a zero storage. However, that case study is pretty much something that can directly apply to a Kofax use case or an OnBase use case. And then we’re going to give you some strategies to get started with your cloud migration.

So, why should everyone hedge this webinar a little bit, Mike?

Mike Madsen:

Well, as everybody knows, cloud is constantly evolving. So, what we’re covering today is going to be as up to date information as possible that we can get today. But for all we know something could change tomorrow. So just always go to your service website to check stuff out, take a look at your documentation just to be sure.

John Marney:

And this information is true right now to the best of our ability. But not only do things change, but sometimes we get things wrong.

So, let’s jump in. What is cloud? What is cloud? What if I told you that the cloud is just someone else’s computer, or probably more appropriately a whole bunch of people’s computers? So, first let’s talk about the infrastructure that actually goes into cloud and you’re hearing this for the first time ever.

This is a John Marney certified marketing term. I Googled it. Nobody else has done this before. So, I’m breaking the cloud down into two different types of implementations. The first is your bright cloud and this is really the best version of cloud. And this means that you’re taking everything you have today and really re-envisioning it and reapplying it into the cloud. So, it takes your data and your files and your applications and distributes them across multiple servers and data centers.

That’s largely driven by a Linux backend. Though you would never know it because the traditional servers, file systems, et cetera, don’t exist. There’s nothing for you to go manipulate and drag and drop and there’s no control panel in a windows server, right? So, it’s less a specific application support. You’re not going to find, for the most part, OnBase 18 supported as an Amazon web service.

It’s mostly web-based services that can be utilized in connection with each other for a series of services. So, it is a service-oriented architecture. And then you have the dark cloud. Dark cloud is actually basically just what you’re doing today, but on someone else’s hardware. It allows you to spin up Windows or Linux virtual machines to run whatever you want. And as far as your files and storage are concerned, you can do blobs, which some applications support today, you can do your traditional file directory system. And this is what actually allows you, for the most part right now, to map that cloud storage to your on premises traditional file systems and directories.

So, what are the technologies involved? And this is mostly bright cloud versus dark cloud. So, you’ve got blobs vs file shares. So blobs are actually in support of a lot more different file types, file structures, data types. It’s not just files. File shares are your more traditional file system, like what you’d find in Windows. Whichever it is, if you want to map it to a Windows file system, like a macro Z drive out to a zero file share, it must support a technology called SMB 3.0, and on top of that there are a number of options whether you’re using blobs or file shares. So, the three main pieces are going to be your replication, your performance, and your location.

Mike Madsen:

This is generally one of the easier first steps into cloud if you’re trying to migrate that direction.

John Marney:

Absolutely. You want to look at your files first. So, the replication is how redundant is this data? In all of them, they began at 99.999, like six nines, and it’s really deciding how many decimal places you want after that. So, it goes 6, 11, 16, something like that.

Performance-wise, we’re talking generally about hot versus cold storage. Cold being something that may take longer for the services to retrieve. Hot meaning it’s meant to be more readily available. And then the location is the region or where the actual data center exists. But it can also mean how redundant is that data within a given data center or region? So that if they did suffer some sort of hardware failure or loss, how quickly can that data be retrieved?

Next, you’ve got cloud databases versus traditional databases. SQL server or Oracle.

Mike Madsen:

Yeah. The cool thing about cloud databases is that we’re no longer talking about just a standard database table, where you may store just string values or something like that. Cloud DBs actually allow us to place objects in specific locations where we can access those, even applications. So, it’s really interesting what you can get into with the cloud DB.

John Marney:

Yeah, you really could store tables inside of tables inside of the tables. It’s all generally structured in…so, it’s not really a traditional relational database. Though, you can structure it to act like that or really act just like that. And there is some ability to migrate existing SQL databases into a cloud database.

So, for example, Azure offers the cosmos DB. There is a path for that, but that may not necessarily be the wisest way to implement. What we’re going to talk about a little bit later is a hybrid approach that allows you to use your traditional SQL servers and utilize some database services. And then lastly you have your cloud services versus just virtual machines.

So, the cloud services seek to just fill gaps or replace specific components inside your organization. So, we’re talking about things like web app development and app hosting. Your visual studio work could all take place in the cloud. Data management and access management, so things like your active directory. Whereas your virtual machines really are meant for more specific applications that are meant