Skip navigation

Provide a mechanism in which the TrueSight Development Studio can connect to previous versions of the CDP

score 50
You have not voted. Below Review Threshold

In its current form, the TrueSight Development Studio cannot properly communicate with CDP servers that are not running the same version.  For example, the Dev Studio version 8.2.0 cannot talk to any other CDP unless it is running v8.2.0 as well.

 

Proposal:

Provide a mechanism in which the Development Studio can connect to previous versions of the CDP, whether this is a new WSDL or API, or a different Java connector.

 

Impact:

When upgrading an installation, in most cases there are at least 2 if not more environments (DEV, pre-production, QA, testing, Production, etc.).  The standard procedure is to upgrade the lowest environment first, and then test it.  In this method and combined with the current inability of the Dev Studio to talk to previous versions of the CDP, we are required to install parallel versions of the Development Studio.

 

In many environments, installing software is restricted to accounts with elevated privileges, or even to teams that have to manually package an installer for use within their software deployment strategy. This adds significant amounts of work and time to the upgrade process.

Comments

Vote history