Reconfiguring the data collector if you change the offering type on Cloud APM server

If you changed the offering type that you installed on the Cloud APM server from Cloud APM, Base to Cloud APM, Advanced and the WebSphere® Applications agentwas installed and configured with the Cloud APM, Base offering, to use the agent advanced capabilities provided in the Cloud APM, Advanced offering, you must uninstall the previous WebSphere Applications agent and install the agent again with the Cloud APM, Advanced offering. Alternatively, you can reconfigure the data collector for the capabilities to be available in the new offering.

• Remove the agent that you installed with the previous offering and then install the agent in the new offering.
  1. Unconfigure the data collector. For instructions, see WebSphere Applications agent: Unconfiguring the data collector.
  2. Uninstall the WebSphere Applications agent that you installed with the agent package of previous offering. For instructions, see Uninstalling your agents.
  3. Install the WebSphere Applications agent with the agent package in the new offering and configure the data collector again. For instructions, see Configuring the data collector with the simple configuration utility.
• Reconfigure the data collector again to use the capabilities in the new offering.
  1. Edit the offering.id file in the data collector home directory by changing the IOFFERING value to one of the following values, depending on your new offering type:

     BASE

     If your new offering type is Cloud APM, Base Private.

     ADVANCED

     If your new offering type is Cloud APM, Advanced Private.

     The data collector home directory is as follows:

     • install_dir\dchome\7.3.0.14.08
     • install_dir/yndchome/7.3.0.14.08
  2. Reconfigure the data collector to enable diagnostics, transaction tracking, or both in the data collector based on what is supported in the new offering type. For instructions about how to configure the data collector, see Configuring the data collector with the simple configuration utility.
  3. Restart the WebSphere Application Server.
  4. From any page of the Cloud APM console, click System Configuration > Agent Configuration to open the Agent Configuration page. Ensure that the transaction tracking setting matches the capabilities available in your new offering type. If not, update the setting.

     The transaction tracking setting should be enabled for Cloud APM, Advanced, but be disabled for Cloud APM, Base.