09.12.2012 Views

Advanced Queuing - Oracle

Advanced Queuing - Oracle

Advanced Queuing - Oracle

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The servlet parses the content of the IDAP document and uses the AQ Java API<br />

to perform the designated operation. On completion of the call, the servlet<br />

formats either a response or an error response as indicated by IDAP and sends<br />

it back to the client.<br />

IDAP is transport independent and therefore can work with other transport<br />

protocols transparently. <strong>Oracle</strong>9i supports HTTP and SMTP; other proprietary<br />

protocols can also be supported using the callout mechanism through<br />

transformations.<br />

<strong>Advanced</strong> <strong>Queuing</strong> Security over the Internet<br />

<br />

AQ functionality allows only authorized Internet users to perform AQ<br />

operations on AQ queues. An Internet user connects to a Web server, which in<br />

turn connects to the database using an application server. The Internet user<br />

doing the operation is typically not the database user connected to the database.<br />

Also, the AQ queues may not reside in the same schema as the connected<br />

database user. <strong>Advanced</strong> <strong>Queuing</strong> uses proxy authentication so that only<br />

authorized Internet users can perform AQ operations on AQ queues.<br />

LDAP Integration<br />

<br />

OID Integration: To leverage LDAP as the single point for managing generic<br />

information, <strong>Advanced</strong> <strong>Queuing</strong> is integrated with the <strong>Oracle</strong> Internet<br />

Directory (OID) server. This addresses the following requirements:<br />

Global topics (queues): AQ queue information can be stored in an OID<br />

<br />

server. OID provides a single point of contact to locate the required topic or<br />

queue. Business applications (users) looking for specific information need<br />

not know in which database the queue is located. Using the industry<br />

standard Java Messaging Service (JMS) API, users can directly connect to<br />

the queue without explicitly specifying the database or the location of the<br />

topic or queue.<br />

Global events: OID can be used as the repository for event registration.<br />

<br />

Clients can register for database events even when the database is down.<br />

This allows clients to register for events such as “Database Open,” which<br />

would not have been possible earlier. Clients can register for events in<br />

multiple databases in a single request.<br />

XML Integration: XML has emerged as a standard for e-business data<br />

representations. The XMLType datatype has been added to the <strong>Oracle</strong> server to<br />

support operations on XML data. AQ not only supports XMLType data type<br />

payloads, but also allows definitions of subscriptions based on the contents of<br />

an XML message. This is powerful functionality for online market places where<br />

xxxix

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!