SAS 9.1.3 Integration Technologies » Administrator's Guide (LDAP Version)


Setting up a COM/DCOM Server
Server and Client Requirements
Summary of Setup Steps
Metadata Overview
Creating the Metadata for a COM/DCOM Server
Using the IT Administrator Wizard
Using IT Administrator
Using a Configuration File
Configuration File Example: Minimal Configuration
Configuration File Example: Using Logical Names
Enabling DCOM on the Server and the Client
Configuring SAS for DCOM
Setting SAS Permissions on the Server
Global on Windows NT/2000
Per Application on Windows NT/2000
Global on Windows XP / Server 2003
Per Application on Windows XP / Server 2003
Configuring DCOM on Windows XP SP2 / Server 2003 SP1
Configuring COM/DCOM for Active Server Page Access
Accessing a Local COM Server from an Active Server Page
Accessing a DCOM Server from an Active Server Page
Administering the Server:
Using the IT Configuration Application
Troubleshooting
Reference Materials
AppIDs for Configuring DCOM
Object Server Parameters
Attributes for Servers
Attributes for Logical Names
COM/DCOM

Summary of Setup Steps (COM/DCOM Server)

Standalone Windows Development Machine

To set up a standalone Windows development machine, just install SAS Version 9 (including Integration Technologies) on the machine. On Windows, the SAS Integration Technologies Client is installed with base SAS software.

You can then develop your Windows client application as described in Developing Windows Clients in the Developer's Guide. To use the object server in a Visual Basic environment, for example, you would reference the IOM type libraries from within your Visual Basic project (refer to Programming with Visual Basic) for details).

For more information about developing Windows client applications, see Windows Clients in the Developer's Guide.

Separate Client and Server machine

To set up a the server machine:

  1. Install SAS Version 9 (including Integration Technologies) on the server machine. Refer to the SAS documentation for the details of this procedure.

    Note: If you are using the Integration Technologies client with 64-bit SAS, extra setup steps are required for IOM COM servers on 64-bit Windows. For details, see the SAS installation documentation.

  2. Enable DCOM on the server machine. For details, see Enabling DCOM on the Server and on the Client.

  3. Edit your SAS CONFIG file (SASV9.CFG) for use with DCOM. For details, see Configuring SAS for DCOM.

  4. Set SAS launch policies on the server. You can set global policies that affect all COM-enabled applications, or set application policies for individual to grant permissions to users and groups specifically for accessing and launching the object server. For details, see Setting SAS Permissions.

  5. Before attempting to run a COM/DCOM application, test the client-server connection by using the tips provided in Troubleshooting the DCOM Connection.

  6. If your applications need to access metadata that describes your COM/DCOM server configuration, you must create the necessary definitions for server objects and (optionally) logical name objects. For details, see Creating the Metadata for a COM/DCOM Server. The method for creating the metadata depends on whether you are using an LDAP server for your metadata repository:

To set up the client machines:

  1. On each client machine, enable DCOM. For details, see Enabling DCOM on the Server and on the Client.
  2. On each client machine, install the client software, either as part of the installation of a pre-written application or as a separate installation of a custom application. For details about installing custom applications, refer to Developing Windows Clients in the Developer's Guide. If you are not using an LDAP server and need metadata definitions, you may also need to copy the configuration file (created in Step 5) to the client machine.

This completes the basic configuration steps that are necessary to do client development on a Windows platform. For information about developing applications that access COM/DCOM servers, refer to Developing Windows Clients in the Developer's Guide.