1z0-599 Practice Test

Use flag -version when redeploying the application. This will switch on the Side By Side
deployment feature and preserve existing sessions.

Restrictions on Production Redeployment Updates
WebLogic Server can host a maximum of two different versions of an application at one
time.
Note:
* When you redeploy a new version of an application, you cannot change:
An application's deployment targets
An application's security model
A Web application's persistent store settings
To change any of the above features, you must first undeploy the active version of the
application.
Incorrect:
* (not A)
Production redeployment enables you to update and redeploy an application in a
production environment without stopping the application or otherwise interrupting the
application's availability to clients. Production redeployment saves you the trouble of
scheduling application downtime, setting up redundant servers to host new application
versions, manually managing client access to multiple application versions, and manually
retiring older versions of an application.
* (not C) Not dependant on whether the application is JRockit or Hotspot.
* (not E)
The production redeployment strategy is supported for:
Standalone Web Application (WAR) modules and enterprise applications (EARs) whose
clients access the application via a Web application (HTTP).
Enterprise applications that are accessed by inbound JMS messages from a global JMS
destination, or from inbound JCA requests.
All types of Web Services, including conversational and reliable Web Services, but not 8.x
Web Services.
Production redeployment is not supported for:
Standalone EJB or RAR modules. If you attempt to use production redeployment with such
modules, WebLogic Server rejects the redeployment request. To redeploy such modules,
remove their version identifiers and explicitly redeploy the modules.
Applications that use JTS drivers. For more information on JDBC application module
limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC
Data Sources for Oracle WebLogic Server.
Applications that obtain JDBC data sources via the DriverManager API; in order to use
production redeployment, an application must instead use JNDI to look up data sources.
Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use
production redeployment with applications that include CMP EJBs, use EJB 2.x CMP
instead of EJB 1.1 CMP.
Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c,
Redeploying Applications in a Production Environment

simplified disaster recovery architecture and efforts

common storage of transaction logs with application data

common replication of transaction logs with application data

Comparing File Stores and JDBC-accessible Stores
The following are some similarities and differences between file stores and JDBCaccessible
stores:
* (A) JDBC stores may make it easier to handle failure recovery since the JDBC interface
can access the database from any machine on the same network. With the file store, the disk must be shared or migrated.
* The default persistent store can only be a file store. Therefore, a JDBC store cannot be
used as a default persistent store.
* Both have the same transaction semantics and guarantees. As with JDBC store writes,
file store writes are guaranteed to be persisted to disk and are not simply left in an
intermediate (that is, unsafe) cache.
* Both have the same application interface (no difference in application code).
* (not B, not E) All things being equal, file stores generally offer better throughput than a
JDBC store.
/ If a database is running on high-end hardware with very fast disks, and WebLogic Server
is running on slower hardware or with slower disks, then you may get better performance
from the JDBC store.
* File stores are generally easier to configure and administer, and do not require that
WebLogic subsystems depend on any external component.
* File stores generate no network traffic; whereas, JDBC stores generate network traffic if
the database is on a different machine from WebLogic Server.
Reference: Configuring Server Environments for Oracle WebLogic Server 12c, Comparing
File Stores and JDBC-accessible Stores

If there are multiple versions of the shared library deployed, WebLogic will use the one
with the highest Implementation-Version.

An internal application may be configured to always use a minimum version
of the same library. Applications that require no specific version can be configured to use
the latest version of the library.
Note:
* Specification-Version (a manifest Attributes for Java EE Libraries)
An optional String value that defines the specification version of the shared Java EE library.
Referencing applications can optionally specify a required Specification-Version for a
library; if the exact specification version is not available, deployment of the referencing
application fails.
The Specification-Version uses the following format:
Major/minor version format, with version and revision numbers separated by periods (such
as "9.0.1.1")
Referencing applications can be configured to require either an exact version of the shared
Java EE library, a minimum version, or the latest available version.
* Implementation-Version (a manifest Attributes for Java EE Libraries)
An optional String value that defines the code implementation version of the shared
Java EE library. You can provide an Implementation-Version only if you have
also defined a Specification-Version.
* Extension-Name (a manifest Attributes for Java EE Libraries)
An optional string value that identifies the name of the shared Java EE library. Referencing
applications must use the exact Extension-Name value to use the library.
As a best practice, always specify an Extension-Name value for each library. If you do not
specify an extension name, one is derived from the deployment name of the library. Default
deployment names are different for archive and exploded archive deployments, and they
can be set to arbitrary values in the deployment command.
After a library is deployed, the extension-name, specification-version and implementationversion
of the library can be found in Administration console.
Reference: Creating Shared Java EE Libraries and Optional Packages

Deployment Descriptor

META-INF sub directory

A WAR file deployed to WebLogic Server always includes the following files:
One servlet or Java Server Page (JSP), along with any helper classes.
An optional web.xml deployment descriptor, which is a Java EE standard XML document
that describes the contents of a WAR file.
A weblogic.xml deployment descriptor, which is an XML document containing WebLogic
Server-specific elements for Web applications.
A WAR file can also include HTML or XML pages and supporting files such as image and
multimedia files.

Configure one Node Manager per machine with any number of WebLogic instances
running on it.

A Node Manager process is not associated with a specific WebLogic domain
but with a
machine. You can use the same Node Manager process to control server instances in
any WebLogic Server domain, as long as the server instances reside on the same
machine as the Node Manager process. Node Manager must run on each computer
that hosts WebLogic Server instances—whether Administration Server or Managed
Server—that you want to control with Node Manager.
Reference: Overview of WebLogic Server Domains