Oracle 1z0-599 Exam Dumps

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?

Implementation-Version

Extension-Name

When an application that references a shared library or package is deployed,
WebLogic Server checks the names and version string requirements against the libraries
registered with the server. If an exact match for a library or package name is not found, or if
the version requirements are not met, the application deployment fails.
If WebLogic Server finds a name and version string match for all of the libraries referenced
in the application, the server adds the libraries' classes to the classpath of the referencing
application and merges deployment descriptors from both the application and libraries in
memory. The resulting deployed application appears as if the referenced libraries were
bundled with the application itself.
Note:
As a best practice, your development team should always include version string information
for a library or optional package in the manifest file for the deployment. See Editing
Manifest Entries for Shared Libraries in Developing Applications for Oracle WebLogic
Server for more information.
If you are deploying a library or package that does not include version string information,
you can specify it at the command line using one or both of the following options:
libspecver—Defines a specification version for the library or package.
libimplver—Specifies an implementation version for the library or package.
Reference: Deploying Applications to Oracle WebLogic Server, Deploying Shared Java EE
Libraries and Dependent Applications

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