How BEA TOP END Client Requests Are Authorized

A BEA TOP END client request to a product/function or RTQ group/queue offered by the TEDG (DM_LOCAL_SERVICES) is subjected to the standard BEA TOP END authorization by the BEA TOP END client's system. The TEDG then subjects it to an optional access check based on the ACL parameter and the remote domain DOMAINID as configured in the DMCONFIG file. It then forwards the request to the BEA Tuxedo system along with the remote domain identifier of the BEA TOP END node as the client ID. Depending on the BEA Tuxedo security level (that is, if ACL and MANDATORY_ACL are being used), this request is then subjected to BEA Tuxedo authorization that takes place in the server application. Security associated with the dequeuing or forwarding of messages from a BEA Tuxedo /Q is unaffected by the TEDG.