One of the aspects of Smart View that often annoyed me was having to either update the shared connection URL or create private connections when jumping around different applications. At various times I may need to access three or more different applications. Then one day a colleague enlightened me to another way to manage multiple connections. Create an XML file with all the connections and reference that file in the Smart View shared connections field.
Starting with that colleague’s example, I was able to create a file that I can now update as needed. It took some trial and error to get the correct URL syntax for some of the connections.
Here’s the original XML file.
Using the original as my starting point, I changed id, names, and context paths to the connections I wanted. The critical piece is the context path, that needs to be the URL to the application and have the correct syntax for the type of connection (i.e. Essbase, Planning).
That’s a lot to try and decipher, so let me break into smaller screen shots for easier descriptions.
- Product id helps identify the application, it is not visible to the user. Since this is a connection to Essbase, I identified it as such.
- Name is also for reference and not visible to the user. This is true for display/Version, you could use something more descriptive if needed.
- Server name is visible to the user and should be an easy to understand name. This is more important when you have many connections in the XML, it should be easy for users to select the connections they need.
- Context is the URL to the application. The last part of this URL is essbase/SmartView since this is an Essbase connection.
- The Context this next connection ends with is HyperionPlanning/SmartView since it is a Planning connection.
The context differences are important. The URL needs to be accurate to the application and type of application. All the connections I used are for cloud applications, and mostly go to either Essbase or Planning. But I do have some connections to Narrative Reporting, and that context uses epm/SmartView.
Some additional items to point out.
- The XML file must start with the text on lines 1 and 2,
- And must end with the text on line 48.
Once the XML file is created with the connections you want, save it to the user’s computer or a location that users can access. Then open Smart View and go to Options. From the Advanced tab, update the Shared Connection URL field with the path to the XML file.
Now when you go to the Smart View Panel all the connections are available. From Shared Connections, select the connection from the server drop down. The list displays all the friendly names from the XML file.
I’ve been using an XML file for my Smart View connections for several months. Whenever I have a new application to work on, I add it to my file. This gives me easy access to current and past applications without having to change the shared connections URL or decipher various private connections to find the right one. And it also makes it easy to share the XML file with others or use on another computer.
And if you’re wondering what Oracle thinks about this, it’s actually in Smart View documentation. Here’s the link to 220.127.116.11.810 https://docs.oracle.com/applications/smartview/810/SVICF/setting_up_the_shared_connections_xml_file.htm#SVICF-shared_conn_19