Finit infrastructure webinar 03212011 master final

Getting the Most out of EPM:Getting the Most out of EPM:
Infrastructure for Finance People
March 23, 2011
Jay HamptonJay Hampton
jhampton@finitsolutions.com
www.finitsolutions.com

Th Fi it S l ti S iTh Fi it S l ti S i
Getting the Most out of EPM: Infrastructure for Finance People
Finit Introduction The Finit Solutions SeriesThe Finit Solutions Series
Finit Solutions specializes in consulting services in the Oracle Hyperion Enterprise
Performance Management Solutions suite of products:
Financial Consolidation
– Financial Management (HFM)
Hyperion Enterprise
Planning and Business Intelligence
– Planning
Essbase– Hyperion Enterprise
– Financial Close Management
– Disclosure Management
– Essbase
– Profitability & Cost Management
(HPCM)
Data Integration
– Financial Data Quality Management
(FDM)
BI+ Reporting Tools
– Financial Reporting
– Smartview
( )
– Oracle Data Integrator (ODI)
– Data Integration Management (DIM)
– Other (EPMA, ERPi, etc)
– Web Analysis
– Essbase Excel Add‐in
‐ 2 ‐
Other (EPMA, ERPi, etc)

Finit’s EPM Expertise The Finit Solutions SeriesThe Finit Solutions Series
• Finit consultants bring deep experience in external SEC reporting, tax reporting, and
i t l t l i id f i d t i
p
internal management analysis across a wide range of industries.
• Our backgrounds in accounting and reporting, combined with our product expertise, make
us uniquely qualified to assist and advise clients on developing reporting packages that q y q p g p g p g
provide better insight and analysis for management.
• In addition to strong backgrounds in accounting and finance, the Finit consulting team has
subject matter expertise related to Oracle EPM technical and infrastructure componentssubject matter expertise related to Oracle EPM technical and infrastructure components.
Our ability to know both sides adds value in areas such as environment strategy planning,
product selection, deployment planning and overall infrastructure implementation activities.
• Finit is a member of the Oracle HFM, Planning, FDM and Hyperion Enterprise Customer
Advisory Boards.  In this role, we work directly with product development and quality
engineering teams to address future product enhancements.
‐ 3 ‐

Finit’s Client Service The Finit Solutions SeriesThe Finit Solutions Series
We take client service very seriously and our results areWe take client service very seriously and our results are
unmatched in the industry:
Our client service approach has led to 100% customer
satisfaction for every Finit client (136 and counting) forsatisfaction for every Finit client (136 and counting) for
every project (over 250 and counting).
‐ 4 ‐

Some Finit Clients The Finit Solutions SeriesThe Finit Solutions Series
•
‐ 5 ‐

About the Presenter The Finit Solutions SeriesThe Finit Solutions Series
Jay Hampton
( )(jhampton@finitsolutions.com)
• Partner of Finit Solutions
• 8 years of experience8 years of experience
implementing Hyperion products
• Frequent presenter at Hyperion
conferencesconferences
• Serves as the Hyperion FDM
Domain Lead for the Oracle
Hyperion Special yp p
Interest Group
‐ 6 ‐

How to Ask a Question The Finit Solutions SeriesThe Finit Solutions Series
‐ 7 ‐

Purpose of this Webinar The Finit Solutions SeriesThe Finit Solutions Series
Purpose of this Webinar
• Provide an overview and education on some of the technical
components of deploying Oracle Hyperion EPM.  This will be
geared to the key things Finance / Business supporting or running
EPM applications should know.
• Key webinar components will include:• Key webinar components will include:
– Server Environment deployment
– Disaster & Recovery
– Introduction to Virtual Machines
– Product Details
– Third party productsp y p
– Server roles and usage during processing
‐ 8 ‐

Why do a webinar on this? The Finit Solutions SeriesThe Finit Solutions Series
Why do a webinar on this?
Hot‐
Pluggable
64 bit
Hyper‐
Threading
Cores
“The Cloud”
Load
Balanced
Redundancy Java
Virtualization
Three‐Tier
Hot Failover
NET
Architecture
High
A il bilit
.NET
SOA
‐ 9 ‐
Availability

My IT department wants to
The Finit Solutions Series
My IT department wants to
start using virtual machines in
H i iour Hyperion environment.
What is this and is this OK?

Server Virtualization The Finit Solutions SeriesThe Finit Solutions Series
Virtual servers and physical servers act in similar manners.  You can log into both
types of servers, you can install products on both types of servers and you can
H i li i b h Th f diff
Server Virtualization
run Hyperion applications on both types.  There are a few differences:
• A physical server is real.  It is the actual server that sits in your data center.  It
has processors, memory (RAM) and hard drive storage with it.
• A physical server can be used for one specific purpose (i.e. as the database
server in your Hyperion environment) or it can be split into multiple servers.
• Virtual servers are those multiple servers or instances that exist on a physical
server.  Virtual servers have to sit on some physical server.  Each virtual server
that sits on a physical server is given a share of that physical server’s processors,
memory, etc.
• Multiple virtual servers can exist on a physical server.  When set up, your
interaction with a virtual server and physical server are the same:  each has a
‐ 11 ‐
server name, IP address and look the same.

Server Virtualization, Cont. The Finit Solutions SeriesThe Finit Solutions Series
Server Virtualization, Cont.
Physical Server ‘A’
Ph i l S ‘A’
Virtual Server 1 Virtual Server 2
Physical Server ‘A’
Specs
- 4 CPU
- 16 GB of RAM
Specs Specs
2
- 250 GB disk drive
capacity
- Virtualization
Software - 2 processors
(CPU)
- 8 GB of RAM
(memory)
G
- 2 processors
(CPU)
- 8 GB of RAM
(memory)
40 GB di k
Software
- 40 GB disk
drive
- Windows
Server 2008
- 40 GB disk
drive
- Windows
Server 2008
‐ 12 ‐

Server Virtualization, Cont. The Finit Solutions SeriesThe Finit Solutions Series
• VMWare is a type of virtualization software.  It allows you to create virtual
servers from a physical server.  It is not the only virtualization software though
d O l ( i h O l Vi l M hi (OVM)) d Mi f ( i h H V)
Server Virtualization, Cont.
and Oracle (with Oracle Virtual Machines (OVM)) and Microsoft (with Hyper‐V)
have offerings.  So VMWare refers to a software company that makes
virtualization software, not virtualization itself.
Vi li i ff b fi i i• Virtualization offers some benefits to organizations:
– Virtual servers can be quickly set up, backed up and restored.  ‘Snapshots’ of the
server environment can be taken and quickly restored if issues exist.
O i ti ffi i tl d ff ti l th i h d h– Organizations can more efficiently and effectively manage their hardware purchases.
It is typically cheaper to buy one large server and splitting it into multiple virtual
machines than buying separate physical servers.
– Each virtual server can run its own operating system. So you can have one virtualEach virtual server can run its own operating system.  So you can have one virtual
server running Windows and another Unix with both residing on the same physical
server.
‐ 13 ‐

Virtualization with Hyperion EPMThe Finit Solutions SeriesThe Finit Solutions Series
While virtualization is powerful and offers advantages, there are some key
considerations related to using virtualization with your Hyperion EPM products.
Virtualization with Hyperion EPM
• It is always recommended to use physical servers for your databases (i.e. SQL /
Oracle) and Essbase.  This is because the databases / Essbase are very process
intensive and physical servers offer maximum resources to be devoted if
d dneeded.
• Some advanced virtualization practices can cause significant performance issues
with Hyperion EPM.  Two main items include:
– Pooling Hyperion / Non‐Hyperion servers together – the key is whether Hyperion servers will
always receive their dedicated server resources (processors, RAM, etc).  Since virtual servers
reside on a physical server, if another virtual server is taking up significant resources it can affect
the resources dedicated to Hyperion.
– Virtual server swapping (VMotion) – Virtual servers should not be moved from one physical
server to another while users may be in the system.
• It is a best practice to have dedicated physical servers for Hyperion EPM that are
then split into multiple virtual servers that are constant on those physical hosts
‐ 14 ‐
then split into multiple virtual servers that are constant on those physical hosts.

How many environments should I
plan for in my Fusion 11 upgrade? p f y pg
Does it matter where the servers
are physically located?p y y

Environment Strategy The Finit Solutions SeriesThe Finit Solutions Series
Most Common
• Production (Prod) – Prod is the main environment where users access their Hyperion
EPM li ti d f th i l i l i ti d l i ti iti
Environment Strategy
EPM applications and perform their closing, planning, reporting and analysis activities.
• Development (Dev) – The development environment generally is only accessible by
application administrators and power users.  This environment serves as a place to test
application and patches prior to putting them into the Prod environment.application and patches prior to putting them into the Prod environment.
Additional Environments:
• QA / UAT – If deployed QA / UAT test sits between the Dev and Prod environments It’sQA / UAT If deployed, QA / UAT test sits between the Dev and Prod  environments.  It s
purpose is generally to separate end user testing in this environment from where
application development occurs.
• Sandbox – If used, a Sandbox environment can be used for product / patch installation or
less formal application development.
• Disaster & Recovery (DR) – A separate DR environment can be used as a failover in the
event of a disaster.  Generally these would be stored in a different physical location from
Prod if used for DR
‐ 16 ‐
Prod if used for DR.

Environment Strategy, Cont. The Finit Solutions SeriesThe Finit Solutions Series
We always recommend a client use a minimum of two environments to separate
end users from pure application development activities.  Some considerations
f i ddi i l i
Environment Strategy, Cont.
for using additional environments:
• Determine if any internal controls policies exist that require a UAT / QA
environment.  Generally this third environment is only deployed with
organizations with many applications and / or a large user base.
– The benefit of a UAT / QA environment is to separate application development from end user
access You can still do this with two environments with using multiple applications on theaccess.  You can still do this with two environments with using multiple applications on the
same environment (one for the admins, one for users to test).
‐ 17 ‐

• The physical location of the servers can matter.  The closer you and your users
are physically to the servers, the less your requests have to travel over the
k
network.
– It is less important where the servers are physically located than how good of a network
connection you have from your physical location to the physical location of the servers.
– It is optimal to have all the servers within an environment located in the same physical location.It is optimal to have all the servers within an environment located in the same physical location.
This enables the server to server connections to travel across the network less.
• If a Sandbox is not used, how will you test applying patches or new version If a Sandbox is not used, how will you test applying patches or new version
installations?
– Installing and testing a new version or patch may extend across a period of weeks or month.  If
you only have 2 environments and apply patches to your Dev environment, you may be limited
i d l i h P d il h P d li i d d h iin deploying changes to Prod until the Prod applications are updated to the same version.
– A Sandbox environment also gives you flexibility to install additional Hyperion EPM products
without disrupting your core applications.
‐ 18 ‐

• Things to consider if IT policies mandate that Prod and Dev or Prod and QA
MUST be exact matches in terms of the number of servers.
– We rarely see companies utilize this additional hardware in the secondary environment because
the secondary environment is rarely utilized to the same extent as a production environment.
– Having a ‘mirrored’ secondary environment does allow for performance test simulations but to
make it really worthwhile, those companies own stress testing software / tools and have in‐
house expertise to use stress testing on an ongoing basis.
– Without a ‘mirrored’ secondary environment, you can still test product patch deployments.  We
recommend to have your secondary environment match Prod in terms of the architecture and
design but to be less in scale. So if you have 2 HFM servers in Prod, you can use 1 Dev.design but to be less in scale.  So if you have 2 HFM servers in Prod, you can use 1 Dev.
– Everything is relative though. If your production environment only has 2 servers than it’s a lot
more affordable to ‘mirror’ those two server in QA but if your production environment contains
7 servers this is a much more expensive decision.
‐ 19 ‐

What does a three tier architecture
mean?

Three Tier Architecture The Finit Solutions SeriesThe Finit Solutions Series
A three tier architecture relates to the way that software can be deployed.  A three
tier architecture separates processing functions into 3 tiers:
W b Ti
Three Tier Architecture
• Web Tier
– The web tier consists of the processes used when users interact with Hyperion EPM over the
web.  The web layer would be used as a user is going through the work flow in FDM.  Each step
launches a new web page through the navigation and that traffic and effort to generate and
display web pages to users is performed in this layer.
– Third party software such as IIS, Apache and WebLogic are used in the Web Tier to help with
these web page processing activities.
• Application Tier• Application Tier
– The application tier is typically where the main application processing is performed.  For
example, the main HFM application activities such as Consolidation, Translation, Data
Submission, etc are performed in this layer.  The Application tier works closely with the
database to properly perform its tasks.
• Database Tier
– The database tier relates to the relational database (i.e. SQL, Oracle) and is where the data, and
potentially calculations are computed and stored It is also typically where logs and other
‐ 21 ‐
potentially, calculations are computed and stored.  It is also typically where logs and other
application information are stored.

Three Tier Architecture, Cont. The Finit Solutions SeriesThe Finit Solutions Series
• All three tiers can reside on a single server.  However, a three tier architecture
separates different application processing activities out to allow organizations to
l b B i i i i h h diff
Three Tier Architecture, Cont.
scale better.  By separating process activities out, you can then have different
tiers reside and run on different servers as needed.  This also allows for overall
performance improvement as application tasks are not fighting for resources
with the database tasks (which would occur if all items were installed on thewith the database tasks (which would occur if all items were installed on the
same server).
• So as your organization needs more power, it can scale and grow the
environment by adding specific servers to the environmentenvironment by adding specific servers to the environment.
‐ 22 ‐

Web Tier Example The Finit Solutions SeriesThe Finit Solutions Series
Web Tier Example
‐ 23 ‐

App Tier Example The Finit Solutions SeriesThe Finit Solutions Series
App Tier Example
‐ 24 ‐

Database Tier Example The Finit Solutions SeriesThe Finit Solutions Series
Database Tier Example
‐ 25 ‐

Client Tier Example The Finit Solutions SeriesThe Finit Solutions Series
Client Tier Example
‐ 26 ‐

What is a High Availability environment? How
does it differ from a Disaster & Recovery
i t? Al h d IT d t benvironment? Also why does IT need to be
involved with backups when I could back up my
apps before?

High Availability / Redundancy The Finit Solutions SeriesThe Finit Solutions Series
• An environment built for High Availability means that it is designed to minimize
downtime or potential disruptions to user access.  It is a different focus than
Di & R hi h f i li i b k f
High Availability / Redundancy
Disaster & Recovery which focuses on getting your applications back up for users
after a disaster has occurred.
• Typically, only the Production environment would be designed for High
A il bili d i h D QA i h dAvailability as secondary environments such as Dev, QA, etc can withstand some
downtime and interruptions.
• One of the key items in building an environment for High Availability is to
li i t i l i t f f ileliminate single points of failure.
– Single points of failure mean that a component only exists on one server.  As a result, if that one
server goes down, users would not be able to perform the activities the server enables.
– An example of this would be Financial Reporting. If it is only installed on one server and it goesAn example of this would be Financial Reporting.  If it is only installed on one server and it goes
down, users would not be able to run Financial Reports until the server is back up.
‐ 28 ‐

High Availability / Redundancy The Finit Solutions SeriesThe Finit Solutions Series
• Eliminating single points of failure usually means duplication of servers or
‘Redundancy’.  Unless you have a large deployment, this will mean you will need
f d li i ( di h d d d d)
High Availability / Redundancy
to extra servers for duplication (versus needing them due to expected demand).
• Multiple servers can be linked together through load balancing activities or
through an on / off switch (known as active / passive). Load Balancing spreads
h l d diffthe load onto different servers.
• In Hyperion EPM, load balancing is done either via a hardware device or
internally in product clustering.
– Hardware devices are used for redirecting web activity to different servers.
– Some products, like HFM and FDM, have internal clustering functionality to cluster servers
together.
‐ 29 ‐

Disaster & Recovery The Finit Solutions SeriesThe Finit Solutions Series
• Disaster & Recovery relates to recovering from an error or failure.  This can
apply to both recovering onto the same environment or by recovering onto an
l i i (i Di & R i )
Disaster & Recovery
alternative environment (i.e. a Disaster & Recovery environment).
• With Hyperion EPM, all major data and logs are stored in relational databases
(i.e. SQL, Oracle).  As a result, these databases need to be backed up as they are
h i f i b d h i i T i ll Fithe main source of items to be restored when an issue arises.  Typically Finance
users do not have access to the relational databases and this is where IT support
is required for backing up relational databases and restoring it the appropriate
environmentenvironment.
• Many different strategies for Disaster & Recovery exist.  Here are a few:
– Some clients perform some monthly or quarterly steps to prepare and sync up the Recovery
environment with items like Security, Reports, etc. Then they focus on the true data fromenvironment with items like Security, Reports, etc.  Then they focus on the true data from
applications like HFM or Essbase if a recovery is needed.
– Some clients choose to do ‘real‐time’ synchronizations onto another environment.  In a disaster
they just repoint and reconfigure to the other environment as the data is already there.
Y t t h Di t & R i t b i diff t l ti With
‐ 30 ‐
– You may want to have your Disaster & Recovery environment be in a different location.  With
this, software is needed to help move the database backups to the alternate location.

What are ‘services’?
When IT says they are stopping / starting
services what does that mean?
Why do they have to start in a certain
order?order?

Services The Finit Solutions SeriesThe Finit Solutions Series
Services
• A service is an application type that runs in the background of a
server. Services provide core operating system features, such as
Web serving, event logging, file serving, help and support, printing,
cryptography, and error reporting.
• Most operating system are designed so that only the key services• Most operating system are designed so that only the key services
that are required for common server roles are started.
• Depending on the applications you want to run you can configure
the services associated with those application to start
automatically when your computer / server is turned on.
‐ 32 ‐

Services The Finit Solutions SeriesThe Finit Solutions Series
Services
‐ 33 ‐

Hyperion Services The Finit Solutions SeriesThe Finit Solutions Series
Hyperion Services
• Many Hyperion products have services in them that are required to be
running in order for the applications to function properly.
• These services need to be running on the servers where those products
are installed (i.e. Reporting services run on the Reporting application
server).
• Many of these services communicate with one other as users perform
tasks in the applications and are there fore dependant upon one another
to function correctly.to function correctly.
• Difference between a service and an application process is a service is
always running where as a process is ‘invoked’ and not constant.
M l i l H i i i i li h bili• Multiple Hyperion services exist to give clients the ability to separate
components on different servers. If there was just one big service
everything would have to be installed on one server.
‐ 34 ‐

Stopping and Starting Services The Finit Solutions SeriesThe Finit Solutions Series
Stopping and Starting Services
• Like any other piece of software or hardware there are times
where Hyperion applications don’t behave has expected. Because
Hyperion applications are so interconnected now (i.e. Shared
Services, Reporting, HFM, etc.) the services for each product are
very dependant on one another.very dependant on one another.
• Thus a disruption in the shared services service or connection
could have an impact on other applications and services.
• Because of this it is required to “stop and start” or “restart”
services from time to time.
• This process is similar to rebooting a server or computer but only• This process is similar to rebooting a server or computer but only
involves restarting the services specific to Hyperion.
‐ 35 ‐

Stopping and Starting Services The Finit Solutions SeriesThe Finit Solutions Series
Stopping and Starting Services
‐ 36 ‐

Importance of Order In Services The Finit Solutions SeriesThe Finit Solutions Series
Importance of Order In Services
• Depending on the application and version of the software you are
using the order that the services are started in can be very
important.
• Many of the services are dependant upon other services being
started so if they are not started in the correct order thestarted so if they are not started in the correct order the
applications will not work .
– For Example ‐ in Version 9.3.0 Hyperion Core Services needed to be running
b f th W k S i ld b t t d If l th W kbefore the Workspace Service could be started. If only the Workspace
Service was running users could not log into the applications
• To deal with this many clients will either create scripts or utilities
that they use to control the stopping and starting of services.
• Doesn’t apply to all clients. We’ve seen some that let all their
services start automatically and it doesn’t cause an issue
‐ 37 ‐
services start automatically and it doesn t cause an issue

Why does Rebooting a Server Tend toWhy does Rebooting a Server Tend to
Solve Problems?

Rebooting a Server The Finit Solutions SeriesThe Finit Solutions Series
Rebooting a Server
• Reboot, Bounce, Shut Down, Restart – are all different names for the act
of powering down and restarting a server (Physical or Virtual).
• Just like your own PC a reboot is usually the first line of defense when
applications are not behaving correctly.
• While reboots do sometimes fix issues, they shouldn’t be the IT solution , y
to your problems.
• It’s important to try and identify and address the root cause of the issue
to prevent them from occurring in the futureto prevent them from occurring in the future.
• Most Hyperion Applications and Servers shouldn’t need to be ‘rebooted’
on a frequent basis to function correctly.
• Some Hyperion applications are more memory intensive so reboots do
help to clear that memory and give it a fresh start.
• A reboot does cause all the services to stop so they will need to be
‐ 39 ‐
A reboot does cause all the services to stop so they will need to be
restarted as well.

IT wants to install new Microsoft Updates
// Patches on my Hyperion servers.
Should I let them?

Microsoft Patches The Finit Solutions SeriesThe Finit Solutions Series
Microsoft Patches
• Many Microsoft Patches are required by IT departments to stay in
compliance with Microsoft or to address security or vulnerabilities
in the Microsoft Operating Systems.
• As much as you’d like to say no to IT many times it’s unavoidable or
sometimes it’s required to fix an issue that is causing problemssometimes it s required to fix an issue that is causing problems
with your current environment.
‐ 41 ‐

Microsoft Patches The Finit Solutions SeriesThe Finit Solutions Series
Microsoft Patches
• If IT is going to install Microsoft Patches you should:
– Take Backups of applications and serversTake Backups of applications and servers
• If Virtual Environment this should be easy
• If Physical backup all relevant application files and datay p pp
– Research if the Windows Patches are supported by Oracle
– Test the patches with admin users or select users before p
opening up the application to all users
• This is easier done in a testing environment
– Do isolated patch only changes, don’t try and bundle
application changes with IT changes
If thi it th P t h th l h ?
‐ 42 ‐
• If something goes wrong was it the Patch or the rule change?

IT wants to move our application to new
servers or install the latest operating
system and Office products? Is this okay?

Changing Environment ComponentsThe Finit Solutions SeriesThe Finit Solutions Series
Changing Environment Components
• Just like Oracle, Microsoft continues to introduce new products:
– Windows Server 2008
– Windows 7
– Office 2010
– Internet Explorer 8/9Internet Explorer 8/9
– 64 Bit Processing
• Because Microsoft Products are constantly changing Oracle needs
i k h i d ibl i h htime to make their products compatible with them.
• This compatibility can vary depending on the product and version
of Hyperion you are using.of Hyperion you are using.
‐ 44 ‐

• Oracle provides updates on what 3rd party products their
applications are compatible with:
http://www.oracle.com/technetwork/middleware/downloads/fmw‐
11gr1certmatrix.xls
I dditi d t ti f ll f th i d t i il bl• In addition, documentation for all of their products is available as
well:
http://www.oracle.com/technetwork/middleware/ias/documentationp // / / / /
/index.html
‐ 45 ‐

‐ 46 ‐

• If you are considering upgrading Environment
Components:p
– Take Backups of applications and servers
• If Virtual Environment this should be easyy
• If Physical backup all relevant application files and data
– Research if the Windows Patches are supported by Oracle
– Test the patches with admin or select users before opening
up the application to all users
• This is easier done in a testing environment
‐ 47 ‐

What is a Domain?
What are Native/External users and
groups?
Is Administering Shared Services an IT or
Finance Function?Finance Function?

What is a Security Domain The Finit Solutions SeriesThe Finit Solutions Series
What is a Security Domain
• A security domain is considered to be an application or collection
of applications that all trust a common security token for
authentication, authorization or session management.
– Does the user exist? What is their password?
• A network with a different security domain is kept separate from• A network with a different security domain is kept separate from
other networks.
• Each domain has its own Authentication hierarchy meaning a user
has to exist in that domain in order to be able to log into it.
• Can have 1 or multiple domains within 1 company.
‐ 49 ‐

Native versus External Security The Finit Solutions SeriesThe Finit Solutions Series
Native versus External Security
• Native Security means that users and passwords for an application
are stored in the application directly.
– To deny a user access you must remove them from the application
• External Security means that users and password are not stored in
one application but in one common directory that applications canone application but in one common directory that applications can
use.
– To deny a user access to ALL application you can just remove them from the
E t l A th ti ti GExternal Authentication Group
• Most companies have gone to an External Authentication Security
model where all users are administered centrally and applications y pp
within an organization rely on that external authentication to
control access this provides centralized user controls to enable or
disable a user from all applications
‐ 50 ‐
disable a user from all applications.

Native versus External Security The Finit Solutions SeriesThe Finit Solutions Series
Native versus External Security
• Hyperion application have the ability to use a combination of both
Native and External Users and/or Groups.
• In the EPM products (HFM, Essbase, Planning, etc.) all of our
clients use External Authentication for USERS.
Only exception is Hyperion Enterprise some clients still use Native security– Only exception is Hyperion Enterprise, some clients still use Native security
• In terms of Groups, clients have used both methods to maintain.
– Native Groups – allow HFM administrators the ability to add and remove
users from groups without IT involvement
– External Groups – requires IT to maintain and gives the application admin
less control over security
– In both cases the users security and authentication is external but control of
the group or she belongs to lies with different people
‐ 51 ‐

Who Should Administer Shared ServicesThe Finit Solutions SeriesThe Finit Solutions Series
Who Should Administer Shared Services
• Domains and External Authentication are always maintained by IT
– Example if a new hire needs to be set up at a client that set up is always an IT function
• Hyperion Application Security is typically handled by the
application administrator and administered using external user id’s
but Native Groupsbut Native Groups
– Example: New Hire is set up in External Authentication, but once they are
there the Hyperion Administrator can put that user in the
‘EuropeReportingUser’ group at their choosing. They don’t have to open aEuropeReportingUser group at their choosing. They don t have to open a
ticket with IT to get the user moved between groups.
‐ 52 ‐

Contact

Finit Contacts The Finit Solutions SeriesThe Finit Solutions Series
Questions?
insights@finitsolutions.com
Questions? ‐> Jay Hampton
jhampton@finitsolutions.com
216.870.3657
Email us for a ‐> Ed DeLise
edelise@finitsolutions.com
copy of the slides or
link to the recording
@f
678.296.3611
‐>Joe Mizerk
jmizerk@finitsolutions.com
link to the recording. j @f
919.349.5029
‐ 54 ‐

Finit infrastructure webinar 03212011 master final

Recommended

Recommended

More Related Content

Similar to Finit infrastructure webinar 03212011 master final

Similar to Finit infrastructure webinar 03212011 master final (20)

More from finitsolutions

More from finitsolutions (20)

Recently uploaded

Recently uploaded (20)

Finit infrastructure webinar 03212011 master final