On-host Apache: Fix logic that allows mixture of Linux and Window instructions

src/install/apache/appInfo.mdx

@@ -1,4 +1,4 @@
 ---
 componentType: appInfoConfig
-headingText: Choose your framework
+headingText: Select your environment
 ---

src/install/apache/install-infra.mdx

@@ -3,4 +3,9 @@ componentType: default
 headingText: Install the infrastructure agent
 ---
 
-To use the Apache integration, you need to also [install the infrastructure agent](/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic/) on the same host. The infrastructure agent monitors the host itself, while the integration you'll install in the next step extends your monitoring with specific data such as database and instance metrics.
+To use the Apache integration, you need our infrastructure agent on the same host. The infrastructure agent monitors the host itself, while the Apache integration extends monitoring to your Apache instance.
+
+If you haven't already installed the infrastructure agent:
+
+1. Open the [infrastructure agent](/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic/) instructions in a new tab and complete that installation.
+2. After you've installed in the infrastructure agent, return to this tab and complete the remaining steps to install and configure the Apache integration.

src/install/apache/intro.mdx

@@ -5,30 +5,16 @@ componentType: default
 
 Our Apache integration reports data from your Apache web server to the New Relic platform. You can view dashboards of your Apache metric data, create alert policies, and create your own custom queries and charts.
 
-To get the most out of this page, select the installation method that fits your environment. You need a [New Relic account](https://newrelic.com/signup) before starting the installation process.
+## Start our interactive instructions
 
-<Callout variant="tip">
-  **Use guided install to quickly see your data in the UI**
+This page is interactive, which means we'll ask you a little about your environment so we can give you specific steps to install the Apache monitoring integration.
 
-  The guided install is a single CLI command you can run to monitor your  instance. It's a good option for small organizations, or for anyone who wants to test out New Relic.
+If you change your mind after making selections, click **Reset the form** to start again:
 
-  <ButtonGroup>
-    <ButtonLink
-      role="button"
-      to="https://one.newrelic.com/marketplace/install-data-source?state=45bfc665-2948-40d2-898e-f289e8cae631"
-      variant="primary"
-    >
-      Guided install
-    </ButtonLink>
-
-    <ButtonLink
-      role="button"
-      to="https://one.eu.newrelic.com/marketplace/install-data-source?state=45bfc665-2948-40d2-898e-f289e8cae631"
-      variant="primary"
-    >
-      EU guided install
-    </ButtonLink>
-  </ButtonGroup>
-
-  For a more permanent and scalable solution, we recommend the standard manual install of the agent: keep reading for how to do that.
-</Callout>
+<ButtonLink
+  role="button"
+  to="/install/apache"
+  variant="primary"
+>
+  Reset the form
+</ButtonLink>

src/install/apache/linux/install-tarball.mdx

@@ -15,18 +15,4 @@ To install an integration from a tarball:
 2. Unpack the tarball file according to our [integration file structure and placement rules](/docs/integrations/integrations-sdk/getting-started/integration-file-structure-activation), so the agent is able to find the definitions, configurations, and executables of the integration.
 3. Place the binary that contains the definition file inside `newrelic-integrations` or `custom-integrations` in the [agent directory](/docs/infrastructure/install-configure-manage-infrastructure/linux-installation/tarball-manual-install-infrastructure-linux#agent-directory).
 4. Place the integration's config file under the [plugin directory](/docs/infrastructure/install-configure-manage-infrastructure/linux-installation/tarball-manual-install-infrastructure-linux#configure-plugin).
-5. Follow the JMX tool instructions below.
 
-   ### Use of the New Relic JMX tool [#nrjmx]
-
-Download the JMX tool from [our repository](https://download.newrelic.com/infrastructure_agent/binaries/linux/noarch/) and unpack it.
-
-<Callout variant="important">
-  `nrjmx` requires Java 8 or higher.
-</Callout>
-
-For JMX integration version 2.3.3 or higher and Cassandra integration version 2.3.0 or higher, the `nrjmx` tool is included as a dependency. For this reason, when using a package manager, the `nrjmx` tool doesn't have to be installed manually.
-
-If you have `nrjmx` already installed and install `nri-jmx`, our JMX tool keeps the already-installed version. If you don't have `nrjmx` already installed, it gets the latest `nrjmx` release.
-
-By default, the `nrjmx` location is `/usr/bin/nrjmx/*`. To install in a different location, set the new path in the `NR_JMX_TOOL` environment variable.

src/install/apache/whatsNext.mdx

@@ -3,6 +3,10 @@ componentType: default
 headingText: Metrics collected by the integration
 ---
 
+## Post-installation tasks [#post-installation-tasks]
+
+After you complete the installation, you can take some additional steps for your integration.
+
 ### Apache configuration options [#config-options]
 
 The Apache integration collects both metrics and inventory information. This table provides a description for each config setting and whether it applies to metrics, inventory, or both.
@@ -30,7 +34,7 @@ The Apache integration collects both metrics and inventory information. This tab
 
   <tbody>
     <tr>
-      <td>
+      <td class="children-nowrap">
         `STATUS_URL`
       </td>
 
@@ -48,7 +52,7 @@ The Apache integration collects both metrics and inventory information. This tab
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         [`REMOTE_MONITORING`](/docs/remote-monitoring-host-integrations)
       </td>
 
@@ -70,7 +74,7 @@ The Apache integration collects both metrics and inventory information. This tab
     }
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `BINARY_PATH`
       </td>
 
@@ -92,7 +96,7 @@ The Apache integration collects both metrics and inventory information. This tab
     }
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `CA_BUNDLE_FILE`
       </td>
 
@@ -114,7 +118,7 @@ The Apache integration collects both metrics and inventory information. This tab
     }
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `CA_BUNDLE_DIR`
       </td>
 
@@ -136,7 +140,7 @@ The Apache integration collects both metrics and inventory information. This tab
     }
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `VALIDATE_CERTS`
       </td>
 
@@ -162,7 +166,7 @@ The Apache integration collects both metrics and inventory information. This tab
     }
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `METRICS`
       </td>
 
@@ -182,7 +186,7 @@ The Apache integration collects both metrics and inventory information. This tab
     }
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `INVENTORY`
       </td>
 
@@ -199,7 +203,7 @@ The Apache integration collects both metrics and inventory information. This tab
   </tbody>
 </table>
 
-## Example configurations [#examples]
+### Example configurations [#examples]
 
 Here are some example YAML configurations:
 
@@ -413,7 +417,7 @@ labels:
   role: load_balancer
 ```
 
-## Metric data [#metrics]
+### Metric data [#metrics]
 
 The Apache integration collects the following metric data attributes. Each metric name is prefixed with a category indicator and a period, such as `net.` or `server.`.
 
@@ -432,7 +436,7 @@ The Apache integration collects the following metric data attributes. Each metri
 
   <tbody>
     <tr>
-      <td>
+      <td class="children-nowrap">
         `net.bytesPerSecond`
       </td>
 
@@ -442,7 +446,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `net.requestsPerSecond`
       </td>
 
@@ -452,7 +456,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.busyWorkers`
       </td>
 
@@ -462,7 +466,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.idleWorkers`
       </td>
 
@@ -472,7 +476,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.closingWorkers`
       </td>
 
@@ -482,7 +486,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.dnsLookupWorkers`
       </td>
 
@@ -492,7 +496,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.finishingWorkers`
       </td>
 
@@ -502,7 +506,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.idleCleanupWorkers`
       </td>
 
@@ -512,7 +516,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.keepAliveWorkers`
       </td>
 
@@ -522,7 +526,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.loggingWorkers`
       </td>
 
@@ -532,7 +536,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.readingWorkers`
       </td>
 
@@ -542,7 +546,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.startingWorkers`
       </td>
 
@@ -552,7 +556,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.totalWorkers`
       </td>
 
@@ -562,7 +566,7 @@ The Apache integration collects the following metric data attributes. Each metri
     </tr>
 
     <tr>
-      <td>
+      <td class="children-nowrap">
         `server.scoreboard.writingWorkers`
       </td>
 
@@ -573,11 +577,11 @@ The Apache integration collects the following metric data attributes. Each metri
   </tbody>
 </table>
 
-## Inventory data [#inventory]
+### Inventory data [#inventory]
 
 Inventory data captures the version numbers from running Apache and from all loaded Apache modules. Those version numbers are added under the `config/apache` namespace. For more about inventory data, see [Understand data](/docs/infrastructure/integrations-getting-started/getting-started/understand-integration-data-data-types#inventory-data).
 
-## System metadata [#metadata]
+### System metadata [#metadata]
 
 Besides the standard attributes collected by the infrastructure agent, the integration collects inventory data associated with the `ApacheSample` [event type](/docs/using-new-relic/data/understand-data/new-relic-data-types#events-new-relic):
 
@@ -596,7 +600,7 @@ Besides the standard attributes collected by the infrastructure agent, the integ
 
   <tbody>
     <tr>
-      <td>
+      <td class="children-nowrap">
         `software.version`
       </td>
 
@@ -607,7 +611,7 @@ Besides the standard attributes collected by the infrastructure agent, the integ
   </tbody>
 </table>
 
-## Troubleshooting
+### Troubleshooting [#apache-troubleshooting]
 
 <CollapserGroup>
   <Collapser

src/install/apache/windows/install-windows.mdx → src/install/apache/windows/configure-windows.mdx

@@ -1,6 +1,6 @@
 ---
 componentType: default
-headingText: Configure the  integration
+headingText: Configure the integration
 ---
 
 1. In the Integrations directory, `C:\Program Files\New Relic\newrelic-infra\integrations.d\`, create a copy of the sample configuration file by running: