Configuration Overview
The configuration phase is critical for establishing secure and reliable communication between the EPMware Agent and your EPMware instance. This section guides you through all aspects of agent configuration.
Configuration Components
-
Agent Properties
Core configuration file containing connection settings, tokens, and paths -
Service Configuration
Service script setup for starting and managing the agent -
REST API Token
Authentication token generation and management -
Testing Connection
Verify agent connectivity and troubleshoot issues
Configuration Workflow
The typical configuration process follows these steps:
graph TD
A[Agent Installed] --> B[Configure Properties]
B --> C[Modify Service Script]
C --> D[Generate REST Token]
D --> E[Update Properties with Token]
E --> F[Test Connection]
F --> G{Test Successful?}
G -->|Yes| H[Configuration Complete]
G -->|No| I[Troubleshoot]
I --> B
Quick Configuration Guide
Step 1: Basic Properties Setup
Edit agent.properties with essential settings:
# Minimal configuration
ew.portal.server=your-server-name
ew.portal.url=https://your-instance.epmwarecloud.com
ew.portal.token=your-rest-token-here
agent.interval.millisecond=30000
agent.root.dir=/home/your-user
Step 2: Service Script Adjustment
Update ew_target_service.sh with correct path:
#!/bin/bash
HOME=/home/your-user # Update this line
cd $HOME
java -jar epmware-agent.jar --spring.config.name=agent
Step 3: Token Configuration
- Generate token in EPMware UI
- Copy token value
- Update
agent.properties - Secure the configuration file
Step 4: Connection Test
Configuration Files Reference
Primary Configuration Files
| File | Purpose | Location |
|---|---|---|
agent.properties |
Main configuration | Agent home directory |
ew_target_service.sh |
Service startup script | Agent home directory |
application.yml |
Spring Boot config (optional) | config/ directory |
logback.xml |
Logging config (optional) | config/ directory |
Configuration Hierarchy
Configuration values are loaded in this order (later overrides earlier):
- Default values in JAR
agent.propertiesfile- Environment variables
- Command line arguments
Environment-Specific Configurations
Development Environment
Optimized for debugging and testing:
# Development settings
ew.portal.url=https://dev.epmwarecloud.com
agent.interval.millisecond=60000 # Less frequent polling
agent.log.level=DEBUG
agent.test.mode=true
Production Environment
Optimized for reliability and performance:
# Production settings
ew.portal.url=https://prod.epmwarecloud.com
agent.interval.millisecond=30000
agent.log.level=INFO
agent.retry.count=3
agent.timeout.seconds=3600
Security Configuration
Protecting Sensitive Data
-
File Permissions
-
Token Security
- Never commit tokens to version control
- Use environment variables for tokens
-
Rotate tokens regularly
-
Encrypted Properties
Network Security
Configure secure communication:
# TLS/SSL settings
agent.ssl.enabled=true
agent.ssl.verify-hostname=true
agent.ssl.trust-all=false
agent.ssl.protocol=TLSv1.2
Advanced Configuration Topics
High Availability Setup
Configure for redundancy:
# HA configuration
agent.ha.enabled=true
agent.ha.heartbeat.interval=5000
agent.ha.failover.timeout=30000
Performance Tuning
Optimize for your environment:
# Performance settings
agent.thread.pool.size=10
agent.connection.pool.size=5
agent.batch.size=100
agent.compression.enabled=true
Monitoring Configuration
Enable monitoring endpoints:
# Monitoring
management.endpoints.enabled=true
management.endpoint.health.enabled=true
management.endpoint.metrics.enabled=true
management.server.port=8081
Configuration Validation
Pre-Flight Checklist
Before starting the agent:
- [ ] Server name matches EPMware configuration
- [ ] URL is correct and accessible
- [ ] Token is valid and properly formatted
- [ ] Paths use correct format for OS
- [ ] Service script has correct HOME directory
- [ ] Java is accessible and correct version
- [ ] Network connectivity is established
- [ ] File permissions are properly set
Configuration Testing
Test each component:
-
Properties Validation
-
Token Validation
-
Service Script Test
Common Configuration Patterns
Multi-Application Setup
Supporting multiple applications:
# Application-specific settings
hfm.enabled=true
hfm.server=hfm-server.com
planning.enabled=true
planning.server=planning-server.com
Proxy Configuration
For environments with proxy servers:
# Proxy settings
http.proxyHost=proxy.company.com
http.proxyPort=8080
https.proxyHost=proxy.company.com
https.proxyPort=8080
http.nonProxyHosts=localhost|127.0.0.1
Custom Scripts Integration
Integrating with existing scripts:
# Custom script hooks
agent.script.pre-deploy=/opt/scripts/pre-deploy.sh
agent.script.post-deploy=/opt/scripts/post-deploy.sh
agent.script.on-error=/opt/scripts/error-handler.sh
Troubleshooting Configuration
Common Issues
| Issue | Likely Cause | Solution |
|---|---|---|
| Agent won't start | Invalid configuration | Check syntax and required fields |
| Connection failed | Wrong URL or token | Verify server URL and regenerate token |
| Permission denied | File permissions | Fix ownership and permissions |
| Path not found | Incorrect directory | Update paths in configuration |
Debug Mode
Enable comprehensive debugging:
# Debug configuration
agent.debug=true
agent.log.level=TRACE
agent.log.verbose=true
agent.log.include-stacktrace=true
Configuration Backup
Always backup before changes:
# Backup configuration
cp agent.properties agent.properties.backup.$(date +%Y%m%d)
cp ew_target_service.sh ew_target_service.sh.backup.$(date +%Y%m%d)
# Restore if needed
cp agent.properties.backup.20231115 agent.properties
Best Practices
Configuration Management
- Version Control - Track configuration changes
- Documentation - Document all customizations
- Validation - Test changes before production
- Standardization - Use consistent naming conventions
Security Guidelines
- Least Privilege - Grant minimum required permissions
- Encryption - Encrypt sensitive values
- Rotation - Regular token and password rotation
- Auditing - Log configuration changes
Maintenance Tips
- Regular Reviews - Audit configurations quarterly
- Update Tracking - Document version updates
- Performance Monitoring - Track configuration impact
- Disaster Recovery - Maintain configuration backups
Getting Help
If you encounter configuration issues:
- Check the Troubleshooting Guide
- Review agent logs for specific errors
- Verify all prerequisites are met
- Contact EPMware Support with:
- Configuration files (sanitized)
- Error messages
- Log excerpts
Configuration Templates
EPMware provides configuration templates for common scenarios. Contact support for templates matching your environment.
Production Changes
Always test configuration changes in a non-production environment first. Have a rollback plan ready before making production changes.
Next Steps
After completing configuration:
- Test the Connection - Verify everything works
- Schedule the Agent - Set up automatic startup
- Configure Applications - Set up target integrations
- Monitor Operations - Implement monitoring