Unable to install the package(WxAppDynamicsAgent) in Integration server

[andrewprabinrajyesuraj]

 Exported the zip file from the github (WxAppDynamicsAgent)
 Placed it in */replicate/inbound directory of wM server FS and installed it
 Installation was completed and I could see the package installed in Packages>Management list (I don’t think the package has been installed properly as I don’t see any contents in the package from designer)
 The next instruction was “Then restart your runtime server. Open the admin portal and click on Packages -> Management”
 When I restarted the wM IS App server the package (WxAppDynamicsAgent) was not in the list of Packages -> Management

can you let me know how to proceed there is an SI created in SAG empower SI-560905 regarding this as well

[johnpcarter]

I think your unzip did not create the package at the right level, it may have been in a subfolder hence why it did shows up in packages but is empty.

I would not recommend the technique you used. Either use wpm cli tool or do a git clone directly into your packages directory. The installation is explained in the README.md file

Check the content of the package and verify that the ns folder is there before then restarting your Integration Server.

[andrewprabinrajyesuraj]

Hi John,

I was able to install the WxAppDynamicsAgent package by unzipping in packages folder and restarting the IS server.

Even after I updated the controller-info.xml in (*/packages/WxAppDynamicsAgent-main/resources/ver23.12.0.35361/conf) and restarting the IS I still see the same message attached. the controller details are correct.

kindly let me know how to proceed here ?

[johnpcarter]

Is this a complete screenshot of your browser window ? I don't see anything else ?
Can you confirm what version of webMethods that you have deployed the package to ?
Also please stop your server, delete the server.log file and then restart, access the above page and then upload a copy of your server log here.
thanks.

[andrewprabinrajyesuraj]

The screen shot was what I see when I click the home button of the installed AppD package, wM 10.7 version is used . Attaching logs

server.log

[johnpcarter]

The java services in the package had been recompiled to java 17 by mistake. I have now recompiled them for backward compatibility on the main branch and I have now also created an official 2.0.0 release.
Give this a try and let me know how you get on
thanks.

[andrewprabinrajyesuraj]

Hi John,

Thanks for the new package , which worked .

In the merge custom_wrapper.conf file I see the below entries , shouldn't the path to javaagent.jar be the the one in the version folder (e.g. -javaagent:./packages/WxAppDynamicsAgent/resources/ver23.12.0.35361/javaagent.jar) ?

Let me know which javaagent.jar needs to be referred [I updated the controller-info.xml in (*/packages/WxAppDynamicsAgent-main/resources/ver23.12.0.35361/conf)] ?

AppDynamics

wrapper.java.additional.601=-Xbootclasspath/a:./packages/WxAppDynamicsAgent/resources/javaagent.jar:./packages/WxAppDynamicsAgent/resources/agent-api.jar:"%JAVA_BOOT_CLASSPATH%"
wrapper.java.additional.602=-javaagent:./packages/WxAppDynamicsAgent/resources/javaagent.jar

[johnpcarter]

The setup is rather strange and I don't why AppDynamics insist on having the jar in two places but they do. The one advantage is that you do not need to reconfigure your wrapper if swapping out the AppDynamics for a different version.

[andrewprabinrajyesuraj]

Hi John ,

AppD controller was able to detect the node after placing their cacerts.jks file in */config.

Noted the ^M character insertion in wM IS custom_wrapper.conf file every line after appD entry merge, can you check on this ?
Will you be releasing newer version of this package as and when AppD agent version is upgraded, please me know ?

[chini007]

Hello @johnpcarter,
I think the AppD agent shouldnt be part of package and rather be outside, as it will be maintained by customer and will have different lifecycle than our IS and package, what do you think?

[johnpcarter]

You can do this of course. I bundle it for ease of use, getting the AppD agent and configuring it is not simply hence why I took this route.

[johnpcarter]

We will periodically update the package to include the latest/greatest AppDynamics library. You can always choose to swap out the existing one or externalise it for a different version.