Skip to Content

New JDK? Don’t forget about Wily Introscope.

In a bid to keep our monitoring software current, we decided to upgrade the JDK (to SR13) on our CRM 7.0 system. One thing we found out (the hard way) – is that you must redeploy the Wily Introscope agent.

 

We use Wily Introscope extensively to monitor our J2EE instances. Without Wily, J2EE monitoring is like driving your car with a foggy windscreen.

 

Unless you follow these 10 simple steps, the J2EE instance restart will fail and you will be left scratching your head.

 

  1. Remove the following J2EE cluster entries using the configtool.
  2. Shutdown the J2EE instance
  3. Unpack and deploy the new JDK
  4. Restart the J2EE instance.
  5. Go to the Solution Manager RCA workcenter and select the “diagnostics setup” link
  6. Check the Wily Introscope agent, it should be in a “setup not done” state
  7. Press the “setup Introscope Agent”
  8. Check the Wily Introscope agent, it should be in a “needs restart” state
  9. Restart the J2EE instance.
  10. Check the Wily Introscope agent, it should be in a “running” state.

 

Follow these steps and you will continue to enjoy a trouble free Wily Introscope deployment.

 

Please see notes 1024539 and 1008311 for more good JDK tips.

 

Thanks to Tony de Thomasis my AusPost mentor buddy who gave me the inspiration to write my first blog.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply