ISPW for multi-platform applications

ISPW for multi-platform applications

Objectives

Provide large Mainframe / Windows / Open Systems installations with end-to-end software change management.  Deliver improved synchronization, visibility and control at every stage of the application process while maximizing developer productivity.  Save time and reduce failed changes by automating processes and eliminating points of failure.

ISPW - an elegant solution for both mainframe and distributed applications

ISPW Remote DeployChange is not viewed lightly within large installations.  Most existing processes have withstood countless hours of testing and optimization, so why try something new?

Because ISPW actually enhances cross-platform change management by integrating familiar tools and processes.

And because it delivers a comprehensive software change management solution that embraces central and local development processes.  Developers on all platforms can interact with IDEs, testing tools and version control systems as they normally do.

ISPW works with (rather than displaces), distributed version control software such as:

  • Subversion (open source tool – supported by IBM, Google, etc.)
  • CVS (predecessor to Subversion)
  • ClearCase from IBM
  • Visual SourceSafe from Microsoft
  • PVCS from Serena

ISPW’s lightweight, collaborative framework supports a choice of 3270, Eclipse and browser based interfaces so every ISPW user has disruption-free interaction with the change management cycle.  This solution delivers immediate transparent management and control across Mainframe, Windows, AIX, HP-UX, Solaris, Linux and other open platforms.

Benefits of integration

Developers on distributed and mainframe systems continue to work as usual, with the additional advantages of enterprise-wide approval, audibility, visibility and multi-platform deploy/back-out.

Reduced costs
  • Developers, testers, QA, project managers, auditors and managers are highly productive working from their platform of choice with their standard tools, using any interface they like
  • Local version control programs are free or low cost and ISPW extensions are inexpensive
Less work
  • Utilize site standard processes for development, testing, approval, audit, disaster recovery, versioning, and security - and apply them to distributed platforms
  • Minimize the impact to both the mainframe and distributed sides – no changes for production control, audit, management
  • Text and binary change components reside in the ISPW Warehouse fully integrated with mainframe Disaster Recovery
More control
  • End-to-end visibility for project managers: consistency of approval, audit trail of testing steps and real-time communication
  • Automated processes reduce errors and ensure consistency
  • Parallel development change impacts can be identified and reconciled at an early stage avoiding unnecessary conflicts and promoting higher success rates.
  • Extends the rigor of mainframe processes to the distributed world without major disruptions to either environment.

How it works

ISPW ties into the distributed build process by utilizing standard Ant tasks. The ISPWAnt scripts are customized XML files that are included in build processes to incorporate site-specific services and access ISPW functions.  When testing is complete the entire code package (executables only or executables and source) is uploaded to ISPW and released for approval. Once all approvals are in place, ISPW deploys all components (mainframe and distributed) in a single synchronized process to all selected run-time environments. Reverting to a previous production level requires only a single ISPW back out command to unwind the updates from every applicable runtime server.  Each change in motion is visible from the ISPW console, so project management becomes intuitive.

The Bottom Line

This solution is both simple and complete.  While both mainframe and distributed developers continue to work the same way as they do today, ISPW records each module’s change history as it steps though the life cycle.  This communication, coupled with powerful traceability, approvals and work visibility, provide cohesive project management for today’s complex cross-platform applications.

Exploiting the strengths of familiar products and existing procedures, the ISPW distributed platform provides a comprehensive solution requiring minimal training at an affordable price.

ChangeMan and CA-Endevor (now known as SCM for Mainframe) are registered trademarks of Serena Software Inc. and CA Inc., respectively.

ChangeMan and CA-Endevor (now known as SCM for Mainframe) are registered trademarks of Serena Software Inc. and CA Inc., respectively.