Select Page

Art of BI: Print Options Customization Settings for BITeamwork

Christian Screen | | November 26, 2015

In the 3.8.1 version of BITeamwork, we’ve provided a new approach using JSON to provide a very seldom used configuration option to those implementations that need special SSL Print Functionality. A good use case for this is for implementations that are using SSL and have a custom SSL handler or if they wish to create a delay for printing for users which may be required as a result of using a VPN or any other restrictive browser latency control at the client level.  With this new approach for on the fly configuration, we plan to expand this to other areas of BITeamwork and the BITeamwork API in order to provide more seamless integration points within the BITeamwork framework.

var bitwprintoptions = { isUsingSunHttps:false, clientUseWait:true, clientWaitMS:3000 };

Then in the $.teamwork.. function, append to the end of the list of arguments within the curly brackets, the following snippet after the last double quotes:


The example shown here is to create a JS variable as a simple JavaScript object, and then to add one or more of the properties associated with the object which follows the BITeamwork naming convention.  Here the BITeamwork object configuration, bitwPrintOutput has the attributes of isUsingSunHttps, clientUseWait, and clientWaitMS.

  • isUsingSunHttps: [true | false]
    • Determines if system is using the -DSunHttpsHanlder switch. BITeamwork assumes true by default. Change to false if unable to correctly follow the instructions in this blog post on SSL Printing Configuration.
  • clientUseWait:  [true | false]
    • If isUsingSunHttps is set to true then rendering of some images takes place on the client browser.  This should be set to true if your users connect through VPN or experience any latency in general or believe images are missing from a PDF print output.
  • clientWaitMS: [integer]
    • If the clientUseWait attribute is set to true then this will be the number of milliseconds that the client’s browser will wait to render the images necessary for print output. There is no default, so a number from 0 – 10000 is recommended to be the range of acceptability. In our demonstrations of this solution we use 3000 (equivalent to 3 seconds).

It is then passed into the biteamwork plug-in startup method as a parameter of the start-up objects as $.teamwork…, is called by the browser rendering.

Save the core custom messages XML file and restart the presentation services in order to see the changes reflected in the BI Portal.

Be sure that if the settings are not needed that you either remove the argument from the $teamwork… function or you maintain the bitwprintoptions variable in the code but comment it out (using two forward slashes at the beginning of the line) and replace it with an empty JSON object, resulting in the following:

var bitwprintoptions = {};
//var bitwprintoptions = { isUsingSunHttps:false, clientUseWait:true, clientWaitMS:3000 };

More Understanding

One of our customers asked why this process is necessary as they were not fully educated to the workflow of how OBIEE is architected. This issue circumvention mainly occurs as a WebLogic configuration default issue. When OBIEE uses its native print functionality, the print command is essentially passed to the OBIEE server (OBIS) service which in OBIEE 11g is managed by the OPMN system. Since this not part of WebLogic directly this issue is irrelevant to native OBIEE printing, though its printing output is less sophisticated compared to BITeamwork print output capability. BITeamwork is an application deployed directly into WebLogic as a deployed application and therefore abides by many of WebLogics constraints. When the BITeamwork print command is run, the logic routes through the WebLogic Application server and back down to the presentation layer of OBIEE. When OBIEE 4.1 is released, it will contain a BITeamwork Server side component which will allow this particular issue to be a non-issue similar to how the OBI Server Component doesn’t have this issue today.

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

Oracle EPM Cloud Vs. On-Premises: What’s the Difference?

EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.

Bobby Ellis | April 10, 2018

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.


Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.