This chapter contains the following topics:
See Oracle Traffic Director Terminology for the definitions of the Oracle Traffic Director terminology such as configuration, administration node, and instance. To understand the relationship between configurations, node managers, and instances, see Overview of Administration Tasks.
You can create configurations that define your Oracle Traffic Director instances. A configuration is a collection of metadata that you can use to instantiate Oracle Traffic Director. Oracle Traffic Director reads the configuration when a server instance starts and while processing client requests.
Before You Begin
Before you begin creating a configuration, decide the following:A unique name for the configuration. Choose the name carefully. After creating a configuration, you cannot change the name.
A unique listener host:port
combination for the default virtual server that you create as part of the configuration.
host:port
addresses of the servers in the origin-server pool that you create as part of the configuration.
(optional) Host names of the Node Managers on which you want to create instances of the configuration.
While creating a configuration using the New Configuration wizard, you can also choose to instantiate the configuration on one or more Node Managers. The wizard displays the host names of the Node Managers that are registered with the server.
To create a configuration by using Fusion Middleware Control, do the following:
To create a configuration, run the otd_createConfiguration
command. This command can be run in online and offline mode.
The example creates a configuration named soa.example.com
with an origin server, vault.example.com:80
.
# Online props = {} props['name'] = 'soa.example.com' props['listener-port'] = '12345' props['server-name'] = 'foo' props['origin-server'] = 'vault.example.com:80' otd_createConfiguration(props)
The example creates a configuration named foo
with an origin server, vault.mycompany.com:80
.
# Offline readDomain('/export/domains/otd_domain') props = {} props['name'] = 'foo' props['listener-port'] = '12345' props['server-name'] = 'foo' props['origin-server'] = 'vault.mycompany.com:80' otd_createConfiguration(props) updateDomain() closeDomain()
After creating Oracle Traffic Director configurations, you can view a list of the available configurations at any time. To view a list of configurations, run the otd_listConfigurations
command.
Topics
You can view the list of configurations by using either Fusion Middleware Control or the WLST as described in the following topics:
To view a list of the available configurations, run the otd_listConfigurations command, as shown in the following example. You can run this command in online and offline mode.
# Online otd_listConfigurations()
# Offline readDomain('/export/2110_12c/iplanet/ias/server/work/TD_Linux2.6_DBG.OBJ/domains/otd_domain') otd_listConfigurations() closeDomain()
See Offline Commands in the WebLogic Scripting Tool Command Reference for Oracle Traffic Director for information about using WLST commands in offline mode.
You can activate configuration changes to instances using the activate
command. The activate
command activates changes done after starting an edit session by executing the command startEdit
.
activate
command also activates changes to other components and managed servers done after starting an edit session. Certain configuration changes cannot be applied dynamically without restarting the instances.You can activate the configuration changes by using either Fusion Middleware Control or WLST as described in the following topics:
All commands executed in WLST must be activated using the activate
command.
For example, the following command updates all instances of the configuration with the latest configuration settings.
wls:/mydomain/edit !> activate(200000, block='true') Activating all your changes, this may take a while ... The edit lock associated with this edit session is released once the activation iscompleted. Action completed. wls:/mydomain/edit>
Note:
See Updating Oracle Traffic Director Instances Without Restarting for information about parameters that can be re-configured without restarting Oracle Traffic Director instances.
After you create a configuration and create instances from it, you might need to change some of the settings such as log preferences, performance parameters, virtual server listener, origin-server pools, and so on.
Topics
You can modify a configuration by using either Fusion Middleware Control or the WLST as described in the following topics:
WLST provides several commands that you can use to change specific parameters of a configuration.
Table 5-1 WLST Commands for Modifying a Configuration
Task | WLST Commands |
---|---|
Change the configuration properties |
|
Change access-log buffer properties |
|
Change caching properties |
|
Change DNS properties |
|
Change DNS caching properties |
|
Change HTTP request properties |
|
Change keep-alive settings for client connections |
|
Change error log settings |
|
Enable SNMP |
|
Change SSL/TLS session caching properties |
|
Change statistics collection properties |
|
Change TCP thread pool properties |
|
Change HTTP thread pool properties |
|
Change TCP thread pool properties |
|
For example, the following command changes the log level for the configuration foo
to the most verbose (finest) setting, TRACE:32
.
props = {} props['configuration'] = 'foo' otd_getConfigurationProperties(props)
See WebLogic Scripting Tool Command Reference for Oracle Traffic Director or run the commands with the --help
option.
When you want to create a configuration that is similar to an existing configuration, you can copy the existing configuration and make the required changes later.
Topics
You can copy a configuration by using either Fusion Middleware Control or the WLST as described in the following topics:
To copy a configuration, run the otd_copyConfiguration
command.
For example, the following command copies the configuration foo
to a new configuration named foo1
.
props = {} props['source-configuration'] = 'foo' props['dest-configuration'] = 'bar' otd_copyConfiguration(props)
You can delete configurations that are not required. To delete Oracle Traffic Director configurations, run the otd_deleteConfiguration
command.
Topics
You can delete Oracle Traffic Director configurations by using either Fusion Middleware Control or the WLST.
Note:
To delete a configuration that has one or more failover groups, you should first delete the failover groups. See Managing Failover Groups.
To delete a configuration, run the otd_deleteConfiguration
command, as shown in the following example. You can run the command in online and offline modes.
# Online props = {} props['configuration'] = 'foo' otd_deleteConfiguration(props)
# Offline readDomain('/export/2110_12c/iplanet/ias/server/work/TD_Linux2.6_DBG.OBJ/domains/otd_domain') props = {} props['configuration'] = 'foo' otd_deleteConfiguration(props) updateDomain() closeDomain()