Introduction to Oracle WebLogic Server for OC4J Users 3-7
dedicated ports and port ranges can be configured on an OC4J instance for RMI and JMS traffic.
The WebLogic Server request port and protocol management model is by default different from OC4J’s in two important ways:
■
First, an Oracle WebLogic Server instance is configured to have only two listen ports for incoming application requests: one port for accepting non-encrypted
requests which has to be set and the other for accepting SSL encrypted requests which is optional.
■
Second, these ports are configured to accept requests for all supported protocols as opposed to being dedicated to a specific one as is the case with OC4J instances.
Although in general, this default listening port model is sufficient for a majority of use cases, Oracle WebLogic Server offers a feature called network channels, which allows
you to configure a WebLogic Server instance with additional ports dedicated to specific protocols. This feature can be used for the special use cases where such a
configuration is required.
3.1.3.2.4 A WebLogic Server Instance Is Always Configured With an HTTP Listener and Does Not
Support AJP One of the supported OC4J configurations is a topology where a front-end Web server in most cases, Oracle HTTP Server is configured to receive incoming
HTTP requests. The requests are then routed from Oracle HTTP Server to the appropriate OC4J instance via the AJP protocol. In this configuration, the OC4J
instance does not receive HTTP requests directly and no HTTP listener is configured on the OC4J instance.
In contrast, an Oracle WebLogic Server instance must always accept HTTP requests and has no support for AJP. However, WebLogic Server domains can be and
frequently are fronted by a Web tier for security and scalability purposes. A number of Web servers, including Oracle HTTP Server, are certified to act as a Web tier to
servers within a WebLogic Server domain.
For more information, see Chapter 7, Upgrading a Java EE and Web Server
Environment .
3.2 Oracle WebLogic Server Installation and Configuration Tools for OC4J Users
Unlike Oracle Application Server 10g, Oracle WebLogic Server separates the tasks of installing and configuring your environment.
In Oracle Application Server 10g, you use Oracle Universal Installer to install and configure your Oracle Application Server environment, including the OC4J instances
within that environment.
With Oracle WebLogic Server, you use two separate tools to install and configure your environment:
■
The Oracle WebLogic Server installer , which you use to create the Middleware
home and place the necessary Oracle WebLogic Server files on disk, in preparation for configuring your Oracle WebLogic Server domains.
■
The Oracle WebLogic Server Configuration Wizard , which you use to create and
configure your Oracle WebLogic Server domains. This separation of installation and configuration tasks allows you create multiple
domains from a single Oracle WebLogic Server instance, as described in Section 3.1.3.2.1
.
