This tutorial provides instructions on how to configure Oracle GoldenGate to take DML transactions from an Oracle database and send them to an Oracle WebLogic Server (WLS) JMS queue using GoldenGate Java Adapters.
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 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 shows how to use the PlanGenerator utility to generate an initial deployment plan for an existing web application. The tutorial then shows how to edit the deployment plan and use the Oracle WebLogic Server 12c(12.2.1) administration console to associate the plan with the application when it is redeployed.
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.
This tutorial describes the Policies and Actions component of the WebLogic Diagnostics Framework (WLDF) that provides the means for monitoring server and application states and then sending actions based on criteria set in the policies. Policies and actions are configured as part of a diagnostic module targeted to one or more server instances in a domain.
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.
Use the Domain to Partition Conversion Tool (D-PCT) to migrate existing applications and resources from a non-multitenant domain to a multitenant domain partition. D-PCT consists of two tools: an export tool, which you use on the WebLogic Server installation that hosts the source domain; and an import tool, which you use on the target WebLogic Server 12.2.1 installation.
For more information, see the documentation.
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.
This tutorial shows you how to use FMWC to manage different aspects of a WebLogic Server 12.2.1 domain, including:
This tutorial covers how to configure Java Message Service (JMS) System Modules and JMS Resources in WebLogic Server 12c(12.2.1).
Elasticity allows you to configure elastic scaling for a dynamic cluster based on either of the following:
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.