Service Virtualization

  • 1.  Error during DevTest installation

    Posted Jan 11, 2017 07:53 AM

    Hello,

     

    Since we are expanding our VSE's, we are installing DevTest on 2 new Linux servers.

    So far, we have installed java and tomcat on the servers, and are now installing the DevTest software based on the response.varfile that we retrieved in LISA_HOME\install4j folder from a previous installation on another server.

     

    This is the content of the response.varfile:

    #install4j response file for DevTest Solutions 8.4.0 (build 8.4.0.227)
    #Wed Apr 13 11:02:10 CEST 2016
    sys.adminRights$Boolean=true
    sys.programGroupDisabled$Boolean=true
    installServer=Yes
    createDesktopLinkAction$Boolean=false
    installWorkstation=Yes
    installEnterpriseDashboard=Yes
    sys.languageId=en
    sys.installationDir=/appl/casvp00/CA/DevTest
    licenseXmlFile=/appl/casvp00/FBBE/bin/install_files/devtestlic.xml
    installDemoServer=No

     

    Now when running the installation (./devtest_linux_x64.sh -q -varfile response.varfile), we receive the following error message:

     

    Unpacking JRE ...

    Starting Installer ...

    log4j:WARN No appenders could be found for logger (com.itko.util.XMLUtils).

    log4j:WARN Please initialize the log4j system properly.

    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

    In screen "Display CA license agreement [LicenseAgreementScreen]", property "Validation expression":

    java.lang.NullPointerException

            at I4jScript_Internal_606.eval(I4jScript_Internal_606.java:18)

            at I4jScript_Internal_606.evaluate(I4jScript_Internal_606.java:30)

            at com.install4j.runtime.installer.helper.Script.evaluate(Unknown Source)

            at com.install4j.runtime.installer.ContextImpl.runScript(Unknown Source)

            at com.install4j.runtime.installer.ContextImpl.runScript(Unknown Source)

            at com.install4j.runtime.installer.ContextImpl.runBooleanScript(Unknown Source)

            at com.install4j.runtime.installer.ContextImpl.runBooleanScript(Unknown Source)

            at com.install4j.runtime.installer.frontend.headless.UnattendedScreenExecutor.handleScreen(Unknown Source)

            at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.execute(Unknown Source)

            at com.install4j.runtime.installer.controller.Controller$1.run(Unknown Source)

            at java.awt.event.InvocationEvent.dispatch(Unknown Source)

            at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

            at java.awt.EventQueue.access$200(Unknown Source)

            at java.awt.EventQueue$3.run(Unknown Source)

            at java.awt.EventQueue$3.run(Unknown Source)

            at java.security.AccessController.doPrivileged(Native Method)

            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

            at java.awt.EventQueue.dispatchEvent(Unknown Source)

            at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

            at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

            at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

            at java.awt.EventDispatchThread.run(Unknown Source)

     

    Any help is highly appreciated.

     

    Kind regards,

    Dave



  • 2.  Re: Error during DevTest installation
    Best Answer

    Posted Jan 11, 2017 08:29 AM

    In case anyone should ever experience the same error, adding below line in the response.varfile solved the issue:

    caAgreementChoice=2



  • 3.  Re: Error during DevTest installation

    Broadcom Employee
    Posted Jan 11, 2017 09:35 AM

    Here is the link that show a sample response.varfile, and i noticed you were missing a few items in the file.

    "Installing DevTest Solutions with a Silent Install - DevTest Solutions - 8.4 - CA Technologies Documentation "

     

    That line you mentioned above is what also needs to be there.  Glad it is working for you.