Preparing for a project

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

Related topics

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.
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.

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

Important

Do not enclose the variable values in single or double quotation marks.
Comment out any variables in the plug-in variables file that you do not plan to use.
The default name of the plug-in variables file is AMI_DevOps.properties. The plug-in variables file can have any name, but the file name extension must be .properties.

Variable type	Variable
SSL certificate validation	TSFLAG
Limit settings	maxlimit dsrecalltime
LPAR/Subsystem information	acctno lpar1 dsnexit dsnload
Installation information	rtehlq usrhlq proclib joblib1 joblib2
SQL Assurance	gudplan pssplan ruledsn rules currency
SQL Explorer	pssplan ruledsn rules currency

Tip

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

Make sure that the plug-in variables file is available in the environment in which you run the deployment.

On this page