|Oracle® Traffic Director Administrator's Guide
11g Release 1 (188.8.131.52.0)
Part Number E21036-04
|PDF · Mobi · ePub|
You can create an origin-server pool by using either the administration console or the CLI.
When you create an origin-server pool, you are, in effect, modifying a configuration. So for the settings of the new origin-server pool to take effect in the Oracle Traffic Director instances, you should redeploy the configuration as described in Section 4.3, "Deploying a Configuration."
The CLI examples in this section are shown in shell mode (
tadm>). For information about invoking the CLI shell, see Section 2.3.1, "Accessing the Command-Line Interface."
Before you begin creating an origin-server pool, decide the following:
A unique name for the origin-server pool. Choose the name carefully; after creating an origin-server pool, you cannot change its name.
host:port combinations for the servers in the origin-server pool.
If the origin servers for which you want to create a pool are Oracle WebLogic Server managed servers in a cluster, it is sufficient to create the pool with any one of the managed servers as the origin server. You can then configure Oracle Traffic Director to discover the other managed servers in the pool dynamically. For more information, see Section 6.5, "Configuring an Oracle WebLogic Server Cluster as an Origin-Server Pool."
The communication protocol—HTTP, HTTPS or TCP—of the servers in the pool.
The address family that the servers in the origin-server pool use to listen for requests.
The supported address families are:
inet-sdp (Sockets Direct Protocol): Select this family if the servers in the origin-server pool are on the InfiniBand fabric and listen on an SDP interface, such as Oracle WebLogic Servers deployed on Oracle Exalogic machines.
For Oracle Traffic Director to communicate with WebLogic Server over SDP, further configuration steps are required on the WebLogic Server. For more information about these configuration steps, see "Enabling Cluster-Level Session Replication Enhancements" in the Oracle Fusion Middleware Exalogic Enterprise Deployment Guide.
To create an origin-server pool by using the administration console, do the following:
Log in to the administration console, as described in Section 2.3.2, "Accessing the Administration Console."
Click the Configurations button that is situated at the upper left corner of the page.
A list of the available configurations is displayed.
Select the configuration for which you want to create a virtual server.
In the Common Tasks pane, click New Origin-Server Pool.
The New Origin-Server Pool wizard starts.
Follow the on-screen prompts to complete creation of the origin-server pool by using the details—name, load balancing method, origin servers, and so on—that you decided earlier.
After the origin-server pool is created, the Results screen of the New Origin-Server Pool wizard displays a message confirming successful creation of the origin-server pool.
Click Close on the Results screen.
The details of the origin-server pool that you just created are displayed on the Origin-Server Pools page.
In addition, the Deployment Pending message is displayed at the top of the main pane. You can either deploy the updated configuration immediately by clicking Deploy Changes, or you can do so later after making further changes as described in Section 4.3, "Deploying a Configuration."
To create an origin-server pool, run the
For example, the following command creates an origin-server pool
osp-soa containing two origin servers
http://soa.example.com:1902 in the configuration
tadm> create-origin-server-pool --config=soa --type=http --origin-server=soa.example.com:1901,soa.example.com:1902 osp-soa OTD-70201 Command 'create-origin-server-pool' ran successfully.
For the updated configuration to take effect, you should deploy it to the Oracle Traffic Director instances by using the
For more information about
create-origin-server-pool, see the Oracle Traffic Director Command-Line Reference or run the command with the