An engineer is developing an instance of IdentitylQ using the Services Standard Build (SSB) for a client. Is this a valid action the engineer can…

The SailPoint Services Standard Build (SSB) is a framework designed to standardize and automate the development and deployment of IdentityIQ. A core principle of the SSB is to manage all components, including base product files, custom code, and patches, in a structured and repeatable manner. The base/patch directory is the designated location within the SSB structure for placing patch JAR files. The SSB's Apache Ant build script (build.xml) is specifically configured to find any JARs in this folder and automatically overlay them into the WEB-INF/lib directory of the identityiq.war file during the build process. This ensures patches are applied consistently every time the application is built.

B. No: This is incorrect. The described action is the standard, prescribed procedure for applying patches within the SSB framework to ensure automated, consistent, and repeatable builds.

1. SailPoint Services Standard Build (SSB) Documentation: The official SSB documentation, provided as part of SailPoint Professional Services engagements, explicitly details the directory structure. The section on "Project Structure" or "Applying Patches" specifies that patch JAR files must be placed in the base/patch directory to be included in the automated build. (Note: This documentation is typically available on the SailPoint Compass portal for customers and partners).

2. IdentityIQ Installation Guide: While this guide describes the manual process of applying a patch (which involves copying files into the WEB-INF/lib directory of the exploded WAR), the SSB automates this exact step. The SSB's use of the base/patch folder is the input for this automated process, confirming the logic behind the framework's design. See the section on "Applying a Patch to an IdentityIQ Installation."