It was also the easiest to use administratively. In the following post I will re-evaluate these advantages EPMA had and provide some insight on when and where it should be used in the latest version. Automation of metadata loads is important for companies. When processes run in the middle of the night, it greatly reduces user down time. It also reduces manual maintenance needed in the application. However, starting with the With that patch, it allowed the outline load utility to connect directly to a relational database, something that previously could only have been done with EPMA.
Now in the Administrators can now schedule metadata builds within the planning console itself. This is only available is the application is built as a Classic Planning application.
This option does not exist for EPMA. Manually creating dimensions has always been simple in EPMA. All the settings were displayed on the right, and with the grid spreader it was easy to make large scale changes across an entire dimension.
On the opposite side of that, Classic Planning administration has always been sort of a hassle. Expanding the hierarchy to find members was rather cumbersome, and to change a setting you would have to open an entirely new window. That changed significantly in Now it became possible to perform mass updates on dimensions from Smart View.
The console is easy to use and with the Excel front end, it feels very similar to an average Essbase query. They also enable simple exports and imports of metadata with the While creating a quick application is likely still easier in EPMA, I think dimensional administration is now easier with Classic Planning. If you have ever truly shared dimensions you know that maintenance is drastically simplified by having one dimension as opposed to many copies of the same one.
This is still not available in Classic Planning, but in the current version it would be much easier to replicate something similar.
You could now create the dimension in one application, export to a common location, and import that dimension into all other applications. That still requires more setup and process than sharing a dimension in EPMA. Because there is no out of the box option to share dimensions in Classic Planning, EPMA is still your best option for sharing dimensions. Yes the annoying Configuration Manager service is gone :. FM utilities are deprecated from The first information I can find about the The documentation release will be interesting I am not sure I trust everything in the support matrix at the moment, some of it just looks like it has been copied and pasted from previous versions.
Copy App? Only over LCM! Hi John, Great info as always. Did you do anything special to the Windows server roles added Application Server, added Web Server role or use the loopback adapter? Did these steps like I have in the previous releases and all is working except an error on the Web Server configuration which renders the box pretty much useless for Hyperion :. I checked that on my essbase server there is a hybrid folder created. Cheers yannis.
Did you notice any issues deploying against this version of IIS? I presume not, but no harm in asking. With this new version, I have to use no more with WS Server. Do know if it is possible to use the Lifecycle Management to perform the migration process from Thanks, Railton. I believe it is one of those things which you will have to try and depending on product will have varying succes rates. Please help in this. What exactly could be the issue?
Wednesday, 28 January EPM As expected there was a flurry of activity on social media that As windows is at last supported I am going to take the plunge and install on it and configuring against Oracle 12c Now on to the configuration which remains in the whole pretty much similar to
0コメント