Just ran into this as well - the documentation is not very helpful / outdated.
After you install the agent open the configuration file of the agent located in (replacing $DT_HOME with your install directory) $DT_HOME/agent/conf/ruxitagent.conf and copy the value of Server, Tenant, and TenantToken for later use.
Then these are the lines you would add to your httpd.conf in order to instrument (I'm sure you could just use the local activegate address or cluster address for server if you wanted as well):
LoadModule oneagent_module $DT_HOME/agent/lib64/liboneagentloader.so
The proper method is to put those variables into IHSHOME/bin/envvars file. Same for Apache HTTP server.
This is standard file for environment variables picked up when starting / shutting down IHS / Apache using apachectl (the standard and preferred method for starting / stopping IHS or apache).
If you are using default Oneagent installation directory, the file should look like this:
Another method is to use the autoinstrumentation on AIX available as EAP feature.
The method by putting the module into httpd.conf is obsolete and should be avoided. This applies for very old Oneagent.
You are welcome. The approach will definitely work both IHS, Apache HTTP server and probably also to other derivations (OHS for example). You just need to start the HTTP server using the startup scripts and not directly by running httpd binary.
I've seen customers with custom apache builds starting and stopping the process directly, but this is not very common.
Just in your case ensure the process is started using the startup script (apachectl or other script caling apachectl).