rh._.exports({"0":[[" ","Customizing a Build Server"]],"1":[[" ","Customizing \n a Build Server"," ","This appendix describes parameters that \n control the function of the build server applet running in the web server. \n You can customize these parameters to change the behavior of the build \n server to meet your specific needs. The parameters are located in the \n following file on the primary build server."," ","<dm_root>/Common Tools/tomcat/8.5/webapps/bws/WEB-INF/web.xml"," ","NOTE  ","This \n appendix does not discuss all the parameters in web.xml, only the most \n commonly used ones."," ","<init-param>"," ","<param-name>","view.brd.enabled","</param-name>"," ","<param-value>false</param-value>"," ","</init-param>"," ","Adds a link in the build launch wizard \n in the Build user interface that enables you to view the Build Request \n Definition (BRD) file before submitting the build. This is helpful when \n you want to check what data is available to your build script and in what \n order the build steps run."," ","Default: false"," ","<init-param>"," ","<param-name>","brd.force.dependencies","</param-name>"," ","<param-value>0</param-value>"," ","</init-param>"," ","Forces dependency information from previous \n builds to be added to the BRD file regardless of platform. By default, \n only z/OS build requests contain dependency information in the BRD as \n it is used by the mainframe build tool. This information is omitted from \n BRD files for other platforms to save space. If you enable this option \n you could write a custom build script to use this information."," ","<init-param>"," ","<param-name>","session.timeout","</param-name>"," ","<param-value>60</param-value>"," ","</init-param>"," ","Specifies the number of minutes after \n which your build session times out."," ","Default: 60 minutes"," ","<init-param>"," ","<param-name>","build.missing.target.status","</param-name>"," ","<param-value>4</param-value>"," ","</init-param>"," ","Specifies the action to be taken if a \n BRD step contains a target that is not specified in the build configuration. \n For example, specifying 2 (WARNING) allows the build to continue."," ","Default: 4 (issue an ERROR and stop the \n build)."," ","<init-param>"," ","<param-name>","build.job.execution.timeout","</param-name>"," ","<param-value>60</param-value>"," ","</init-param>"," ","Specifies the number of minutes after \n which a response of any kind is expected from the PBEM. This information \n can help you to analyze the abnormal termination of build processes (crashes, \n hangs, etc). After this period the build job is cancelled. You can change \n this timeout for each build configuration. "," ","Default: 60 minutes."," ","<init-param>"," ","<param-name>","build.job.execution.start.timeout","</param-name>"," ","<param-value>60</param-value>"," ","</init-param>"," ","Specifies the number of seconds after \n which a response is expected from the PBEM with the ’build start ’ event. \n After this period the build job is cancelled. You can change this timeout \n for each build configuration. "," ","Default: 60 seconds."]],"id":"411"})