locked
APP-V 5 sequencing main app and oracle using connection groups RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am currently trying to find a solution for the below scenario:

    App1 - Main business application.  Includes the TNSNAMES.ORA file located under C:\Program Files (x86)\TNSNAMES.  Installed to VFS

    App2 - Oracle app.   Includes ENV variables including TNS_ADMIN=C:\Program Files (x86)\TNSNAMES. Installed to VFS

    App1 and App2 published globally and added to connection group.

    When I launch App1 shortcut the login fails (basically cannot find TNSNAMES.ORA).  I open up CMD prompt from APP1 bubble and check the env variable for TNS_ADMIN.  This variable references the app2 cache path eg.  C:\ProgramData\Appv\[PACKAGEID-APP2]\[VersionID-APP2]\Root\VFS\ProgramFilesx86\TNSNAMES

    TNSPING from App1 fails to find the tnsname.

    If i open explorer from the app1 bubble i can see C:\Program Files (x86)\tnsnames\tnsnames.ora

    Now here is the weird piece.  If I now go back to the cmd prompt and cd into this folder and run a dir.  I can now tnsping ok.

    After this the TNSNAMES.ORA appears in the connection group (open write?) under %localappdata%\Microsoft\AppV\Client\VFS\[GROUPID]\ProgramFilesx86\Tnsnames\ .  This process seems to force the file into the connection group and I suppose kind of fixes it.

    Anyone any thoughts on this?  Ideally we want to keep the TNSNAMES.ORA in the main app and the env in the oracle package as this will allow us to easily change to later version of oracle if needed.....(just by changing app1 into another connection group).   My assumption is that both these apps would be merged when added to a conection group so env variables from one app should be able to reference files that exist in another connected app.

    Wednesday, March 13, 2013 4:41 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    It might be worth logging this with Microsoft if that behaviour you've described is persistent. In the meantime, you could write a script that at launch of the application touches the TSNAMES.ORA by performing a DIR or CD on the target folder.


    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.


    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V


    Wednesday, March 13, 2013 4:53 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for your reply Aaron.  I have logged this behaviour with Microsoft and they have confirmed my finding are valid.  Appv 5 was intentionally designed this way because it satisfies 90%+ of the scenario's.   An RFC has been submitted for consideration.....in the meantime I am looking at having a separate application to manage the TNSNames and ENV variable which other apps can use via another connection group.  
    Monday, March 18, 2013 3:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    It might be worth logging this with Microsoft if that behaviour you've described is persistent. In the meantime, you could write a script that at launch of the application touches the TSNAMES.ORA by performing a DIR or CD on the target folder.


    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.


    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V


    Wednesday, March 13, 2013 4:53 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Have you determined with PROCMON what happens in attempt 1 versus attempt 2?

    Nicke Källén | The Knack| Twitter: @Znackattack

    Thursday, March 14, 2013 8:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for your reply Aaron.  I have logged this behaviour with Microsoft and they have confirmed my finding are valid.  Appv 5 was intentionally designed this way because it satisfies 90%+ of the scenario's.   An RFC has been submitted for consideration.....in the meantime I am looking at having a separate application to manage the TNSNames and ENV variable which other apps can use via another connection group.  
    Monday, March 18, 2013 3:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Nicke.......yes, basically doing a TNSPING forces a copy of the TNSNAMES.ORA into the connection group cache.  This can be seen using procmon...so now the main app can referrence TNSNAMES.ORA.   As detailed above Microsoft have confirmed this behaviour.
    Monday, March 18, 2013 3:44 PM