• Replies 2 replies
  • Subscribers 337 subscribers
  • Views 11 views
  • Users 0 members are here
Related

Mapping the contents of Tessitura Folder on the Server

Former Member
Former Member $organization
Hi All,
Our requirement is to access Tessitura by four different venues where three of the venues connect to the Tessitura servers using a VPN Tunnel and the contents of the Tessitura folder are mapped to a network drive on the local machines (T:\ drive).
 
We are currently having speed and bandwidth issues with one of the sites using the VPN Tunnel and the application is running very slow. I was wondering if the contents of this Tessitura folder on the server can be copied to a folder on the local system and make appropriate changes to the .bat and .ini files to point to the correct location, so that the VPN connection can be used only for accessing the database. Does this kind of setup has any implications on the functionality or usage of the application?
 
Please advice.......
Kind Regards,
Naga Kakarla
DBA - TNEM.
Parents
  • Former Member
    Former Member $organization

    Hi Naga

    You shouldn't have any problems running from a  local tess folder - apart from the added complexity of updates - you need to keep them in step.

    But I suspect that won't have much effect on your performance issues. The normal T:\ drive stuff is really only referred to when the client starts up, or when you run a report (assuming your local report libraries are accessed from there.)

    If you're having ongoing performance issues with remotely connected workstations, you probably should look at the possibility of running them via a Terminal Server. Term Serv sessions work with very limited bandwidth quite happily. They're quite efficient. Lots of Tess sites run Tess in remote sessions via Terminal Server with no problems. That setup also brings a number of other advantages, like being able to log into Tess from other locations yourself, to fix problems.

    Ken

Reply
  • Former Member
    Former Member $organization

    Hi Naga

    You shouldn't have any problems running from a  local tess folder - apart from the added complexity of updates - you need to keep them in step.

    But I suspect that won't have much effect on your performance issues. The normal T:\ drive stuff is really only referred to when the client starts up, or when you run a report (assuming your local report libraries are accessed from there.)

    If you're having ongoing performance issues with remotely connected workstations, you probably should look at the possibility of running them via a Terminal Server. Term Serv sessions work with very limited bandwidth quite happily. They're quite efficient. Lots of Tess sites run Tess in remote sessions via Terminal Server with no problems. That setup also brings a number of other advantages, like being able to log into Tess from other locations yourself, to fix problems.

    Ken

Children