| Oracle® Communications WebRTC Session Controller Installation Guide Release 7.0 E40974-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications WebRTC Session Controller Installation Guide Release 7.0 E40974-02 |
|
|
PDF · Mobi · ePub |
This chapter describes the steps required to create your WebRTC Session Controller Signaling Engine (Signaling Engine) domain after your software has been successfully installed.
After you install the Signaling Engine software, you must create a domain for your deployment. Before continuing in this chapter, you need to understand WebLogic domains and clustering, and the domain topologies available for use with WebRTC Session Controller Signaling Engine
To learn about WebLogic domains and clustering, see "WebLogic Server Domains" and "WebLogic Server Clustering" in Understanding Oracle WebLogic Server.
To learn about the domain topologies available for use with WebRTC Session Controller Signaling Engine, see "Understanding Signaling Engine Installation Topologies".
This section provides instructions for creating a WebRTC Session Controller domain using the configuration wizard. For more information on other methods available for domain creation, see "Additional Tools for Creating, Extending, and Managing WebLogic Domains" in Creating Domains Using the Configuration Wizard.
The following topics are covered in this section:
There are a selection of domain templates to choose from but only two are relevant to Signaling Engine:
Oracle Communications WebRTC Session Controller Replicated Domain
The Replicated Domain template enables you to create a replicated WebRTC Session Controller Signaling Engine domain. The Replicated Domain topology is designed for use with WebRTC applications that require high levels of scalability, availability, and performance.
Oracle Communications WebRTC Session Controller Basic Domain
The Basic Domain template enables you to create a simple Signaling Engine domain. Such a domain configuration can be used during development where it is more convenient to deploy and test applications on a single server.
In addition, each domain type can be extended to add Diameter support. For more information, see the discussion of WebRTC Session Controller Diameter Rx to Policy Charging and Rules (PCRF) configuration in the Oracle Communications WebRTC Session Controller System Administrator's Guide.
To begin domain configuration, navigate to the Oracle_home/oracle_common/common/bin directory and start the Fusion Middleware Configuration Wizard:
./config.sh
Note:
If, while installing Signaling Engine using the GUI installation wizard, you checked the Automatically Launch the Configuration Wizard check box, the Domain Configuration wizard will already be running.Follow the instructions in this section to configure the domain using the Configuration Wizard.
On the Configuration Type screen, select Create a New Domain.
In the Domain Location field, specify your Domain home directory.
It is recommended that you locate your Domain outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or re-install your software.
Tip:
More information about the Domain home directory can be found in "
Choosing a Domain Home" in Planning an Installation of Oracle Fusion Middleware.
More information about the other options on this screen can be found in "Configuration Type" in Creating Domains Using the Configuration Wizard.
Click Next.
The Templates window appears.
On the Templates screen select one of the following templates:
Oracle Communications WebRTC Session Controller Replicated Domain
Selecting this template also selects WebLogic Coherence Cluster Extension.
Oracle Communications WebRTC Session Controller Basic Domain
Selecting this template also selects Basic WebLogic SIP Server Domain and WebLogic Coherence Cluster Extension.
Note:
The template Basic WebLogic Server Domain is selected by default and cannot be deselected.More information about the options on this screen can be found in "Templates" in Creating Domains Using the Configuration Wizard.
Click Next.
The Administrator Account screen appears.
On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain. This account is used to connect to the domain's Administration Server.
Tip:
You must make a note of the user name and password you choose to enter here; you will need this in order to be able to start and access the Administration Server.Click Next.
The Domain Mode and JDK screen appears.
On the Domain Mode and JDK screen:
Select Development or Production in the Domain Mode field.
Select Oracle Hotspot JDK in the JDK field or choose a different supported JDK.
See "Signaling Engine Software Requirements" for information on supported JDKs.
Selecting Production Mode on this screen gives your environment a higher degree of security, requiring a user name and password to deploy applications and to start the Administration Server.
Tip:
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.Click Next.
There are several advanced options you can choose to configure on the Advanced Configuration screen:
Administration Server
Checking this option lets you configure the listen address of the Administration Server.
Node Manager
Checking this option lets you configure Node Manager.
Managed Servers, Clusters and Coherence
Checking this option lets you configure the Managed Servers, Clusters, and also lets you configure the machine and assign Managed Servers to the machine.
Tip:
If you want to configure dynamic clusters, see the following:"Overview of Dynamic Clusters" in Understanding Oracle WebLogic Server.
"Creating Dynamic Clusters" in Administering Clusters for Oracle WebLogic Server.
Deployments and Services
Checking this option lets you customize how application deployments and services are targeted to servers and clusters.
Check the advanced options you wish to configure.
Note:
If you are configuring a Oracle Communications WebRTC Session Controller Replicated Domain in Production Mode, you must select the following advanced options:Administration Server
Managed Servers, Clusters and Coherence
Failure to configure those options will cause the WebLogic server to fail to start.
If you have not checked any advance options, click Next and continue to step 8. Otherwise, click Next and follow this sub procedure:
If you have chosen the Administration Server advanced option, the Administration Server screen appears.
For more information on the options available on this screen, click the Help button and refer to the Wizard's online help.
Note:
If you are configuring a Oracle Communications WebRTC Session Controller Replicated Domain in Production Mode, you must enter the Listen Address for the Administration Server.Make any updates required and click Next.
If you have chosen the Node Manager advanced option, the Node Manager screen appears.
For more information on the options available on this screen, click the Help button and refer to the Wizard's online help.
Make any updates required and click Next.
If you have chosen the Managed Servers, Clusters and Coherence advanced option, the following four screens will appear in succession: Managed Servers, Clusters, Coherence Clusters, and Machines.
For more information on the options available on these screens, click the Help button and refer to each screen's online help.
Note:
If you are configuring a Oracle Communications WebRTC Session Controller Replicated Domain in Production Mode, you must select or enter the Listen Address for each engine and replica in the Managed Servers screen.You must also enter the Cluster Address for the engine cluster in the Clusters screen.
Make any updates required and click Next on each screen.
If you have chosen the Deployments Targeting advanced option, the Deployments Targeting screen appears.
For more information on the options available on this screen, click the Help button and refer to the Wizard's online help.
Make any updates required and click Next.
The Configuration Summary screen appears.
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain creation will not begin until you click Create.
The Configuration Success screen will show the following items about the domain you just configured:
Domain Location
Administration Server URL
You must make a note of both items as you will need them to start the servers and access the Administration Server.
Click Finish to close the configuration wizard.
After configuration is complete, in order to access the tools with which you can manage your domain, you must start the necessary servers. See the following topics for more information:
To start your per-domain Node Manager, go to the Domain_home/bin directory.
Start Node Manager as shown below, using nohup and nm.out as an example output file:
nohup ./startNodeManager.sh > nm.out&
Note:
It is recommended that you install Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.
To start the Administration Server, go the Domain_home/bin directory and run:
./startWebLogic.sh
If you selected Production Mode on the Domain Mode and JDK screen in step 5, you will be prompted for the login credentials of the Administrator user as provided on the Administrator Account screen in step 4.
Tip:
For more information about starting the Administration Server, see "Starting and Stopping Administration Servers" in Administering Oracle Fusion Middleware.
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
To start the Managed Servers, go the Domain_home/bin directory and run the following command:
./startManagedWebLogic.sh managed_server_name admin_server_url
Replace managed_server_name with the name of the Managed Server you want to start.
Replace admin_server_url with the full URL of the Administration Server, as provided on the Configuration Success screen in step 9.
Below are sample commands used to start wls_server_1 and wls_server_2 on UNIX operating systems:
./startManagedWebLogic.sh wsc-se_server_1 t3:\\host.example.com:7001 & ./startManagedWebLogic.sh wsc-se_server_2 t3:\\host.example.com:7001 &
Tip:
For more information about starting Managed Servers, see "Starting and Stopping Managed Servers" in Administering Oracle Fusion Middleware.After you have configured the Signaling Engine domain, you must complete Signaling Engine post-installation tasks. See "WebRTC Session Controller Signaling Engine Post-Installation Tasks" for instructions.
|
 Copyright © 2013, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|