Why Use a Shared Connections XML File?

If you manage Oracle EPM for a team, you've probably faced the challenge of getting everyone's Smart View configured correctly. The default approach — each user manually entering connection details — doesn't scale. It creates inconsistency, generates helpdesk tickets, and becomes a maintenance burden every time an environment changes.

The solution is a centrally-hosted XML file that defines all your Smart View connections. Administrators update one file; all users get the changes automatically on their next Smart View launch.

Step-by-Step Setup

Step 1: Create the XML file

The shared connections file follows Oracle's defined XML schema. Here's a minimal example for an Oracle EPM Planning connection:

<?xml version="1.0" encoding="UTF-8"?>
<res_GetProviders>
  <Product id="HP" name="Oracle Hyperion Provider Services">
    <Server name="Planning - Production"
            context="https://your-tenant.pbcs.us2.oraclecloud.com/HyperionPlanning/SmartView"/>
    <Server name="Planning - Test"
            context="https://your-tenant-test.pbcs.us2.oraclecloud.com/HyperionPlanning/SmartView"/>
  </Product>
</res_GetProviders>

Step 2: Host the XML file

Save the file as connections.xml and host it on an internal web server, SharePoint, or any URL accessible by your Smart View users. The URL might look like: https://intranet.yourcompany.com/smartview/connections.xml

Step 3: Configure Smart View clients

In Smart View, go to Options → Advanced → Shared Connections URL and enter the URL to your XML file. This can also be pushed via a registry key for a fully automated deployment.

Step 4: Verify the connection

Open the Smart View panel, click Shared Connections, and you should see your defined servers listed. Users can connect to any server from this list without any manual configuration.

Pro Tips

  • Add both Production and Test environments to the XML — clearly labeled — so users can switch between them easily.
  • If you use EPM Automate or have multiple Oracle tenants, you can include multiple <Product> blocks in one file.
  • Version-control your XML file in Git so you have an audit trail of connection changes.
  • For Vena users, this same pattern can apply to any tool that supports centralized connection strings.

Frequently Asked Questions

What is a Smart View shared connections XML file?
A centrally managed file that defines connection details for multiple Oracle EPM applications. Administrators host it on a web server so all Smart View users pull connections from a single source — no manual configuration needed per user.
Where should I store the XML file?
Host it on any internal web server or SharePoint site accessible by all Smart View users. The URL to the file is configured in Smart View under Options → Shared Connections URL.
Can I push the Shared Connections URL via Group Policy?
Yes. Oracle supports a registry key deployment for the Shared Connections URL, which can be distributed via Group Policy Objects (GPOs) — making it fully automated for enterprise environments.