IntroductionGiven the excitement around this release (geeks get enthused by some pretty odd things), you’d think an Oracle-red lightning bolt would shoot down from the heavens when I type that and smite me mightily like Thor’s hammer right on the noggin. BONG! Ouch, that hurt. But I have an excuse for writing that.
I have the problem all (most) EPM implementers face – ask us to build an Essbase database, write a calc script, craft an MDX formula, proof of concept a Planning app – that we can do with aplomb and flair. We do that for a living; we better be good at it.
But install a package that requires more than double-clicking on setup.exe and we (or at least I) go all wobbly. I have spent countless and fruitless hours trying to get development environments to work since System 9. Oh, eventually I mostly get them running but we are sometimes talking months (say hello System 9.0.1 and Oracle Fusion EPM 11.1.13 and 11.1.2) to get to a working state. It is my no-longer-secret shame. I suck at installations. There, I have said it and I feel much better.
The problem is, I want to experience the joy that is 188.8.131.52. Alas, my successful installation will likely occur sometime around the general release of 184.108.40.206. What to do?
There is an answer to my (and your) problemThe answer’s name is John Booth. He has very generously provided an Amazon Web Services (AWS) Amazon Machine Image (AMI) with the basics of 220.127.116.11 installed on it FOR FREE.
That means, with an AWS account, you (and I) can run 18.104.22.168 without installing anything. Oh joy, oh rapture. Maybe I can even have a life. Maybe. Maybe you can, too.
You can stop reading right now and go to his blog here to try out his EPM Test Drive to get all of the details. Or keep on reading to see how someone even as technically lame as yr. obdnt. srvnt. can run 22.214.171.124 with practically no effort at all.
Sign up for Amazon Web ServicesYou must have an Amazon Web Services account. Go here to start the process. Once you have that, follow these steps to 126.96.36.199 nirvana.
Amazon has put together a nice tutorial. I recommend that you go through it, following the Windows path as the 188.8.131.52 EPM Test Drive AMI is on Windows. Even if you’re a Linux bigot, Go Team Windows!
Don’t be overwhelmed by all of the steps. There is a bit of a learning curve but it isn’t that bad.
Launching 184.108.40.206 in the cloud
1) Assuming you’ve signed up and run through the tutorial, find your IP address at http://www.whatsmyip.org/ You are going to need this to define your security access to the 220.127.116.11 image.
2) Log onto Amazon Web Services at http://aws.amazon.com
3) Username = youremailaddress.com, password = whateveritis.
4) Make sure you have Adobe Flash 10.2 installed. The below message only pops up if you don’t have Flash 10.2 installed.
5) Click on the EC2, the Security Group, and finally the Create Security Group link. You are going to need your IP address from step #1
6) Name the group and give a description. I am going to pretend my name is Alice and that she/I live in Philly, PA. We will not talk about my identity crisis.
7) In the bottom half of the screen, select RDP as a connection protocol:
You need only enter your will need your IP address with a /32 switch. Then click on Add Rule.
8) Change the IP address to: youripaddress:32, e.g., 18.104.22.168/32 and then click on Save. You will see the following as confirmation:
9) Then click on Apply Rule Changes.
10) Now click on the AMIs link.
11) Select All Images, type in
12) Right click on the AMI and select Launch Instance
13) Select m2.xlarge aka Extra Large and then Continue. Don’t worry about the Availability Zone. The power is almost yours.
14) Take the default on the Advanced Instance Options.
15) Take the default on Tags, or put in a value if you like. It doesn’t really matter unless you managing multiple instances.
16) If you haven’t already created a key pair, do so now. Make sure that you keep that in a secure place as it is part of your authentication into AWS. In this case I created one called “AmazonCloud”.
17) Leave the security group at default and click on Continue.
18) You will get a chance to review your selection. Once you’re satisfied, click on Launch.
19) You will receive a confirmation message. Click on the View your instances on the Instances page link.
20) You will see a list of running instances. Now you play the waiting game as you are now subject to a delay equivalent to powering up a real server in your data center.
21) Once you’ve waited 10 to 15 minutes, right click on the AMI line, and select Connect.
22) You will get information on how to connect to the instance. Don’t be discouraged if you can’t; remember, it’s a virtual server oh-so-slowly booting off the drive. You can either download the shortcut to your hard drive, or copy the public DNS to the clipboard. Either way, you’re going to be running the Terminal Services client, aka, Remote Desktop, to connect to the server.
23) If you click on the Download shortcut file link, save it to your Windows desktop for sanity’s sake.
NB – This is in FireFox; Internet Explorer’s dialog box looks a little different.
24) Double click on the icon to see if it’s really running or not.
25) You will get this scary-looking error message. Ignore it, it’s much worse than it looks and click on Connect.
26) Happy, happy, joy, joy. You have now connected.
27) Once started, check out how much power you have.
28) Go ahead, start EPM 11.1.21 by double-clicking on the Workspace shortcut . Admit it, you’ve been waiting all day for this. Now play, play, play or more seriously (and boringly – see, I just invented a word, my 22.214.171.124 exuberance knows no linguistic bounds) learn, learn, learn.
29) When your brain cannot take any more, use the Start menu to Shut Down the server. Remember, if the instance is running, you are getting charged by the hour.
30) Your 126.96.36.199 instance is now stopped. Any work that you have done is stored on the stopped hard drive. If you are well and truly done with the instance of the virtual machine, right click on that Stopped AMI and select Terminate. This will delete the AMI and its drives. You lose all work. If you want to keep the drive in the state you left it, leave it a Stopped state or make your own AMI from it and then Terminate the instance. So long as the instance exists, even in a Stopped state, you are being charged, albeit a small amount.
31) That’s it. Have you sent John an note of appreciation yet? :)
The best way to thank John is to come see our presentation at KaleidoscopeYou’ll have to tolerate me, as well. Seriously, I come at this from an implementation perspective, John from an infrastructure perspective. It’s the best of both worlds.
Think of us as Martin and Lewis. Just call me Jerry; Dino’s the infrastructure guy. Have a gander of us entertaining your spiritual ancestors at their convention.