Preface
This document is written for application developers who want to develop JMS .NET client applications that access WebLogic JMS resources.
Audience
This document is a resource for software developers who want to develop and configure applications that include WebLogic Server Java Message Service (JMS). It also contains information that is useful for business analysts and system architects who are evaluating WebLogic Server or considering the use of WebLogic Server JMS for a particular application
The topics in this document are relevant during the design and development phases of a software project. The document also includes topics that are useful in solving application problems that are discovered during test and pre-production phases of a project.
This document does not address production phase administration, monitoring, or performance tuning JMS topics. For links to WebLogic Server documentation and resources for these topics, see Related Documentation.
It is assumed that the reader is familiar with Java EE and JMS concepts. This document emphasizes the value-added features provided by WebLogic Server JMS and key information about how to use WebLogic Server features and facilities to get a JMS application up and running.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Diversity and Inclusion
Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.
Related Documentation
This document contains JMS-specific design and development information.
For comprehensive guidelines for developing, deploying, and monitoring WebLogic Server applications, see the following documents:
-
Administering JMS Resources for Oracle WebLogic Server for information about configuring and managing JMS resources.
-
Developing JMS Applications for Oracle WebLogic Server is a guide to JMS API programming with WebLogic Server.
-
Administering the Store-and-Forward Service for Oracle WebLogic Server for information about the benefits and usage of the Store-and-Forward service with WebLogic JMS.
-
Administering the WebLogic Persistent Store for information about the benefits and usage of the system-wide WebLogic Persistent Store.
-
Deploying Applications to Oracle WebLogic Server is the primary source of information about deploying WebLogic Server applications.
Samples and Tutorials for the JMS Developer
In addition to this document, Oracle provides a variety of code samples and tutorials for JMS developers. The examples and tutorials illustrate WebLogic Server JMS in action, and provide practical instructions on how to perform key JMS development tasks.
Oracle recommends that you run some or all of the JMS examples before developing your own JMS applications.
Avitek Medical Records Application (MedRec) and Tutorials
MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.
MedRec demonstrates WebLogic Server and Java EE features, and highlights
Oracle-recommended best practices. MedRec is optionally installed with the WebLogic
Server installation. You can start MedRec from the
ORACLE_HOME
\user_projects\domains\medrec
directory, where ORACLE_HOME
is the directory you specified
as the Oracle Home when you installed Oracle WebLogic Server.
MedRec includes a service tier comprised primarily of Enterprise Java Beans (EJBs) that work together to process requests from web applications, web services, and workflow applications, and future client applications. The application includes message-driven, stateless session, stateful session, and entity EJBs.
Conventions
The following text conventions are used in this document:
Convention | Meaning |
---|---|
boldface |
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
italic |
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
|
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |