The scenarios covered by the primary pipelines, the other pipeline examples, and more generally the use of the Compuware and third party plugins, require certain configurations and settings, both within Jenkins and within other tools provided by Compuware.
Compuware Enterprise Services
Next to serving as web application server for Compuware's web based tools like iStrobe or the ISPW web interface, Compuware Enterprise Services (CES) provides a set of services that allow interfacing with Compuware tools outside the mainframe. In the context of Jenkins and CI/CD these are
ISPW allows registering webhooks to use events in the ISPW software life cycle to trigger events outside of ISPW like triggering a Jenkins pipeline. CES may be used as one source to define and register webhooks for ISPW. Both primary pipelines make use of such webhooks defined in CES. Refer to the CES online help, chapter Compuware Enterprise Services, section Webhooks for documentation on setting up ISPW webhooks, and the parameters that may be passed from ISPW to the webhook.
CES Credentials Token
The Compuware plugins (and other operations) make use of credential tokens defined in CES. These tokens store mainfram TSO user id and password and allow authentication against the mainframe without using clear text credentials within script code.