Summary of Setup Steps (COM/DCOM)

Standalone Windows Development Machine

To set up a standalone Windows development machine, simply install SAS 9.1 (including SAS 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 SAS Integration Technologies: Developer's Guide. To use the 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 in the SAS Integration Technologies: Developer's Guide) for details).

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

Separate Client and Server Machine

To set up the server machine:

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

   Note: If you are using the SAS Integration Technologies client with 64-bit SAS, extra setup steps are required for IOM servers with a COM connection 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 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 individuals to grant permissions to users and groups specifically for accessing and launching the server. For details, see Setting SAS Permissions on the Server.

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

6. If your applications need to access metadata that describes your COM/DCOM server configuration, you must create the necessary metadata, including definitions for servers. You can use SAS Management Console to create the necessary metadata on the SAS Metadata Server.

   Note: COM-based workspace servers do not necessarily require a definition within the SAS Metadata Server. The most common reason for defining a COM-based workspace server in metadata would be to enable clients to connect by logical server name, without needing to know the actual network location. Pooling parameters also require a metadata definition. Another possible reason to define a workspace server in metadata is so that you can use the METAAUTOINIT option to enable metadata-based LIBNAME preassignments or OBJECTSERVERPARMs.

   OLAP servers always require a definition within the SAS Metadata Server.

   For planning details, see Planning Your Server Configuration Metadata.

   For details about using SAS Management Console to create the metadata, see Creating the Metadata Using SAS Management Console.

7. Start the server. For details, see Starting Servers.

To set up the client machines:

1. On each client machine, enable DCOM. For details, see Enabling DCOM on the Server and 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 SAS Integration Technologies: Developer's Guide.

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 SAS Integration Technologies: Developer's Guide.