www.it-ebooks.info

Configuration and Administration of Tuxedo
There are mainly five types of incremental security provided by Tuxedo, which are
as follows:
• No authentication (NONE): This level might be used in a development
environment or in physically secured environments, as the clients do not
need to be authenticated to join the application.
• Application password (APP-PW): This is a single password for the entire
application; all the clients must provide this password to join the application.
• End user authentication (USER_AUTH): In this level, the client needs to provide
a username and password; this is to customize the security for applicationspecific
users to ensure that they can access the Tuxedo application.
• Optional access control (ACL): For all the previously mentioned levels,
information needs to be provided by the client and the administrator so
that access can be controlled to services, application queues, and events
with access control lists. This level allows you to configure access only for
those resources that need security; there is restricted access to a certain set of
services while still allowing unprotected access to other services.
• Mandatory access control (MANDATORY_ACL): This is very similar to the
ACL level; the only difference is that the resources without an ACL are
considered restricted, that is, access is not granted to resources that do not
have an ACL permission.
In this section, we have discussed all the different types of security features that
you may like to consider to secure your Tuxedo application.
Data-dependent routing (DDR)
Data-dependent routing (or context-based routing) is used to enable a client to send
requests for a service to have multiple/distributed copies of it; this is determined by
the data in the requested message. Once an administrator has set up data-dependent
routing for an application, the client requests can be routed automatically to servers
based on the data in the requests. This DDR can be used in three different ways; we
will discuss this in the following sections.
Horizontally partitioned
When a Tuxedo service is associated with a horizontally partitioned database (which
means the database has been divided into segments), each segment is used to store
a different category of information. As an example, there are different sections in a
hospital (for example, ENT and cardiology). So, the same service can be called from
different clients, but the request will be routed to the service-particular department
server as the database was designed as horizontally partitioned.
[ 58 ]
www.it-ebooks.info