Skip Headers
Oracle® Fusion Middleware Using the WebLogic JMS Client for Microsoft .NET for Oracle WebLogic Server
12c Release 1 (12.1.1)

Part Number E24386-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Installing and Copying the WebLogic JMS .NET Client Libraries

This chapter 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.

Installing the WebLogic JMS .NET Client

The WebLogic JMS .NET Client is bundled with WebLogic Server 10g Release 3 and later. When you perform a Complete installation of WebLogic Server on a supported platform, including non-Windows platforms, the WebLogic JMS .NET Client is installed by default. If you choose the Custom installation option, ensure that the WebLogic Server Clients component of WebLogic Server is selected. If you deselect this component, the WebLogic JMS .NET Client is not installed.

For a list of supported platforms for WebLogic Server, see "Supported Configurations" in What's New in Oracle WebLogic Server.

For details about installing WebLogic Server, see the Installation Guide.

Location of Installed Components

The WebLogic JMS .NET client is installed in the following directory on the WebLogic Server platform:

MW_HOME/modules/com.bea.weblogic.jms.dotnetclient_x.x.x.x

where MW_HOME is the top-level installation directory that you selected during the installation process and x.x.x.x is the version number of the client. If there is more than one .NET client module directory, its recommended to use the latest version in order to obtain the most recent updates.

The JMS .NET client installation consists of the following components:

  • WebLogic.Messaging.dll—The fully-managed JMS .NET client library used by the client for the JMS client application.

  • WebLogic.Messaging.pdb—The debug version of the JMS .NET client library that can be used by the client, together with the WebLogic.Messaging.dll, to debug the JMS .NET client application.

  • jms.dotnet.api.zip—HTML and Windows help-style documentation for the WebLogic JMS .NET API

    Note:

    The WebLogic JMS .NET client API documentation is also available at Microsoft .NET Messaging API for Oracle WebLogic Server.

Copying the Library to the Client Machine

After installing WebLogic Server on a supported platform, you need to copy the WebLogic.Messaging.dll library from the installation directory specified in Location of Installed Components to your development directory on a supported .NET client machine, and you need to ensure that your .NET application references the library. The JMS .NET client is a fully-managed runtime library that is supported on the following Windows platforms running version 3.0 to 4.5.1 of the .NET Framework:

If you are using Visual Studio, you can add the WebLogic.Messaging.dll as a reference assembly in your project as follows:

  1. Select Project > References

  2. Select Add Reference and specify the WebLogic.Messaging.dll from the directory into which you copied it on the .NET machine

Optionally, you can also copy the debug version of the JMS .NET client library, WebLogic.Messaging.pdb, and the API documentation to your client machine, but it is not required.