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

Creating the Metadata for a COM/DCOM Server

If your applications need to access metadata from the LDAP server or from a configuration file, you must create the metadata that describes your COM/DCOM server configuration. If you require metadata, use the appropriate method depending on whether you use an LDAP server or a configuration file to store your metadata:

  • If you are using an LDAP server:

  • If you are not using an LDAP server, you can create and install configuration files that contain the object definitions. For instructions, see Using a Configuration File to Define the Metadata.

    Note: If your configuration requires more than one or two servers, or if multiple clients will be using the servers, we strongly recommend the use of LDAP as a central metadata repository. The use of LDAP also gives you the ability to use access control lists to control access to the servers in your enterprise.