ISPW

Modern Mainframe Continuous Integration/Continuous Delivery (CI/CD)

null
ISPW

Without a modern mainframe CI/CD tool, you can’t ensure your mainframe code pipelines are secure, stable and streamlined throughout the DevOps lifecycle. With ISPW®, you’ll have the confidence of knowing that you can quickly and safely build, test and deploy mainframe code.

With ISPW, users can:

  • See the status of all programs throughout the lifecycle; be alerted when code is checked out; perform concurrent development; confidently merge code updates
  • Connect with modern DevOps toolchains using Jenkins plugins, REST APIs and command line interfaces (CLIs)
  • Automate, standardize and monitor deployments into multiple target environments and smoothly fallback when issues occur
  • Use in-depth zAdviser metrics to continuously improve

The Value of ISPW

  • Enables DevOps practitioners to build mainframe-inclusive DevOps toolchains and improve developer productivity
  • Eliminates manual steps and helps staff iterate quickly through the development, test and QA cycles
  • Supports multiple developers working on the same program at the same time
  • Enhances the developer experience by integrating with Compuware Topaz® Workbench for a modern suite of application development and testing tools
  • Integrates with Git to simplify the process of managing code throughout the enterprise
  • Connects with leading IT Service Management (ITSM) solutions like BMC, ServiceNow and Tivoli via Topaz® Connect
  • Confidently automates mainframe code approval and deployment activities while maintaining critical audit controls necessary for large enterprises
ISPW Migration Services Webcast

Key Features of ISPW

Agile Source Code Management

Enterprise-wide Parallel Development

ISPW’s multiple development areas enable concurrent development common with modern Agile and DevOps development practices. The Life Cycle chart shows multiple versions of code in flight for better collaboration. End-to-end tracking shows every action that affects code running at any level, including production. Users are provided with an audit trail of all activities throughout the development lifecycle.

Impact Analysis

Impact Analysis lets developers see how a potential code changes can impact the rest of the mainframe environment.

ISPW_Webpage_Impact_Analysis

Side-by-side Compare

Side-by-side Compare provides the ability to quickly compare versions of code to spot changes and easily merge them.

ISPW Test Compuware

Build

ISPW is much easier to set up and administer than other SCM solutions. Requiring less custom coding through processors, development teams need only select the specific pre-coded capabilities they want to use. In another example, ISPW uses modular, reusable compile skeletons for simple substitution, nesting and conditional pathing. With a few skeletons, you can cover a wide range of compiles, from COBOL to Db2 and more. And because skeletons substitute version libraries, they rarely need to be changed.

Deploy

Web Interface

ISPW’s web interface allows you to view the status of all deploy requests and the environments into which code was deployed.

Easy Full or Partial Fallback

ISPW allows you to fallback some or all code changes at once and replace the current production program with a valid previous program version. Production source will be synchronized with the fallback so versions always match.

Automate Processes Across Platforms

Devops Integrations

ISPW integrates into a cross-platform DevOps toolchain to enable Continuous Build and Deploy while ensuring code quality.

  • The Compuware Source Code Downloader plugin allows source code stored in ISPW to be downloaded into Jenkinsfor code quality analysis and reporting by SonarSource’s SonarQube.
  • The Compuware ISPW Operations plugin enables users to build a DevOps pipeline in Jenkins to manage code throughout the development lifecycle. Developers can generate, promote, compile, and deploy on the mainframe, or pull in source code from Git, all within a Jenkins pipeline. (For organizations that want to use one SCM tool, a Git integration eases the processing of managing cross-platform data.)
  • ISPW integrates with XL Release to automate, standardize and monitor code deployments across multiple platforms into multiple target environments. Users can view and manage deployments in one place and monitor their statuses across teams and environments with detailed analytics on release flow.
  • ISPW’s integration with CloudBees Flow helps users create, promote and deploy on the mainframe.
  • ISPW also integrates with CollabNet VersionOne’s Continuum to enable users to track the progress of their software development activities from the same Continuum dashboards as they use to manage development.

REST APIs

ISPW’s REST APIs enable you to:

  • Compile, promote, regress, deploy, fallback and check statuses of code releases and more using popular tools like Jenkins and XebiaLabs XL Release
  • Gain visibility into mainframe activity to easily run and monitor a deploy
  • Achieve Continuous Delivery in multi-platform enterprise environments
ISPW_Webpage_Pipeline_Graphic

Webhook Notification

Webhooks enable you to:

  • Communicate information about ISPW activities such as generate, promote, regress, deploy and fallback to other DevOps tools in real time
  • Integrate ISPW with other deployment tools
  • Drive Continuous Integration processes using Jenkins
  • Send instant notifications about DevOps activities to Slack and HipChat as they happen

Webhooks can be triggered whether developers or operators use Topaz, 3270 or REST APIs.

Advanced Analytics

ISPW usage data can be leveraged with machine learning based zAdviser. With the help of zAdviser dashboards and intelligence, teams can:

  • Locate areas within code that should be prioritized for reducing technical debt
  • Visualize constraints in changing source code so they can focus their development efforts to better meet business and customer requirements
  • Improve efficiency by seeing how much time is spent developing and testing code, how long it takes for code to be promoted to production and more