Before using the build script it is important to set up the connection information for the databases and ETL tools. This is set up in the BIBootstrap.properties file which needs to be created in the Reporting\project\properties folder. When running the build script the connection information is obtained from this properties file.
A sample file, called BIBootstrap.propertiessamplexxx, has been provided for guidance. It can be found in the..\Reporting\project\properties folder. This file can be copied and renamed as BIBootstrap.properties as a start point. It must be kept in the same folder.
The following lists the main components in the properties file:
- Database Type - Set this for Oracle (db.type=ORA) or DB2 (db.type=DB2)
- DB2 Source Type - Only set for DB2. The type must be set to UDB if using DB2 Universal Database (db2.source.type=UDB)
- Connection information for the target databases (Source, Staging, Central, Datamarts). The server, database name, username, SID, port number (if applicable) and password must be set. We will use the target database (staging, central, or datamarts) set up in the previous section as the username. Note: For DB2 Central and Staging should be set up on the same database.
- Connection information for the Demo Data database (curamdmdemo). The server, database name, SID, username, port number (if applicable) and password must be set. The Demo Data schema is set up by running the appropriate Build Environment command.
- Design time repository connection information. The server, port (if applicable), database name, username and password and service name (if applicable) should be set. For Oracle we will use the design time repository user previously set up as the username. For DB2 we will use the control database automatically set up as part of the install as the username.
- Run time repository connection information (Oracle Only). The server, port (if applicable), database name, username and password and service name (if applicable) should be set. For Oracle we will use the runtime repository owner previously set up as the username. For DB2 we will use the control database automatically set up as part of the install as the username.
- Password - passwords for Oracle, DB2, WLS and WAS need to be encrypted in the BIBootstrap.properties as follows:
- Open a command prompt from Reporting\components
- Run appbuild encrypt.password -Dpassword=<p> where <p> is the assigned password to be encrypted
- Enter the full encrypted password returned, for example: qqnscP4c4+s== as the password in BIBootstrap.properties