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 and BIApplication.properties files which are in the Reporting\project\properties folder (note: both of these files should be setup during the installation process but they should be checked before using the build script). When running the build script the connection information is obtained from the BIBootstrap.properties file.
A sample properties file is provided with the Reporting solution. To change the connection information please refer to Appendix A. Security details for the BIBootstrap.properties file is provided in Appendix N
Now that the databases, ETL tools, and 2 property files have been created and configured the developer can use the build script to populate the metadata.
The build script is used by calling build.bat in the Reporting\components folder. Executing build commands in the components folder will build all platform and all component artifacts. If you want to build all installed components then you must first set the component order property in the BIApplication.properties file.
The component.order property must be set listing the installed components, for example if you have a Cúram Child ServicesCúram Child Services (CCS) component installed you must set this property accordingly component.order=core,childservices
Some examples:
To build all Cúram Enterprise FrameworkCúram Enterprise Framework (CEF) and CCS artifacts the build commands must be executed from the components directory. For example if you needed to rebuild all tables, then run build database.all from the components directory.
However if you require to only build the CCS artifacts then you can run the build commands from the components\childservices directory. For example, if you only wanted to drop and re-create the CCS tables, then you would run the command build database.all from the components\childservices folder. To get a list to the build commands enter buildhelp.
After running this command the developer is presented with a list of commands with their description. These commands can be run by typing 'build x' where x is one of the commands that are listed and described in Appendix B.