Discussion Feed

Has Anyone actully tried to instrument the actual WebLogic Admin Server ?   We are having some issues with an LDAP process and would like to instrument the admin server so we can see exactly where our calls are going and what is going on in that end point.   I used the standard config we use to instrument our app but it is not showing up in the console.   So I was wondering if anyone here had done this.   normal config to instrument our app. -javaagent:/opt/appdynamics/appAgent/javaagent.jar -Dappdynamics.agent.applicationName=cps-test -Dappdynamics.agent.tierName=HRP_UI  -Dappdynamics.agent.nodeName=claimserver_nodenamehere   config we used to instrument admin -javaagent:/opt/appdynamics/appAgent/javaagent.jar -Dappdynamics.agent.applicationName=cps_test -Dappdynamics.agent.tierName=HRP_ADMIN -Dappdynamics.agent.nodeName=admin_nodenamehere   Pretty much the same.   I also added an entry to the weblogic.policy to make sure weblogic security features had access to /opt/appdynamics/appAgent-   ... View more

Hi -   We had an install of the 4.3 controller. we installed it to /opt/appdynamics/controller When we ran the command line update of 4.4 platform, it installed a new mysql DB and did not replace files in /opt/appdynamics/controller/bin   So our startup is still starting 4.3.   This install rutine seemed a lot different than the controller install for 4.3.   What are we missing ? Why did this not upgrade the 4.3 package, why did it install a new mysql.   What is the standard method for upgrades ?  the 4.3 package we used was controller_64bit_linux-4.3.7.1.sh the 4.4 package was, platform-setup-x64-linux-4.4.0.4220.sh   Are we using the correct bins ? Is this a matter of pointing the install to the correct location ?    ... View more