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.

Deploying the AQ XML Servlet<br />

If an AQ Internet agent is mapped to more than one db_user, then all the db_<br />

users must have the FORCE ANY TRANSACTION privilege:<br />

grant FORCE ANY TRANSACTION to OE;<br />

grant FORCE ANY TRANSACTION to CBADM;<br />

To disable the mapping between an agent and a database user, use DBMS_<br />

AQADM.DISABLE_DB_ACCESS.<br />

The SYSTEM.AQ$INTERNET_USERS view lists AQ agents, the protocols they are<br />

enabled for, and the mapping between AQ agents and database users. Example<br />

entries in this view are shown in Table 17–8.<br />

Table 17–8 The SYSTEM.AQ$INTERNET_USERS View<br />

agent_name db_username http_enabled smtp_enabled<br />

scott cbadmin YES NO<br />

scott buyer YES NO<br />

aqadmin OE YES YES<br />

aqadmin seller YES YES<br />

bookstore - NO YES<br />

Using an LDAP Server with an AQ XML Servlet<br />

An LDAP server is required if:<br />

The AQ agent is accessing the AQ servlet using SMTP. (See "Setup for Receiving<br />

<br />

AQ XML Requests Using SMTP (E-mail)" on page 17-55 for details.)<br />

The lookup_type destination attribute is specified as LDAP. In this case the<br />

<br />

destination name is resolved to a schema.queue_name using the LDAP<br />

server.<br />

You use agent_alias instead of (agent_name, address, protocol). If<br />

<br />

an agent_alias is specified in a client request, it is resolved to agent_name,<br />

address, protocol using the LDAP server.<br />

The LDAP context must be specified by the setLDAPContext(DirContext) call,<br />

as follows:<br />

public void init()<br />

{<br />

17-54 <strong>Oracle</strong>9i Application Developer’s Guide - <strong>Advanced</strong> <strong>Queuing</strong>

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

Saved successfully!

Ooh no, something went wrong!