1Z0-133: Oracle WebLogic Server 12c: Administration IDemo

A WebLogic HTTP proxy application is deployed to a Managed Server that is not assigned to a cluster, while the target cluster must contain Managed Servers. A topology with three cluster members and one separate proxy host therefore requires one cluster, four Managed Servers total, and assignment of three servers to that cluster. Oracle HTTP Server and Coherence are not required, and the proxy is not configured by specifying a proxy port for the Administration Server.

In Oracle WebLogic Server, the Show Inline Help preference controls whether inline help appears on forms and applies only to the individual user account in the current domain. Disabling it therefore must be performed separately by each user rather than once for all administrators. Oracle: Preferences: User Preferences

The WebLogic Monitoring Dashboard presents runtime and collected diagnostic metrics in charts, including historical time ranges. A custom view is required to configure a modifiable comparison, and a view can contain multiple charts with metrics added to them. Placing the HTTP-session and heap-size metrics in charts within the same custom view enables their values to be viewed together and correlated.

A transaction spanning several databases requires distributed transaction coordination. WebLogic Server uses XA-capable JDBC resources for this purpose and applies the two-phase-commit protocol to XA data sources. Each data source should therefore be configured with an XA-compliant driver available for its DBMS.

Manual Node Manager Setup causes the Configuration Wizard to skip creating the domain’s Node Manager configuration. If Node Manager is to be used, its configuration must be created and maintained manually afterward.

File persistence externalizes HTTP session state to a configured persistent directory, allowing the in-memory session cache to remain bounded. With a highly available shared file store, surviving cluster members can access persisted sessions after multiple server failures. JDBC/database persistence requires a database table using a prescribed schema, while in-memory replication maintains only a primary session and a secondary replica on cluster servers; whole-server migration is server failover rather than HTTP-session persistence.

In WebLogic Server, a higher channel weight gives an eligible network channel preference for outbound server-to-server connections. Accept Count is the number of sockets accepted on a channel, including both current and past sockets, so it indicates the overall connection rate. Byte counts measure data volume, while Connections measures active connections at a point in time.

A database-backed WebLogic JDBC TLOG store is configured on the managed server as a JDBC transaction-log store and requires a domain JDBC data source that uses a non-XA driver (with global transactions disabled). XA data sources cannot be used for a JDBC TLOG store.

The RDBMS security store requires datastore tables created by the supplied SQL scripts located in WL_HOME/server/lib, and the Configuration Wizard provides a Test Connection option for the database. Tablespace allocation and importing external LDAP users are not part of this security-store configuration process.

WebLogic Administration Console monitoring tables can be customized by sorting rows on a chosen column, limiting the number of displayed rows, and changing the displayed-column order. These controls alter the table presentation; they do not combine columns or select a time range.

WebLogic jCOM is a bidirectional Java-to-COM bridge that lets applications deployed in WebLogic Server access COM/DCOM components as Java objects. Oracle describes jCOM as a migration path for interim Java-to-COM integration and notes that web services and REST are the preferred long-term approach.

Oracle Notification Service (ONS) delivers RAC/FAN state changes to a GridLink data source, allowing it to rapidly remove invalid pooled connections and adapt to RAC node changes without polling and testing connections. A GridLink data source also requires configuration of the target RAC database service and database-server listener connection details, such as host and port. Oracle: Using Active GridLink Data Sources

Logging Last Resource (LLR) enables one non-XA JDBC resource to participate in a global transaction with XA resources while preserving ACID guarantees. WebLogic records the transaction decision on the LLR resource and coordinates it with the other transaction participants. One-Phase Commit cannot be used when multiple resources participate.

lsof can select Internet socket files by IP address and port and reports the owning process. netstat reports listening ports and their local IP addresses; supported platform options can also show the associated process or PID. These capabilities identify the process that already owns the socket address responsible for a bind conflict.

A network channel is bound to a listening endpoint defined by its listen address and listen port. Channels assigned to the same WebLogic Server instance must therefore use a unique endpoint combination; Oracle’s complete channel rule also accounts for protocol.

Oracle WebLogic Node Manager manages server-process lifecycle operations. It can start servers, automatically restart failed server instances under its control, and forcibly kill an unresponsive server process. Server definition is a domain-configuration task, and Node Manager acts on server processes rather than individual failed applications. About Node Manager

Machine definitions provide the information needed to connect to Node Manager and identify the WebLogic Server instances it manages. In a cluster, machine assignments help WebLogic Server select a server on separate hardware for session-state replication, improving resilience to a machine failure.

A WebLogic cluster belongs to a single WebLogic domain and cannot be configured across multiple domains. The other options represent supported clustering, load-balancing, session-management, or cluster-communication configuration choices.

When recovering an Administration Server on another machine, deployed application files must be restored or shared at the same relative location as on the original Administration Server. Automatic reconnection by already running Managed Servers requires the restarted Administration Server to remain reachable at the endpoint they know, such as the same DNS name or IP address; a DNS name can map to multiple IP addresses for recovery on a different IP.

A multitier architecture places web/presentation services and EJB/object services in separate clusters. The tiers can therefore be scaled independently according to their workloads, and multiple web clusters can use the same dedicated EJB tier. Oracle WebLogic documentation describes separate web and EJB clusters as providing greater flexibility for distributing load and independently concentrating web versus EJB capacity.

Oracle Fusion Middleware provides compareInventory.sh to compare the contents of two Oracle homes. On UNIX, it is located in ORACLE_HOME/oui/bin and uses the required -oracle_home1 and -oracle_home2 parameters to identify the two installations.

Oracle WebLogic Server supports binding dynamic servers to any machine configured in the domain, to one selected machine for all dynamic servers, or to a subset of domain machines selected with a machine-name match expression. It does not provide percentage-of-machines or subnet-based machine-binding options.

On UNIX/Linux, Java-based Node Manager can be started with the startNodeManager.sh script. It can also run as an operating-system service or daemon, allowing it to start automatically at system boot. A direct Java launch uses the weblogic.NodeManager class rather than nodemanager.RunTime.

For a dynamic cluster with calculated listen ports enabled, WebLogic Server adds each server instance ID to an explicitly configured base listen port. With base port 8101, instances 1 and 2 bind to ports 8102 and 8103.