This tutorial shows you how to install Oracle WebLogic Server 12c using the generic installer and how to create a basic WebLogic Server domain.
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.
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 how to use the Oracle WebLogic Server 12c (12.2.1) production redeployment feature to have two versions of the same application deployed simultaneously.
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 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.
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.
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 video shows how to manage Java EE applications using the WebLogic Server RESTful Management Services. The main points/steps are:
This video provides a short overview and demonstration of the new elastic scaling feature in WebLogic Server 12.2.1. A dynamic cluster is created and then elastically scaled both up and down using WLST commands.
This video follows on from the "Elastic Cluster Scaling using WLST video" and demonstrates using the WebLogic Server Administration Console to configure elasticity in a dynamic cluster.
This demonstration of the elastic cluster scaling features of WebLogic Server 12.2.1 shows how to configure an environment that can automatically scale up and down based on the load that the cluster is experiencing. The WebLogic Administration Console is used to create two policies and actions that elastically scale the cluster based on the memory being utilized by the members of the cluster. A new managed server instance is created and started when memory use is increased. A managed server instance is shutdown when the memory use is
This tutorial shows you how to create, configure, and start Oracle WebLogic Server Managed Servers.