1z0-599 Exam Dumps : Oracle WebLogic Server 12c Essentials

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

The major components of the WebLogic JMS Server architecture, as illustrated in the figure below.

*(A) JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

*(B) JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jmsmd.xsd schema.

*Client JMS applications that either produce messages to destinations or consume messages from destinations.

*(E) WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.

The following figure illustrates the WebLogic JMS architecture.

* 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.