On the JMeter's machine you shouldn't need anything other than what your browser needs in order to connect to that remote instance (proxy configuration, if required). So you need to do a functional validation with very light load at first and make sure that your test plan behaves similar to what you see in the browser. Remote instances often come with different configurations than what you'd get locally (tightened security configurations, actual passwords set for default users, integrated authentication systems etc) and the network where you do the load/stress test needs to support the load you intend to generate.
Cheers, Adrian On Thu, Apr 26, 2018 at 11:59 PM, Pankaj Rohira <[email protected]> wrote: > I need help in doing load testing for AEM (Adobe Experience Manager) using > JMeter. I wrote my scripts and it's working fine on my local. Using JMeter, > I can login, perform Omni Search and able to test other custom > functionalities also on my local AEM instance. When I try to do the same > thing on remote instances, JMeter is error'ing out. > > > > First step is to login to remote instance - I am doing a POST call to > /libs/granite/core/content/login.html/j_security_check and passing all the > parameters but I get a 403 Forbidden error. As part of the POST call, I am > passing necessary Request Headers as well such as: Host, User-Agent, > Referer. (I actually traced the POST call using Firefox when I normally > login to AEM using browser and grabbed all the Request Headers from there). > > > > Just wondering if I need to enable RMI or something on remote instance to > connect or am I missing anything? > > > > Thanks. >
