This chapter describes the contents and organization of this guide—Developing JMS .NET Client Applications for Oracle WebLogic Server.
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.
This chapter, Chapter 1, "Introduction and Roadmap," introduces the organization of this guide.
Chapter 2, "Overview of the WebLogic JMS .NET Client," provides an overview of the WebLogic JMS .NET client, illustrates how a JMS .NET client application accesses WebLogic JMS resources, and provides a brief summary of the WebLogic JMS .NET API.
Chapter 3, "Installing and Copying the WebLogic JMS .NET Client Libraries," describes the JMS .NET client components installed on a WebLogic Server platform, the location to which they are installed, and how to copy them to a .NET Framework machine.
Chapter 4, "Developing a Basic JMS Application Using the WebLogic JMS .NET API," describes the steps required to develop a basic JMS application in C# using the JMS .NET API.
Chapter 5, "Programming Considerations," provides programming considerations and best practices to use when creating a JMS .NET client application.
Appendix A, "JMS .NET Client Sample Application," provides a .NET client sample program written in C# which includes basic features of the WebLogic JMS .NET API.
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.
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.
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.