We now have a working server with Oracle DB running. All we need now is to finish prepping the system to begin the installation of EPM. One of the first things that needs to be done is make sure the profile for the oracle user has the right ORACLE_HOME and PATH variables. Next we'll create the users which we'll use. To get into this you'll need to use SQLPLUS. You should be able to just type sqlplus at the command line provided the profile changes above were done. If you have an issue you can always log out and back in. In this example we created a user for all components of the application to use and one for the Planning application we'll be using later. EPM System Database: epm Planning Database: Budget Here we unpack all the epm zip files we downloaded from the edelivery website. Navigate to the folder where you unpacked all the zip files and run the installTool.sh script. Click through the first few screens. I used the same folder where our database was stored and put Middleware alongside the database folder. Select New installation and Click Next Since this is pretty much a simple build, with Essbase, Planning, Calc Manager and Financial Reporting. We'll make the following installation options. From there click through until the installation is complete. Once the install is done we'll click the Configure. If you accidentally close before you configure you can always run configtool.sh as described here. epm online help Here you can choose the name of the instance. Unless you intend to co-locate multiple environments here, you'll probably be best served by sticking to the default. Enter the details for the database to create it. Here we can pretty much select everything and click next. Note, if you are putting different pieces of the environment on different servers you'll be better off installing sections at a time. Follow the online documentation for the order of configuration. Make sure you remember the location for import_export. This is where LCM stores the files and it always pays to know where this is. Select all and click Next This is important if you ever plan to have Reporting Analysis on multiple servers. Otherwise it's not such a big deal. If you do intend to have multiple Reporting Analysis folders make sure it's in a shared location and all nodes have full access to this location. This section is where ewe configure the domain. This is also important for any tuning efforts you intend to do later. Since we're running a tight install with limited memory we'll be deploying to a single managed server. Otherwise you can always deploy each product to its own server. This provides much finer control on the memory each piece can use. Also note the port this is very important. Here we can chose the cluster name for Essbase. I prefer to stick to the standard unless there is a requirement otherwise. It helps to be default when it's time to troubleshoot potential issues. We'll be keeping the defaults here so, Click Next We'll be keeping the defaults here so, Click Next We'll be keeping the defaults here so, Click Next The port used by Oracle HTTP Server is important. Note it well. Click Next Choose your admin username and password. It doesn't hurt to change this to something obscure. Almost there, Click Next to configure. To startup the server you'll want to run the start.sh in the user_projects/epmsystem1/bin folder. If everything went to plan you should now be able to log into the website from your client machine. Thanks for following along the way.
1 Comment
|
AuthorCharles Torry Archives
September 2016
Categories
All
|