Install BI Portal Web Application
7 Create a subdirectory for the Web application below the <tomcat_dir>\webapps\ directory; for example, qadbi.
8 With Tomcat not running, unzip data.zip into the Tomcat webapps subdirectory. To shut down Tomcat, in Windows, go to Start|Administrative Tools|Services and find Apache Tomcat in the list of running services. Right-click on it and choose Stop.
9 Configure Tomcat’s server.xml file, which can be found in the /conf directory of Tomcat. Add the maxPostSize directive, which is case-sensitive, and set it to 0:
<Connector port= 8888
protocol= HTTP/1.1
connectionTimeout= 20000
redirectPort= 8443
maxPostSize= 0 />
Configure BI Portal
10 Copy the XML file <tomcat_dir>\webapps\qadbi\WEB-INF\config\server-config.xml.default to a file named server-config.xml in the same directory.
11 Edit the server-config.xml file to match the values for the configuration parameters to the appropriate values for your environment.
Contents are as follows:
• repository Element:
• dbType. Database platform. Value must be SQL for SQL Server.
• driver. JDBC driver to be loaded at runtime for business intelligence server database. For SQL Server, the value is com.microsoft.sqlserver.jdbc.SQLServerDriver.
• jdbcUrl. JDBC URL to connect to Business Intelligence Portal database.
• user. User name for the database. Note that the BI Portal requires a SQL Server login; it cannot use a Windows login to authenticate itself.
• pwd. Password for the database.
• logCheckInterval. How often, in minutes, the portal performs its maintenance tasks; for instance, log the system state, clean up logs, and so on. Default is 15 minutes.
• logDaysToKeepEvents. Number of days to store system events in the database; aw_evt_system and aw_evt_request tables. Default is 14 days.
• log Element:
• watch. Whether to watch the log file for changes and update log4j settings dynamically; true or false.
• configFile. The name of the log4j configuration file.
• Example contents of the server-config.xml file:
<root>
<repository
dbType=SQL driver=com.microsoft.sqlserver.jdbc.SQLServerDriver jdbcUrl=jdbc:sqlserver://myhost:1433;database=QAD_PORTAL user=myuser password=mypwd
logCheckInterval=15
logDaysToKeepEvents=14 />
<log watch=true configFile=LoggerConfig.properties />
</root>
Configure log4j in LoggerConfig File
12 Copy the file <tomcat_dir>\webapps\qadbi\WEB- INF\config\ LoggerConfig.properties.default to a file named LoggerConfig.properties in the same directory. Edit the Log4j configuration file to specify a path for the log file that is the R1 appender defined in the properties file. If you are running Tomcat as a Windows Service, the log file name must be a full path, and the backslashes must be escaped; for example,
log4j.appender.R1.File=D:\\apache-tomcat-6.0.20\\logs\\qadbi.log
Install BI Portal Repository
13 Connect to the SQL Server database where BI Portal Repository is to reside, using the SQL tool of choice.
14 Locate the BI DDL script in the <tomcat_dir>\webapps\qadbi\install\sqlserver file.
15 Run the bi3_ddl.sql SQL script to create required repository tables.
Note: This script drops the tables first if they exist and re-creates them. Make sure that you are running this script in the correct database.
16 Edit the seed script seed.sql to set any variables to the specific values necessary for your installation.
a Set the e-mail address for the initial root user to the e-mail address of the application administrator. If necessary, customize the authorization roles, which are the values being entered into aw_auth_role table and into aw_user_auth_role for the initial root user. Do not modify any of the aw_app_role descriptions. The aw_data_role table, as well as the data_role column in aw_user, are no longer used.
b Set the different aw_sys_config entries as follows:
• DATASERVICE. Configure with the information required to connect to the DWD data warehouse. This includes the dbType (SQL), whSchema (the name of the database owner—typically dbo for SQL Server), the jdbcDriver and jdbcURL, jdbcUser, and jdbcPassword for accessing the database, and the metadataAdapter (com.awbi.server.data.adapter.WhereScapeAdapter). For example:
<dataConfig dbType= SQL whSchema= dbo
jdbcDriver=
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbcURL= jdbc:sqlserver://myhost:1433;database=QAD_DW jdbcUser= myuser jdbcPassword= mypwd
metadataAdapter= com.awbi.server.data.adapter.WhereScapeAdapter />
• WELCOME_EMAIL. Customize the text that is contained in the Welcome E-mail sent to new users. Make sure that the link to the BI Portal Web application is correct for your environment.
• SMTP and MAILER. Configure this with your specific mail server parameters.
• USERSERVICE. Customize the text that is used in the Subject of the Welcome and Password Change e-mails as desired.
• PWD_RESET_EMAIL. Customize the text that is contained in the Password
• Reset e-mails sent to users who request a new password.
• SECSERVICE. Do not edit; security models are built in the Administration UI.
• AUTHSERVICE. If a custom authentication class is used, set the custom authClass to the customized authorization class and uncomment this section. Otherwise, leave this section commented out.
17 Run the modified seed.sql script against your database to load the data into your portal database.
Install Portal Constraint Tables in Data Warehouse
18 Connect to the database in which the data warehouse is to reside. This is the database specified in the DATASERVICE key. Locate the bi3_wh_ddl.sql script in the <tomcat_dir>\webapps\qadbi\install\sqlserver directory. Run the bi3_wh_ddl.sql SQL script to create the required portal tables in the data warehouse database.
Getting Started in the BI Portal Web Application
The initial login is root, with a password of root. You are required to change the password immediately.
19 You must build your model before you can do any analysis. Select Administration|Model Administration and then click Rebuild Master.