Upgrading Wasp3d Version 1.3.
Download the updated setups of the Wasp3d Modules Version 1.3 (May 2008 Build) & Follow the Following steps given below. You will need to update all the modules for deploying this release.
Please follow the process for updating the Modules :
1. Update the Kernel Controller (Be sure that no user is using any of the Wasp3d Modules including Data Buzz integrated with the Automation Systems like iNews, ENPS or Octopus etc.)
a. Take a backup copy of the configuration file Web.Config of the Kernel Controller located at C:\Inetpub\wwwroot\KernelController\ and store it at some other location in the computer from where you can copy it later.
b. Remove the current build of Kernel Controller by going to Control Panel/Add-Remove Programs, Select Kernel Controller and Click on Remove.
c. Install using the New Setup of Kernel Controller downloaded from our FTP Site using the Wasp'3DLink.htm webpage. (please enable the ActiveX Control on the Webpage)
You will need to put the name of the Kernell Controller in the Dialog Box and the Username and Password.
The name of the Server will be the same as in the older Version. The User-ID has to be "sa" and the password has to be "BeeSys". Define the location of the favourites folder as in the older version
d. Copy the Web.Config file back to the C:\Inetpub\wwwroot\KernelController\
e. Copy the folder Database Updater in the C drive, Open it
f. Right Click on WaspCommandUpdater.exe.config, Select Open With Notepad/Wordpad and write the name of your database server in place of NAME OF THE DATABASE SERVER* and save the file.
NOTE: NAME OF YOUR DATABASE SERVER WILL REMAIN SAME AS IT WAS BEING USED EARLIER
<add key="SERVER_NAME" value="NAME OF THE DATABASESERVER"></add>
g. Run the Application WaspCommandUpdater.exe
h. A Dialog Box will open
i. Click on the Playlist Update Button and close the dialog box by clicking on the Close Button
j. Go to Start/Run and type iisreset and click on OK.
The following updates need to be done as per the Version of Microsoft SQL Server used on the Web Server.
SQL Server 2000
1. Start the SQL Server Network Utility on the computer where MSDE/SQL Server is running.
Normally you can do this by select Run from the Start menu and entering svrnetcn.exe and selecting OK. (If that does not work you can launch it from the following locationC:\Program Files\Microsoft SQL Server\80\Tools\Binn\ svrnetcn.exe).
2. On the SQL Server Network Utility screen select the correct MSDE/SQL Server instance name.
On most servers there will only be one instance name. If you are using SQL Server is it is usually the name of the computer. If you are using MSDE it is probably in the format of ComputerName\SQLEXPRESS.
3. Select the TCP/IP entry and Named Pipes in the Enabled Protocols section.
4. Click Apply and then Ok and Restart the Computer.
SQL Server 2005
To enable the TCP/IP protocol for the database instance
1. Log on to the data-tier server on which the database instance is defined.
2. Open the Start menu, point to All Programs, point to Microsoft SQL Server 2005 or Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.
3. In the tree pane, click SQL Server 2005 Services or SQL Server 2008 Services.
4. In the results pane, verify that, under the State column, Running appears next to the name of each service. If Stopped appears, right-click the name of the service, and click Start.
5. In the tree pane, click SQL Server 2005 Network Configuration or SQL Server 2008 Network Configuration to expand it, and then click Protocols for MSSQLServer/MyInstanceName.
If you specified the default instance during installation, the instance name will be MSSQLSERVER.
6. In the results pane, verify that, under the Enabled column, Enabled appears next to the name of the TCP/IP protocol.
If Disabled appears, right-click TCP/IP , and then click Enable. If Disabled appears, right-click Named Pipes, and then click Enable.
7. In the tree pane, click SQL Native Client Configuration to expand it, and then click Client Protocols.
8. In the results pane, verify that, under the Status column, Enabled appears next to the name of the TCP/IP protocol. If Disabled appears, right-click TCP/IP, and then click Enable.
9. In the tree pane, click SQL Server 2005 Services or SQL Server 2008 Services
10. In the results pane, right-click SQL Server (MSSQLServer/MyInstanceName), and then click Restart.
11. Restart the Computer.
The Kernel Controller is ready to use.
2. For the following modules:
a. Drone Designer (Includes Playout Component)
b. Comb Builder
c. Data Buzz (Includes Playout Component)
d. Hive Manager
e. Sting Client
f. Sting Server (Includes Playout Component and Wasp Engine Manager
Note : To remove the Playout Component, find Wasp Graphics Server in the Control Panel > Add/Remove Programs
Remove the Respective module from the Control Panel/Add-Remove Programs and install the New Software downloaded from the FTP Site.
3. Previously we used to put the Name of the database server in the Start/Programs/Beesys/Wasp3d 1.3/Module(for e.g. Drone Designer)/Configuration.
Now we will need to do it the other way, by editing the CommonConfig.config file at C:\Program Files\Beehive Systems Ltd\1.3\COMMON.
Right Click on CommonConfig.config, Select Open With – Notepad/Wordpad and write the name of your database server in place of NAME OF THE DATABASE SERVER* and save the file.
*NOTE: NAME OF YOUR DATABASE SERVER WILL REMAIN SAME AS IT WAS BEING USED EARLIER
<add key="WEBSERVICEHELPER_URL" value="http:// NAME OF THE DATABASESERVER/Kernelcontroller/WebServiceHelper.asmx"/>
This configuration file applies for all the modules installed on one machines.
Step no. 3 will only be followed for the following Modules : Drone Designer, Comb Builder, Data Buzz, Hive Manager, Sting Client
4. For Sting Server you will need to go to Start/Programs/Beesys/Wasp3d/ WaspEngineManager / Application.Configuration.exe and change the name of the Database Server
WEBSERVICEHELPER_URL - http://NAME OF THE DATABASESERVER/KernelController/WebServiceHelper.asmx
5. For any further queries or issues please logon to www.wasp3d.com\support and report the same.
