Dear Ashok There is our AppDynamics configuration for the Siebel SBS: create named subsystem "JAVAMX384qAppD" for subsystem "JVMSubSys" with DLL="D:\\APPL\\Siebel\\jdk\\jre\\bin\\server\\jvm.dll", CLASSPATH="D:\\APPL\\Siebel\\siebsrvr\\CLASSES\\Siebel.jar;D:\\APPL\\Siebel\\siebsrvr\\CLASSES\\SiebelJI_deu.jar;D:\\APPL\\Siebel\\siebsrvr\\CLASSES\\SiebelJI_enu.jar;D:\\APPL\\Siebel\\siebsrvr\\jms;D:\\APPL\\Siebel\\siebsrvr\\jms\\jms.jar;D:\\APPL\\Siebel\\siebsrvr\\jms\\jndi;D:\\APPL\\Siebel\\siebsrvr\\rules\\jbs.jar", VMOPTIONS="-Xrs -Xmx384M -server -Djavax.net.ssl.trustStore=D:\\APPL\\Siebel\\siebsrvr\\jms\\***TrustStore.jks -Djavax.net.ssl.trustStorePassword=*** -Djavax.net.ssl.keyStore=D:\\APPL\\Siebel\\siebsrvr\\jms\\client.jks -Djavax.net.ssl.keyStorePassword=*** -Dappdynamics.agent.applicationName=***_kt0 -Dappdynamics.agent.tierName=mtsjvm -Dappdynamics.agent.reuse.nodeName=true -Dappdynamics.agent.reuse.nodeName.prefix=mtsjvm -Dappdynamics.agent.runtime.dir=D:\\Temp\\connect_appd\\ -Dappdynamics.agent.logs.dir=D:\\Temp\\connect_appd\\log\\ -Dappdynamics.controller.hostName=***.zkb.ch -Dappdynamics.agent.accountAccessKey=*** -Dappdynamics.controller.port=8181 -Dappdynamics.controller.ssl.enabled=true -javaagent:D:\\APPL\\AppDynamics\\AppServerAgent\\javaagent.jar" We found a memory leak related to the process management of siebel. Also the "Shutting down AppDynamics Agent" and the mark as historical doesn't work. Probably because the siebel implementation of java via java.dll doesn't stop the process anf threads like a normal jvm. With the same configuration and a "normal jvm" we don't have that problem. On the screenshots you can see some views from the Siebel JBS in AppDynamics. Best regards Marc ... View more

Dear Ravi You can use the Machine Agent (zip) "(Standalone machine agent (no JRE) to monitor your servers.)" with a jre that are compiled for aix. For example install over smitty: https://surajgyawali.com/2015/10/15/how-to-setup-ibm-java-runtime-environment-jre-and-add-jre-as-a-system-variable-on-aix-7-1/ Best regards Marc ... View more

Dear Ahmad We are currently in a POC for monitoring some Java Business Service in Siebel. It works with a configuration for Dynamic Environments: https://docs.appdynamics.com/display/PRO45/Instrument+JVMs+in+a+Dynamic+Environment important is also the -Dappdynamics.agent.auto.node.prefix= setting because the jvms are start and stop dynamic: https://docs.appdynamics.com/display/PRO45/Java+Agent+Configuration+Properties#JavaAgentConfigurationProperties-AutoNodeNamePrefixProperty   If you want i can post a sample enterprise configuration next week. Best regards Marc ... View more

Dear santhosha I've deploy the SampleApp around three or four months ago. As i remind i've the same issue as you. I resolved the issue with the following steps: 1. comment out "downloadInstallers" on line 181 in rest/install-appdynamics.sh (Because the download isn't work for me) 2. Download the current app, machine and db agent from https://download.appdynamics.com and store in /tmp/appdagents 3. Change the path on the function installAppServerAgent,installDatabaseAgent and installMachineAgent in rest/install-appdynamics.sh for example: installMachineAgent() { echo "Installing Machine Agent to ${MACHINE_AGENT_HOME}..." unzip -qo ${MACHINE_AGENT_ZIP} -d ${MACHINE_AGENT_HOME} && rm ${MACHINE_AGENT_ZIP} } to installMachineAgent() { echo "Installing Machine Agent to ${MACHINE_AGENT_HOME}..." unzip -qo /tmp/appdagents/machineagent-bundle-64bit-linux-4.5.0.1285.zip -d ${MACHINE_AGENT_HOME}  } IIRC i have to do this again in the OverlayFS (/var/lib/docker/overlay2/[...] again after the first run. On the node.js component you can also activate EUM for the angular part. Best regards Marc ... View more