Difference between revisions of "Networking.properties"
imported>Aeric |
imported>Aeric |
||
Line 103: | Line 103: | ||
:<tt>vr_integration_master_password</tt> | :<tt>vr_integration_master_password</tt> | ||
::Notes and Usage: | ::Notes and Usage: | ||
::* Configure master | ::* Configure master VerticalResponse credentials to be used throughout the platform. | ||
:''Learn more:'''' [http://www.verticalresponse.com/support/ VerticalResponse] | :''Learn more:'''' [http://www.verticalresponse.com/support/ VerticalResponse] | ||
|valign="top"| These variables are optional. They are not automatically included in the configuration file, and have no default value. | |valign="top"| These variables are optional. They are not automatically included in the configuration file, and have no default value. | ||
|} | |} |
Revision as of 01:27, 16 August 2011
The networking.properties configuration file is used to enable or disable backend servers and configure performance parameters.
This file is configured automatically at installation, based on options defined in the installation.properties file.
This file can also be modified manually, after which the server will need to be restarted. Often, other servers will need to be modified in compatible ways. When that is the case:
- The modifications should be made to the networking.properties files for all servers.
- All the servers should then be brought down
- The servers can then be restarted.
The networking.properties file is located in the following directory:
- {install_dir}/tomcat/conf/RN directory
Changing Configuration Parameters
To enable a configuration parameter, remove the Hash mark (#):
- config_param (Enabled)
To disable a configuration parameter, add a Hash mark (#):
- #config_param (Disabled)
The networking.properties file includes the following configuration options:
Parameter Default Setting Report Scheduler Service - report_scheduler_manager_instance
- report_threads
- Notes and Usage:
- If report_scheduler_manager_instance is enabled, then report_threads must also be enabled
- The report_threads parameter defines the number of threads to be spawned. It can be changed to manage performance.
- Notes and Usage:
- Learn more: Tuning Report Threads
#report_scheduler_manager_instance =1 (Disabled) #report_threads=2 (Disabled, Default = 2)
Import Service - import_manager_instance
- Notes and Usage:
- In distributed server environments, this parameter should be enabled on a single server, only
- Notes and Usage:
- Learn more: Data Import'
#import_manager_instance = 1 (Disabled) Export Service - export_manager_instance
- Notes and Usage:
- In distributed server environments, this parameter should be enabled on a single server, only
- Notes and Usage:
- Learn more: Export Queue
#export_manager_instance = 1 (Disabled) Memcached Service - MemCachedServers=localhost:1121
- Notes and Usage:
- Hostname and Port must match values set at installation
- Learn more: Installation FAQs
- Distributed Caching
- Notes and Usage:
- Multiple memcached servers can be used for distributed access, and minimized response time:
- MemCachedServers=172.28.1.10:11211 172.28.0.120:11211
- Notes:
- The value is space-separated list of server IP addresses and port numbers (11211, in this example)
- Make sure that all instances are configured the same way, to keep the caches in sync.
- Learn more: Configuring memcached
#MemCachedServers=localhost:1121 (Disabled) Marketing Email Service - marketing_mail_server_instance
- Learn more: Email Campaigns
marketing_mail_server_instance=1 (Enabled) Bounce Service - third_party_marketing_campaign_bounce_processing
- Learn more: Email Bounce Notification
third_party_marketing_campaign_bounce_processing=1 (Enabled) Vertical Response - vr_integration_master_username
- vr_integration_master_password
- Notes and Usage:
- Configure master VerticalResponse credentials to be used throughout the platform.
- Notes and Usage:
- Learn more:'' VerticalResponse
These variables are optional. They are not automatically included in the configuration file, and have no default value.