CONTACT US
RECORDED DEMOS
CrossVista Inc is pleased to announce the addition of some major new functionality.
CrossVista’s core product, TEAM Server, is an application lifecycle management solution built specifically for Software AG’s webMethods Suite. By bundling together the functions of Version Control, Change Management, Configuration Management, and Release Management, CrossVista TEAM Server provides one solution for managing all aspects of the webMethods application lifecycle.
CrossVista is scheduled to release a new Beta version of TEAM Server in November 2009. This new version will allow users to define a change request within TEAM Server, assign code and/or configuration changes to that change request during development, and then automatically promote/deploy changes assigned to that change request directly to their webMethods environments. Each change request can contain code and/or configuration changes from webMethods Integration Server, webMethods Trading Networks, webMethods Broker, webMethods Optimize, webMethods Process Models, and more.
The new functionality is embedded within CrossVista’s TEAM Server VCS plugin for webMethods Designer so developers never have to leave Designer to make use of the change request functionality. The Release Manager’s job also becomes that much easier. Because multiple developers can easily contribute changes to a specific change request in parallel, the Release Manager can easily build full (or patch) releases containing all of the modifications for that change request.
“This new functionality was driven 100% by customer input and will provide immediate benefits for our customers”, says Dan Schirf, Vice President of Sales and Business Development at CrossVista. “We’re also excited about how we can extend this functionality. With this new change request framework in place, we will look to integrate directly with industry leading change management solutions such as IBM Rational ClearQuest and Atlassian Jira. For the first time, users will be able to track a change request and tie it directly to the actual webMethods code and configuration changes that support that change request.”
