Watch Webinar: Modernizing Essbase - Understanding Your Options

Thank you to everyone who could attend our live webinar. If you missed it, or would like to see it again, below is the Q&A along with a link to the recording.

Q: You mentioned that Marketplace Deployment includes a feature that eliminates the need to apply patches, can you explain a little more?

A: The feature is called Stack Image Update. Since Marketplace deploys a customized “Stack” of OCI resources configured for Essbase, this feature allows you to upgrade the existing stack to the latest version without being worried about individual patches.

Q: We are a windows shop and considering deploying Marketplace on OCI.  Would you provide a little more information on using a jump box?

A: A jump box is simply a small Windows server running whichever flavor of Windows OS you prefer, and usually sized to a single OCPU (or 2 cores), with about 8 GB of RAM.  The host then gets all the Essbase client software loaded on it, such as MAXL and ESSCMD clients, and maybe even MS Office (Excel) and SmartView.

Once you have that host built, you can then use it as an administration/execution platform for all your existing Windows MAXL and ESSCMD batches/command files.  This still requires some updating of those scripts for interacting with LINUX and because of some syntax differences between Essbase versions, but it’s much less work than recoding the scripts for LINUX.  More importantly, if your staff isn’t familiar with running things in a LINUX world, when the scripts are completed, they can run them the way they always have.

Q: Can we still use EAS with Essbase 21c

A: Essbase 21c comes with an EAS lite component, with limited functionality. Important to note is that EAS lite is intended to be a stop gap measure while you migrated and familiarize yourself with the new URL. EAS still lets you maintain and edit your outline, but you lose all the new functionality incorporated in the modern UI.