• Replies 18 replies
  • Subscribers 338 subscribers
  • Views 260 views
  • Users 0 members are here
Related

Running Multiple Instances of Tessitura

Britt East
$organization

I am relatively new to Tessitura, and am interested in running multiple instances of the software (v9.0.0.1) on one workstation. I found this article, which describes the process:

Issue Summary:Is it possible to run more than one Tessitura session on a single workstation?
Detailed Description: Is it possible to run more than one Tessitura session on a single workstation?
Resolution:Yes, it is possible to run multiple instances of Tessitura on a single workstation. In order to do so, the following will need to be done for each workstation where you wish to run multiple sessions: 1) On the workstation, create a separate version of the local ini file (tessitura.ini) which specifies a different hostname. This entry should be placed in the [SQLCA] section of the ini file. For example, if the new hostname will be TESTHOST, add an entry to the new tessitura.ini file in the SQLCA section like this: Hostname=TESTHOST 2) Add a new row in the TX_MACHINE_LOCATION table specifying the new hostname. Following the example above, you would add a new row to this table where the Machine Name is "TESTHOST". 3) Create a new Tessitura desktop shortcut that will point to the new ini file.
I think I completed everything successfully, but I get an error message: "This PC ("TESTHOST") does not ha ve a location assigned." I tried to paste a screenshot into this window, but couldn't get that to work.
In reading the Table Help notes in Tessitura for TX_Machine_Location, I see the following:
Entries in this table have the following values:
Machine Name – The Windows name of the workstation.
Location – The location value for the workstation.  Location values come from TR_LOCATION.
The Windows name for this workstation is "CMP137". That is already associated with a table entry in TX_Machine_Location. So that may be the problem. But not sure how to work around that...
Have any of you had any experience with this? Seems like it should be simple, so I'm sure I'm just doing something boneheaded! LOL!
Thanks,
Britt


[edited by: Britt East at 3:37 PM (GMT -6) on 14 Oct 2009]
Parents
  • $organization

    Hi Britt,

    Check the system table within tessitura TX_MACHINE_LOCATION and make sure the "location" is assigned for machine name which I assume would be TESTHOST.

    Normally I just look for the row in TX_MACHINE_LOCATION that has a blank location and assign it.

  • $organization in reply to Ryan Rowell

    Thanks Ryan! I didn't see any blank fields, so I just added a new row, then saved my work.

    In reading the Table Help notes in Tessitura for TX_Machine_Location, I see the following:
    Entries in this table have the following values:
    Machine Name – The Windows name of the workstation.
    Location – The location value for the workstation.  Location values come from TR_LOCATION.
    The Windows name for this workstation is "CMP137". That is already associated with a table entry in TX_Machine_Location.
    So that may be the problem. But not sure how to work around that...
  • $organization in reply to Britt East

    Hmm, well someone else may need to help you out on this since I'm not too familiar with the process but here are a couple things I noticed about my test environment
    which I have set to run at the same time as my production.

    Local .ini file has different hostname
    Ex. here is some of the content of my local file so I can have my test environment

    [sqlca]
    HOSTNAME=rrowell-ps-tst02
    MasterIniFilePath="t:\startup\tessitura_test02_master.ini"


    The target in the shortcut properties points to the local file
    Ex. here is my target

    T:\Startup\Tessitura_test02_Start.bat "c:\windows\system32\tessitura_test02.ini

    I believe the process is the same for having two instances of production.
    Hope you get it figured out!

    Cheers!

  • $organization in reply to Ryan Rowell

    Thanks Ryan! I'm set up the same way.

    I think the error must be in the way I am configuring the entry in the TX_MACHINE_LOCATION table...

    Anybody else have any ideas? :  )

  • Former Member
    Former Member $organization in reply to Britt East

    You should be able to fix this problem by editing the tx_machine_location table from another instance of Tessitura accessing the same database.

    To do so, open tx_machine_location in System Tables, and on the row with machine name "TESTHOST", choose a location value from the dropdown in the Location column.

Reply
  • Former Member
    Former Member $organization in reply to Britt East

    You should be able to fix this problem by editing the tx_machine_location table from another instance of Tessitura accessing the same database.

    To do so, open tx_machine_location in System Tables, and on the row with machine name "TESTHOST", choose a location value from the dropdown in the Location column.

Children
  • $organization in reply to Former Member

    Thanks Steven! I guess I don't understand. Administration is my only choice from the Location drop down menu (other than "none").

    We only have one location built in the TR_Location table, and that is Administration. I'm relatively new here, so I'm not sure why that decision was made. Every row in the TX_Machine_Location table uses Administration as the location.

  • Former Member
    Former Member $organization in reply to Britt East

    That's fine; you can just set it to Administration. That location is part of the default Tessitura setup; basically, this field would be to track the general location of a particular workstation if a site wishes to do so.

    We just require that this value be specified, as an additional means of security, in order to allow a particular "host" or machine to run the Tessitura software against a particular database.

  • $organization in reply to Former Member

    Thanks Steven! I set it to Administration initially, since that was my only choice. Still got the error. I feel like there's something simple I'm just missing...   :  )

  • Former Member
    Former Member $organization in reply to Britt East
    Hi Britt
    Then you should select "administration" as the location for your new dummy workstation name. The Location field doesn't really have any function except to make it easier to administer in large orgs. You can make it anything you like, as long as every real or dummy workstation name has one.
    Ken McSwain
    +61 (0)418 659 360
    Sent from BlackBerry

    -----
    Original Message -----
    From: Tessitura Technical Forum
    To: Ken McSwain
    Sent: Thu Oct 15 09:32:11 2009
    Subject: Re: [Tessitura Technical Forum] Running Multiple Instances of Tessitura

    Thanks Steven! I guess I don't understand. Administration is my only choice from the Location drop down menu (other than "none").

    We only have one location built in the TR_Location table, and that is Administration. I'm relatively new here, so I'm not sure why that decision was made. Every row in the TX_Machine_Location table uses Administration as the location.

    From: Steven Bras
    Sent: 10/14/2009 4:43:31 PM


    You should be able to fix this problem by editing the tx_machine_location table from another instance of Tessitura accessing the same database.

    To do so, open tx_machine_location in System Tables, and on the row with machine name "TESTHOST", choose a location value from the dropdown in the Location column.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
    Please consider the environment before printing this email.
    =====This message is intended for the addressee(s) named and may contain confidential information.
    If you are not the intended recipient, please delete it and notify the sender.
    Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====
  • $organization in reply to Former Member

    Thanks for all the help, guys! It's neat to see so many users on this forum responding to threads!  :  )

    I had already done all of your suggestions in my original attempt, so I'm just going to start a trouble ticket...

    Best,

    Britt

  • $organization in reply to Britt East

    Britt,

     

    At the Trust we have several “shortcuts” that are using different ini files.

     

    Since we have a four instances of Tessitura running for various reason we needed to devise a method for being able to run these four at one time from one workstation/terminal server.

     

    Production is for instance pointing to:  “E:\Tessitura\impresario client\tessitura.exe” e:\startup\ini\production_user_ini\%username%_production.ini

    Test is pointing to:  “E:\Tessitura\impresario TMP client\tessitura.exe” E:\startup\ini\TMP_user_ini\%username%_TMP.ini

    And so forth…

     

    Let’s say user jdoe wants to start production and test at the same time… what you could do is to simply create a second set of tessitura application files and create a second inifile using the same naming convention we are using, thou you can create any that makes sense to you. Inside the TX_Machine_Location you need to insert the hostname that is listed in the inifile to be used for the instance of tessitura to be used.

     

    Examples of ini files:

     

    Production:

    _____________________________________________________

    Jdoe_production.ini

    [sqlca]

    MasterIniFilePath="E:\startup\Tessitura_Production_Master.ini"

    hostname=jdoeprod

    [Login]

    logid=jdoe

    ______________________________________________________

     

    Temp:

    ______________________________________________________

    Jdoe_TMP.ini

    [sqlca]

    MasterIniFilePath="e:\startup\tessitura_TMP_master.ini"

    hostname=jdoetmp

    [Login]

    logid=jdoe

    _____________________________________________________

     

    Hope this isn’t to chaotically described for you, it does make sense in a way but could probably be explained better! J

     

    Let me know if you have any questions on anything, I’ll be glad to assist in the matter.

     

    Douglas T. Diamond

    Pgharts.org

    diamond@pgharts.org

     

     

     

     

     

     

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Britt East
    Sent: Thursday, October 15, 2009 5:42 PM
    To: Diamond, Douglas
    Subject: Re: [Tessitura Technical Forum] Running Multiple Instances of Tessitura

     

    Thanks for all the help, guys! It's neat to see so many users on this forum responding to threads!  :  )

    I had already done all of your suggestions in my original attempt, so I'm just going to start a trouble ticket...

    Best,

    Britt

    From: Ken McSwain <bounce-kenmcswain5454@tessituranetwork.com>
    Sent: 10/14/2009 7:00:25 PM

    Hi Britt
    Then you should select "administration" as the location for your new dummy workstation name. The Location field doesn't really have any function except to make it easier to administer in large orgs. You can make it anything you like, as long as every real or dummy workstation name has one.
    Ken McSwain
    +61 (0)418 659 360
    Sent from BlackBerry

    ----- Original Message -----
    From: Tessitura Technical Forum
    To: Ken McSwain
    Sent: Thu Oct 15 09:32:11 2009
    Subject: Re: [Tessitura Technical Forum] Running Multiple Instances of Tessitura

    Thanks Steven! I guess I don't understand. Administration is my only choice from the Location drop down menu (other than "none").

    We only have one location built in the TR_Location table, and that is Administration. I'm relatively new here, so I'm not sure why that decision was made. Every row in the TX_Machine_Location table uses Administration as the location.

    From: Steven Bras
    Sent: 10/14/2009 4:43:31 PM


    You should be able to fix this problem by editing the tx_machine_location table from another instance of Tessitura accessing the same database.

    To do so, open tx_machine_location in System Tables, and on the row with machine name "TESTHOST", choose a location value from the dropdown in the Location column.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
    Please consider the environment before printing this email.
    =====This message is intended for the addressee(s) named and may contain confidential information.
    If you are not the intended recipient, please delete it and notify the sender.
    Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====

    --
    View this message online at: http://www.tessituranetwork.com/COMMUNITY/forums/p/1347/4518.aspx#4518
    --
    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

    Feeling generous? Meet your match on October 28!