EAS: How to Map the MaxL Script Storage Location to a Shared Drive so the Scripts can be Shared Between Two Load-Balanced Essbase Administration Services (EAS) Servers
(Doc ID 2375702.1)
Last updated on FEBRUARY 03, 2019
Applies to:Hyperion Essbase - Version 188.8.131.52.000 and later
Information in this document applies to any platform.
In a distributed environment, there are two Essbase Administration Services (EAS) servers (EAS1/EAS2) and connection is made through a load-balancer. Users accessing the EAS Server will get the list of the Maxl (mxl) scripts stored on the particular EAS Server they are connected to through the load-balancer. The availability of MaxL (mxl) scripts depends on which EAS server the user gets connected. If the Maxl (mxl) scripts are centrally available across both EAS Servers, then the users will be accessing the MaxL scripts uniformly regardless of the EAS Server that they are directed to by the load-balancer.
Is there a way to point the EAS MaxL script storage location to a shared drive?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document