CrossVista Announces the General Availability of TEAM Server 1.6 for WebMethods!!!
CrossVista is happy to announce the General Availability (GA) of TEAM Server 1.6 for webMethods. This is a major new version that has been under development for a couple of years and includes a great deal of new functionality such as:
– Integration to 3rd party Change Management Systems – This version includes support for Jira, ClearQuest, and HP Quality Center. CrossVista TEAM Server also ships with an internal CM system that can be used instead of those third party solutions. Support for Remedy is planned for next quarter. This means that all TEAM Server actions for a particular change request can be tracked using a ticket within a change management system.
– Ticket Based Development and Release Management – Each ticket within the change management solutions might represent a feature or a bug. Developers can be assigned to work on particular tickets within the supported change management solutions. When checking new revisions into TEAM Server, developers are presented with a list of their assigned tickets (CRs) and can associate their changes to any of their assigned CRs. When development is done, build managers can see all the CRs along with the corresponding code revisions and can include them in the new full Release (or patch) associated with the CR. This makes it very easy to organize, manage, promote, and deploy your changes.
– Improved Release Baselining and Patch Management – Any full TEAM Release can be chosen as the ‘baseline’ release. Then all of the changes – code, configuration as well as the platform changes for core platform releases can be packaged as patches to the baseline. All patches associated with the baseline release can be applied to the baseline (deployed on top of the baseline) or rolled off.
– Extended Site Management – The TEAM Server SITES functionality has been extended and now includes baselining capabilities for the attached projects (i.e. supports syncing baselines and the associated patches) and extended nodes. Also, nodes defined in 1.6 SITES are logical managed nodes and can contain several physical servers. For example, a deployment site can have a set of nodes, each of which can contain one or more instances of Integration Server, Trading Networks, Broker, MyWebMethods, Optimize, and/or Standalone Files.
This new version also has an extended API, improved automation capabilities, and much, much more. Please reach out to your primary contact at CrossVista for more information or send an email to makeiteasy@crossvista.com for more information.
By bundling together the functions of Version Control, Change, Config, and Release Management, CrossVista TEAM Server provides one solution for managing all aspects of the webMethods Application Lifecycle.
Share This Story, Choose Your Platform!