Configure TIBCO JMX Monitoring
JMX metric collection setup
Configure TIBCO Spotfire Log Monitoring
Parsers and directory watching
Configure Dashboards
Views for your TIBCO setup
Troubleshooting
Fix common TIBCO issues
Configure TIBCO JMX Monitoring
1. Open the JVM Wizard
Go to: Germain Workspace -> Left Menu -> Settings —> Wizards -> JVM Use the JVM Wizard to deploy the JMX monitoring component.
2. Select the Node and Engine
Select the GermainUX node and Engine that will execute the monitor. Choose an Engine that:3. Select the Target
Select the:- Target server
- Application
- Connection type
4. Configure the JMX Connection
Specify the JMX target URL. When the connection is secured, configure the required credentials. Verify:- Host
- Port
- JMX URL
- Authentication
- Credentials
- Network access
5. Configure Java Profiling — Optional
If GermainUX Java Profiler will also be used, configure the applicable profiling thresholds. Profiling should be enabled only when the additional Java execution detail is required.6. Review and Submit
Review the JMX monitoring configuration. Confirm:- Node
- Engine
- Server
- Application
- Connection type
- JMX target URL
- Credentials
- Profiling configuration
Configure TIBCO Spotfire Log Monitoring
TIBCO Spotfire monitoring uses dedicated log parsers and a directory monitor. Configure the parsers required for the Spotfire logs available in your environment.Spotfire Action Log
Deploy the: Spotfire Action Log Parser Select:- Parser type
- Application
Spotfire Performance Log
Deploy the: Spotfire Performance Log Parser Select:- Parser type
- Application
Spotfire Server Log
Deploy the: Spotfire Server Log Parser Select:- Parser type
- Application
Configure the Spotfire Log Directory Monitor
After configuring the required parsers, deploy the: TIBCO Spotfire Log Directory Monitor Configure:- Directory monitor type
- Target log directory
- Appropriate Engine
- Application/environment
Configure KPIs
Configure the KPIs required for your TIBCO monitoring use cases. Depending on the monitoring source and TIBCO component, these can include KPIs for:- Availability
- Performance
- JVM
- Memory
- Garbage collection
- Threads
Show all 11
Show all 11
- Transactions
- Errors
- Exceptions
- Logs
- Resource utilization
Configure SLAs
Configure SLA thresholds for conditions requiring attention. Examples include:Availability
TIBCO Component = Unavailable
JMX
JMX Connection = Unavailable
Performance
Response Time -> Expected Threshold
JVM Memory
Memory Usage -> Expected Threshold
Errors
Error Count -> Expected Threshold
Transactions
Transaction Failure Rate -> Expected Threshold
Use thresholds appropriate for each application and environment.
Configure Rules
Use GermainUX Rules for more advanced conditions. Examples include:- JVM Memory Increase + Performance Degradation
- Repeated TIBCO Errors + Transaction Failures
- Spotfire Log Error + Application Availability Issue
- Resource Saturation + Increased Response Time
Configure Alerts and Watches
Configure notifications for conditions requiring attention. Examples:
GermainUX can trigger alerts, Watches, reports, diagnostics, or approved automation.
Configure Dashboards
Create dashboards according to the monitored TIBCO environment.TIBCO Operations
Monitor:- Availability
- Performance
- Errors
- Transactions
- SLA violations
JVM
Monitor:- JVM health
- Memory
- Garbage collection
- Threads
- JMX metrics
TIBCO Spotfire
Monitor:- Action-log events
- Performance-log events
- Server-log events
- Errors
- Performance
- Historical trends
Infrastructure
Correlate TIBCO telemetry with:- CPU
- Memory
- Disk
- Network
- Database
- Operating system
Validate JMX Monitoring
After configuration, verify:1
JMX monitor executes
2
Connection succeeds
3
Authentication succeeds
4
JMX metrics are collected
5
KPIs appear in GermainUX
6
Expected values are populated
7
SLA status is evaluated
Validate Spotfire Log Monitoring
Generate or locate known Spotfire activity. Verify:1
Log files are generated
2
Directory Monitor detects the files
3
Correct parser processes each log type
4
Events are generated in GermainUX
5
Application and environment are correct
6
Expected fields are populated
7
Errors can be searched and analyzed
Troubleshooting
No JMX Data
Verify:- Engine is running.
- JMX monitoring component is enabled.
- Target server is reachable.
- JMX port is reachable.
- JMX URL is correct.
- Credentials are valid.
- Required JMX metrics are exposed.
JMX Connection Fails
Verify:- Host
- Port
- Firewall
- Network routing
- JMX configuration
- Authentication
- Credentials
- TLS/security requirements
Spotfire Logs Are Not Collected
Verify:- Spotfire is generating the expected logs.
- Log directory is correct.
- Engine can access the directory.
- Monitoring account has read permission.
- Directory Monitor is enabled.
- Correct parser is configured.
- Parser is associated with the correct application.
Some Spotfire Events Are Missing
Verify that the appropriate parser is deployed for the relevant log type:- Action
- Performance
- Server
Get More Information
GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Tibco environment. Contact GermainUX Support.Get Help
Contact GermainUX Support
The Germain Team can help you set this up.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE LLC.