Summary of Setup Steps (COM/DCOM Server)

Standalone Windows Development Machine

To set up a standalone Windows development machine, just install SAS Version 8, 8.1, or 8.2 (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. To use the object server in a Visual Basic environment, for example, you would reference the IOM type libraries from within your VB project (refer to Programming with Visual Basic) for details).

For more information about developing Windows client applications, see Windows Clients.

Separate Client and Server machine

To set up a DCOM server:

1. Install SAS Version 8, 8.1, or 8.2 (including Integration Technologies) on the server machine. Refer to the SAS documentation for the details of this procedure.

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

3. 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 Launch Policies.

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

5. 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:

   • If you are using an LDAP server, you can use IT Administrator to create the necessary metadata on the LDAP server. For details, see Using the IT Administrator Wizard to Define a COM/DCOM Server or Using IT Administrator to Define a COM/DCOM Server.

   • If you are not using an LDAP server, you must create a configuration file that contains the necessary metadata, and then install the configuration file on the server machine. For details, see Using a Configuration File to Define the Metadata (COM/DCOM).

6. On each client machine, install the IT software for Windows clients. For instructions, refer to Developing Windows Clients. If you are not using an LDAP server, you must also copy the configuration file (created in Step 2) 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.