CFG_OIBRW Configuration

Introduction

CFG_OIBRW is another configuration record which is stored in the SYSENV system table. Its purpose is to control how the Banded Report Writer (BRW) connects to OpenInsight (i.e., OpenEngine) and which stored procedure to use as a filter for locating data sources.

Like other configuration records, CFG_OIBRW can be named to be applicable to all applications and users, or limited to a specific application and a specific user. Multiple CFG_OIBRW records can exist in this way, where the more specific configuration will always take precedence over the more generic configurations:

Default Configuration

Each attribute setting within the configuration record will have its own way of resolving default behavior (see the Settings section below for more information), but if no applicable CFG_OIBRW configuration record can be found, then helper routines like CFG_OIBRW Configuration will assume the following settings:

<1> .
<3> *
<4> 0
<5> 0
<6> RTI_BRW_FILTER

Attributes 2, 7, 8, and 9 will be empty.

Settings

The configuration settings for CFG_OIBRW are varied and can cause unexpected behavior if not set up properly. This can be anywhere from the wrong database tables being used versus OpenInsight crashing. Therefore, while the settings information is provided for thoroughness, see the following Recommended Configurations section for examples that will work well. 

Recommended Configurations

As noted above, not all configurations work equally well. Some will cause OpenInsight to crash or leave various processes hanging in the Task Manager. There are three basic options to consider, each one has advantages and disadvantages:

• Direct Connect to In-Process Engine - The advantage of this configuration is that it allows the BRW to have access to dynamically attached tables. It is also faster since it doesn't have to connect to another engine or launch one. The disadvantage of this configuration are the memory leaks which have been reported above. It does not fully support the syntax for multiple reports with a single RTI_BRW_GenerateReport command. Generally speaking, these leaks only manifest when OpenInsight is closed and often only when the Banded Report Designer has been used.
  
  Use this configuration for the quickest implementation setup of the Banded Report Writer:
  

  <1> .
  <2> 
  <3> *
  <4> 0
  <5> 0
  <6> RTI_BRW_FILTER
  <7> 
  <8> 
  <9>  

   

• Direct Connect to a New Engine - The advantage of this configuration is that it is a relatively stable way to launch BRW reports. It also fully supports the syntax for multiple report usage with a single RTI_BRW_GenerateReport command. The disadvantage of this configuration is the lack of access to dynamically attached tables. It also requires an additional user license for the new engine that is launched, although the startup/shutdown flags can be configured to close the engine and release the user license when the report is finished.
  
  Use this configuration for the most balanced setup of the Banded Report Writer:
  

  <1> .
  <2> 
  <3> 
  <4> 65
  <5> 1
  <6> RTI_BRW_FILTER
  <7> 
  <8> 
  <9> 

   

• EngineServer Connection - The advantage of this configuration is that it allows the BRW to offload reports to an EngineServer. This is probably the most stable configuration since all engine management is handled by the EngineServer. This also allows engines used to handling BRW requests to exist on a separate machine. The disadvantages of this configuration is the lack of access to dynamically attached tables. Additional user licenses are also needed, but these can be managed in smaller pools because of the queuing capability of the EngineServer.
  
  Use this configuration for the strongest engine management or for special circumstances setups of the Banded Report Writer.
  

  <1> <URL> (e.g., 10.0.0.15, 127.0.0.1, or localhost)
  <2> <PortNo> (e.g., 8088 or 8089)
  <3> 
  <4> 
  <5> 
  <6> RTI_BRW_FILTER
  <7> 
  <8> 
  <9>