Skip navigation.

Licensing

WebLogic SIP Server offers a separate license file in addition to the installation media. This file provides description on conditions such as terms of usage upon purchase, such that you can check your license conditions by consulting it with this document.

Especially, when WebLogic SIP Server performs an unexpected operation, it it possible that you are requesting WebLogic SIP Server to perform more than what is licensed. In such case, consult this document and check again the licensed items that you have purchased.

Note: You cannot edit this file. If the content of the file is modified, WebLogic SIP Server will not run.

Location

Location of the license file is fixed at BEA_HOME/sip-license.xml. After making a backup of the license file you obtained, place it in BEA_HOME.

License Example

Since the license is written in XML format, you can view it with an editor that you normally use.

The following is an example of the license file.

<?xml version="1.0" encoding="UTF-8"?>

<license-group format="1.0" product="BEA WebLogic SIP Server" edition="Design Partners Release" release="2.0.1.0"> <license component="Registrar Servlet" licensee="BEA Evaluation Customer" type="EVAL" signature="/zTp6+FZcXwsqHn+WJ3DPAgWLT0="> <max-registers>any</max-registers> </license> <license component="SIP Servlet Engine" licensee="BEA Evaluation Customer" type="EVAL" signature="WBDWfnJeHGnFgggVtols2AHhcBs="> <ip-address>any</ip-address> <expiration>2005-08-30</expiration> <max-sessions>any</max-sessions> </license> <license component="Subscribers Manager" licensee="BEA Evaluation Customer" type="EVAL" signature="SmHLKsr3xao9qI9LuVFOvOznCnA="> <max-users>any</max-users> </license> </license-group>

License Information

This section provides information on the tags and attributes described in the license file.

In this license file, two types of tags are used. Each of them has the following meaning.

<license-group> tag

The root node name of the license file.

<license> tag

This is a child node of license-group, described in units of licensed components. Currently, there are the following three component that can be specified.
Within these three, SIP Servlet Engine and Subscriber Manager are components requisite to the operation of WebLogic SIP Server, and thus they should always exist. Usage of Registrar Servlet is not mandatory, but if it is not specified, you will not be able to use any of the features provided by this component.

<license-group> Tag Attributes

Attribute Name Example Description
format 1.0 The attribute indicating the format of the license file. Currently, only 1.0 is supported.
product BEA WebLogic SIP Server The attribute to indicate the product name of the licensed product. Currently, only BEA WebLogic SIP Server is supported.
release 2.0.1.0 The attribute to indicate the release number of the licensed product.
The asterisk (*) represents a wildcard. For example, 2.* represents all the releases with major version number 3, and * represents all the releases regardless of version numbers.
edition Design Partners Release The attribute to indicate the edition information of the licensed product.

<license> Tag Attributes

Attribute Name Example Description
component SIP Servlet Engine The name of the licensed component. Only the above-mentioned three types exist if format="1.0".
licensee BEA Evaluation Customer Indicates the user of this license. The name specified when you purchased the product must be used for this attribute value.
type EVAL Specifies the type of license. Currently, there are following four types of licenses.
EVAL: License for evaluation
DEVELOP: License for development
SERVICE: License for service operation
BACKUP: License for backup server
signature The signature created from the license information. If your license information and the signature do not match, you cannot use any of the functionalities.

The following describes the license information to be specified for each component.

Information on SIP Servlet Engine Component

In WebLogic SIP Server license, the license information relating to the body of the SIP servlet container is specified.

Tag Name Example Description
ip-address tag 192.168.1.100 Specifies the IP address of the host on which WebLogic SIP Server can operate. WebLogic SIP Server does not run on a host having an address other than the one specified here. If multiple IP addresses are registered as hosts, they will be provided as a list separated by commas (,).
Note that if any is specified, WebLogic SIP Server is operable at any IP address.
expiration tag 2010-01-01 Specifies the term in which WebLogic SIP Server can be used, in yyyy-MM-dd format.
Note that if none is specified, WebLogic SIP Server can be used for an indefinite period.
max-sessions tag 3000 Indicates the maximum number of concurrently usable SIP application sessions (or, simply AP sessions). For details of AP sessions, see chapter 10 of "SIP Servlet API 1.0 Specification." Note that if any is specified, any number of AP sessions are usable.

Information on Subscribers Manager Component

In the Subscribers Manager license, the license information relating to the user management component is specified.

Tag Name Example Description
max-users tag 100 Indicates the maximum number of users that can be registered. This example shows that only up to 100 users can be registered. Note that if any is specified, any number of users can be registered.

Information on Registrar Servlet Component

In Registrar Servlet license, the license information relating to registrar server which is one of the development tools is specified.

Tag Name Example Description
max-registers tag 50 Indicates the maximum number of terminals that is concurrently available for REGISTER. In this example, the number of terminals that can be connected at the same time is limited to 50. Note that if any is specified, any number of terminals are available for REGISTER.

If You Go Beyond the License Conditions

If usage or access that exceeds the limitations of the conditions specified in the license file is detected, WebLogic SIP Server behaves in the following manner.