This section contains the following topics:
For information about creating a WebLogic domain, see Creating Domains Using the Pack and Unpack Commands or Creating WebLogic Domains Using the Configuration Wizard
You can install Oracle Traffic Director as collocated with Oracle WebLogic Server in a WebLogic Server Domain. Oracle Traffic Director can also be installed as a standalone domain. You can select which environment you want to use during server configuration. Be aware that certain functionality will not be available to standalone domains.
Oracle Traffic Director supports the following domain types:
When a WebLogic domain is extended for Oracle Traffic Director, the Oracle Traffic Director instances and configurations can be managed like any other elements of the WebLogic domain for Oracle Traffic Director. Specifically, the instances can be managed from Enterprise Manager and WLST command-line reference.
To configure Oracle Traffic Director in a WebLogic domain for OTD, Oracle Traffic Director must be installed in an existing Oracle Fusion Middleware Infrastructure Oracle home.
Using Oracle Fusion Middleware Configuration Wizard from an Oracle home, you can configure or extend a WebLogic domain for Oracle Traffic Director so that it contains one or more Oracle Traffic Director instances, in addition to the Administration Server, Managed Servers, and other elements of the domain.
Note:
The Oracle Traffic Director instances cannot be created using the Configuration Wizard. You must use either Enterprise Manager or WLST command-line reference.
The Standalone domain supports only one type of system component and has only one Node Manager. The custom WLST commands for administering Oracle Traffic Director cannot be used in a Standalone Domain.
Note:
The custom WLST commands for administering OTD cannot be used in a standalone domain. For information about the standalone WLST commands, see WebLogic Scripting Tool Command Reference for Oracle Traffic Director
Use the following guidelines to decide on an Oracle Traffic Director domain option that will best suit your needs:
Table 2-1 Selecting Oracle Traffic Director Domain Configuration
| Collocated Domain | Standalone Domain |
|---|---|
|
To take advantage of advanced management capabilities of Fusion Middleware Control to manage your Oracle Traffic Director instances. You can also use WLST custom commands for the administration of Oracle Traffic Director. See WebLogic Scripting Tool Command Reference for Oracle Traffic Director for more information. You want to scale out your domain to multiple hosts and still manage the Oracle Traffic Director instances from a single FMW Control. |
If you do not wish to manage the Oracle Traffic Director instances with Fusion Middleware Control. Instead, you can use the WLST command-line and other features available in a standalone domain. Please note that not all offline wlst commands are available in the standalone domain. Standalone domains are not managed, and there are no management capabilities available (including FMWControl and wlst custom commands). |
This is the recommended mode of creating an OTD domain. The restricted JRF mode, basically, creates a WLS runtime without a datasource connection. Hence, one does not need a running Oracle database to create the domain.
Follow these steps to create the OTD domain using Restricted JRF Template:
Run the config wizard using config.sh located in the Run the config wizard using config.sh located in the $FMW_HOME/oracle_common/common/bin directory.
The first screen of the Config Wizard appears (Create Domain).
Choose Create a new domain, and enter the desired domain home path.
Click Next. The Templates screen appears. In the Available Templates section, choose Oracle Traffic Director - Restricted JRF 12.2.1 [otd]. Oracle Enterprise Manager - Restricted JRF, Oracle Restricted JRF and Weblogic Coherence Cluster Extension will be automatically selected. Other templates can be selected. Refer to those individual component documents for details.
Click Next. The Application Location screen appears. Keep the default value for Application location.
Click Next. The Administrator Account screen appears. Enter the WebLogic Domain administration username and password. This information will be needed to access WebLogic Server Control and Fusion Middleware Control.
Click Next. Choose the Domain Mode Development.
Click Next. The Advanced Configuration screen appears. Select Admin Server, Managed Servers, Clusters and Coherence.
Click Next. The Administration Server screen appears. Enter the following:
Server Name: Use default (AdminServer)
Listen Address: Use default (All local Addresses)
Listen Port: $WLS_ADMIN_PORT
Enable SSL: Use default (unchecked)
SSL Port: Use default (disabled)
Server Groups: Use default (unspecified)
Click Next. The Node Manager screen appears. Do not add any nodes. Use defaults (default: Per Domain). For Node Manager Credentials, enter the following:
User Name: $NM_USER
Password: $NM_PASSWORD
Confirm password: $NM_PASSWORD
Click Next.
Click Next. The Managed Servers screen appears. Do not add any managed servers.
Click Next. The Clusters screen appears. Do not add any clusters.
Click Next. The Coherence Clusters screen appears. Do not add any clusters.
Click Next. The Machines screen appears. Click Add. Enter the following information:
Name: $MACHINE_NAME
Node Manager Listen Address: Use default (localhost)
Node Manager Listen Port: $NM_PORT
Click Next. The Configuration Summary screen appears. If the message The Security configuration in your domain is invalid appears, you may ignore it.
Click Create. The Configuration Progress screen appears.
Click Next. Wait for this part of the configuration to complete. Depending on the location and performance of the Repository database, this process may take a few minutes. Click Finish. The End of Configuration screen appears.
The full JRF template for domain configuration is used in these cases:
Oracle Traffic Director and SOA are in the same domain
The Domain is expected to support various components/scenarios such as CCWS, OPSS support for partitions, OPSS support for up-stack components of WebLogic, and so on.
Follow these steps to create the Oracle Traffic Director domain using the Full JRF Template:
Run the config wizard using config.sh located in the Run the config wizard using config.sh located in the $FMW_HOME/oracle_common/common/bin directory.
The first screen of the Config Wizard appears (Create Domain).
Choose Create a new domain, and enter the desired domain home path.
Click Next. The TemplatesThe dependent templates will be automatically selected. The dependent templates are Oracle Enterprise Manager Plug-in for OTD - 12.1.4.0 [em] and Oracle JRF screen appears. In the Available Templates section, choose Oracle Traffic Director - 12.2.1 [otd].
Click Next. The Application Location screen appears. Keep the default value for Application location.
Click Next. The Administrator Account screen appears. Enter the WebLogic Domain administration username and password. This information will be needed to access WebLogic Server Control and Fusion Middleware Control.
Click Next. The Domain Mode and JDK screen appears. Choose the Domain Mode Development. Leave the default JDK selection as it appears.
Click Next. The Database Configuration Type screen appears. Enter the RCU DB connection information. Enter the following:
Auto Configuration Option: RCU Data
Vendor: Oracle
Driver: Oracle's Driver (Thin) for Service connection; Version:9.0.1 and later
DBMS/Service - $SERVICE_ID (xe for Oracle XE)
Port: $DB_PORT (default is 1521)
Schema owner - ${SCHEMA_PREFIX}_STB
Passwd - $DB_PASSWORD
Click Get RCU Configuration. Wait for the verification process to complete.
Click Next. The Component DataSources screen appears. Ensure that the hostname and port information is correct.
Click Next. The Component JDBC Schema Test screen appears. Wait for the test to complete.
Click Next. The Advanced Configuration screen appears. Select Admin Server, Managed Servers, Clusters and Coherence.
Click Next. The Administration Server screen appears. Enter the following:
Server Name: Use default (AdminServer)
Listen Address: Use default (All local Addresses)
Listen Port: $WLS_ADMIN_PORT
Enable SSL: Use default (unchecked)
SSL Port: Use default (disabled)
Server Groups: Use default (unspecified)
Click Next. The Node Manager screen appears. Do not add any nodes. Use defaults (default: Per Domain). For Node Manager Credentials, enter the following:
User Name: $NM_USER
Password: $NM_PASSWORD
Confirm password: $NM_PASSWORD
Click Next.
Click Next. The Managed Servers screen appears. Do not add any managed servers.
Click Next. The Clusters screen appears. Do not add any clusters.
Click Next. The Coherence Clusters screen appears. Do not add any clusters.
Click Next. The Machines screen appears. Click Add. Enter the following information:
Name: $MACHINE_NAME
Node Manager Listen Address: Use default (localhost)
Node Manager Listen Port: $NM_PORT
Click Next. The Configuration Summary screen appears. If the message The Security configuration in your domain is invalid appears, you may ignore it.
Click Create. The Configuration Progress screen appears.
Click Next. Wait for this part of the configuration to complete. Depending on the location and performance of the Repository database, this process may take a few minutes. Click Finish. The End of Configuration screen appears.
Note:
The creation of Oracle Traffic Director configuration/instance is not supported using config wizard, the system component screen in the config wizard should be ignored while configuring Oracle Traffic Director. For creating Oracle Traffic Director configurations/instances, please use either Oracle Traffic Director custom wlst commands or FWMControl.
Before proceeding to the next tasks, use the Repository Creation Utility (RCU). RCU is available with the Oracle Fusion Middleware Infrastructure distribution. Follow these steps.
Run $FMW_HOME/oracle_common/bin/rcu.sh
The Welcome page appears. Click Next.
The Create Repository page appears. Select CreateRepository, and System Load and Product Load (default). Click Next.
The Database Connection Details page appears. Enter the RCU DB connection information as shown in the screen below. Click Next.
The Checking Prerequisites box pops up. It shows the progress of prerequisites checking. When it is complete, click OK.
The Select Components page appears. Select the Create newprefix radio button and provide a schema prefix (such as DEMO). Select the following components: Oracle Platform Security Services, Audit Services, Audit Services Append and Audit Services Viewer. Click Next.
The Checking Prerequisites box pops up. It shows the progress of prerequisites checking. When it is complete, click OK.
The Schema Passwords page appears.Leave the default Use same passwords for all schemas radio button selected, and enter the password in the Password field. Click Next.
The Map Tablespaces page appears. No action is required. Click Next.
A Repository Creation Utility box pops up, requiring your confirmation. Click OK.
A Creating Tablespaces pop up appears, showing the progress of tablespace creation. Click OK, then Next.
The Summary page appears, showing your actions and choices. Click Create.
A System Load progress box appears, showing progress.The box will disappear when complete.
Click Close.
When you install Oracle Traffic Director in a Collocated domain, the recommended configuration is to use the Restricted JRF domain template. In that configuration a database is not required, and you do not have to create a repository.
However, in the case where you did not use the Restricted JRF domain template in the Collocated domain, you will require a database and a repository with schema space for the domain. To create a repository:
Run the repository creation:
$ORACLE_HOME/oracle_common/bin/rcu -silent -createRepository -connectString $DB_HOST:$DB_PORT:$SERVICE_ID -dbUser $DB_USER -dbRole $DB_ROLE -schemaPrefix $SCHEMA_PREFIX -useSamePasswordForAllSchemaUsers true -selectDependentsForComponents true -component OPSS -component IAU -f < <path_to_password_file>
The contents of the password file should appear as follows:
welcome1 welcome1 welcome1 welcome1 welcome1 welcome1
Example:
$ORACLE_HOME/oracle_common/bin/rcu -silent -createRepository -connectString ${DB_HOST}:1521:xe
-dbUser sys -dbRole SYSDBA -schemaPrefix $SCHEMA_PREFIX -useSamePasswordForAllSchemaUsers true -selectDependentsForComponents true
-component OPSS -component IAU -f < /tmp/pass.txt
Processing command line ....
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
The database you are connecting is not a supported version. Refer to the certification matrix for supported DB versions.
...
Repository Creation Utility - Create : Operation Completed
After installing Oracle Traffic Director, you can verify the installation by trying to log in to the administration console of the Oracle Traffic Director administration server, by performing the following steps:
Start the administration server instance, by running the following command:
$DOMAIN_HOME/bin/startWebLogic.sh
In your web browser, enter the URL that you noted in the previous step.
https://bin.example.com:1895/em
An error message about a problem with the server's security certificate is displayed. The text of the message varies depending on the browser you use. The error message is displayed because the Oracle Traffic Director administration server uses a self-signed certificate, rather than a certificate issued by a trusted certificate authority.
Proceed to the log-in page of the administration console by choosing to trust the certificate.
The steps to be performed to trust a certificate vary depending on the browser you use. As an example, in Mozilla Firefox 4.0, click on the I Understand the Risks link on the error page, then click the Add Exception button, and finally, on the result page, click the Confirm Security Exception button.
Log in using the administrator user name and password that you specified while creating the administration server instance.