| Oracle® Communications Converged Application Server Installation Guide Release 5.0 Part Number E17649-03 |
|
|
View PDF |
| Oracle® Communications Converged Application Server Installation Guide Release 5.0 Part Number E17649-03 |
|
|
View PDF |
This chapter describes post-installation tasks necessary to configure a working Oracle Communications Converged Application Server deployment. Before reading this chapter, you need to understand WebLogic domains and clustering, and the domain topologies available for use with Converged Application Server.
To learn about WebLogic domains and clustering, see Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server 11g Release 1 in the Oracle Fusion Middleware Oracle WebLogic Server documentation set.
To learn about the domain topologies available for use with Converged Application Server, see the Converged Application Server Technical Product Description.
Converged Application Server includes the following domain topology templates:
OCCAS Domain - AdminServer Topology - 5.0.0.0
The AdminServer Topology domain template enables you to create a simple Converged Application Server domain. Such a domain configuration can be used during development phase where it is more convenient to deploy and test applications on a single server. The AdminServer topology can also be used in deployment that do not have high-availability and scalability requirements.
OCCAS Domain - Replicated Topology - 5.0.0.0
The Replicated Topology domain template enables you to create a replicated Converged Application Server domain. The Replicated Topology Domain is designed for use with SIP applications that require high levels of scalabilty, availability, and performance.
OCCAS Proxy Registrar domain - AdminServer Topology - 5.0.0.0
The Proxy Registrar domain AdminServer Topology template lets you create a non-clustered (single-server) Converged Application Server domain with the Proxy Registrar component. The Proxy Registrar combines the functionality of a SIP proxy server and registrar. Its main tasks include registering subscribers, looking up subscriber locations, and proxying requests onward. The Proxy and Registrar functions are described in RFC 3261.
The Proxy Registrar AdminServer template creates a domain appropriate for development environments, or cases where high availability is not an important consideration.
OCCAS Proxy Registrar domain - Replicated Topology - 5.0.0.0
The Proxy Registrar domain Replicated Topology template lets you create a clustered (multi-server) Converged Application Server domain with the Proxy Registrar component. The Proxy Registrar domain Replicated Topology template creates a domain appropriate for production environments where high availability and scalability are crucial.
Diameter domain topology
Diameter is a computer networking protocol for authentication, authorization, and accounting (AAA). Diameter is a Peer-To-Peer architecture, and each computer host that implements the Diameter protocol can act as either a client or a server depending on network deployment.
To learn more about Diameter, see Diameter Protocol Handling in Chapter 4, "Converged Application Server Cluster Architecture" in Converged Application Server Technical Product Description.
Table 5-1, "Configuration Screens for Creating a New Converged Application Server Domain" describes how to select a domain template for the type of domain topology you want to deploy using the Configuration Wizard.
After you install the Converged Application Server software, you must create a Converged Application Server domain for your deployment.
Start the Configuration Wizard in graphical mode from either the Windows Start menu or from the UNIX command line.
To start the Configuration Wizard in graphical mode on a Windows platform, you can either use the shortcut located in the Start menu, or execute the config.cmd script from the Command Prompt.
To start the Configuration Wizard using the shortcut located in the Start menu:
From the Start menu, select Programs, select Oracle Communications Converged Application Server, select WebLogic Server 11gR1, select Tools, then select Configuration Wizard.
The Configuration Wizard Welcome screen is displayed.
To start the Configuration Wizard by executing the config.cmd script from the Command Prompt window:
Log in to the system on which the product is installed.
From the Start menu, select All Programs, select Accessories, then select Command Prompt.
Go to the directory: WL_home\common\bin
Where WL_home is the directory in which WebLogic is installed. For example: C:\Oracle\Middleware\wlserver_10.3\common\bin
Execute the config.cmd command.
The Configuration Wizard Welcome screen is displayed.
To start the Configuration Wizard in graphical mode on a UNIX platform:
Log in to the system on which the product is installed.
Go to the directory: WL_home/common/bin
Where WL_home is the directory in which WebLogic is installed. For example: /Oracle/Middleware/wlserver_10.3/common/bin
Execute the sh config.sh command.
The Configuration Wizard Welcome screen is displayed.
After the Configuration Wizard starts (See "Starting the Converged Application Server Configuration Wizard in Graphical Mode" in the previous section.), create the domain as described in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard 11g Release 1. The Oracle Fusion Middleware documentation describes the Configuration Wizard screens that are common to both WebLogic Server and Converged Application Server.
Table 5-1 shows the values to choose for Configuration Wizard screens that are specific to creating a domain for Converged Application Server. For all other values, refer to the Oracle Fusion Middleware documentation.
Table 5-1 Configuration Screens for Creating a New Converged Application Server Domain
| Screen | Perform the Following Action |
|---|---|
|
Select Domain Source |
Select one of the following options: Generate a domain configured automatically to support the following products: Select the check box for each product to include in the domain. The Converged Application Server domain options are:
Base this domain on an existing template: Select this option if you want to create a Diameter domain topology by using the existing Diameter domain template. Enter the full path to the template JAR file in the Template location field, or click Browse to navigate to the directory containing the required template. The Diameter template JAR file (diameterdomain.jar) is located at: WL_home/templates/domains Where WL_home is the directory in which WebLogic is installed. For example: /Oracle/Middleware/wlserver_10.3/common/bin Click Next to continue. |
|
Configure JDBC Data Sources |
Configure the schema, the database owner and password, or both for each listed data source. Changes to any of the fields on this screen are applied to all of the selected data sources in the table. For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port). However, if you have a different password for each data source, then you must select each data source individually and specify the password for the selected item only. The data sources for Converged Application Server are:
Click Next to continue. |
|
Run Database Scripts |
The Converged Application Server domain templates contain a set of SQL files that you run from the Configuration Wizard while creating the Converged Application Server domain. Database content for each of the data sources defined in the Converged Application Server domain is set up by using the pre-existing SQL files.
|
You can expand your Converged Application Server environment by adding Managed Servers, deploying additional data sources to Managed Servers, and deploying Converged Application Server applications on servers and clusters as described by the following topics:
The Converged Application Server instances you intend to use must be created within a single administrative domain, and servers in the engine and SIP data tiers should be arranged into clusters to simplify deployment and management. The Configuration Wizard creates a replicated Converged Application Server domain with default engine tier servers and SIP data tier servers arranged into clusters; you can modify this configuration to match the number of servers you want to use in your domain.
If you created an AdminServer Topology domain using the Configuration Wizard, only a single server is configured. You will need to manually configure engine and SIP data tier servers and clusters.
WARNING:
When you configure a domain with multiple engine and SIP data tier servers, you must accurately synchronize all server system clocks to a common time source (to within one or two milliseconds) in order for the SIP protocol stack to function properly. See "Configuring NTP for Accurate SIP Timers" in Converged Application Server Administration Guide for more information.
The default, replicated Converged Application Server domain is pre-configured with five separate servers and two clusters. See Table 5-2 for a summary of the default replicated domain.
Note:
These quick-start instructions assume each Managed Server listens on a single network address. If you intend to run servers on multi-homed server hardware, or if you want to configure secure SIP transport protocols, see the discussion on configuring SIP channels for use with mulithomed machines in the Converged Application Server Administration Guide.Access the server computer that runs the Administration Server. The domain directory and associated files for the domain will remain on the Administration Server machine. Other servers in the Converged Application Server installation (SIP data tier and engine tier servers) will obtain their configuration by connecting to the Administration Server at boot time.
Start the Administration Server.
See "Start and Stop the Converged Application Server Domain" for more information.
Access the Administration Console by pointing a browser to:
http://AdminHost:port/console
Where AdminHost specifies the host name or IP address, and port specifies the network listening port number of the domain's Administration Server.
Login to the Administration Console using the administrator username and password.
Locate the Change Center in the upper left of the Administration Console screen, and click Lock & Edit to unlock the configuration edit hierarchy for the domain.
To add a new engine or SIP data tier server:
In the left pane of the Administration Console, select Environment, then select Servers.
Select the name of a server in the list, then click Clone. To add an engine tier server, clone the engine1 or engine2 server instance. To add a SIP data tier server, clone either replica1 or replica2.
Enter the name of the cloned server in the Server Name field.
Each server within a domain must have a name that is unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.
The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.
In Server Listen Address, if you want to limit the valid addresses for a server instance, enter an IP address or DNS name. Otherwise, you can specify any of the host computer's IP address, any DNS name that maps to one of the IP addresses, or the localhost string.
In Server Listen Port, enter the port number from which you want to access the server instance.
If you run multiple server instances on a single computer, each server must use its own listen port.
Specify whether or not this server will be a stand alone server or will belong to a cluster.
If this server is part of a cluster, you can select an existing cluster from the drop down list, or select the button to create a new cluster. For information on creating clusters, refer to the Oracle Fusion Middleware Oracle WebLogic Server documentation.
Click OK.
To delete an existing engine or SIP data tier server:
In the left pane of the Administration Console, select Environment, then select Servers.
Select the name of a server in the list, then click Delete.
Click Yes to delete the server configuration.
To change a server's network listen address, port number, or other properties:
In the left pane of the Administration Console, select Environment, then select Servers.
Select the name of the server you want to modify.
Select the Configuration tab, then select the General tab, and modify the Name, Listen Address, or Listen Port entries as necessary.
Click Save to apply your changes.
You may want to modify the default replicated domain if you want to add, remove, or rename servers in either of the clusters, or to configure the network settings of individual server instances. To modify the default configuration, modify the servers in the default replicated domain listed in Table 5-2.
Table 5-2 Summary of the Default Replicated Domain
| Server | Cluster | Description |
|---|---|---|
|
AdminServer |
N/A |
The Administration Server, AdminServer, is used only for administration. This server is not a member of either cluster, and it does not process SIP requests. |
|
engine1 |
BEA_ENGINE_TIER_CLUST |
The two engine tier servers, engine1 and engine2, can be used for hosting SIP applications and processing SIP messages. |
|
engine2 |
BEA_ENGINE_TIER_CLUST |
See the description in the above table cell. |
|
replica1 |
BEA_DATA_TIER_CLUST |
The two SIP data tier servers, replica1 and replica2, are members of the same SIP data tier partition. Each server manages the same copy of the application call state and can act as a backup should the other server fail. |
|
replica2 |
BEA_DATA_TIER_CLUST |
See the description in the above table cell. |
In the previous section you organized the SIP data tier servers into a cluster for administration purposes. You must also configure the datatier.xml file to define how SIP data tier servers are used to manage SIP application call state for your installation.
The SIP data tier cluster can be arranged into one or more partitions. A partition consists of one or more SIP data tier server instances that manage the same portion of the concurrent call state data. In a single-server Converged Application Server installation, or in a two-server installation where one server resides in the engine tier and one resides in the SIP data tier, all call state data is maintained in a single partition. Multiple partitions are required when the size of the concurrent call state exceeds the maximum size that can be managed by a single server instance. In most cases, the amount of call state that can be managed by a server corresponds to the Java Virtual Machine limit of approximately 1.6GB per server.
Additional servers can also be added within the same partition to manage copies of the call state data. When multiple servers are part of the same partition, each server manages a copy of the same portion of the call data, referred to as a replica of the call state. If any server in a partition fails or cannot be contacted due to a network failure, another replica in the same partition can supply the call state data to the engine tier.
See "Configuring SIP Data Tier Partitions and Replicas" in Converged Application Server Administration Guide to fully understand the role of the SIP data tier and the format of the datatier.xml configuration file.
To start the Converged Application Server domain, first start the Administration Server, then start individual Managed Servers to connect to the Administration Server. The sections that follow provide server startup instructions.
WebLogic Server provides several ways to start and stop server instances. The method that you choose depends on whether you prefer using the Administration Console or a command-line interface. See the WebLogic Server documentation for more information.
The following sections describe the most common methods of starting and stopping the Converged Application Server deployment's Administration Server.
When you create an Administration Server on a Windows computer, the Configuration Wizard creates a shortcut on the Start Menu for starting the server. The command that the Configuration Wizard adds to the Start menu opens a command window and calls a startup script.
Note:
You can also start and stop the Administration Server on the Windows operating system by executing the
startweblogic.cmd and stopweblogic.cmd scripts located in the directory:
MW_home/user_projects/domains/domain_name/bin
To start the Administration Server:
From the Start menu, select All Programs, select Oracle Communications Converged Application Server, select User Projects, select Administration_Server_Name (this is the name you specifed for the Administration Server during installation), then select Start Admin Server for Weblogic Server Domain.
When the server has successfully completed its startup process, it writes the following message to standard output (which, by default, is the command window):
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
To stop the Administration Server:
From the Start menu, select All Programs, select Oracle Communications Converged Application Server, select User Projects, select BasicAdminSrv, then select Stop Admin Server.
To start the Administration Server:
Log in to the Administration Server machine.
Go to the directory: MW_home/user_projects/domains/domain_name/bin
Where MW_home is the directory in which the Converged Application Server software is installed (the installation program refers to this as Middleware Home), and domain_name is the name of the domain whose Administration Server you want to start.
Execute the startWebLogic.sh script to start the Administration Server.
To stop the Administration Server:
Log in to the Administration Server machine.
Go to the directory: MW_home/user_projects/domains/domain_name/bin/
Where MW_home is the directory in which the Converged Application Server software is installed (the installation program refers to this as Middleware Home), and domain_name is the name of the domain you want to start.
Execute the stopWebLogic.sh script to stop the Administration Server.
Note:
Converged Application Server start scripts use default values for many JVM parameters that affect performance. For example, JVM garbage collection and heap size parameters may be omitted, or may use values that are acceptable only for evaluation or development purposes. In a production system, you must rigorously profile your applications with different heap size and garbage collection settings in order to realize adequate performance. See "Tuning JVM Garbage Collection for Production Deployments" in Converged Application Server Administration Guide for suggestions about maximizing JVM performance in a production domain.To start the Managed Servers in the Converged Application Server domain:
If you have not already done so, start the domain's Administration Server.
Access one of the Managed Server machines.
In a shell (command prompt) on the computer that hosts the Managed Server, change to the directory that contains the startManagedWebLogic script. By default, this directory is: MW_home/user_projects/domains/domain_name/bin/
Where MW_home is the directory in which the Converged Application Server software is installed (the installation program refers to this as Middleware Home), and domain_name is the name of the domain you want to start.
Execute the startManagedWebLogic.sh script.
startManagedWebLogic.sh managed_server_name admin_url
where:
managed_server_name specifies the name of the Managed Server.
admin_url specifies the listen address (host name, IP address, or DNS name) and port number of the domain's Administration Server.
For example:
startManagedWebLogic.sh ManagedServer5 http://127.0.0.1:7001
For each Managed Server that you want to start, open a separate command shell and follow steps 3 through 5. If you are starting Managed Servers on another machine, log in to that machine (remotely or locally) and then follow steps 3 through 5.
Converged Application Server is based on the Oracle WebLogic Server 11g. Many configuration tasks are the same for both products. To learn about system administration and configuration tasks associated with Oracle WebLogic Server, see Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server.
For configuration and administrative tasks specific to Converged Application Server, refer to the appropriate document in the Oracle Communications Converged Application Server 5.0 documentation set. The Oracle Communications Converged Application Server Release 5.0 documentation set contains the following titles relevant to system configuration and administration:
Converged Application Server Release Notes
Converged Application Server Technical Product Description
Converged Application Server Administration Guide
To learn how to configure Diameter client nodes or relays in a Converged Application Server domain, see Chapter 24, "Configuring Diameter Client Nodes and Relay Agents" in the Converged Application Server Administration Guide.
To learn about developing SIP and Diameter applications using Converged Application Server, see:
Converged Application Server SIP Application Development Guide
Converged Application Server Diameter Application Development Guide
|
 Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|