IBM webMethods Integration Server

  1. After fix installation, copy the plug-in JAR file:
    • From the directory <INSTALL-DIR>\E2EMonitoring\agent\plugins\uhm-onpremise-is-plugin.jar
    • To directory <INSTALL-DIR>\IntegrationServer\lib\jars\
  2. To set up logs, copy the logback.xml file
    • From the directory <INSTALL-DIR>\E2EMonitoring\agent\config\e2ecustomlogback.xml
    • To directory <INSTALL-DIR>\IntegrationServer\instances\default
    Note: If you cannot locate the file e2ecustomlogback.xml in the installation, then install the latest fixes.
  3. Add the following lines at the end of the file:<INSTALL-DIR>\profiles\IS_default\configuration\custom_wrapper.conf
    • Microsoft Windows 
      wrapper.java.additional.501=-Xbootclasspath/a:..\..\..\E2EMonitoring\agent\uhm-apm-agent.jar;"%JAVA_BOOT_CLASSPATH%"
wrapper.java.additional.502=-javaagent:..\..\..\E2EMonitoring\agent\uhm-apm-agent.jar=logging.dir=.\logs\
    • Linux
      wrapper.java.additional.501=-Xbootclasspath/a:../../../E2EMonitoring/agent/uhm-apm-agent.jar:"%JAVA_BOOT_CLASSPATH%"
wrapper.java.additional.502=-javaagent:../../../E2EMonitoring/agent/uhm-apm-agent.jar=logging.dir=./logs/
    Note: From v10.15 onward, the product code UHM changed to UHA. So, replace uhm-apm-agent.jar with uha-apm-agent.jar in the preceding lines .
  4. Open the file: <INSTALL-DIR>\profiles\IS_default\configuration\custom_wrapper.conf, add the property:
    • Microsoft Windows:
        	wrapper.java.additional.503=-Dlogback.configurationFile=.\e2ecustomlogback.xml
    • Linux:
        	wrapper.java.additional.503=-Dlogback.configurationFile=./e2ecustomlogback.xml
  5. If multiple tenant connections are supported in Integration Server and a custom tenant connection is being used, then open the file: <INSTALL-DIR>\E2EMonitoring\agent\config\agent.config and set the following properties:
    Property Description
    agent.onprem_multitenant_alias = ${SW_AGENT_ONPREM_MULTITENANT_ALIAS:default} Uncomment this property and replace default with the tenant connection name. Restart Integration Server.
Note:
  • When a custom tenant connection is not used, End-to-End Monitoring uses the default tenant connection value for agent.onprem_multitenant_alias in agent.config. You need to save the default tenant connection details in webMethods Integration Server when there is no custom connection.
  • Hybrid data transfer takes place within tenants of one given region only. When multiple tenant connections are created for different tenants that belong to the same region, specify one of the tenant connection names for agent.onprem_multitenant_alias in agent.config. This configuration is sufficient to trace hybrid transactions of other tenants that belong to the same region.
  • To see segment traces of on-premises API Gateway transaction in logs, set all log levels to DEBUG in versions lower than 10.15 <INSTALL-DIR>\IntegrationServer\instances\default\e2ecustomlog4j2.properties
  • From v10.15 onward, set log levels to debug in <INSTALL-DIR>\IntegrationServer\instances\default\e2elogback.xml
  • agent.trace_transfer_interval=${SW_AGENT_TRACE_TRANSFER_INTERVAL:180000}: This property defines the interval between each write operation to the file. The same property is used for data send interval through the gRPC channel. The default value is 18000 ms. It is preferred to reduce this time interval to shorter segment trace writes if you prefer a faster sync time.

Click Common configurable properties for more details on End-to-End Monitoring agent configurable properties for hybrid monitoring with Integration Server.

Click How can I view traces information in the log files? for more details on traces information in logs files.

Important: Complete the Mandatory Configuration after the Integration Server setup.