Examples of processes and methods

This section provides an example of instrumentation process.

To instrument an application using the provided sample

1. Deploy the agent.
2. Start the TMTM Extensible Agent.
3. On the TMTM Services, import the provided sample:
   
   mqsimport -p BMCSOFTWARE --profile ".*" APISamples.zip SA.
4. Change host and platform on activity implementations for samples you wish to try.
5. Generate a model.
6. Deploy the model.
7. Deploy development toolkits.
8. Build the sample:
   • Java: build.bat on Windows or build.sh on UNIX
   • jee: build.bat on Windows or build.sh on UNIX
   • jmx: build.bat on Windows or build.sh on UNIX
9. Deploy runtime toolkits:
   • java: Goes in btmsamples/java
   • jmx: Java EE Runtime goes in btmsamples/jee
10. For jmx you need to enable JMX monitoring for the JRE of the application. In the simplest case edit the management properties file that can be found in the JRE lib/management directory to include the following properties:
    
    com.sun.management.jmxremote.ssl=false
com.sun.management.jmxremote.ssl.need.client.auth=false
com.sun.management.jmxremote.authenticate=false
    
    Note that this enables unauthenticated access to the JMX agent. Review the management properties file and ensure that the settings you use comply with your sites security policy.
11. For both jee and jmx, you must start the Java EE Service toolkit. Unzip pkg_<platform>_btmjee.zip located in the agent distribution where required and then edit the btmjee.xml for your connection properties. For the jmx sample, uncomment the connection properties for Java. For the jee sample, uncomment BEA or IBM for whichever application server you are using.
    
    btmjee --console or btmjee --start
12. Run sample and other steps per sample (ex. start btmjee):

• • Java: run.bat on Windows or run.sh on UNIX
  • jee: Deploy JavaEEBTMSampleServlet.ear to Application Server. Go to http://localhost/JavaEEBTMSampleServlet/JavaEEBTMAPISample.html
  • jmx: run.bat on Windows or run.sh on UNIX