This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SS LR integration

Hi,

 

since we are unable to open this url: sitescopeserver:<port>/.../SiteScope (it gives 404 error) we are not able to connect from LR controller to the SiteScope.

 

We are using LR 12.01, SIS 11.24 SiteScope for Load testing.

We have tried everything, reinstall, etc but still does not work.

 

On the Freemium 11.22 this url works fine.

 

Thank you.

 

Regards,

Aurél

Tags:

  • 0 in reply to 
    I'll check it and let you know my findings.
  • 0
    We recently had a problem integrating APM with SiS 11.23. After checking the firewall, making sure we can connect using the sitescopeserver:port combination from a browser, it turned out to be related to the SiteScope\groups\users.config file not containing the default values. To fix it, we had to update our APM config with the correct _id and username as shown in the users.config file. This may not apply to you but I thought I'd mention it. http://archimedesnewton.com/2012/04/12/integrating-loadrunner-11-and-sitescope-11-with-authentication-enabled/
  • 0 in reply to 
    Problem here may be that you patched 11.20 for Load Testing with 11.24. Patches were not intended for LT versions but sometimes they work. Can you uninstall 11.24 and attempt to integrate 11.20 LT ? If it works then patch up again and check if integration breaks.
  • 0 in reply to 

    Hi,

     

    I don't want to test suggestions that are not 100% the solutions anymore. I have tested so many things based on the advices of the Support but it is like a guessing game. It seems noone knows what might cause it, so I feel like a part of a big experiment.

     

    Tell me that you are 100% sure that it will work with 11.20 and I will do it.

     

    By the way we tried to use the 11.20 first and it did not work, then the support told us to upgrade because the LR 12.01 does not support SiS 11.20 only 11.22 .

     

    We pay for the support a lot and still waiting for a solutions after more then a months.

     

    Check and confirm to me if topaz should work in the SiS for LR too, confirm that this is how they should connect and communicate. If so, tell me what can cause it not working and tell me steps how to fix it. But please stop guessing.

     

    Thank you.

     

    Regards,

    Aurél

  • 0 in reply to 
    As a matter of fact topaz URL shows in Standard version as a plus, because it is used by LR integration so obviously it should show in LT version. I'm sure it should work in 11.20 LT. Patches tend to break integration, most likely with PC (port 8080) but not with LR which is pretty simple, LR reads the topaz URL.

    So I'm guessing your instance is badly patched or corrupted if you get 404 error that's why I recommend to test topaz URL in plain 11.20.
  • 0 in reply to 
    As a matter of fact topaz URL shows in Standard version as a plus, because it is used by LR integration so obviously it should show in LT version. I'm sure it should work in 11.20 LT. Patches tend to break integration, most likely with PC (port 8080) but not with LR which is pretty simple, LR reads the topaz URL.

    So I'm guessing your instance is badly patched or corrupted if you get 404 error that's why I recommend to test topaz URL in plain 11.20.
  • 0 in reply to 
    As a matter of fact topaz URL shows in Standard version as a plus, because it is used by LR integration so obviously it should show in LT version. I'm sure it should work in 11.20 LT. Patches tend to break integration, most likely with PC (port 8080) but not with LR which is pretty simple, LR reads the topaz URL.

    So I'm guessing your instance is badly patched or corrupted if you get 404 error that's why I recommend to test topaz URL in plain 11.20.
  • 0 in reply to 

    Hi,

     

    I told you that we started with version 11.20 (to be exact: HP SiteScope 11.20 32-bit JVM, Build 3571) and it did not work, so it is not about patching.

     

    Based on your confidence about your own knowledge I tried it again (**bleep**, why did I belive you and wasted my time again?) with the 64-bit version (HP SiteScope 11.20 64-bit JVM, Build 3571) and still the same error happens. No topaz URL.

     

    What's next?

     

    Regards,

    Aurél

  • Verified Answer

    0 in reply to 

    Hi All,

     

    this is not a suggestion or taks to follow,just a FYI after I tested a bit:

     

    standard SiteScope (not SiS for LR) 11.23 and 11.24 on Windows

     

    When I access

     http://<sis>:8080/SiteScope/cgi/go.exe/SiteScope?page=topaz&operation=config&account=administrator

    (or whatever the port for the UI has been set to)
    I get the error
     404 - Page Unavailable 
     The page you are trying to access is unavailable.
     

    When I access

     http://<sis>:8888/SiteScope/cgi/go.exe/SiteScope?page=topaz&operation=config&account=administrator
    I get the expected XML file back
     <?xml version="1.0" ?>
    - <PerformanceMonitor>
    - <object class="group" name="SGTest" desc="SGTest">
    - <object class="monitor" name="Logfile swvm406 server_statistics.log" desc="Logfile swvm406 server_statistics.log" type="LogMonitor" host="swvm406.bgr.hp.com">
      <counter name="lines" desc="lines" />
      <counter name="matches" desc="matches" />
      <counter name="matches/min" desc="matches/min" />
      <counter name="lines/min" desc="lines/min" />
      <counter name="UsedMemory" desc="UsedMemory" />
      </object>

     

    What I observer however is that SiS - when accessing the normal GUI port (for example 8080)

    shortyl jumps to the Login page (you can see that the page title changes to "Login - SiteScope"

    and only then reports error 404.

     

    I found one CR stating

     AuthorizedIP parameter in the master.config to allow access to only restricted IP addresses is not working anymore

    dealing with the issue that using _autorizedIP in master.config can invalidate the topaz URL. 

     

    So in general SiteScope still serves this URL.

     

    Greetings

    Siggi

     

  • 0 in reply to 

    Hi,

     

    I have never used port 8080 for cgi.exe URLs alias Topaz URL, if that redirected in other versions then that's a plus; but not correct way to use it in my opinion.

     

      if using port 8888 fixed your issue then it doesn't makes sense  because I stated default port is 8888 in my first comment, which you acknowledged you tested:

     


    @kenneth.gonzalez wrote:
    Hi,

    What's the port you're using in the URL? by default is 8888, but can be customized in master.config. You're right, for LR integration you need to use SiS for Load Testing. I'm not aware of any change on integration set up so this URL should open fine.