2. Define the access service as a remote server

Enter each DirectConnect access service name in the Adaptive Server Enterprise SYSSERVERS table

1. Enter each DirectConnect access service name in the Adaptive Server Enterprise SYSSERVERS table

   sp_addserver service_name service_class
   

   where:

   • service_name is the name of the DirectConnect access service you want to set up as a remote server.

   • service_class must be direct_connect.

   The name is case sensitive and must match the name you used to define connectivity between Adaptive Server Enterprise and the DirectConnect access service.

2. Verify that the DirectConnect access service is successfully defined as a remote server:

   sp_helpserver server_name
   

   This command returns a result set with a list of the services defined to Adaptive Server.

3. Use the sp_addexternlogin system procedure to add an external login password to allow access to the DirectConnect access services.

4. Verify ASE/CIS connectivity using the ASE/CIS extension to Transaction-SQL connect to server_name. This is the same server name you created in a previous step using the sp_addserver system procedure. This command establishes a passthrough mode connection to the DirectConnect access service. The passthrough mode remains in effect until you issue a disconnect command.

5. Enable location transparency of remote data through remote object mapping:

   • Use sp_addobjectdef to define the storage locations of remote objects.

   • Use either create table or create existing table (as applicable) to map remote table schema to ASE/CIS.

6. Use select to perform joins across the DirectConnect access service after following all the previous steps.

For more information about the process plus instructions for configuring and tuning ASE/CIS, see the Component Integration Services Guide for Adaptive Server Enterprise.

RPC issues

When Adaptive Server issues an RPC to a DirectConnect access service, it attempts to connect using a service name identical to the Adaptive Server Enterprise identifier in the interfaces file (for UNIX) or the sql.ini file (for Windows).

To support Adaptive Server RPC events, perform either one of the following procedures:

• Define a service within the access service library using the same name as Adaptive Server.

• Set up service name redirection to redirect the Adaptive Server to the appropriate service.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF