<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Issue while instrumenting Oracle HTTP Server (OHS) on Solaris in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Issue-while-instrumenting-Oracle-HTTP-Server-OHS-on-Solaris/ta-p/302653</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;H2&gt;Summary&lt;/H2&gt;
&lt;P&gt;This article describes a scenario where Oracle HTTP Server (OHS) running on Solaris is not detected or deep monitored by Dynatrace OneAgent. Although WLST-related processes may appear in Dynatrace, the actual OHS (httpd.worker) process isn't instrumented and therefore does not produce service visibility or distributed traces.&lt;/P&gt;
&lt;P&gt;This article explains how to identify the issue and configure Oracle HTTP Server so that OneAgent can successfully instrument the OHS process.&lt;/P&gt;
&lt;H2&gt;Problem&lt;/H2&gt;
&lt;P&gt;Oracle HTTP Server (httpd.worker) is not detected in Dynatrace. Only WebLogic Node Manager or WLST-related processes appear in Dynatrace; however, they don't provide application traces because the actual OHS process isn't instrumented.&lt;/P&gt;
&lt;P&gt;Customers may observe the following:&lt;/P&gt;
&lt;UL type="disc"&gt;
&lt;LI&gt;OHS (httpd.worker or ohs*) is missing from Dynatrace.&lt;/LI&gt;
&lt;LI&gt;Adding Dynatrace LD_PRELOAD_64 variables to startup script&amp;nbsp;only results in monitoring of parent processes and not the actual OHS process.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2&gt;Troubleshooting steps&lt;/H2&gt;
&lt;DIV&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;1. Verify the OHS process environment&lt;/H4&gt;
&lt;P&gt;Identify the OHS process and inspect its environment:&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV tabindex="0" role="group" aria-label="Code Preview"&gt;
&lt;DIV tabindex="-1"&gt;
&lt;DIV&gt;
&lt;DIV aria-live="assertive"&gt;&lt;LI-CODE lang="markup"&gt;pargs -e &amp;lt;httpd_worker_pid&amp;gt;&lt;/LI-CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV&gt;
&lt;P&gt;If the Dynatrace preload variables are missing, the OHS process isn't being started with the required OneAgent configuration.&lt;/P&gt;
&lt;DIV&gt;
&lt;H4&gt;2. Check for legacy Apache module configuration&lt;/H4&gt;
&lt;DIV&gt;
&lt;P&gt;Review &lt;CODE&gt;httpd.conf&lt;/CODE&gt; for entries similar to:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;LoadModule oneagent_module /opt/dynatrace/oneagent/agent/bin/solaris-sparc-64/liboneagentloader.so&lt;/LI-CODE&gt;
&lt;DIV class="___77lcry0 f10pi13n"&gt;
&lt;DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="0" role="group" aria-label="Code Preview"&gt;
&lt;DIV class="scriptor-component-code-block CodeBlock__codeBlockDiv__a08f45e6 scriptor-codeblock-virtualized" tabindex="-1"&gt;
&lt;DIV class="CodeBlock__toasterContainer__c2d42058"&gt;
&lt;DIV class="rrd10u0 fui-AriaLive__assertive" aria-live="assertive"&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;
&lt;DIV&gt;
&lt;P&gt;If present, remove them and restart the service.&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;H2&gt;Resolution&lt;/H2&gt;
&lt;P&gt;The Dynatrace preload variables should be configured through the Oracle HTTP Server property files instead of the startup scripts.&lt;/P&gt;
&lt;P&gt;An Oracle HTTP Server administrator (OHS SME) may be required to help identify the correct files and apply the configuration.&lt;/P&gt;
&lt;P&gt;Oracle-documentation:&amp;nbsp;&lt;A href="https://docs.oracle.com/middleware/1212/webtier/HSADM/property_files.htm#HSADM1198" target="_blank" rel="noopener"&gt;https://docs.oracle.com/middleware/1212/webtier/HSADM/property_files.htm#HSADM1198&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The files to be modified are usually located under:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;DOMAIN_HOME/config/fmwconfig/components/OHS/&lt;/LI-CODE&gt;
&lt;P&gt;Common OHS property files include:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;ohs_admin.properties&lt;/CODE&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;ohs_nm.properties&lt;/CODE&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;ohs.plugins.nodemanager.properties&lt;/CODE&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The environment property syntax is:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;environment[.append][.&amp;lt;order&amp;gt;].&amp;lt;name&amp;gt; = &amp;lt;value&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;Example configuration:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;environment.DT_HOME=/opt/dynatrace/oneagent
environment.LD_PRELOAD_64=$DT_HOME/agent/lib64/liboneagentproc.so
environment.LD_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so&lt;/LI-CODE&gt;
&lt;P&gt;Add the applicable Dynatrace environment variables to the appropriate OHS property files identified by the OHS administrator.&lt;/P&gt;
&lt;P&gt;After applying the changes, restart the Oracle HTTP Server services.&lt;/P&gt;
&lt;P style="margin: 0in; font-family: 'Segoe UI'; font-size: 10.5pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: 'Segoe UI'; font-size: 16.0pt;"&gt;&lt;STRONG&gt;Expected Result&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;After the restart:&lt;/P&gt;
&lt;UL type="disc"&gt;
&lt;LI&gt;The host becomes visible in Dynatrace.&lt;/LI&gt;
&lt;LI&gt;Oracle HTTP Server (ohs* / httpd.worker) is detected.&lt;/LI&gt;
&lt;LI&gt;Deep Monitoring is enabled.&lt;/LI&gt;
&lt;LI&gt;Services and traces generated by OHS become available in Dynatrace.&lt;/LI&gt;
&lt;/UL&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="bhaveshbjoshi_0-1785481025757.png"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/33815i186C5A05E479D989/image-size/large?v=v2&amp;amp;px=999" alt="bhaveshbjoshi_0-1785481025757.png" title="bhaveshbjoshi_0-1785481025757.png" /&gt;&lt;/span&gt;
&lt;H2&gt;What's next&lt;/H2&gt;
&lt;P&gt;If this article did not resolve the issue, please open a Dynatrace Support ticket and mention that this article was followed during troubleshooting.&lt;/P&gt;
&lt;P&gt;Please include the following information in the ticket:&lt;/P&gt;
&lt;UL type="disc"&gt;
&lt;LI&gt;Link(s) to the documentation used during the configuration&lt;/LI&gt;
&lt;LI&gt;Screenshot(s) of the OHS property file configuration showing the added environment variables&lt;/LI&gt;
&lt;LI&gt;Output of: &lt;CODE&gt;pargs -e &amp;lt;httpd_worker_pid&amp;gt;&lt;/CODE&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 25 Aug 2026 09:07:58 GMT</pubDate>
    <dc:creator>bhaveshbjoshi</dc:creator>
    <dc:date>2026-08-25T09:07:58Z</dc:date>
    <item>
      <title>Issue while instrumenting Oracle HTTP Server (OHS) on Solaris</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Issue-while-instrumenting-Oracle-HTTP-Server-OHS-on-Solaris/ta-p/302653</link>
      <description>&lt;P&gt;&lt;LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"&gt;&lt;/LI-TOC&gt;&lt;/P&gt;
&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;*&lt;EM&gt;Use a table of contents for longer articles.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;H2&gt;Summary&lt;/H2&gt;
&lt;P&gt;&lt;EM&gt;*This is a mandatory section.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Short description of which part of the Dynatrace platform the article refers to and what kind of problem it will help resolve/ task it will describe.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Problem&lt;/H2&gt;
&lt;P&gt;&lt;EM&gt;*This is a mandatory section.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Provide a precise description of the problem/ task to be described. Use anonymized screenshots, and include text for&amp;nbsp;important messages, errors, or information that will help the customer find this article when searching.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Troubleshooting steps&lt;/H2&gt;
&lt;P&gt;&lt;EM&gt;*This section can be omitted as necessary.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Explain what troubleshooting steps should be taken to ensure the problem matches this article.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Resolution&lt;/H2&gt;
&lt;P&gt;&lt;EM&gt;*This section can be omitted for articles that guide customers on ticket creation.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Explain the solution or all possible solutions resulting from the troubleshooting steps.&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;H2&gt;What's next&lt;/H2&gt;
&lt;P&gt;&lt;EM&gt;*This is a mandatory section. Customers need a way to respond or follow up if they have questions.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Explain what to do if the article did not help.&amp;nbsp;&lt;/EM&gt;&lt;EM&gt;Note that there are multiple options available, including:&lt;/EM&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;Opening a support ticket&lt;/STRONG&gt; - be as specific as possible about the information the customer should include in the ticket.&amp;nbsp;&lt;/EM&gt; If this article did not help, please open a support ticket, mention that this article was used and provide the following in the ticket:
&lt;UL&gt;
&lt;LI&gt;link to XYZ&lt;/LI&gt;
&lt;LI&gt;screenshot of XYZ&lt;/LI&gt;
&lt;LI&gt;information about XYZ&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;Suggesting Product Idea&lt;/STRONG&gt; - encourage the customer to suggest/ vote for a Product Idea explaining their business use case.&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;Explain this will change in the future&lt;/STRONG&gt; - explain that this behaviour will change in a future release. (No product idea / support ticket needed)&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;Alternatives -&lt;/STRONG&gt;&amp;nbsp;any other actions or links to other articles that could move the customer forward.&lt;/EM&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;*If it exists, link this article to the relevant troubleshooting map using the following guideline&lt;/EM&gt;&lt;/P&gt;
&lt;H3&gt;More articles can be found on the &lt;A href="https://community.dynatrace.com/t5/Troubleshooting/" target="_self"&gt;XXX Troubleshooting Map&lt;/A&gt;&lt;/H3&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 25 Aug 2026 09:07:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Issue-while-instrumenting-Oracle-HTTP-Server-OHS-on-Solaris/ta-p/302653</guid>
      <dc:creator>bhaveshbjoshi</dc:creator>
      <dc:date>2026-08-25T09:07:58Z</dc:date>
    </item>
  </channel>
</rss>

