2. Define the access service as a remote server

StepsTo define the access service as a remote procedure

  1. Enter each access service name in the ASE SYSSERVERS table:

    sp_addserver service_name service_class
    

    where:

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

    • service_class must be direct_connect.

    The access service name is case sensitive and must match the name you used to define connectivity between ASE and the access service.

  2. Verify that the 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 ASE.

  3. Use the sp_addexternlogin system procedure to add an external login password to allow access to the 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 access service that 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 access service after following all the previous steps.

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

RPC issues

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

To support ASE RPC events, perform either one of these procedures: