How to collect thread dumps using midtier configuration tools? 
No need for jvisualvm, jstack or JMX ports

This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

If you are on mid-tier 1805 and above no need to perform step 1 

Step 1
If you are on midtier 8x use the attachment config_thread_dump8.jsp 
If you are on midtier 9x use the attachment config_thread_dump9.jsp 
Place the corresponding file in midtier/shared/config/config_thread_dumpX.jsp 

If you are on midtier 1805 and beyond use the attachment config_thread_dump.jsp  (already installed on your midtier)

Step 2
login into config.jsp page http://MID-TIER:PORT/arsys/shared/config/config_overview.jsp

Step 3
Change the URL from http://MID-TIER:PORT/arsys/shared/config/config_overview.jsp to http://MID-TIER:PORT/arsys/shared/config/config_thread_dump.jsp
or click to Log Settings and after that in the Mid-Tier Thread Dumps interface click on the Launch button

Step 4
On config_thread_dump.jsp Enter
Elapsed time seconds: 300 (300 seconds is a good place to start) 
Select Storage: (One at least, both is feasible). Midtier/Web Server and/or Client
Click Start

What is next? 

There will be 5 thread dumps collected at regular intervals during the elapsed time 
Thread dumps will be stored on the storage option selected
a. Web server: will store thread dumps in the same midtier log folder 
b. Client: will download the thread dumps into the browser that trigger this action 

Once collected : Compress all 5 thread dumps and send them for review.
they will have the format: http___SERVER_PORT_timestamp.tdump
eg: http___clm-aus-015129_8080_1528732930335.tdump