Resources to Protect

Table 16 lists the contexts that must be protected. The syntax for protecting a resource (using interop as an example) for OSSO:

<Location /interop>
Require valid-user
AuthType Basic
order deny,allow
deny from all
allow from myServer.myCompany.com
satisfy any
</Location>

The allow from parameter specifies servers from which the protection of the context can be bypassed.

For EPM Workspace, Financial Reporting, and Web Analysis, you need to set only the parameters indicated in the following example:

</workspace>
Require valid-user
AuthType Basic
</Location>

Table 16. EPM System Resources to Protect

EPM System ProductContext to Protect
Shared Services/interop
Reporting and Analysis Framework

  • /raframework

  • /biplus_webservices

EPM Workspace/workspace
Financial Reporting/hr
Web Analysis/WebAnalysis
Performance Management Architect

  • /awb

  • /hyperion-bpma-server

Planning/HyperionPlanning
Oracle Hyperion Performance Scorecard, Fusion Edition

  • /HPSWebReports

  • /HPSAlerter

Strategic Finance/HSFWebServices
Oracle Integrated Operational Planning, Fusion Edition/interlace
Financial Management

  • /hfm

  • /hfmofficeprovider

  • /hfmlcmserver

  • /hfmsmartviewprovider

  • /hfmapplicationservice

  • /hfmlcmservice

Administration Services/hbrlauncher
FDM/HyperionFDM
Calculation Manager/calcmgr
Oracle Hyperion Provider Services/aps
Profitability and Cost Management/profitability
Oracle Hyperion Financial Close Management/fcc
Disclosure Management[1]

/mappingtool

ERP Integrator/aif

1 Full certificates chain (starting from root certificate) is required on the client machine to support the use of Disclosure Management client with SSL protected web services.