How To Locate the Java Message Service's Physical Destinations In Glassfish Application Server (Doc ID 1372380.1)

Last updated on JUNE 08, 2022

Applies to:

Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.

Goal

Depending on which distribution of the Glassfish Server that the customer has installed, the configuration of the Java Message Service's (JMS) physical destination may differ.

The location of the java Message service's physical destination depends on

#1. the domain's profile, which is manually created
#2. or that of the default domain's profile, created during installation

If you refer to Note:1269664.1 "Primary Note for GlassFish Server Documentation, Release Notes, Certification and Patches", for Glassfish Server 2.1.1, there are three types of patch:

a. 128643 ( File-based with HADB )
b. 128647 ( File-based without HADB )
c. 128640 ( Native package )

The article will illustrate two examples using patch 128643 and patch 128647

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

"File-based without HADB" Patch 128647

"File-based with HADB" Patch 128643

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How To Locate the Java Message Service's Physical Destinations In Glassfish Application Server (Doc ID 1372380.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!