Hi Guillermo,
I was giving information based on the APM 11 training we had.
I just tried the agent in Weblogic and it did work for me.
What happens is you should get a Bootstrap.log in the /wily/logs folder. This will tell us about the startup process, this is what my log showed at startup:
09-04-2019 05:26:59.004 [Process id=200003] Loading Bootstrap Agent
09-04-2019 05:26:59.006 [Process id=200003] Bootstrap Agent install dir: /u01/app/oracle/config/domains/test/wily
09-04-2019 05:26:59.008 [Process id=200003] isRedefineClassesSupported(): true, isRetransformClassesSupported: true
09-04-2019 05:26:59.010 [Process id=200003] Startup arguments passed: null
09-04-2019 05:26:59.010 [Process id=200003] Bootstrap Agent Install location using API:/u01/app/oracle/config/domains/test/wily
09-04-2019 05:26:59.011 [Process id=200003] Bootstrap agent home location: /u01/app/oracle/config/domains/test/wily
09-04-2019 05:26:59.011 [Process id=200003] Agent's policy file location: /u01/app/oracle/config/domains/test/wily/agent.policy
09-04-2019 05:26:59.012 [Process id=200003] release version from policy file: latest
09-04-2019 05:26:59.012 [Process id=200003] introscope.agent.release.version is set to 'latest'
09-04-2019 05:26:59.019 [Process id=200003] Selected agent release version '11.1'
09-04-2019 05:26:59.019 [Process id=200003] Selected agent: /u01/app/oracle/config/domains/test/wily/releases/11.1/Agent.jar for delegation
09-04-2019 05:26:59.024 [Process id=200003] Could not find valid profile passed as system property. So using the default profile: /u01/app/oracle/config/domains/test/wily/releases/11.1/core/config/IntroscopeAgent.profile
09-04-2019 05:26:59.025 [Process id=200003] Updated startup parameters: {bootstrap.jar.absolute.location=/u01/app/oracle/config/domains/test/wily/Agent.jar, core.agent.jar.location=/u01/app/oracle/config/domains/test/wily/releases/11.1/Agent.jar, absolute.profile.location=/u01/app/oracle/config/domains/test/wily/releases/11.1/core/config/IntroscopeAgent.profile, useprofilefromconfigdirifmatch=false, bootstrap.location=/u01/app/oracle/config/domains/test/wily, introscope.agent.release.version=latest, agent.policy.file.location=/u01/app/oracle/config/domains/test/wily/agent.policy, agent.core.dir.path=/u01/app/oracle/config/domains/test/wily/releases/11.1, introscope.agent.bootstrap.home=/u01/app/oracle/config/domains/test/wily}
09-04-2019 05:26:59.025 [Process id=200003] JavaAgentLauncher updating classloader search paths with: /u01/app/oracle/config/domains/test/wily/releases/11.1/Agent.jar
09-04-2019 05:26:59.110 [Process id=200003] Using agent profile /u01/app/oracle/config/domains/test/wily/releases/11.1/core/config/IntroscopeAgent.profile
09-04-2019 05:26:59.110 [Process id=200003] JavaAgentLauncher going to launch Java Agent
09-04-2019 05:27:16.025 [Process id=200003] Successfully launched Java Agent
Then there should be logs also in /wily/releases/<release number>/logs, that is where the IntroscopeAgent and AutoProbe logs that we are familiar with will be written.
If even the Bootstrap.log is not being generated, can you check the Weblogic server log itself to see if it has any complaint to load that first Agent.jar file
Beyond that at the moment I don't have any further suggestions.
Thanks,
David
Original Message:
Sent: 09-03-2019 02:36 PM
From: Guillermo Salgado
Subject: New DXI APM Agent structure and weblogic
Hello David! Excellent tip. :-) The documentation does not mention that neider support. :-(
I followed all procedures to setup the agent at the weblogic:
-Copy the agent (new structure) to the file system
-define the call to -javaagent:-javaagent:$AGENT_HOME/Agent.jar
-the definitions at "Troubleshoot WebLogic to Fix WebAppSupport Failure"
-restart the weblogic but the agent does not create logs or report to the dxi console.
At this point, I don't know that I'm doing wrong.
Have you experience on similar situation?
regards,
Guillermo
Original Message:
Sent: 09-03-2019 02:18 PM
From: DAVID Lewis
Subject: New DXI APM Agent structure and weblogic
Hello Guillermo,
The agent structure is new for APM 11 and can be for SaaS too, you should just have to point to wily/Agent.jar, this is a smaller version of the agent, just to get things started.
There is an agent.policy file which would tell the agent which version to use, it would then go looking for the version specified in the releases folder. You don't need to specify the agent profile as a JVM argument, just the jar file and it works from there.
This structure would make upgrade and downgrade of the agent potentially as simple as modifying the agent.policy file.
So i wouldn't specify the Agent.jar file in the releases folder, perhaps that is where things are going wrong.
Many thanks,
David Lewis
Original Message:
Sent: 09-03-2019 01:54 PM
From: Guillermo Salgado
Subject: New DXI APM Agent structure and weblogic
Hello to all.
Recently a customer was migrated to a new tenant from APM SaaS to DXI APM.
All it's brant new and the oldesd agents point to the old tenant.
I procedure to download the new agent (weblogic), reproduce the configuration at weblogic but when I un tar the tar agent file, this show a new structure diferent from the oldest.
It comes with 2 diferents Agent.jar (diferent size) and a directory /release/11.1/wily/... with all files similar to the oldest version. (I decide to use them)
The documentation doesn't explain nothing about that, but when I configure and restar the weblogic, the agent was invoked, start, looks running on memory, but does not create any logs and does not apperar at DXI Console.
Someone has the same situacion or experience?
Support referer me to the comunities or a hcl. (no coments).
Regards,
Guillermo