TurnOver^™/Version Manager^™ Interface

iSeries (AS/400) developers and PC developers can't always agree on what tools to use to manage their development work. At the same time, it's not practical for IT departments to support two different processes. The integration of TurnOver^™ Change Management and Version Manager^™ solves this problem, because it lets developers use the tools they know best from within a single, enterprise-wide CM system that accelerates your software development life cycle.

The TurnOver/Version Manager interface seamlessly embeds Version Manager's easy-to-use PC version control within TurnOver's broader change management framework, which includes request tracking, project management, automated promotions, and application deployment. The combination of these two products gives you reliable end-to-end management of all your applications, and lets you safely delegate many tasks to less experienced employees.

The TurnOver/Version Manager solution is ideally suited for WebSphere and other web developers who need PC version control for objects such as HTML, JSPs, graphics, and style sheets, but also need more extensive functionality to automate other tasks and coordinate their work with others. Once development is complete, the files pass to TurnOver for promotion, archiving, and so on.

To activate the interface, you set rules within TurnOver to determine how TurnOver and Version Manager will interact. Once the rules are defined, a programmer simply performs standard Version Manager functions, such as Checkout and Check-in. When a defined Version Manager event occurs, the interface performs the additional pre-defined actions, such as adding the item to a TurnOver Worklist. The interface remains completely invisible to the programmer.

Invisible updates between Version Manager and TurnOver

You define which Version Manager events trigger additional actions, such as getting files from the Version Manager repository, applying a version label, adding items to a TurnOver Worklist, or preparing a TurnOver Form for promotion with the correct items. Once defined, the actions automatically execute at the proper time without developer intervention.

Files pass to TurnOver upon check-in

The TurnOver/Version Manager interface prepares files for TurnOver promotion completely behind the scenes. The developer simply checks the item into the Version Manager repository. The interface copies the file to an iSeries or AS/400 directory where it can be used for testing, promotion, archiving, and recovery. TurnOver administrators, even those without PC experience, can easily handle PC promotions.

Support for compiled languages

TurnOver supplements Version Manager's source control with the object control needed for certain Java components, Visual Basic, C++, Delphi, and other languages that generate compiled objects. When you've completed your changes, you use TurnOver eCM's selection criteria (based on date modified, object type, and so on) to populate your TurnOver Worklist with the correct compiled objects for promotion.

Synchronized deployment

TurnOver's reliable promotion and deployment engine rolls out all related changes together, for synchronized installation and complete change history. TurnOver deploys to iSeries, Windows, Unix, and Linux servers.

WebSphere and other IDE integrations preserved

Version Manager plugs into any Eclipse-based IDE (WSAD, WDSc, etc.) and most other popular IDEs. When Version Manager is defined as the external version control system, PC developers simply work within the IDE as usual. Information continues to flow routinely between the IDE, Version Manager, and TurnOver without opening either Version Manager or TurnOver.

Direct links to TurnOver from Version Manager

We provide a set of programs that add TurnOver icons into the Version Manager toolbar. The icons provide direct access to TurnOver information, such as tasks or forms, from within Version Manager.

Version labels linked to TurnOver task

The Version Manager interface can use TurnOver task IDs as version labels for the files being stored in the Version Manager repository, indicating which task prompted the change.

Activity log for fast trouble-shooting

The interface maintains an activity log that shows all history for the current session. If an error occurs during processing, an icon on the developer's desktop tray blinks. The developer double-clicks the icon to identify the cause of the error within the history log.

Single process for all objects

With TurnOver and Version Manager, you will have a single process for request tracking, project management, application deployment (and recovery if necessary), change history, and file archiving. This streamlined process improves efficiency, speeds development, reduces risk, and sets the stage for continuous IT improvement.

Interface & Application Software Support

You can use TurnOver's many APIs or built-in interfaces to bridge to any software package, including:

Built-In Interfaces	Application Support	Optional Interfaces*
Abstract^™	ASI^™	AllFusion 2E^®
AllFusion Plex^™	BPCS^®/ERPLX	AS/SET^®
Code/400^™	PRMS^™	Dimensions^™
Deploy/400^™	PKMS	LANSA^™/Visual LANSA
JD Edwards World^®	HFA^™/Friedman	ProGen Plus^™
Lawson	Infinium^™	Subversion for OS/400
PathFinder	JBA^™	*Optional interfaces licensed separately from TurnOver.
TestBench^™	JDA^™
TurnOver PDQ^™	JHA^™
Version Manager^™	MAPICS
WebSmart^™	Island Pacific
	Kronos
	Movex
	Premenos