Hello Jeremy,
Regarding the agent file, use the default agent package.
Here is an example how to configure the java agent with Mule on Linux:
1. Create an account with Mulesoft Cloud Platform
2. Install API Mule Gateway 2.2.0 on the Linux setup.
3. In the wrapper.conf file, modify the following :
wrapper.java.additional.15=-javaagent:/opt/wily/Agent.jar
wrapper.java.additional.16=-Dcom.wily.introscope.agentProfile=/opt/wily/core/config/IntroscopeAgent.profile
wrapper.java.additional.17=-Danypoint.platform.client_id=XXXXX
wrapper.java.additional.18=-Danypoint.platform.client_secret=XXXXX
4. Put some dummy apps under /apps folder
5. Register the Linux Server with Mulesoft Cloud Platform and it updates the wrapper.conf file.
6. Start the gateway
Please note that if you using a pre-10.3 agent, there is a known issue affecting Mule environments: the Mule gateway registers on-startup with the Mulesoft management layer. The mule_ee.log on the gateway will show that the registration completes successfully however, within the space of 60 mins it will disconnects.
To workaround this issue, open the introscopeAgent.profile, set introscope.agent.deep.entrypoint.enabled=false
About the fieldpack, open a support case, we can get you a copy of the Mule ESB fieldpack.
Thanks,
Sergio