Tip 3: Understand the total impacts and costs of change

Going from SQL Server to Oracle means that you will have case sensitive queries, when the users previously did not need to worry about cAsE.  This is unavoidable and you’ll need to educate the user community on this, so you’ll need to follow change management processes and include lots of comms.

Going from Windows to Linux might mean changes to processing options for the location of files or interoperability.  There are options for bulk Processing Option (PO) changes using the database.  This is very important for finding a “\” for example and turning that into a “/” or vice-versa.  This simple trick of interrogating the BLOB in the F983051 can change a very manual and error prone process to an exact science.

Media Object changes are critical and need to be understood as you upgrade JD Edwards.  There are more storage options that you need to be aware of, some for good and some for your own peril.  I say peril, the storage costs alone are similar (see below), but the database IOPS is something that you need to focus on VERY carefully for a cloud implementation – as this is what generally governs your service limits.

For example, let’s look at this from a pure cloud cost perspective.  In AWS 100GB of s3 is going to cost you 0.023 dollars per GB ($2.50 a month). EFS (Elastic File System), a highly available storage format perfect for media objects, is going to cost you about 0.3 dollars per GB per Month ($36 a month).  Let’s put that into your highly available database instance (multiple availability zone) and that is going to be $27.60 per month.  Remember that you don’t really backup or restore the EFS, so you are only paying for a single copy (you might snap it to S3).

Look at your end game infrastructure and make sure that you understand both the change management impacts and the cost impacts of the new architecture.