Oracle WebLogic Server 12c (12.2.1) Tutorials

This tutorial shows you how to install Oracle WebLogic Server 12c using the generic installer and how to create a basic WebLogic Server domain.

Before you can develop and run WebLogic-based applications, you must first create a domain. The Configuration Wizard guides you through the process of creating a new domain quickly and easily, by selecting the product components you want to include in your domain.

This tutorial describes how to use the Weblogic Server 12.2.1 Reconfiguration Wizard to reconfigure WebLogic Server Domain that was created using WebLogic Server 10.3.6.

This tutorial describes how to patch an Oracle Fusion Middleware environment with Zero Downtime.

By creating and using a customized domain template, you can create domains for multiple development, test, and production environments. Templates are created by using the Domain Template Builder.

This tutorial shows you how to create, configure, and start Oracle WebLogic Server Managed Servers.

In a WebLogic Server domain, machines can be defined to represent physical computers that host one or more Oracle WebLogic Server instances. Machine definitions help WebLogic Server choose backup servers for session replication. Machine definitions also include WebLogic Node Manager configuration.
This tutorial shows you how to create and configure machines by using the Oracle WebLogic Server 12c (12.2.1) administration console.

In a production environment, WebLogic Server instances are often distributed across multiple domains, machines, and geographic locations. Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart the administration server and managed servers from a remote location. Although Node Manager is not required, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.

A Node Manager process is not associated with a specific WebLogic domain, but with a particular machine. You can use the same Node Manager process to control server instances from any WebLogic Server domain, as long as those server instances reside on the same machine as the Node Manager process.

This tutorial covers configuring and starting the Java-based Node Manager and using it to control Oracle WebLogic Server 12c (12.2.1) managed servers. 

A WebLogic Server cluster consists of multiple managed servers running simultaneously, running the same applications, and working together to provide increased scalability and reliability. A cluster appears to a client as one WebLogic Server instance. Web application client requests go to the cluster proxy, which passes those requests to one of the servers in the cluster. A cluster proxy can be a web server, a hardware load balancer, or even another instance of WebLogic Server itself. The managed servers that make up a cluster can run on the same machine or on different machines. For increased reliability, managed servers in a cluster typically run on more than one machine.
This tutorial shows you how to use the Oracle WebLogic Server 12c (12.2.1) administration console to create a basic cluster and add servers to it. Additional tutorials extend this cluster's capabilities to support load balancing and failover of Java Platform, Enterprise Edition applications.

A data source is an object that enables a Java Database Connectivity (JDBC) client to obtain a database connection. The data source has a collection of database connections called a connection pool. An application can request a connection from the data source, use the connection to access the database, and then close the connection. Rather than actually close the connection, however, the data source places it back in the connection pool to be used again. Data sources can be created as part of the configuration of an instance of WebLogic Server. When that server comes up, (or the data source is deployed), the server creates database connections to fill the connection pool of its data source.

A cluster that contains one or more generated (dynamic) server instances that are based on a single shared server template is called as Dynamic Cluster.

Dynamic clusters consist of server instances that can be dynamically scaled up to meet the resource needs of your application. A dynamic cluster uses a single server template to define configuration for a specified number of generated (dynamic) server instances. When you create a dynamic cluster, the dynamic servers are preconfigured and automatically generated for you, enabling you to easily scale up the number of server instances in your dynamic cluster when you need additional server capacity. You can simply start the dynamic servers without having to first manually configure and add them to the cluster.

If you need additional server instances on top of the number you originally specified, you can increase the maximum number of servers instances (dynamic) in the dynamic cluster configuration or manually add configured server instances to the dynamic cluster. A dynamic cluster that contains both dynamic and configured server instances is called a mixed cluster.

Elasticity allows you to configure elastic scaling for a dynamic cluster based on either of the following:

• Manually adding or removing a running dynamic server instance from an active dynamic cluster. This is called on-demand scaling. You can perform on-demand scaling using the Fusion Middleware component of Enterprise Manager, the WebLogic Server Administration Console, or the WebLogic Scripting Tool (WLST).
• Establishing policies that set the conditions under which a dynamic cluster should be scaled up or down and actions that define the scaling operations themselves. When the conditions defined in the scaling policy occur, the corresponding scaling action is triggered automatically.

The elasticity framework leverages the WebLogic Diagnostic Framework (WLDF) Policies and Actions system. Using the WLDF Policies and Actions component, you can write policy expressions that will automatically scale up or scale down a dynamic cluster. These policies will monitor one or more resources, such as memory, idle threads, and CPU. When the configured threshold is met, the scaling action is triggered.

This tutorial covers how to configure Java Message Service (JMS) System Modules and JMS Resources in WebLogic Server 12c(12.2.1).

A Java web application, like any Java EE application, can be deployed to an application server as an archive file. Web application archives use the .war file extension.
This tutorial covers using the Oracle WebLogic Server 12c (12.2.1) administration console to deploy a simple Java EE web application. You learn how to start and run the application, redeploy an updated version of the application, and undeploy the application.

This tutorial shows how to use the Oracle WebLogic Server 12c (12.2.1) production redeployment feature to have two versions of the same application deployed simultaneously.

This tutorial shows you how to generate an initial deployment plan for an existing web application, edit the deployment plan, and then use the WebLogic Server Administration Console to redeploy your application with that plan.

This tutorial shows you how to use REST services to manage different aspects of a WebLogic Server 12c (12.2.1) domain, including:

• Servers and clusters
• Application deployments
• JDBC data sources

With WLST, you can monitor, control, and configure servers and other domain resources from the command line. You can also save groups of commands in files so that you can reliably perform the same tasks many times.
This tutorial introduces you to WLST. It gives you a chance to practice basic commands and to change server attributes from the command line.

This tutorial shows you how to use FMWC to manage different aspects of a WebLogic Server 12.2.1 domain, including:

• Servers and clusters
• Application deployments
• JDBC data sources
• Users and groups

This tutorial shows you how to configure SSL certificates using keytool, and configuring WebLogic servers to use those certificates to establish secure SSL connections.

This tutorial shows you how to configure an external LDAP server and configure the LDAP server as one of the authentication providers of the WebLogic Server security realm.

This tutorial shows you how to configure an Oracle Traffic Director to proxy requests to a WLS Cluster.

Oracle Traffic Director is a fast, reliable, and scalable layer-7 software load balancer. You can set up Oracle Traffic Director to serve as the reliable entry point for all HTTP, HTTPS and TCP traffic to application servers and web servers in the back end. Oracle Traffic Director distributes the requests that it receives from clients to servers in the back end based on the specified load-balancing algorithm, routes the requests based on specified rules, caches frequently accessed data, prioritizes traffic, and controls the quality of service.

It includes a simple, web browser based graphical user interface (using Oracle Enterprise Manager) as well as robust Command Line Interface using Oracle WebLogic WLST.For high availability, you can set up pairs of Oracle Traffic Director instances for either active-passive or active-active failover.

In this tutorial, you will configure Oracle Traffic Director as a front end to a backend WebLogic Server 12c(12.2.1) Cluster.

A specific feature called "Dynamic Discovery", will let Oracle Traffic Director discover an "on the fly" new clustered WebLogic Node associated with it's initial configuration and you will be able to "join" the discovered WebLogic Node(with full HTTP replication capabilities) to your initial two Nodes WebLogic cluster.

This tutorial describes how WebLogic logging services provide facilities for writing, viewing, filtering, and listening for log messages. These log messages are generated by WebLogic Server instances, subsystems, and Java EE applications that run on WebLogic Server or in client JVMs.

WebLogic Server subsystems use logging services to provide information about events such as the deployment of new applications or the failure of one or more subsystems. A server instance uses them to communicate its status and respond to specific events. For example, you can use WebLogic logging services to report error conditions or listen for log messages from a specific subsystem.

Each WebLogic Server instance maintains a server log. Because each WebLogic Server domain can run concurrent, multiple instances of WebLogic Server, the logging services collect messages that are generated on multiple server instances into a single, domain-wide message log. The domain log provides the overall status of the domain.