Preparing for a project

Before creating, configuring, and building a project in Jenkins, perform the following steps:

1. Configure the required objects for explaining SQL statements:
   • User authorities
   • IBM stored procedures

   • Plan tables

     For more information, see SQL Explorer and Db2 authority requirements and Required authorities for Explains and the What-If Index feature.

2. Ensure that your objects used in the SQL statements performs like your production environment. You should copy the object statistics from the Db2 catalog on production to the Db2 catalog that you are running against. You can do this via any of the following BMC products:

   • BMC AMI SQL Explorer for Db2. For more information, see Migrating access path statistics.

   • BMC AMI Command Center for Db2. For more information, see Migrating statistics.

3.  Customize the plug-in variables file. 
   In the plug-in variables file that BMC has provided, customize the following variable values:

   Important

   • Ensure that all variable values are in uppercase.
   • Do not enclose the variable values in single or double quotation marks.
   • Ensure that you comment out any variables in the plug-in variables file that you do not plan to use when you configure the project.
   • The default name of the plug-in variables file is AMI_DevOps.properties. The plug-in variables file can have any name, but it must be a .properties file.

   Variable type	Variable
   BMC AMI DevOps Common	maxlimit
   SSL certificate validation	TSFLAG
   LPAR/Subsystem information	acctno lpar1 dsnexit  dsnload
   Installation information	rtehlq usrhlq proclib joblib1 joblib2
   BMC AMI SQL Assurance for Db2	gudplan
   BMC AMI SQL Explorer for Db2	pssplan currency ruledsn rules

   
   

   Tip

   For reference, see the sample plug-in variables file in Sample-plug-in-variables-file-AMI_DevOps-properties.

4. Ensure that the plug-in variables file is available in the Jenkins environment in which you run the project.