Registering Essbase 9.3.1 with Shared Services

Question

What would you expect to see appear in Shared Services when you register an Essbase server? I seem to get random results:
sometimes something called
Analytic Servers:<hostname>
sometimes nothing.
Should something appear in HSS just by registering or do you have to "externalize users"?
How do I "unregister" an Essbase server from HSS? It seems that this option is never offered by the Essbase config utility unless you manually edit the essbase_<num>config.xml file in <HYPERIONHOME>/common/config/products/essbase/<version>
PK

Answer 1

Philip,
Ah, the sweet mysteries of Essbase/Shared Services.
Okay, the easy one first:
Should something appear in HSS just by registering or do you have to "externalize users"?You do have to externalize users from the security node in EAS for Essbase to show up in Shared Services. This is a one way street, i.e., it cannot be undone, except by stopping Essbase and restoring your pre-externalized essbase.sec file. Obviously this is not a particularly good approach. :) You could also stop Essbase and delete essbase.sec altogether but again, an even worse approach.
Still pretty easy:
What would you expect to see appear in Shared Services when you register an Essbase server? I seem to get random results: sometimes something called Analytic Servers:<hostname>That's what I usually see (I am not an installer, just enough to be dangerous). It usually takes the form of Analytic Server:hostname:n where n is a counter as SS can handle more than one Essbase server. BTW, I may have that string wrong -- I'm not in front of a SS-enabled Essbase right now but what you describe sounds right.
The not so easy one:
How do I "unregister" an Essbase server from HSS? It seems that this option is never offered by the Essbase config utility unless you manually edit the essbase_<num>config.xml file in <HYPERIONHOME>/common/config/products/essbase/<version>Hmm, I don't know how you do it other than the way you state. It is designed to be a one time thing. Really, I think the only reason they keep unexternalized Essbase is so we consultants can run it on our laptops without pulling all of our hair out when SS/OpenLDAP throws a fit when the laptop gets put into standby mode. :) In a real server environment, I don't see a lot of value in not externalizing as going to a SS mode of security gives you a single point of administration for security, roles, etc.
Regards,
Cameron Lackpour