Skip Headers
Oracle® Fusion Middleware Licensing Information
11g Release 1 (11.1.1)

Part Number E14860-47
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A WebLogic Server Basic

This appendix describes WebLogic Server Basic and the WebLogic Server functionality that is available in the WebLogic Server Basic license. The following topics are included:

A.1 WebLogic Server Basic Overview

WebLogic Server Basic is a license-constrained version of WebLogic Server that is available in licenses for the following Oracle products:

The license for each edition of Oracle Internet Application Server and for Oracle Forms and Reports enables the right to full use of the WebLogic Server Basic license.

Note:

All editions of the products Oracle Internet Application Server and Oracle Forms and Reports Server include rights to WebLogic Server Basic. WebLogic Server Basic is only for running components provided within these products such as Forms, Reports, Discoverer and Portal. It can also be used for custom Java applications such as those developed for Oracle Containers for Java EE. Products outside of Oracle Internet Application Server and Oracle Forms and Reports that have licensing dependencies on any edition of Oracle Internet Application Server or Oracle Forms and Reports do not have the right to run those products on WebLogic Server Basic unless stated specifically within their licensing documentation.

The WebLogic Server Basic license includes usage rights, with the limitations summarized in Table A-1, to the following WebLogic Server features:

Table A-1 summarizes the WebLogic Server features that have usage restrictions under the terms of the WebLogic Server Basic license.

Table A-1 WebLogic Server Basic License Feature Constraints

Feature Category Summary of Restrictions in WebLogic Server Basic License

Primary services

WebLogic Server provides a number of services to assist with the construction of production architectures that are restricted, or that may not be used, in the WebLogic Server Basic license. These services fall into the following categories:

  • High availability features, such as whole server migration, service migration, custom Work Managers, and overload management

  • Deployment services and features, such as application versioning; standalone deployment of JMS, JDBC, and WLDF modules; and FastSwap

  • JMS messaging service features

  • Services such as the WebLogic Diagnostics Framework, WebLogic SNMP agents, and the WebLogic Tuxedo Connector

For details about these services and restrictions on their use, see Section A.3, "Restricted Primary Services in WebLogic Server."

WebLogic Web Services

Use of the following WebLogic Web Services features is not permitted in the WebLogic Server Basic license:

  • Buffered Web Services

  • Asynchronous Web Services

  • Conversational Web Services

  • JMS transport

For information about these WebLogic Web Services features and restrictions on their use, see Section A.4, "Restricted WebLogic Web Services Features."

Tooling

Use of the following tooling features is not permitted in the WebLogic Server Basic license:

  • Configuration Wizard, or the pack and unpack commands, for creating custom domains

  • Domain Template Builder, or the pack and unpack commands, for creating domain or domain extension templates

  • Recording WebLogic Server Administration Console operations as a series of WebLogic Scripting Tool (WLST) commands

  • Extending the WebLogic Server Administration Console

For details about these tooling features and restrictions on their use, see Section A.5, "Restricted Tooling Features."

APIs

Use of the following APIs is not permitted in the WebLogic Server Basic license:

  • Custom or CommonJ Work Manager usage outside the default WebLogic Server Work Manager

  • WebLogic JMS client for Microsoft .NET and C

For details about these APIs and restrictions on their use, see Section A.6, "Restricted APIs."


A.2 Installation of WebLogic Server Basic

To install WebLogic Server Basic, use any of the WebLogic Server package or net installers as described in Oracle WebLogic Server Installation Guide, as appropriate for your platform. Each installer includes the core Java EE application server, Administration Console, Configuration Wizard and Upgrade Framework, WebLogic and third-party JDBC drivers, JMS, WebLogic Server clients, Web server plug-ins, UDDI and Xquery Support, WebLogic Server examples, Oracle Enterprise Pack for Eclipse, and Sun or Oracle JRockit JDKs (depending on platform).

To install WebLogic Server Basic, use any of the WebLogic Server package or net installers as described in Oracle WebLogic Server Installation Guide, as appropriate for your platform. Each installer includes the core Java EE application server, Administration Console, Configuration Wizard and Upgrade Framework, WebLogic and third-party JDBC drivers, JMS, WebLogic Server clients, Web server plug-ins, UDDI and Xquery Support, WebLogic Server examples, Oracle Enterprise Pack for Eclipse, and Sun or Oracle JRockit JDKs (depending on platform).

For a description of the individual components of WebLogic Server that may be selectively installed, see Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server.

A.3 Restricted Primary Services in WebLogic Server

The following sections describe the primary services in WebLogic Server that may not be used, or that have usage restrictions in, WebLogic Server Basic.

A.3.1 High Availability Services

Table A-2 lists and describes the high availability services that have restrictions, or that may not be used, in WebLogic Server Basic.

Table A-2 Primary Services Restricted in WebLogic Server Basic License

Feature Description

Whole server migration

Whole server-level migration enables a migratable server instance, and all of its services, to be migrated to a different physical computer. When a migratable server becomes unavailable for any reason, for example, if it hangs, loses network connectivity, or its host computer fails—migration is automatic. Upon failure, a migratable server is automatically restarted on the same computer if possible. If the migratable server cannot be restarted on the computer where it failed, it is migrated to another computer.

In the license for WebLogic Server Basic, whole server migration is not permitted.

For more information about this feature, see "Whole Server Migration" in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.

Service migration

In a WebLogic Server cluster, most subsystem services are hosted homogeneously on all server instances in the cluster, enabling transparent failover from one server to another. In contrast, pinned services, such as JMS-related services, the JTA Transaction Recovery Service, and user-defined singleton services are hosted on individual server instances within a cluster—for these services, the WebLogic Server migration framework supports failure recovery with service migration, as opposed to failover. Service-level migration in WebLogic Server is the process of moving the pinned services from one server instance to a different available server instance within the cluster.

In the license for WebLogic Server Basic, the configuration and execution of automatic service-level migration is not permitted.

For more information about this feature, see "Service Migration" in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.

Managed Server cloning

WebLogic Server provides the capability of cloning an existing Managed Server instance that is part of a cluster. This capability is typically used when an administrator wants to make a duplicate copy of an existing Managed Server.

In the WebLogic Server Basic license, the use of the WebLogic Server Administration Console for cloning a Managed Server instance is not permitted.

For information about how to clone a Managed Server instance, see "Clone machines" in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

MAN and WAN state replication

In addition to providing HTTP session state replication across servers within a cluster, WebLogic Server provides the ability to replicate HTTP session state across multiple clusters in a Metropolitan Area Networks (MAN) or in a Wide Area Network (WAN). This improves high-availability and fault tolerance by allowing clusters to be spread across multiple geographic regions, power grids, and Internet service providers.

Resources within a MAN are often in physically separate locations, but are geographically close enough that network latency is not an issue. Network communication in a MAN generally has low latency and fast interconnect. Clusters within a MAN can be installed in physically separate locations which improves availability. Resources in a WAN are frequently spread across separate geographical regions. In addition to requiring network traffic to cross long distances, these resources are often separated by multiple routers and other network bottle necks. Network communication in a WAN generally has higher latency and slower interconnect.

Slower network performance within a WAN makes it difficult to use a synchronous replication mechanism like the one used within a MAN. WebLogic Server provides failover across clusters in WAN by using an asynchronous data replication scheme.

In the license for WebLogic Server Basic, the use of either the MAN and WAN state replication type is not permitted.

For more information about this feature, see "Session State Replication Across Clusters in a MAN/WAN" in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.

Singleton service

Within an application, or as a standalone artifact, you can define a singleton service that can be used to perform tasks that you want to be executed on only one member of a cluster at any give time. A singleton service is active on exactly one server in the cluster at a time and processes requests from multiple clients. A singleton service is generally backed by private, persistent data, which it caches in memory. It may also maintain transient state in memory, which is either regenerated or lost in the event of failure. Upon failure, a singleton service must be restarted on the same server or migrated to a new server.

In the license for WebLogic Server Basic, the configuration of either a standalone or application-provided singleton service is not permitted.

For more information about singleton services, see "Service Migration" in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.

Cluster constraints deployment

The default cluster deployment behavior ensures homogeneous deployment for all clustered server instances that can be reached at the time of deployment. However, if the Administration Server cannot reach one or more clustered servers due to a network outage, those servers do not receive the deployment request until the network connection is restored.

It is possible to change WebLogic Server default deployment behavior for clusters by setting the ClusterConstraintsEnabled option when starting the WebLogic Server domain. This option enforces strict deployment for all servers configured in a cluster. A deployment to a cluster succeeds only if all members of the cluster are reachable and all can deploy the specified files.

In the license for WebLogic Server Basic, the use of cluster constraints deployment is not permitted.

For more information about cluster constraints deployment, see "Enforcing Consistent Deployment to All Configured Cluster Members" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

Overload management

WebLogic Server has features for detecting, avoiding, and recovering from overload conditions. WebLogic Server overload protection features help prevent the negative consequences—degraded application performance and stability—that can result from continuing to accept requests when the system capacity is reached.

In the license for WebLogic Server Basic, the configuration of any overload protection scheme at either a cluster or server level is not permitted.

For more information about overload management, see "Avoiding and Managing Overload" in Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server.

Server ADMIN and STANDBY mode

The series of states through which a WebLogic Server instance can transition is called the server life cycle. At any time, a WebLogic Server instance is in a particular operating state. Two states in which WebLogic Server can be started include the following:

  • ADMIN — WebLogic Server is up and running, but available only for administration operations, allowing you to perform server and application-level administration tasks.

  • STANDBY — WebLogic Server does not process any request; its regular Listen Port is closed. The Administration Port is open and accepts life cycle commands that transition the server instance to either the RUNNING or the SHUTDOWN state. Other administration requests are not accepted.

    Starting a server instance in STANDBY is a method of keeping it available as a "hot" backup, a useful capability in high-availability environments.

In the license for WebLogic Server Basic, starting a WebLogic Server instance in either ADMIN or STANDBY state is not permitted.

For more information about these operating states, see "Understanding Server Life Cycle" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.

GridLink data sources, also known as Active GridLink for RAC

A single GridLink data source provides connectivity between WebLogic Server and an Oracle Database service targeted to an Oracle RAC cluster. It uses the Oracle Notification Service (ONS) to adaptively respond to state changes in an Oracle RAC instance.

In the license for WebLogic Server Basic, the configuration and usage of GridLink data sources are not permitted.

For more information about GridLink data sources, see "Using GridLink Data Sources" in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.


A.3.2 Deployment Services and Features

Table A-3 lists and describes the deployment services and features that have restrictions, or that may not be used, in WebLogic Server Basic.

Table A-3 WebLogic Deployment Features Restricted in WebLogic Server Basic License

Feature Description

Production redeployment

Production redeployment strategy involves deploying a new version of an updated application alongside an older version of the same application. WebLogic Server automatically manages client connections so that only new client requests are directed to the new version. Clients already connected to the application during the redeployment continue to use the older version of the application until they complete their work, at which point WebLogic Server automatically retires the older application. This capability is supported by deploying the application in Administration mode, which makes it available only through a configured Administration channel.

In the license for WebLogic Server Basic, deploying any application that uses a version identifier is not permitted.

For more information about this feature, see "Distributing a New Version of a Production Application" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

Application Administration mode

Distributing an application copies deployment files to target servers and places the application in a prepared state. You can then start the application in Administration mode, which restricts access to the application to a configured Administration channel so you can perform final testing without opening the application to external client connections or disrupting connected clients. You can start an application in Administration mode with the -adminmode option. After performing final testing, you can either undeploy the application to make further changes, or start the application in Production mode to make it generally available to clients.

In the license for WebLogic Server Basic, configuring any application to start in Administration mode is not permitted.

For more information, see in "Administration Mode for Isolating Production Applications" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

Changing the order of deployment

You can change the deployment order for a deployed application or standalone module by setting the AppDeploymentMBean DeploymentOrder attribute in the Administration Console (or programmatically using the AppDeploymentMBean). The DeploymentOrder attribute controls the load order of deployments relative to one another—modules with lower DeploymentOrder values deploy before those with higher values. By default, each deployment unit is configured with a DeploymentOrder value of 100. Deployments with the same DeploymentOrder value are deployed in alphabetical order using the deployment name. In all cases, applications and standalone modules are deployed after the WebLogic Server instance has initialized dependent subsystems.

In the license for WebLogic Server Basic, deploying an application or module with a non-default deployment order setting is not permitted.

For more information about deployment order, see "Changing the Order of Deployment at Server Startup" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

FastSwap

Java SE 6 introduced the ability to redefine a class at run time without dropping its ClassLoader or abandoning existing instances. This allows containers to reload altered classes without disturbing running applications, vastly speeding up iterative development cycles and improving the overall development and testing experiences. The usefulness of the Java EE dynamic class redefinition is severely curtailed, however, by the restriction that the shape of the class—its declared fields and methods—cannot change. The purpose of FastSwap is to remove this restriction in WebLogic Server, allowing the dynamic redefinition of classes with new shapes to facilitate iterative development.

With FastSwap, Java classes are redefined in-place without reloading the ClassLoader, thereby having the decided advantage of fast turnaround times. This means that you do not have to wait for an application to redeploy and then navigate back to wherever you were in the Web page flow. Instead, you can make your changes, auto compile, and then see the effects immediately.

In the license for WebLogic Server Basic, deploying an application in which FastSwap is enabled is not permitted.

For more information about FastSwap, see "Using FastSwap Deployment to Minimize Redeployment" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

WebLogic JMS and JDBC module deployment

Standalone JDBC, JMS, and WLDF application modules can be deployed similar to standalone Java EE modules. For a standalone JDBC, JMS, or WLDF application module, the target list determines the WebLogic Server domain in which the module is available. JNDI names specified within an application module are bound as global names and available to clients. For example, if you deploy a standalone JDBC application module to a single-server target, applications that require resources defined in the JDBC module can only be deployed to the same server instance. You can target application modules to multiple servers, or to WebLogic Server clusters to make the resources available on additional servers.

In the license for WebLogic Server Basic, the standalone deployment of WebLogic JDBC, JMS and WLDF modules is not permitted.

For more information, see "Deploying JDBC, JMS, and WLDF Application Modules" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.


A.3.3 JMS Messaging Services

Table A-4 lists and describes the JMS messaging services and features that have restrictions, or that may not be used, in WebLogic Server Basic.

Table A-4 JMS Messaging Services Features Restricted in WebLogic Server Basic License

Feature Description

Message Unit-of-Order

Message Unit-of-Order is a WebLogic Server value-added feature that enables a standalone message producer, or a group of producers acting as one, to group messages into a single unit with respect to the processing order. This single unit is called a Unit-of-Order and requires that all messages from that unit be processed sequentially in the order they were created.

In the license for WebLogic Server Basic, changing the default Unit-of-Order for a message producer is not permitted.

For more information about this feature, see "Using Message Unit-of-Order" in Oracle Fusion Middleware Programming JMS for Oracle WebLogic Server.

Unit-of-Work Message Groups

Many applications need an even more restricted notion of a group than provided by the Message Unit-of-Order (UOO) feature. If this is the case for your applications, WebLogic JMS provides the Unit-of-Work (UOW) Message Groups, which allows applications to send JMS messages, identifying some of them as a group and allowing a JMS consumer to process them as such. For example, a JMS producer can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can be processed as a unit. Further, the client will not be blocked waiting for the completion of one unit when there is another unit that is already complete.

In the license for WebLogic Server Basic, changing the default value of the UnitOfWorkHandlingPolicy value for a JMS resource is not permitted.

For more information about this feature, see "Using Unit-of-Work Message Groups" in Oracle Fusion Middleware Programming JMS for Oracle WebLogic Server.

JMS Store-and-Forward agents

The WebLogic Store-and-Forward (SAF) client provides a mechanism whereby standalone clients can reliably send JMS messages to server-side JMS destinations, even when the SAF client cannot reach the JMS destination due to a network connection failure (for example, a temporary blip or a network failure). While disconnected, messages sent by a SAF client are stored locally on the client and are forwarded to server-side JMS destinations once the client is reconnected.

In the license for WebLogic Server Basic, configuring any SAF agents is not permitted.

For more information about this feature, see "Configuring SAF for JMS Messages" in Oracle Fusion Middleware Configuring and Managing Store-and-Forward for Oracle WebLogic Server.


A.3.4 Additional Primary Services

Table A-5 lists and describes additional services and components that have restrictions, or that may not be used, in WebLogic Server Basic.

Table A-5 Additional Services Restricted in WebLogic Server Basic License

Component or Feature Description

WebLogic Diagnostics Framework

The WebLogic Diagnostic Framework (WLDF) is a monitoring and diagnostic framework that defines and implements a set of services that run within WebLogic Server processes and participate in the standard server life cycle. Using WLDF, you can create, collect, analyze, archive, and access diagnostic data generated by a running server and the applications deployed within its containers. This data provides insight into the run-time performance of servers and applications and enables you to isolate and diagnose faults when they occur.

In the license for WebLogic Server Basic, the use of WLDF is not permitted.

For more information about the WebLogic Diagnostic Framework (WLDF), see "What Is the WebLogic Diagnostic Framework?" in Oracle Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

WebLogic Server SNMP agents

WebLogic Server SNMP agents query the WebLogic Server management system and communicate the results to managers over the SNMP protocol. The WebLogic Server management system exposes management data through a collection of managed beans (MBeans). When a WebLogic Server SNMP agent receives a request from a manager, it determines which MBean corresponds to the OID in the manager's request. Then it retrieves the data and wraps it in an SNMP response.

In the license for WebLogic Server Basic, all SNMP agents must be disabled.

For more information about WebLogic Server SNMP agents, see Oracle Fusion Middleware SNMP Management Guide for Oracle WebLogic Server.

WebLogic Tuxedo Connector

The Oracle WebLogic Tuxedo Connector provides interoperability between WebLogic Server applications and Tuxedo services. The connector allows WebLogic Server clients to invoke Tuxedo services and Tuxedo clients to invoke WebLogic Server Enterprise Java Beans (EJBs) in response to a service request.

In the license for WebLogic Server Basic, use of Oracle WebLogic Tuxedo Connector is not permitted.

For more information about WebLogic Tuxedo Connector, see Oracle Fusion Middleware Tuxedo Connector Administration Guide for Oracle WebLogic Server

WebLogic HTTP Publish-Subscribe Server

An HTTP Publish-Subscribe Server is a mechanism whereby Web clients subscribe to channels and then publish messages to these channels using asynchronous messages over HTTP.

In the license for WebLogic Server Basic, use of the WebLogic HTTP Publish-Subscribe Server is not permitted.

For more information about this feature, see "Using the HTTP Publish-Subscribe Server" in Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.

Use of Work Managers to prioritize and optimize work

WebLogic Server prioritizes work and allocates threads based on an execution model that takes into account administrator-defined parameters and actual run-time performance and throughput.

Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components. For example, you can associate one set of scheduling guidelines for one application, and another set of guidelines for other applications. At run time, WebLogic Server uses these guidelines to assign pending work and enqueued requests to execution threads.

In the license for WebLogic Server Basic, the creation of either global or application-specific Work Managers to modify the default work model is not permitted.

For more information about Work Managers, see "Understanding Work Managers" in Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server.


A.4 Restricted WebLogic Web Services Features

Table A-6 describes the WebLogic Web Services features that are not available for use under the terms of the WebLogic Server Basic license.

Table A-6 WebLogic Web Services Features Restricted in WebLogic Server Basic License

Feature Description

Buffered Web Services

When a buffered operation is invoked by a client, the method operation goes on a JMS queue and WebLogic Server deals with it asynchronously. As with Web Service reliable messaging, if WebLogic Server goes down while the method invocation is still in the queue, it will be dealt with as soon as WebLogic Server is restarted. When a client invokes the buffered Web Service, the client does not wait for a response from the invoke, and the execution of the client can continue.

In the license for WebLogic Server Basic, the use of buffered Web Services is not permitted.

For more information about this feature, see "Creating Buffered Web Services" in Oracle Fusion Middleware Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server.

Asynchronous Web Services

When you invoke a Web Service synchronously, the invoking client application waits for the response to return before it can continue with its work. In cases where the response returns immediately, this method of invoking the Web Service is common. However, because request processing can be delayed, it is often useful for the client application to continue its work and handle the response later on, or in other words, use the asynchronous request-response feature of WebLogic Web Services.

In the license for WebLogic Server Basic, the use of the asynchronous request-response feature is not permitted.

For more information about this feature, see "Invoking a Web Service Using Asynchronous Request-Response" in Oracle Fusion Middleware Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server.

Conversational Web Services

A Web Service and the client application that invokes it may communicate multiple times to complete a single task. Also, multiple client applications might communicate with the same Web Service at the same time. Conversations provide a straightforward way to keep track of data between calls and to ensure that the Web Service always responds to the correct client.

In the license for WebLogic Server Basic, the use of conversational Web Services is not permitted.

For more information about this feature, see "Creating Conversational Web Services" in Oracle Fusion Middleware Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server.

JMS transport

WebLogic Web Services may be configured to use the JMS transport as an alternative to the HTTP/HTTPS connection protocol for use by WebLogic clients. Using JMS transport offers the following benefits: reliability, scalability, and quality of service. As with Web Service reliable messaging, if WebLogic Server goes down while the method invocation is still in the queue, it will be dealt with as soon as WebLogic Server is restarted. When a client invokes a Web Service, the client does not wait for a response from the invoke, and the execution of the client can continue.

In the license for WebLogic Server Basic, the use or configuration of JMS transport in either WebLogic Web Services or WebLogic Web Services clients is not permitted.

For more information about this feature, see "Using JMS Transport as the Connection Protocol" in Oracle Fusion Middleware Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server.


A.5 Restricted Tooling Features

Table A-7 describes the tooling features in WebLogic Server that are not available for use under the terms of the WebLogic Server Basic license.

Table A-7 WebLogic Server Tooling Features Restricted in WebLogic Server Basic

Feature Description

Configuration Wizard, Domain Template Builder, and pack and unpack commands

The Configuration Wizard guides you through the process of creating a domain for your target environment by selecting the WebLogic Server components to include in your domain, or by using domain templates. If required, you can also customize the domain to suit your environment by adding and configuring Managed Servers, clusters, and computer definitions, or customizing predefined JDBC data sources, and JMS file store directories.

After you create a domain and add resources and applications to it, you can use the Domain Template Builder, or pack and unpack commands, to create a custom domain or domain extension template. These templates provides a convenient means to replicate a domain, or domain extension, throughout your environment.

In the license for WebLogic Server Basic: none of the following are permitted:

  • Use of the Configuration Wizard to create domains based on templates not supplied by Oracle

  • Use of the Domain Template Builder to create custom domain or domain extension templates

  • Use of the pack or unpack commands to create custom domains, domain extension, domain templates, or domain extension templates

For more information about these tools, see the following:

Recording Administration Console operations

To help automate the task of configuring a domain, you can record your configuration actions in the WebLogic Server Administration Console as a series of WebLogic Scripting Tool (WLST) commands and then use WLST to replay the commands.

In the license for WebLogic Server Basic, use of the Record element in the Administration Console tool bar is not permitted.

For more information about this feature, see "Record WLST Scripts" in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

Extending the Administration Console

Administration Console extensions enable you to add content to the WebLogic Server Administration Console, replace content, and change the logos, styles and colors without modifying the files that are installed with WebLogic Server. For example, you can add content that provides custom monitoring and management facilities for your applications.

In the license for WebLogic Server Basic, the modification or extension of the Administration Console is not permitted. This restriction is placed on making any additions or changes to the Administration Console using the console extension mechanism.

For more information about this feature, see Oracle Fusion Middleware Extending the Administration Console for Oracle WebLogic Server.


A.6 Restricted APIs

Table A-8 describes the APIs in WebLogic Server that have restricted use under the terms of the WebLogic Server Basic license.

Table A-8 WebLogic Server APIs Restricted in WebLogic Server Basic

API Description

Use of CommonJ Work Manager for application initiated work

WebLogic Server also provides a programmatic way of handling work from within an application. This is provided through the CommonJ API. WebLogic Server implements the commonj.work and commonj.timers packages of the CommonJ specification.

In the license for WebLogic Server Basic, the use of CommonJ Work Manager for application initiated work is not permitted.

For more information about this feature, see "Using CommonJ With WebLogic Server" in Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server.

WebLogic JMS clients for Microsoft .NET and C

The WebLogic JMS .NET client is a fully-managed .NET run-time library and application programming interface (API). It enables programmers to create .NET C# client applications that can access WebLogic Java Message Service (JMS) applications and resources.

The WebLogic JMS C API is an application program interface that enables you to create C client applications that can access WebLogic JMS applications and resources. The C client application then uses the Java Native Interface (JNI), described at http://download.oracle.com/javase/1.5.0/docs/guide/jni/index.html, to access the client-side Java JMS classes

In the license for WebLogic Server Basic, the use of WebLogic JMS clients for .NET and C is not permitted.

For more information about the WebLogic JMS .NET client, see Oracle Fusion Middleware Using the WebLogic JMS Client for Microsoft .NET for Oracle WebLogic Server. For more information about the WebLogic JMS C API, see "WebLogic JMS C API" in Oracle Fusion Middleware Programming JMS for Oracle WebLogic Server.


A.7 Feature Usage Measurement

It is the end user's responsibility to ensure that the features available in WebLogic Server Basic are used in accordance with the terms of the license agreement. This section explains how the appropriate usage of license-restricted features can be easily measured, or how their usage can be prevented, to help ensure that each installation of WebLogic Server Basic is used in accordance with the terms of the license agreement.

To help with determining that WebLogic Server is being used in accordance with the WebLogic Server Basic license, a WLST script is available from My Oracle Support that you can download and run. This script is described in the following My Oracle Support article:

Doc ID: 885587.1

Subject: WebLogic Server Basic Feature Usage Measurement Script

This script measures the features of a WebLogic Server installation and generates a report that provides data about the usage or configuration of restricted WebLogic Server features defined by WebLogic Server Basic. Not every license-restricted feature is measured by this script, so its coverage is not exhaustive. But it can simplify feature usage measurement of most restricted features. (None of the data gathered by this script is transmitted or reported anywhere, and the use of this script is not mandatory. It is provided only as a convenience.) You can log in to My Oracle Support at the following URL to obtain this script:

https://support.oracle.com/CSP/ui/flash.html

For each license-restricted feature in WebLogic Server Basic, Table A-9 provides the following information:

Table A-9 Methods of Determining License Compliance

Feature Restriction and Method of Measurement

Whole server migration

This feature may not be used.

Whole server migration must be disabled.

You can confirm that whole server migration is disabled in a domain either by viewing Migratable Targets in the Administration Console or by examining the values of the following MBean attributes:

  • ServerMBean::AutoMigrationEnabled

  • ClusterMBean::MigrationBasis

You can obtain the values of these attributes by running the measurement script.

Service migration

This feature may not be used.

Make sure that none of the following services are configured in the domain:

  • Server Migration framework

  • User defined Singleton Services

  • Migratable targets with migration policy other than manual

  • Clustered EJB Timers

  • JTA Transaction Recovery service

You can determine whether these services are configured by running the measurement script.

MAN/WAN state replication

The use of either of these replication types is not permitted.

You can confirm that these replication types are not configured by running the measurement script.

Managed Server cloning

You may not enable the Clone attribute, which is available in the Administration Console by navigating to the Environment > Machines page.

Singleton services

Configuring either a standalone or application-provided singleton service is not permitted.

You can confirm that no singleton services are configured by running the measurement script.

GridLink data sources (also known as Active GridLink for RAC)

By validating the within the JDBC data source configuration files the elements <fan-enabled>, <ons-node-list> and <ons-wallet-file> are not configured.

Cluster constraints deployment

Setting the ClusterConstraintsEnabled option in a cluster is not permitted.

You can confirm that this feature is not in use by running the measurement script.

Overload management

Configuring any of the following overload protection schemes at either a cluster or server level is not permitted:

  • Limiting requests in the thread pool. You may not change the value of the Shared Capacity For Work Managers attribute in the Administration Console from the default value of 65536.

  • Limiting HTTP sessions. You may not use <max-in-memory-sessions> in the <session-descriptor> element of the Web application deployment descriptor file.

  • Exiting on "Out of Memory" exceptions. You may not configure this, either in the Administration Console or by editing the config.xml file.

  • Stuck thread handling. You may not configure WebLogic Server to exit if all application threads are stuck.

You can confirm this feature is not used by running the measurement script.

Server ADMIN and STANDBY mode

You may not use the ADMIN or STANDBY parameters in the command to start a WebLogic Server instance.

You can confirm that neither of these states is enabled by running the measurement script.

Production redeployment

Deploying an application in which a version identifier is specified, either indirectly through the manifest.mf file or directly through the weblogic.Deployer utility, is not permitted.

You can confirm this feature is not used by running the measurement script.

Application Administration mode

You may not use the -adminmode option to start any application hosted in a WebLogic Server instance.

You can confirm this feature is not used by running the measurement script.

Changing the order of deployment

This feature may not be used.

Do not change the value of the Deployment Order attribute, which can be set in the Administration Console or in the DeploymentOrder attribute of the AppDeploymentMBean.

You can confirm this feature is not used by running the measurement script.

FastSwap

This feature may not be used.

Make sure the <fast-swap>true</fast-swap> element is not present in the weblogic-application.xml file.

You can confirm this feature is not used by running the measurement script.

Deploying standalone JMS, JDBC, and WLDF modules

The deployment of standalone JMS, JDBC, or WLDF modules is not permitted. This restriction encompasses both module-level targeting as well as sub-module targeting.

You can confirm this feature is not used by running the measurement script.

Message Unit-of-Order

Configuring a JMS resource in which the default Unit-of-Order for a message producer is changed from the default value of None is not permitted.

You can confirm this feature is not used by running the measurement script.

Unit-of-Work Message Groups

Configuring a JMS resource to set the value of UnitOfWorkHandlingPolicy to anything other than the default value of Pass-Through is not permitted.

You can confirm this feature is not used by running the measurement script.

JMS Store-and-Forward agents

Configuring any store and forward agents is not permitted.

You can confirm this feature is not used by running the measurement script.

WebLogic Diagnostics Framework

The WebLogic Diagnostics Framework may not be configured.

You can confirm this feature is not used by running the measurement script.

WebLogic Server SNMP agents

All SNMP agents must be disabled.

You can confirm this feature is not used by running the measurement script.

WebLogic Tuxedo Connector

This component may not be used.

WebLogic HTTP Publish-Subscribe Server

The installation of this component is not permitted.

Use of custom Work Managers to prioritize and optimize work

This feature may not be used.

You can confirm that no custom Work Managers are configured in the domain by examining the value of the WorkManagerMBean. Note that the Console Work Manager is permitted in the WebLogic Server Basic license. This configuration MBean is accessed in the run-time tree or configuration tree, depending on how the Work Manager is accessed by an application:

  • If a Work Manager is defined at the module level, the WorkManagerRuntimeMBean is available through the corresponding ComponentRuntimeMBean.

  • If a Work Manager is defined at the application level, then WorkManagerRuntimeMBean is available through the ApplicationRuntimeMBean.

  • If a Work Manager is defined globally in the domain, each application creates its own instance of the Work Manager. Each application has its own corresponding WorkManagerRuntimeMBean available at the application level.

Buffered Web Services

Using the buffered Web Services feature of WebLogic Web Services is not permitted. None of the following tasks involving the use of this feature are permitted by the WebLogic Server Basic license:

  • Configuring a WebLogic Server instance for buffered Web Services

  • Implementing or deploying a buffered Web Service

  • Implementing a client that invokes a buffered Web Service

Asynchronous Web Services

Using the asynchronous request-response feature of WebLogic Web Services is not permitted. None of the following tasks involving the use of this feature are permitted by the WebLogic Server Basic license:

  • Configuring a WebLogic Server instance so that asynchronous Web Services may be deployed on it

  • Implementing or deploying clients that invoke Web Services asynchronously

Conversational Web Services

Implementing or deploying a Web Service that uses the conversational Web Service feature of WebLogic Web Services is not permitted.

JMS transport

Configuring or using the JMS transport feature of WebLogic Web Services as a connection protocol for invoking Web Services is not permitted. None of the following tasks involving the use of this feature are permitted by the WebLogic Server Basic license:

  • Configuring the JMS transport Web Service in a WebLogic domain

  • Using the @WLJmsTransport JWS annotation in a Web Service

  • Creating Web Service clients that use the JMS transport

Configuration Wizard, or the pack and unpack commands, for creating custom domains

Only domain templates and domain extension templates provided by Oracle may be used to create WebLogic domains. The use of these tools to create custom domains, create custom domain extension templates, or modify an existing domain through a custom domain extension template, is not permitted.

Domain Template Builder, or the pack and unpack commands, for creating domain or domain extension templates

The following tools may not be used:

  • Domain Template Builder

  • pack command

  • unpack command

Recording WebLogic Server Administration Console operations as a series of WebLogic Scripting Tool (WLST) commands

You may not use this feature in the Administration Console.

Extending the WebLogic Server Administration Console

You may not modify the WebLogic Server Administration Console through using the console extension feature.

Custom or CommonJ Work Manager usage outside the default WebLogic Server Work Manager

Any use of the CommonJ API in deployed applications is not permitted.

WebLogic JMS client for Microsoft .NET and C

Neither JMS client may be used.