Appdynamics monitoring for Siebel

[Abhishek.Singhal]

Hi,

I'm looking out for ways to monitor Siebel performance through appdynamics.

The problem is I'm not sure which agent to use monitor Siebel application and Siebel gateway servers.

Any help on this will be much appreciated.

Thanks.

[Cody.Naumann · Accepted solution]

Hi Abhishek,

As far as I know, AppDynamics cannot be used to monitor Siebel. See: https://community.appdynamics.com/t5/Archive/Does-Appdynamics-Support-Siebel/m-p/22135

@Jean-Baptiste.Marzolf -- has there been any change to this in the last year?

Cody

[Abhishek.Singhal]

Thank you Cody!!

[ahmad.alkhgandaqji]

is there any update to this statement.

[Marc.Pfister]

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#JavaAgentConfiguratio...

If you want i can post a sample enterprise configuration next week.

Best regards

Marc

[ASHOKREDDY.BANA]

Hi Marc,

Could you please share the sample enterprise configuration.

we are using siebel CRM and Oracle HTTP server as backend. we have enabled AppD at OHS end but it is not showing the transaction. we may need to do something at Siebel part also. 

Could you please respond as soon as you can.

Thanks,

Ashok Bana

[Marc.Pfister]

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