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.
Note: For the complete FTS Deployment and Configuration Whitepaper, see
KA000159890
For the ITSM Configuration Best Practices document, please see
KA000114508For specific information on setting up Load Balanced FTS Searchers, see
KA000157036
configuration for Remedy 9.1 release. It is applicable to all releases of 9.1.x. The document may be updated as more testing and observation is complete. So please check periodically for updates. For more information on Performance Tuning for Remedy, check this link
For Email Engine Best Practice Configuration Guide, check this link
For Approval Server Best Practice Configuration Guide, check this link
For the DWP Configuration Checklist, check this link
For the FTS Best Practice Configuration Guide, check this link
For information on Hardware Requirements, check this link
For the Remedy on-premises Solution Architecture, check this linkThis configuration is specific to small, medium and large model defined as follows:
| Environment | BMC Remedy ITSM (concurrent users) | BMC Remedy Smart Reporting (concurrent users) | Number of managed devices |
| Small | 800 | 50 | 2,000 or fewer |
| Medium | 2,000 | 100 | 10,000 or fewer |
| Large | 5,000 | 250 | 30,000 or fewer |
General Recommendations:1- BMC Recommends putting FTS Indexer on a Backend Server.
2- SmartIT/MyIT heavily uses FTS/MFS compared to standard ITSM.
- Recommended adding FTS resources to support this.
3- For environments that heavily use FTS/MFS, setup multiple indexers.
4- If multiple Indexers, none should be on user-facing servers.
5- Currently testing use of LB in from of the Searcher Plugin Servers.
- This has been implemented and tested but is not yet a Best Practice.
6- Make sure to have enough capacity on secondary FTS server in case primary FTS server fails.
ARServer and Plugin Server Settings:
| | Small | Medium | Large |
| Number of Users | 800 | 2,000 | 5,000 |
| Physical RAM | 24 GB | 32 GB | 64 GB* |
| ARServer Heap Size | 10 GB | 14 GB | 32 GB* |
| Plugin Server Heap Size | 4 GB | 6 GB | 10 GB |
| numCoreThreads** | 10 | 12 | 16 |
| 390602 Threads | 3 3 | 5 5 | 7 7 |
*Recommend HA setup.
** This value will change based on usage and environment.
FTS Search Threshold recommended to be 2000.
Since this can cause records to not be found, customer needs to test to identify if this is acceptable.
GC settings
BMC recommends using these GC parameters (same as ARServer) with Plugin Server for FTS.
.................................................
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-XX:+DisableExplicitGC
-XX:NewRatio=2
-XX:+UseCompressedOops
.................................................
For Example using the Small Model (armonitor.cfg):
........................................
"C:\Program Files\Java\jdk1.8.0_73\jre\bin\java" -Xmx4096m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:NewRatio=2 -XX:+UseCompressedOops
-Dcom.sun.management.jmxremote.port=8004 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
-classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr\fts\secondary;C:\Program Files\BMC Software\ARSystem\pluginsvr\fts\core;C:\Program Files\BMC Software\ARSystem\pluginsvr;
C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build002.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR_Server_Name} -i "C:\Program Files\BMC Software\ARSystem" -m
........................................
