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
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
is there any update to this statement.
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:
If you want i can post a sample enterprise configuration next week.
Best regards
Marc
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
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
Hi Marc and Community,
Wondering if in 2022 anyone has more information on Siebel integration with AppDynamics. Most recent thread that I could find on this is from 2020, referring to this thread for further information.
This page from Oracle is meant to explain this setup, however without Oracle Support account I am unable to view. Anyone know of any documentation from AppDynamics for this integration?
Regards,
Tim
Hi @Tim.de Boer,
I was not able to find anything either except for this Idea Exchange post: https://community.appdynamics.com/t5/Idea-Exchange/Siebel-monitoring/idi-p/43047
Note: Idea Exchange can only be accessed by AppD customers who are under contract at this time.
Good day @Ryan.Paredez ,
This will bring us further in the right direction, thank you for sharing!
Kind regards,
Tim
Hi Tim
We recently instrumented a Siebel Environment - IP17 and since the change in architecture from Siebel from their old setup, we can instrument some of the key components as below as they are all Java based
1. Siebel Application Interface Servers
2. Siebel Gateway Servers
3. Siebel Enterprise Servers
4. Siebel BIP Servers
We have instrumented the above, as well as added End User Monitoring into the Siebel Postload script to track sessions from the Front Ends.
The main components where you can see the actions are the Application interface nodes, which we can now track and correlate the request from the front end with.
The majority of work is now extracting the important data from the Siebel Requests in these Java Components which we have made some good progress on, with the absence of a deep technical knowledge around the internal working of Siebel to know where to extract the data This then enables you to track and build business journey's with, which is our current goal e.g. to see an end-2-end CRM Create Order Journey
Ciao
Hi @Tim.de Boer,
I should have mentioned giving it a vote (thumbs up) and subscribing to the Idea so you get updates on the status of the Idea. Also, if you have further info to add to the Idea, leave a comment with your use case to provide further content for AppD PMs and other customers.