Custom Environment Parameters
By Tim Dexter on Jan 15, 2010
I have been trying to help out a customer recently with a nasty SSL setup for their BIP instance. Wont get into detail but although BIP is running on an SSL server its not seeing itself as running on it. Links and images in the outputs are not 'https' but rather 'http'. Having got the dev team to dig into their code, it appears to be the web server set up that is at fault.
I came up with an idea to work around the issue for now so that they could move forward with their project while the web server issue is addressed - a custom parameter.
Some of you that have turned debug on might have seen several parameter values going by in the log prefixed with 'xslt.' This is what gave me the idea.
You will need to set up the xdo.cfg file to hold the parameter. It needs to sit in the $JDK_HOME/jre/lib directory. Or under the config directory in the reports repository e.g. XMLP\Admin\Configuration for the standalone release.
Heres the beginning of mine:
<config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/">
<!-- Properties -->
<!-- System level properties -->
<!-- PLEASE SELECT A VALID TEMPFILE DIRECTORY!!! -->
<!-- PDF compression -->
<!-- PDF security -->
<!-- Custom Properties -->
I have a custom property(parameter) SERVER_PROTOCOL. Notice the double quotes surrounding the value, they are a must!
Now in my template I just need to declare the parameter<?param:SERVER_PROTOCOL?>
Notice you dont need the 'xslt.'prefix. Then I can reference the value
Im using this as a workaround in this case but Im sure you will come up with other uses.