I just installed EAS in my database server (and the HSS and other applications are in other server)
I can log in to EAS but I cannot create any application.
When I right-click Essbasecluster1-Create, the APPLICATION is greyed out.
Do I need to do anything in HSS or in EAS so that I will be able to start creating application.
Also, since we are trying to make it a replica of our dev environment, do we need to export the security/ native directory in HSS before we do anything else. Please help.
Give the user this specific Provisions from the Shared service for Essbase Server - Create/Delete Application and the user should be able to create applications.
Edited by: hyperionEPM on Dec 4, 2012 9:14 PM
but when I log in to HSS to provision the user, under AVAILABLE ROLES, there is no EAS, the only things it has are: BUSINESS RULES, FOUNDATION, and REPORTING and Analysis.
Am I doing something wrong?
As John has mentioned, you should be looking under Essbase Server; it should be something like this Essbase:<Servername> and then under Administrator
HyperionEPM Please mark answers as helpful or correct for others to find them easily
Hi Do you mean in EAS or in HSS.
When I look under HSS, the APPLICATION GROUP does not have ESSBASECLUSTER-1.
In EAS, under Essbase Servers, I just added Essbase server called EssbaseCluster1, but from there, I cannot create application as it is blank. The name of the essbase server should be EssbaseCluster1 right? OR can it be something else?
You had mentioned
As John has mentioned, you should be looking under Essbase Server; it should be something like this
Essbase:<Servername> and then under Administrator
Can you give me a little more detail please. I am missing something here I guess.
I configured HSS, etc in one server and Essbase in another server. This means, I may not have configured essbase in the server properly right? So Can I reconfigure Essbase again. Do I need to do anything specific (remember anything in particular) while configuring Essbase?
When you first configured the essbase server you should have configured to point to the existing shared services database, if you did that correctly then it should be registered with the same shared services.