DX NetOps

Expand all | Collapse all

PC 3.2 installation

Jump to Best Answer
  • 1.  PC 3.2 installation

    Posted 11-03-2017 09:00 AM

    Dear CA Guru's,


    During the installing of Performance center (v3.2) we encounter the following error in the Performance_Center_Install_10_27_2017_15_24_48.log log file


    Custom Action: com.ca.im.installanywhere.action.GetUserInstallDir
    Status: FATAL ERROR
    Additional Notes: FATAL ERROR - class com.ca.im.installanywhere.action.GetUserInstallDir FatalInstallException: $APP_DIR$ is not a valid directory name


    It seems that a certain variable is not properly defined ($APP_DIR$)

    We are running RHEL 7.4, dubblechecked a prereqs and checked with Linux Team, any ideas??


    Kind regards,

    Lieven Stubbe

    Belgian railways

  • 2.  Re: PC 3.2 installation

    Broadcom Employee
    Posted 11-03-2017 12:11 PM

    Hi Lieven, Dominiek,


    Is there a RH 7.3 system you can test with? I wonder if a difference in 7.4 might be causing this as it's not actually a supported OS per the Wiki Docs.


    Review Installation Requirements and Considerations - CA Performance Management - 3.2 - CA Technologies Documentation 


    What install path did you select when the PC install was launched? Default? Something custom?




  • 3.  Re: PC 3.2 installation

    Posted 11-06-2017 05:00 AM

    Hi Mike,


    Concerning RH 7.4, Simac Belgium (our reseller) did tests in their test environment and they got it working.

    Concerning the install path, we used a different path than proposed in the docs (Default: /opt/CA), the second time we wanted to (re)install PC, the installation didn't ask for an installation dir anymore, so we suppose the installation process keeps using the old (custom) directory.  How do you trigger (read:which tmp files need to be deleted) that the installation procedure asks the names of dirs again?


    Kind regards,

    Lieven Stubbe

    Belgian railways

  • 4.  Re: PC 3.2 installation
    Best Answer

    Broadcom Employee
    Posted 11-06-2017 02:24 PM

    Hi Lieven:


    Glad you got it working, but to repeat what Mike mentioned, redhat 7.4 is not supported for 3.2, and that may be the cause of the error you got.  There may be some difference in that version of redhat that caused the issue you saw


    That said, you could check for a file called /var/.com.zerog.registry.xml.  That is the file installanywhere reads to see if it is an upgrade or a fresh install.  The install tries to read that from that file (inside InstallAnywhere). If it does, it uses that. if not, I'd assume that it sets it based on their choice for where to install to.


    Given that you are all set, I am going to close this thread