Table of Contents

Configuration Management

BI PLUS System Architecture

BI PLUS runs as a Client-Server web-based architecture. Browser sessions request information from the Server, and Server uses BI PLUS repository to pull information from a Database and deliver it to the client via HTTP. From the diagram above, we can see that there are always at least 2 connections involved. One of these connections is always to the BI PLUS Repository database, the other is the target database, which is any SQL compliant database.

Setting up Configuration

Open the Configuration Management dialog by navigating to Admin Menu ⇒ Repository Administration ⇒ Configuration Management.

Now you will see the Configuration Management dialog as shown below.

Configuration Management has the following tabs:

General

General tab supports the following features. Server Home:-

This feature sets the system variable for server home which is used for scheduling, for referencing certain gif’s and other objects that are dependent on a location. For instance, you could set up the Tomcat server on a localhost setting, but if the server is to be referenced by applications across a network, referencing a file at http://localhost:8123/BIPLUS/images/my_image.gif will just not work. However, if the image is referenced as «server-home>/images/my_image.gif by all applications, the file will be found. This is the variable that all calls to BI PLUS should be using for FTP, GIF locations, etc.

Display Name:-

The Display Name is the logical name of the environment that is presented to the user as a drop-down combo box when logging in. You will see that the display name in this environment is set to “BIPlus”, and from the screen shot, you will see that the first value of the combo-box populated is from the first environment listed in BIPLUS.xml file, and the two names match. The user never needs to know the finer details of how the connection is established, any tnsnames properties or database connect strings, these are all set up. If multiple environments are set up in the BIPLUS.properties file, then it is important to have unique names for each of the <display-name> properties for the environments found in BIPLUS.xml, because these are the values that are popped up to the user at run-time during login.

Note: By default Display Name is hidden. You can enable this by making Show Environment to TRUE in Admin → Repository Administration → Configuration Management → Defaults → Overridden Values → Add → Show Environment

Unique Identifier Prefix:-

When we create a report in BI PLUS, every report is given a Unique Identifier, which is displayed on every report itself (in developer mode). The default prefix is UID. One can set their own prefix according to their comfort. The screen shot shows how the prefix appears in a BI PLUS report.

Logging Level:-

When Tomcat is started, for the BI PLUS application, it reads the biplus.xml configuration file to see what level of logging it should produce. The output is sent to multiple log files in the log sub-directory of the application. The available levels of logging are:

  1. Detail: Every type of event can be viewed using Detail log. It also includes development logs.
  2. All: When logging is set to all mode, every single request to Tomcat is displayed in the log file. This is typically used for initial setup, testing, development and debugging. In a production environment with thousands of users hitting the server, you would typically not want the logging level set to “all”, as it will flood the tomcat log and consequently the file systems with an unnecessary amount of data as it logs every call event, most of which will be meaningless in such a highly concurrent environment. All details of every SQL statement are also shown in the log file, which is good for debugging purposes. This logging mode also requires additional disk space to be made available to handle all the logging information that is written to the file system. This does not include development logs.
  3. Debug: Debug information is included in this type of log mode.
  4. Info: When logging is set to “info”, the amount of detail sent to the server is substantially less. Every call to the server is logged with the relevant call request code.
  5. Warn: Warning information only is included in this log mode.
  6. Error: When logging level set to error, messages will be displayed in the Tomcat console log only when some failure occurred, for example “could not connect to database” etc. or some other untrapped error condition or critical bug.

Features

Next tab in Configuration Management is Features. Using feature tab we can hide/display various features.

Login Configuration

Login Configuration tab has following features…

Default login: Set the default Login type .

Admin Timeout: If a session is idle for specified time (minutes) then the session will b e terminated. The default timeout duration is 120 minutes.

Login Types: BIPLUS supports 4 login types.

Single Signon Configuration: Single sign-on (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them. This accepts User Attribute & Domain Attribute provided by network team.

Email Configuration

Admin Email: This is where the system administrator's email should be entered. Any notification from BI PLUS (related scheduler, license key, tomcat, errors) are forwarded to this email address.

Default Domain: If in scheduling a report, you simply specify Bob, Julie, Jack and you have the <default-domain> set to “mycompany.com”, then when BI PLUS finds no ‘@’ in the email , it will translate these email addresses at run-time to: Bob@mycompany.com ; Julie@mycompany.com ; Jack@mycompany.com .

Valid Domain: The list of domains that scheduled reports can be sent to is listed here, with a comma separating the list of various domains.

Domain Validation Required: Enable /Disable whether BIPLUS is to check outgoing email addresses against the list of valid domains.

SMTP Configuration:

POP3 Configuration:

Scheduler

The Scheduler is one of the most powerful features of BIPLUS.

SMS Configuration

Defaults

Defaults tab in Configuration Management dialog has two sub-tabs…

Overridden Value: Overwrite default values for specific attributes.

Existing Value: The current and default values of the various configuration attributes.

There are several features in defaults tab. Let's examine each of these and how they affect BI PLUS.

BIPLUS configuration settings are saved in the biplus.xml file. This file is found at C:\BIPLUS\Tomcat7\webapps\BIPLUS\configuration which is the default location. Open this XML file in WordPad or Notepad or in your favourite editor.