1z0-599 Practice Test

Use SmartUpgrade to analyze the OAS/OC4J server configuration and create WebLogic
configuration files.

Use the Configuration Wizard to extend an existing WebLogic domain with OAS/OC4J
support libraries and redeploy the application.

Use SmartUpgrade to generate application artifacts and deployment descriptors that can
be deployed to WebLogic.

Note:
* Oracle WebLogic SmartUpgrade is part of the Oracle Fusion Middleware 11g upgrade
tools that were designed to maximize the automation of the upgrade process, minimize the
application
downtime and allows for rapid and seamless uptake of the Oracle Fusion Middleware 11g
features and capabilities.
* SmartUpgrade : (B) When generating an upgrade report into an existing project, an
Oracle Application Server
configuration home could be specified to be included as part of the report. Additionally,
both the
server home and OracleAS enterprise archives can be localized into the JDevelopoer
project file
system by checking "Copy OC4J Deployment Archives Into Project".
* SmartUpgrade : (E) The advisory reports and the configuration artifacts will be generated.
The generated artifacts will be located at the JDeveloper project mywork directory
* You can add product component functionality or additional applications and services to an
existing WebLogic domain by extending it using the Configuration Wizard. For example, if
you created a base WebLogic domain and you want to add the Avitek Medical Records
Examples functionality, you can extend the domain by using the medrec.jar template.
The Configuration Wizard simplifies the task of extending an existing WebLogic domain by
using extension templates. Oracle provides various sample extension templates, as well as
extension templates for various Fusion Middleware products. You can also create your own
extension templates using WLST or the unpack command.

You need to install and configure only one instance of Node Manager for all products,
regardless of the WebLogic version number.

* In managing multiple servers, Node Manager uses multiple configuration files and outputs
log files to multiple directories.
* nodemanager.domains
This file contains mappings between the names of domains managed by Node Manager
and their corresponding directories.
* Node Manager in the WebLogic Server Environment

Description of Figure 2-1 follows
Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

GET

PUT

DELETE

POST

The following principles encourage RESTful applications to be simple,
lightweight, and fast:
Resource identification through URI
* Uniform interface: Resources are manipulated using a fixed set of four create, read,
update, delete operations: PUT, GET, POST, and DELETE. PUT creates a new resource,
which can be then deleted by using DELETE. GET retrieves the current state of a resource
in some representation. POST transfers a new state onto a resource. See Responding to
HTTP Methods and Requests for more information.
* Self-descriptive messages
* Stateful interactions through hyperlinks
Reference: The Java EE 6 Tutorial, What Are RESTful Web Services?

Oracle WebLogic Server clusters; Oracle Database RAC

The WebLogic Server JDBC subsystem has supported Oracle RAC since
WLS
version 8.1 SP5, originally developed for Oracle9i RAC. This support is based on a
particular type of data source configuration, called a multi data source. A multi data
source is a data source abstraction over one or more individual data sources. It
serves JDBC connections from each of the member data sources according to a
specified policy2. A RAC multi data source configuration requires that each
member data source obtain connections to a particular RAC instance, as illustrated
in the following diagram of a three-node RAC cluster configuration.

Reference: Oracle WebLogic Server Active GridLink for Oracle Real Application
Clusters(RAC)

boot.properties file automatically stored

creation of an auto deploy folder used for the application to deploy automatically

The saviour of having to type in the username and password each and
every time that you start a server. A very useful little file to have, particularly if you have
multiple managed servers.
By default, this appears in the Admin Servers security directory
($DOMAIN_HOME/servers/AdminServer/security) when a domain is created in
development mode and is called boot.properties. The file is only created for the admin
server, not for any additional servers; simply copying the security directory over is enough.
The password is encrypted for the domain, so it can only be used for servers within tha
domain.
In production mode, the boot.properties file doesn’t exist.
D: Development mode enables a WebLogic Server instance to automatically deploy and
update applications that are in the domain_name/autodeploy directory (where
domain_name is the name of a WebLogic Server domain). Production mode disables the
auto-deployment feature and prevents any applications you place in the autodeploy
directory after you switch to production mode from being deployed.
Note:
* By default, a WebLogic Server domain runs in development mode.
* You can run a WebLogic Server domain in two different modes: development and
production. Only development mode allows you use the auto-deployment feature