Migrating your Tango2000 Application to Witango 5
Set out below is a list of topics which provides easy access to all of the information you will need to migrate your Tango 2000 application to Witango 5. Should you have any further questions please email info@witango.com.
Latest Witango 5 Installers
To access the latest Witango 5 installers visit the WITANGO DOWNLOADS section of this web site. These links are also available from the banner at the top of the Homepage of this site. You will need to download the installers for Witango 5 Server on a platform of your choice and Witango 5 Studio on the platform of your choice.
Latest Witango 5 Documentation
You will also need to download the latest Witango 5 documentation also found on WITANGO DOWNLOADS section. You should download the Programmers Guide,the Server Installation Guide for your platform of Choice and the What's New Documentation.
What's New in Witango 5
HTTP headers
HTTP headers must be a complete HTTP response header. Partial headers will now throw a http 500 error on the server. An example of a complete header is below:
-
<@ASSIGN request$httpHeader "HTTP/1.1 <@HTTPSTATUSCODE> <@HTTPREASONPHRASE><@crlf>Date: <@CURRENTTIMESTAMP FORMAT='datetime:http'><@crlf>Server: Witango 5.0.1.062<@crlf>MIME-Version: 1.0<@crlf>Content-Type: text/html<@crlf><@crlf>">
Two new tags exist to assist <@HTTPSTATUSCODE> and <@HTTPREASONPHRASE>.Local scope is now known as REQUEST scope
The scope which used to be known as 'local', in Witango 5 is known as 'request'. The change in name was made because Request better reflects that the lifespan of the variables in this scope is limited by the duration of the current http request. The old name is still supported so that both names, Local and Request, may be considered as aliases. The user should however be aware that when the Witango 5 Editor opens the taf files all 'local' scoping will be made 'request' and therefore will exhibit different behaviour when run on the Tango2000 server.
Variables which are NOT scoped
The default scope for the Witango Server has been changed from 'user' to 'request'. If you application relies on the default scope being USER then the witango.ini file should be changed such that the parameter DEFAULTSCOPE is set to USER.
This information is detailed in the What's New Documentation mentioned above,in most cases your application will run without issue. However, the issues which if applicable that should be addressed are:
Server Admin Application
What used to be known as 'config.taf' is now known as the Witango 5.5 Admin Application. It can be downloaded at this link.
Upgrade Pricing
Witango upgrade pricing is available at Pricing Page.
Educational discounts are available for educational institutions, please contact sales@witango.com with your enquiries.
Purchasing Upgrades
Upgrade orders can be placed through the site at the PURCHASE WITANGO page, any enquiries for bulk orders should be made to sales@witango.com .
Customer Support
To obtain assistance in upgrading your Tango 2000 applications please email support@witango.com






