Chapter 6: Using Service Name Redirection  Editing service name redirection (snrf) tables

Chapter 6: Using Service Name Redirection

How service name redirection works

When a client application accesses a service, it specifies an access service name. That name must correspond either to the name of an actual access service or to an entry in the service name redirection file (snrf).

Service name redirection allows you to control access to services using the user profile: requested access service, user ID, and application name. You can assign each user profile to any access service supported by an access service library. The DirectConnect server attempts to match the client request with an entry in the service name redirection file before connecting directly with the access service.

Different users who request the same general service name can be routed to different actual access services. For example, three individuals requesting “AS400” could receive completely different access services, such as:

Thus, you can manage multiple sets of clients with a single Access Service Library. However, you must still configure the sql.ini (NT) or interfaces (UNIX) file to connect clients to the DirectConnect server. For instructions on editing the sql.ini or interfaces file, see the appropriate Open ClientConnect Installation Guide for your platform.





Copyright © 2005. Sybase Inc. All rights reserved. Editing service name redirection (snrf) tables

View this book as PDF