Service Virtualization

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

LISA Invoke API

  • 1.  LISA Invoke API

    Posted Aug 15, 2018 10:02 PM

    Hi

     

    When I a using LISA Invoke API to run the test i am getting "This page can’t be displayed " error. 

     

     

    Devtest Version - 10.2.4

     

    Registry IP - 10.1.111.2

    Cordinator & Simulator IP - 10.1.111.3

     

    Note:- Team city going to checkout the files in "10.1.111.3" and I am executing the below url in "10.1.111.3"

     

    http://10.1.111.3:1505/lisa-invoke/runTest?testCasePath=D:/Lisa/Tests/test1.tst&stagingDocPath=D:/Lisa/Tests/StagingDocs/Run1User1Cycle.stg&configPath=D:/Lisa/Configs/TBCICS.config

     



  • 2.  Re: LISA Invoke API

    Broadcom Employee
    Posted Aug 15, 2018 10:39 PM

    Yes that is the correct behavior because your url points to 1505 port on the coordinator/simulator box which is incorrect. It should instead point to the Registry box which is on .2. Change the url to point to .2 and it should work as long as the files are in the location you mentioned.



  • 3.  Re: LISA Invoke API

    Posted Aug 15, 2018 10:50 PM

    I am getting below error

     

    My project copied to 10.1.111.3

     

    -<invokeResult>


    -<method name="RunTest">


    -<params>

    <param name="testCasePath" value="D:/Lisa/Tests/test1.tst"/>

    <param name="configPath" value="D:/Lisa/TBCICS.config"/>

    <param name="callbackKey" value="5EEBF7D4A0FE11E8961E005056917AED"/>

    <param name="coordName" value="Coordinator"/>

    <param name="stagingDocPath" value="D:/Lisa/Tests/StagingDocs/Run1User1Cycle.stg"/>

    </params>

    </method>

    <status>ERROR</status>


    -<result>

    <message>An error occured in 'runTest'. Message: The test case is not in a project. Test Case:D:/Lisa/Tests/test1.tst Stack: java.lang.IllegalArgumentException: The test case is not in a project. Test Case: D:/Lisa/Tests/test1.tst at com.itko.lisa.model.mar.ModelArchiveInfo.createTestMARInfo(ModelArchiveInfo.java:248) at com.itko.lisa.model.mar.TestMariBuilder.build(TestMariBuilder.java:102) at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.runTestNewSchool(LaunchLisaTestHelper.java:469) at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.runTest(LaunchLisaTestHelper.java:417) at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.invokeLisaTest(LaunchLisaTestHelper.java:273) at com.itko.lisa.invoke.webapp.InvokeLisaTestServlet.service(InvokeLisaTestServlet.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) at com.ca.devtest.http.XSSFilter.doFilter(XSSFilter.java:55) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.server.Server.handle(Server.java:524) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) at java.lang.Thread.run(Thread.java:745)</message>

    </result>

    </invokeResult>



  • 4.  Re: LISA Invoke API

    Broadcom Employee
    Posted Aug 15, 2018 10:41 PM

    Hi,

     

       As you have mentioned that, registry service is running on server 10.1.111.2, please use the lisa-invoke url as below and test it. Because, lisa-invoke API call will be triggered using registry host name (not with Teamcity ip-address)

     

    http://10.1.111.2:1505/lisa-invoke/runTest?testCasePath=D:/Lisa/Tests/test1.tst&stagingDocPath=D:/Lisa/Tests/StagingDocs/Run1User1Cycle.stg&configPath=D:/Lisa/Configs/TBCICS.config

     

    Thanks & Regards

    Srikanth Gajawada



  • 5.  Re: LISA Invoke API

    Posted Aug 15, 2018 10:51 PM

    I am getting below error

     

    My project copied to 10.1.111.3

     

    -<invokeResult>


    -<method name="RunTest">


    -<params>

    <param name="testCasePath" value="D:/Lisa/Tests/test1.tst"/>

    <param name="configPath" value="D:/Lisa/TBCICS.config"/>

    <param name="callbackKey" value="5EEBF7D4A0FE11E8961E005056917AED"/>

    <param name="coordName" value="Coordinator"/>

    <param name="stagingDocPath" value="D:/Lisa/Tests/StagingDocs/Run1User1Cycle.stg"/>

    </params>

    </method>

    <status>ERROR</status>


    -<result>

    <message>An error occured in 'runTest'. Message: The test case is not in a project. Test Case:D:/Lisa/Tests/test1.tst Stack: java.lang.IllegalArgumentException: The test case is not in a project. Test Case: D:/Lisa/Tests/test1.tst at com.itko.lisa.model.mar.ModelArchiveInfo.createTestMARInfo(ModelArchiveInfo.java:248) at com.itko.lisa.model.mar.TestMariBuilder.build(TestMariBuilder.java:102) at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.runTestNewSchool(LaunchLisaTestHelper.java:469) at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.runTest(LaunchLisaTestHelper.java:417) at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.invokeLisaTest(LaunchLisaTestHelper.java:273) at com.itko.lisa.invoke.webapp.InvokeLisaTestServlet.service(InvokeLisaTestServlet.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) at com.ca.devtest.http.XSSFilter.doFilter(XSSFilter.java:55) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.server.Server.handle(Server.java:524) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) at java.lang.Thread.run(Thread.java:745)</message>

    </result>

    </invokeResult>



  • 6.  Re: LISA Invoke API

    Broadcom Employee
    Posted Aug 15, 2018 11:08 PM

    Hello,

      Thank you for validating using registry ip. From above error, it says that test case "D:/Lisa/Tests/test1.tst" is not available on server. So, can you please verify whether the test case is available on correct path on registry server. Please make sure test case, config file and staging doc are on correct path in registry machine (10.1.111.2).

     

    Thanks & Regards

    Srikanth Gajawada



  • 7.  Re: LISA Invoke API

    Posted Aug 15, 2018 11:26 PM

    I can't copy manually. Automatically copied from team city agent. 



  • 8.  Re: LISA Invoke API
    Best Answer

    Broadcom Employee
    Posted Aug 15, 2018 11:29 PM

    The answer to this question is on this link, please check - the xxxxx.***.test.root property that needs to be set to the right location. 


    https://docops.ca.com/devtest-solutions/10-3/en/using/using-the-apis/lisa-invoke-api




  • 9.  Re: LISA Invoke API

    Broadcom Employee
    Posted Aug 16, 2018 04:20 PM

    Jays - were you able to get this to work?



  • 10.  Re: LISA Invoke API

    Posted Aug 29, 2018 05:06 AM

    I started the registry in the same machine. 



  • 11.  Re: LISA Invoke API

    Posted Sep 05, 2018 11:22 AM

    Hello Jayachandran.Anbalagan,

     

    Is this still an issue for you?

     

    Were you able to get it working?

     

    Thank you,

    Heloisa



  • 12.  Re: LISA Invoke API

    Posted Oct 01, 2018 10:28 PM

    Issue fixed