Oracle Service Bus JMS Deployments Utility by Mike Muller
- by JuergenKress
For
proxy services utilizing the JMS transport, OSB receives messages from
destinations by using an MDB. These MDBs get generated and deployed
during activation of the service configuration. OSB creates a random,
unique name for the J2EE application that gets deployed to WLS. The name
starts with “_ALSB_” and ends in a unique series of digits. The EAR
files are written to the sbgen subdirectory of the domain home
directory. You will see these applications on the WLS console page for
“Deployments”.
For various operational reasons, there are times
when the application name for a given proxy service needs to be
determined. Since the generated name of the application doesn’t reflect
the name of the service, it becomes difficult to determine the
relationship between the service and its EAR file. In fact, it can not
be discerned from either the OSB or WLS consoles.Read the full article here.
SOA & BPM Partner Community
For
regular information on Oracle SOA Suite become a member in the SOA
& BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog Twitter LinkedIn Facebook Wiki Mix Forum
Technorati Tags: Service bus,OSB,JMS,SOA Community,Oracle SOA,Oracle BPM,Community,OPN,Jürgen Kress
