Before using the build script it is important to set the variables for the Build Environment and ETL tools. They are set in the BIApplication.properties file which needs to be created in the Reporting\project\properties folder.
A sample file, called BIApplication.propertiessamplexxx, has been provided for guidance. It can be found in the..\Reporting\project\properties folder. This file can be copied and renamed as BIApplication.properties as a start point. It must be kept in the same folder.
The following lists the main components in the properties file:
- Component Order Warning Level - this is set to Error which means that if the Build Environment gets an Error it will stop processing the last command. If it is changed to Warning then it will carry on processing after getting an error.
- Component Order - If you are just using the CEF Framework then please delete childservices and cgis, leaving core, e.g. component.order=core. If you are using the Child Services Module then set component.order=core, childservices If you are using any of the other Solution Modules CGIS then please refer to the Application Properties section of their Reporting Developer Guides.
- Component.locale.order.installedLanguage - This is the language code for choosing the correct localizations and translations, see Appendix L
- Environment IExplorer URL - This is the path to Microsoft Internet Explorer.
- Environment Variables - This lists the Environment Variable that are used by the Build Environment.
- Environment ResetETL Date - This is used by the Build Environment Targets resetetl.staging, resetetl.central and resetetl.datamarts. It resets all of the Last ETL Dates in each schema Control Table. It should only be used in a Development Environment and not in Production.
- Environment ResetETL Dateformat - this specifies the date format that environment.resetetl.date expects
- Aggmonth - these 3 properties are used by the Build Environment Target transform.aggmonth, they specify the Start Date, End Date and Date Format to be used to load the DM_AGGCASEMONTH fact
- Environment.jdbc.drivers - This is the Oracle driver that BIA Reporting uses, i.e. oracle.jdbc.driver.OracleDriver.
- Environment.jdbc.jars Change the path to point to the specified JAR files, e.g. environment.jdbc.jars=C:\\Oracle\\product\\11.2.0\\db_1\\jdbc\\lib\\ojdbc5.jar Please note that the double back slashes are required to fix a bug. This bug will be removed in the next release.
- Environment.owb.oracleinstalled - Only set this to false if there is no Oracle database on the server where OWB has been installed. Otherwise set this to true.
- Environment.owbconfig.validate.failonwarnings - This will check the oracle ETL's for successful validation. This will fail even if the ETL's validates with warnings.
- Environment.owbconfig.remotedatamanagerdir - If the Data Manager folder is on the local machine then leave it blank or it will cause an error.
If the staging, central and datamart schemas are being created on a remote server then the Data Manager folder and contents will need to be copied to this server after the build staticdata command has been run, refer to Section 6.8.3, Step 12. You then need to set the variable to the path of the Data Manager folder on the remote server, using the java convention for path separators (\\),e.g. Reporting\\bin\\data_manager\\. Please ensure that the trailing \\ is added or it will cause an error.
- Environment.owbconfig.version - Set this to the version of Oracle you are using.
- Environment.owbconfig.version.sourceDB - Set this to the version of Oracle you are using as the source database, e.g. 11.2.
- Environment.owbconfig.exectemplate - Set this to be sqlplus_exec_template.sql.
- Environment.databases.curam.privilages.autogrant - This grants select on all Source Tables to the Staging Schema. See Appendix G. This should be set to false.
- Environment.databases.bi.privilages.autogrant - This grants select on all Staging Tables to the Central Schema. See Appendix G. This should be set to false.
- Environment.databases.curam.updatenulls.autorun - This turns on/off the privilege of granting from Source Applications to Reporting Staging Schemas. See Appendix H. Set this to be false.