Intellicus Enterprise Reporting and Business Insights 18.1

Configuring Database Connections

0 views June 28, 2020 0

Intellicus Server supports multiple database connections.  A database connection needs to be configured for Intellicus to fetch data for reports and to access metadata.

You need to have Super Administrator privileges to be able to setup database connections.

To get to the Database connections page, click Navigate > Administration > Configure > Databases.

Connection Configuration
Figure 1: Connection Configuration page

If Intellicus is running under security disabled mode, specify the following URL in the browser’s address bar to get this page.

If you are using the computer that acts as web server,

http://localhost:<portnumber>/intellicus/pattern/conf and then click Databases tab

In other cases,

http://<IP of the server:port number>/Intellicus/pattern/conf and then click Databases tab

The underneath table mentions properties common to most connections in application.

Property Values Comments
Connection Name Type Yourself Name of the database connection
Provider Select from list Data provider used for the connection
Max Rows Type Yourself Specify the maximum number of rows to be fetched from dataset
Username Type Yourself Username used to open the connection
Password Type Yourself Password for the connection

Blank= If user name and password is not required to connect to the database.

Runtime= To provide username and password when he/she tries to access database (for example, to generate a report or to open SQL Editor, etc.).

Connection String Auto generated Connection String to connect to database
Mask Connection String Check/Uncheck If checked connection string is masked
Charset Encoding Select from list Select UTF-8 if the database is created or started with UTF-8 encoding. Otherwise, it is blank
Is Default Check/Uncheck Check this checkbox to use this connection as the application default data connection to fetch report data
Is Repository Check/Uncheck Check this checkbox to use this repository as the application default repository to fetch meta data
Is Staging Check/Uncheck Check this checkbox to use staging database (in case of H2 database) to store intermediate results for optimization purpose
Read Only Check/Uncheck Check this checkbox to make sure only SQLs having read operations are executed on this connection
Pool Settings

 

Initial Connection(s) Type Yourself Specify the number of connections that should be opened initially.

Default: 5

Incremental Size Type Yourself Specify the number of connections to open when the all open connections are consumed.

Default: 5

Resubmit Time Type Yourself Specify the waiting-time in seconds before generating re-submitting request. Default: 30 seconds
Max. Connections Type Yourself Specify the maximum number of connections that can be opened to the selected database at a time.

Default: 30

Database Time Zone Select from list Select time zone to receive output of date / time fields as per time zone in which the data was entered in database
Get Configuration File Click the button You can get the configuration file of Report Server in either Encrypted or Unencrypted format.
Cache Enable Metadata Caching Check/Uncheck Check = The list of table names with column names (or other data source objects) from this connection will be pulled and stored locally for populating in SQL Editor or respective Query designer screens.
MetaData Cache Purge Frequency Select from list MetaData Cache Purge Frequency defines the time when metadata (table names, field names, etc.) cached for the selected connection should be deleted and refreshed:

NEVER = application will never delete and refresh the metadata.

BOOTUP= If this is set to Boot Up, every time server is booted, metadata for this data connection will be deleted and refreshed.

On this screen, you can

  • Add a new database connection
  • Update an existing database connection
  • Remove an existing database connection
  • Test a database connection’s validity

Action Buttons

  • Add: To start configuring a new connection.
  • Modify: To modify selected connection.
  • Delete: To delete selected connection.
  • Refresh Schema: To manually refresh schema of the selected connection.

Finding a Connection

List of connections can be filtered based on:

  • Starting characters (Starts with)
  • Characters that appear anywhere in the connection name (Contains)

filter connections filter connections
Figure 2: Filtering list of Connections

To filter the list of connections, you need to follow the below steps:

  1. Under Connections on the left panel of the screen, you can see the search icon search icon .
  2. Click arrow icon and select either Starts with or Contains option.
  3. Specify character(s) that you wish to search in the textbox.

The list will be filtered (not case sensitive) as per the criteria.

Adding Database Connections

To add a new connection from a data source, you need to follow the steps as mentioned below.

  1. Click Add
  2. In Connection Name entry box, specify name of the new connection.
  3. In respective entry boxes, specify information for new connection depending upon the chosen Provider.
  4. Optionally, click Test button to test the validity of the connection detail.
  5. Click Save

The new connection is set.

Add database connection
Figure 3: Adding a database connection

Provider specific details for Database Connections

When you select a provider from the list, text boxes specific to the selection are made available on screen. The following tables list the properties specific to various providers supported in Intellicus.

BIG DATA
ASTERDATA
Property Values Comments
Host Type Yourself The IP or name of the machine where database is installed
Port Type Yourself The port at which database server listens
Database Type Yourself The name of the database to connect to
CASSANDRA
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Keyspace Type Yourself The keyspace is a container for your application data
ELASTICSEARCH
Property Values Comments
Server Type Yourself The IP or name of the machine where Elasticsearch server is running
Port Type Yourself The port at which Elasticsearch server is listening
Index Type Yourself An index is a collection of documents that have some similar characteristics
GREENPLUM
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
SID Type Yourself This is a unique name that identifies a specific database from number of databases on a server
HADOOP CLUSTER

Copy all libraries from Hadoop and Hadoop\lib folders and place them at <Intellicus_Install>\ReportEngine\lib\HADOOP_COMMON\version-specific folder. You should modify run.sh file to point to your Hadoop version. Restart the Intellicus Report Server before creating the connection.

Property Values Comments
Driver Version Select from the list Version of Hadoop Cluster
Job Tracker Server Type Yourself IP address of Job Tracker Server
Job Tracker Port Type Yourself Port of Job Tracker Server
HDFS Server Type Yourself IP address of HDFS named node
HDFS Port Type Yourself Named node Port
Location Type Yourself Default path for the connection on this HDFS
Group Type Yourself User group on HDFS

 

Temp Path

(Optional)

Type Yourself Path to keep the temporary files on HDFS
Extra Arguments

(Optional)

Type Yourself Any extra set of arguments that are required while executing map reduce job on this connection

 

HBASE

Copy all libraries from HBase and Hbase\lib folders and place them at <Intellicus_Install>\ReportEngine\lib\Hbase\version-specific folder. Modify run.sh file to point to your Hbase version and restart the Intellicus Report Server before creating the connection.

Property Values Comments
Zookeeper Server Type Yourself IP address of Zookeeper Server
Zookeeper Port Type Yourself Port of Zookeeper Server
HIVE

You need to download the driver and place it in <Intellicus_Install>\ReportEngine\lib\HIVE folder.

Select Hive if your data is stored on hadoop.

Property Values Comments
Driver Version Select from the list Version of HIVE
Host Type Yourself The IP or name of the machine where database is installed
Port Type Yourself The port at which database server listens
Database Type Yourself The name of the database to connect to
IMPALA

You need to download the driver and place it in <Intellicus_Install>\ReportEngine\lib\IMPALA folder.

Property Values Comments
Driver Version Select from the list Version of IMPALA
Host Type Yourself The IP or name of the machine where database is installed
Port Type Yourself The port at which database server listens
Database Type Yourself The name of the database to connect to
MONGODB
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Keyspace Type Yourself The keyspace is a container for your application data
TERADATA

You need to download driver and place it at \ReportEngine\lib\TERADATA.

Property Values Comments
Driver Version Select from the list Version of TERADATA
Host Type Yourself The IP or name of the machine where database is installed
Database Type Yourself The name of the database to connect to
VERTICA

You need to download driver and place it in \ReportEngine\lib\VERTICA folder.

Property Values Comments
Host Type Yourself The IP or name of the machine where database is installed
Port Type Yourself The port at which database server is listening
Database Type Yourself The name of the database to connect to using this connection
Schema (optional) Type Yourself The schema to be used for a specified user for this database connection
CLOUD
AMAZONEC2
Property Values Comments
Access Key Type Yourself Access Key ID identifies you as the party responsible for service requests. You include it in each request
Secret Key Type Yourself Each Access Key ID has a Secret Access Key associated with it. This key is just a long string of characters that you use to calculate the digital signature that you include in the request
Bucket Type Yourself Any object that needs to be stored in Amazon EC2 is organized into buckets
FILES/STREAM
File Location

You can configure a file location such as FTP, Shared Network Folder, Local Folder, HTTP location, HDFS or Amazon S3 as a connection in report server.

Then Data Administrators can use this connection to pull data files from these locations, as if, they are pulling tables’ data from an RDBMS connection.

This model enables access control security and enables abstraction of the file source to the other users beyond System Administrator.

Common Properties
Connection Name Type Yourself You and end users will identify this connection by this name.
Provider FILES/STREAM Fixed value for connecting to File systems
Driver Type NETWORKPATH,

FTP,

HTTP,

HDFS,

S3,

MAPR-M5,

KAFKA,

SAX,

GOOGLE SHEET

Details are given below
NETWORK PATH
Property Values Comments
Location Network path starting with \\, E:\, or

..\

 

\\ = a network location address follows

E:\ = You are configuring a local drive (local to report server machine) absolute path as location

..\ = You are configuring a local drive path relative to \reportengine\bin as location.

Username Type Yourself OS Username
Password Type Yourself OS password
FTP
Property Values Comments
Server FTP server name of IP address Internet address of FTP Server
Port Port number The port at which FTP server is listening
Secure Yes/No Yes=SFTP (Secured FTP)

No = Normal FTP

Passive Yes/No Yes = PASV mode

Required when there is a firewall between report server and FTP server

Location Type Yourself Folder path from home or root (whichever is applicable) under which required data files are available
Username Type Yourself FTP Username
Password Type Yourself FTP password
HTTP
Property Values Comments
URI Type Yourself Website address
Location Type Yourself Application + path suffixing the web address
Secure Yes/No Yes = HTTPS
HDFS
Property Values Comments
Server Type Yourself IP address of HDFS named node
Port Type Yourself Named node Port
Location Type Yourself

(Optional)

Default path for the connection on this HDFS

Blank = location is root

Group Type Yourself User group on HDFS
User name Type Yourself User name on HDFS
S3
Property Values Comments
Access Key Type Yourself Key Value obtained from Amazon
Secret Key Type Yourself Key Value obtained from Amazon
Bucket Type Yourself Bucket Name where data files will be available
GOOGLE SHEET

Intellicus has added Google Sheet as a data source to access data under your Google spreadsheet. You need to follow the below steps to get Service Account (client email), Private Key, Client Id, Client Secret required for creating a connection in Intellicus.

  1. Go to https://console.developers.google.com/ and login with your Google account’s credentials.
  2. Create a new Project.
  3. Go to Dashboard > Enable API to enable Drive API and Sheets API.
  4. Click Credentials to create a Service account key.
  5. Next, create OAuth client Id. Click Configure Consent screen to give your product name and save it.
  6. Choose Other as Application Type and give a name to it.
  7. You can now download the credentials that are required to create a connection in Intellicus as shown in the table below.
Property Values Comments
Service Account Type Yourself Key used to enable server to server authentication
Private Key Type Yourself Key Value obtained from Google
Client ID Type Yourself Client ID Value obtained from Google
Client Secret Type Yourself Secret Key Value obtained from Google
Username Type Yourself Username of the Google account
Password Type Yourself Password of the Google account
WEB SERVICE

Web Service
Figure 4: Web Service

Provide the following properties to create a connection to a web service:

Property Values Comments
Connection Name Type Yourself To identify the connection by this name
Provider WEBSERVICE Select this option to connect to SOAP enabled web services
Authentication Mode None

 

Soap Authentication

 

 

Basic Authentication

No authentication is required

 

The application uses the username and password in the SOAP header request to authenticate the web service

 

The application directly uses the username and password to authenticate the web service

WSDL URI Type Yourself The URI path of your web service’s WSDL file
OBJECT DB
CACHEDB
 Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Namespace Type Yourself This is a unique name that identifies a specific namespace on CACHE database
RDBMS
CUSTOM JDBC

Select this provider when you use non-SQL way to access from data source.

Property Values Comments
Driver Class Name Type Yourself Specify the driver class name for the driver
DB2
Property Values Comments
System Type Yourself The IP or name of the machine where database server is running
Port Type Yourself

 

The port at which database server is listening
Database Type Yourself Specify name of the database to connect to using this connection
Schema (optional) Type Yourself The schema to be used for a specified user for this database connection
H2
Property Values Comments
Path Type Yourself The path (including the file name) to the location where database file is available
H2 (Embedded)
Property Values Comments
Path Type Yourself The path (including the file name) to the location where database file is available
H2 (Standalone)
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Path Type Yourself The path to the folder where database files are residing
MSSQL
Property Values Comments
Driver Version Select from the list Select the driver version of MSSQL Database to connect to using this connection
Authentication Mode Select from the list Select Server Authentication if you want the Database server should authenticate.  You need to provide user name and password for the database.

Select Windows Authentication to use the credentials used for windows authentication.  In this case, Windows user name and password used to log into the machine where Intellicus report server is running will be used for authentication

Driver Type Select from the list Select Microsoft or JTDS based on the driver you want system to use
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Database Type Yourself Specify name of the database to connect to using this connection
SSL Check/Uncheck In case of forced encryption at the database server, you can check the SSL option to enable you to connect
Domain Type Yourself Specify the name of the network domain .(Domain is asked when you select Authentication Mode as Windows and Driver Type as JTDS)
Instance Type Yourself

 

Specify the name of the instance with which you want to connect
MYSQL

You need to download the driver and place it in <Intellicus_Install>\ReportEngine\lib\MYSQL folder.

Property Values Comments
Driver Version Select from the list Select the desired driver version for MYSQL
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Fetch size Type Yourself Specify -1 to receive one by one record as a stream. This is good if you have a very large recordset.  Leave it blank to receive entire recordset at a time
SID Type Yourself This is a unique name that identifies a specific database from number of databases on a server
ODBC
Property Values Comments
DSN Type Yourself Specify the System DSN created for the ODBC connection
ORACLE
Property Values Comments
Driver Type Select from the list Select one of the drivers you are using to connect to the database
Driver Version Select from the list From options, select the driver version
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself

 

The port at which database server is listening
SID Type Yourself This is a unique name that identifies a specific database from number of databases on a server
ORACLE_THIN
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
SID Type Yourself This is a unique name that identifies a specific database from number of databases on a server
OTHERS

Note: Before specifying driver details for OTHERS connection, you need to add respective driver using Add Driver button on Databases page.

Property Values Comments
Driver Class Name Type Yourself The class name for the driver
POSTGRES
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself

 

The port at which database server is listening
SID Type Yourself This is a unique name that identifies a specific database from number of databases on a server

 Note: If you are using a database that is derived from PostgreSQL, (for example, EnterpriseDB) select POSTGRES as database provider.

SQLLITE
Property Values Comments
Path Type Yourself Path of the database files
SYBASE
Property Values Comments
Driver Type Select from the list Select the driver type to be used to connect with this database
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Database Type Yourself The name of the database to connect to using this connection
SAP HANA
Property Values Comments
Server Type Yourself The IP or name of the machine where database server is running
Port Type Yourself The port at which database server is listening
Database Type Yourself The name of the database to connect to using this connection
Fetch size Type Yourself Specify 1 to receive records one by one as a stream. This is useful when you have a very large recordset. Leave it blank to receive entire recordset at a time
Max Rows Type Yourself Specify the maximum number of rows to be fetched from dataset
SOCIAL MEDIA
TWITTER

Intellicus has added Twitter as a data source to fetch and analyze your Twitter account’s data. You need to follow the below steps to get App ID, App Secret, Token, Token Secret required for creating a connection in Intellicus.

  1. Go to https://apps.twitter.com/app/new/  and login with your Twitter account’s credentials.
  2. Create a new application to get App ID and App Secret.
  3. Go to Keys and Access Tokens to Access Token, Access Token Secret.
  4. You can now download the credentials that are required to create a connection in Intellicus as shown in the table below.
Property Values Comments
App ID Type Yourself Key to identify the application on server (Twitter)
App Secret Type Yourself API Secret Value obtained from Twitter
Token Type Yourself Access token can be used to make API requests to the server
Token Secret Type Yourself Secret Key Value obtained from Twitter
DATA SCIENCE

Creating connection to R Data Science Engine requires a prerequisite file system based connection. This connection’s file location helps as a shared location to exchange data between Intellicus and R server.

When you create connection to the Data Science Engine, you need to provide the file connection location created above under Dump Connection Name field.

Data Science Engine
Figure 5: Data Science Engine

Provide the following properties to create a connection to external R server (Rserve):

Property Values Comments
Connection Name Type Yourself To identify the connection by this name
Provider DATA SCIENCE ENGINE Select this option to connect to Data Science platform
Server Type Yourself The IP or name of the machine where R server is running
Port Type Yourself The port at which R server is listening
Dump Connection Name Type Yourself The file system connection that is accessible to both R server and Intellicus Report Server for storing temporary data
Rows To Dump While Verification Type Yourself Number of rows of the dummy dataset to be dumped during syntactical verification of R script

Miscellaneous Actions

Upload a new database driver

If the provider you are looking for is not listed in the Provider dropdown but you have its library files, click Add Driver button on top-right corner to add respective driver files (if not added already). You need to then select ‘Others’ option in Provider. In this case you will also have to specify Driver Class Name.

Add Driver dialog
Figure 6: Add Driver dialog box

To add a driver you need to:

  1. Click Add Driver button to open Add Driver dialog box.
  2. In Driver File entry box, specify the driver file name along with the path or simply browse the driver file.
  3. Click Upload
  4. The file will be updated and success message will appear.  Failure message will appear in case driver could not be uploaded.
  5. Click Close button to close the dialog box.

Note: You need to restart Report Engine for the added driver(s).

OCI and OCI_TNS connections on Solaris

Before creating OCI and OCI_TNS connections on Solaris, make sure the machine has Oracle client installed and Oracle Client library file (libocijdbc9.so) is set in PATH environment variable (LD_LIBRARY_PATH).

To set the file PATH,

  1. Open run.sh file in vi editor. This file is located at <Install>/reportengine/bin

    Append  <OracleHome>/OraHome1/lib32  path like:

    LD_LIBRARY_PATH=$JRE_HOME/lib:$JRE_HOME/lib/sparc/server:$JRE_HOME/lib/sparc:/export/home/oracle/OraHome1/lib32

  1. Save the file run.sh
  2. Restart Intellicus server

Note: While creating an OCI connection with Oracle 8 or above, remove the number 8 from connection URL created automatically in Intellicus.  For example, change URL from jdbc:oracle:oci8:@tns_name to jdbc:oracle:oci:@tns_name.

Connect using Oracle client installed on Windows

Intellicus recommends Oracle JDBC THIN connections for smooth and compatible access to Oracle Databases of various versions – 8, 9, 10, 11g or 12c.

Intellicus also supports OCI_TNS (Oracle Call Interface Net Service Names) for those who want to use their Oracle client installations to connect to Oracle databases.

If Oracle client is not installed on report server machine, then Intellicus chooses to use ojdbc14.jar, for THIN connections.

If the report server machine has Oracle client installed, then Intellicus chooses to use classes12.zip, assuming that client is compatible with the server version being connected to.

Intellicus allows Administrator to decide which driver Intellicus should use by following the below mentioned steps.

Steps to make changes in Report Engine loader batch file are as below:

  1. Open the file from path

    <install dir>/ReportEngine/bin/run.bat

  1. Add the highlighted line to the file:

    @echo off

    set JRE_HOME=..\..\jre

    set ORACLE_DRIVER=..\lib\ojdbc14.jar

    set PATH=”.”;%JRE_HOME%\bin;%JRE_HOME%\lib;%JRE_HOME%\bin\server;%PATH%

    SET INTELLICA_CLASSPATH=

    FOR %%i in (“..\lib\*.jar”) DO CALL includelib %%i notIncludeIEngine

    FOR %%i in (“..\lib\*.ZIP”) DO CALL includelib %%i notIncludeIEngine

    iEngine –oracledriver%ORACLE_DRIVER%%INTELLICA_CLASSPATH% “../config/ReportEngine.properties” -Xms20M -Xmx128M

    In the batch file, a variable is being set to the name & path of the oracle driver we wish Intellicus to use.

    set ORACLE_DRIVER=..\lib\ojdbc14.jar

  1. Change the iEngine calling line to pass the variable.

    iEngine -oracledriver%ORACLE_DRIVER%%INTELLICA_CLASSPATH% “../config/ReportEngine.properties” -Xms20M -Xmx128M

    The above example forces Intellicus to use ojdbc14.jar driver for Oracle connections.

Note: Intellicus can use only one type of Oracle driver, so cannot make connections to various server versions, if it needs different drivers.

Warning: If due to Oracle client version or due to administrator decision, classes12.zip is used for connections then there might be some problems in activities like publishing or emailing a report having large number of parameters.

Warning: When ojdbc14.jar is forcefully used on machines with Oracle 8 or 9 client installs, then, OCI_TNS type of connections cannot be created.

Test connection’s validity

Follow the below steps to check the connection validity on Databases tab of Configure page:

  1. Select the connection by clicking on the connection name in the table. The information set up for the selected connection appears in respective entry boxes.
  2. Click Modify
  3. Click Test

If the selected connection is valid, Connection Test Succeeded message will appear.

Update connection details

You can update connection details by following the below steps on Databases tab of Configure page:

  1. Select the connection by clicking on a connection name in the table.
  2. Click Modify The information set up for the selected connection appears in respective entry boxes.
  3. Specify new information where required.
  4. Optionally, click Test button to test the validity of the connection detail.
  5. Click Save
Remove a connection

To remove a connection follow the below steps on Databases tab of Configure page:

  1. Select the connection by clicking on a connection name in the table. The information set up for the selected connection appears in respective entry boxes.
  2. Click Delete A dialog confirming delete operation appears.
  3. Click OK to proceed with the deletion.
Refresh metadata cache

Metadata is cached when a database connection is created.  It is refreshed depending on value set in MetaData Cache Purge Frequency.  To refresh the metadata manually, select the data connection and click Refresh Schema button.  On Confirm Refresh dialog, click Yes to proceed.  A message ‘A request for refreshing (name of the connection) schema has been sent to the Report Server’ will be displayed.

Deciding the preference of connections for a report run

The data that user gets on a report is fetch from a database using a data connection.  Based on the edition of Intellicus and license, you can set one or more data connection in Intellicus.

Database (data connection) to be used to run reports can be set in following ways:

  • While actually running the report.
  • While specifying just after login into Intellicus (at session level). This remains default for any type of database use (report running, running queries, etc.).
  • By setting up on User Preferences
  • By specifying it as a part of Report Details (while uploading a report through portal or through cab).
  • By specifying it in while designing the report (IRL file).
  • By specifying a default data connection.

When a report is being run, Intellicus will use the data connection in following order:

  1. Use the data connection that was selected while actually running the report from Report Delivery Options
  2. If the connection was not selected on Report Delivery Options page, use the database connection selected at the time of login into Intellicus (session level).
  3. If the connection was not selected while login, use the connection selected on User Preferences
  4. If a connection is not selected on User Preferences page, use the connection selected while deploying the report (report details).
  5. If a connection is not selected as report details, use the connection selected while designing the report (irl file).
  6. If a connection is not selected in the irl file, use the default connection set in Intellicus on Connection Configuration
Changing the order of preference

Order is controlled by values specified in <CONNECTIONPRIOIRTY> tag in ProviderInfo.xml located at path:

<installation path>\Intellicus\ReportEngine\Config .

Values (and the default sequence) are:

  • CALLBACK: Connection set on Report Delivery Options page.
  • SESSION: Connection set from the home page of Intellicus.
  • USERPREFERENCE: Connection set on user preference page.
  • REPORTDEPLOYMENT: Connection set at the time of report deployment.
  • NAMEDCONNECTION: Connection set during report design.
  • DEFAULT: Connection set as default on Database page of Intellicus.

To change the order, change the order of appearance of above values in CONNECTIONPRIORITY tag.  This tag is the last tag in the file.

For example, default order:

<CONNECTIONPRIOIRTY>CALLBACK, SESSION, USERPREFERENCE, REPORTDEPLOYMENT, NAMEDCONNECTION, DEFAULT</CONNECTIONPRIOIRTY>

Modified order:

<CONNECTIONPRIOIRTY> SESSION, CALLBACK, USERPREFERENCE, REPORTDEPLOYMENT, NAMEDCONNECTION, DEFAULT</CONNECTIONPRIOIRTY>