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

Setting Permissions per Application on Windows NT/2000

To grant permissions to users and groups specifically for accessing and launching the SAS server (instead of defining global permissions as shown in the previous section):

  1. From the Windows taskbar, click Start Run.

  2. Type dcomcnfg and click OK. The Distributed COM Configuration Properties window appears.

  3. Select the Applications tab:

    DCOMCNFG Applications Dialog

    This tab shows the AppID description for each DCOM server that can be run on your machine. (The AppID GUID is shown for servers that register without a description.)

  4. Locate the IOM server that you are configuring and select it. For example, if you want to set policies for the Workspace, select SAS.Workspace (SAS Version 9.1. The application listing differs depending on which version of SAS is installed. See AppIDs for Configuring DCOM to determine which AppID to look for.

  5. After you highlight the selection, click on the Properties button. The Properties dialog box for the server object appears.

  6. Select the Location tab.

    DCOMCNFG Location Dialog

  7. Check the default location setting. By default, the only option enabled is Run application on this computer, as shown in the illustration. No other options are required for SAS applications.

  8. Select the Identity tab.

    DCOMCNFG Identity Dialog

  9. Select the identity based on the type of server:

    • For multi-user servers (SAS Metadata Server, and the SAS System 9 OLAP server), select This user and specify the User, Password, and Confirm Password information.

      CAUTION: Support for the use of COM in the SAS Metadata Server is experimental in SAS 9.1. Do not use COM in the SAS Metadata Server in production jobs.

    • For SAS Workspace Servers, check the desired default identity setting. For maximum security, select the option The launching user.

    Note that some versions of Windows prevent servers with COM connections that are configured with the "This user" identity choice to be run from a command prompt. The recommended approach for multiuser servers is to install them as a Windows service, generally with "protocol=(com,bridge)" in order to support the maximum possible range of clients. See Choosing a Server Configuration for details.

  10. Select the Security tab.

    DCOMCNFG Security Dialog

  11. To use the system-wide default access permissions, select Use default access permissions, click Apply, and then continue with Step 12.

    To give IOM server application its own set of access permissions:

    1. Select Use custom access permissions and click the adjacent Edit button. The Registry Value Permission dialog box appears:

      Custom Access Permissions Dialog

    2. Select Add. The Add Users and Groups dialog box appears.

      Add Users and Groups dialog

    3. Use this dialog box to grant users and groups access to SAS through DCOM. You should also give access permission to System. (For field descriptions, refer to the Windows NT Help.) You can also identify users and groups that are denied access to SAS by changing the selection in Type of Access.

    4. When you are finished, click OK in the Add Users and Groups dialog box, and then click OK in the Registry Value Permissions dialog box.

  12. If you are configuring a Workspace server, which is launched by COM, you will also need to choose your launch permissions. It is recommended that they be the same as the access permissions; additionally, ensure that the System account has launch permissions.

    To use system-wide default launch permissions, select Use default launch permissions, click Apply, and then continue with Step 13.

    To give the IOM server application its own set of launch permissions:

    • On the Security tab, select Use custom launch permissions and click the adjacent Edit button. The Registry Value Permissions dialog box appears.

      Custom Launch Permissions Dialog

    • Select Add. The Add Users and Groups dialog box appears.

      Add Users and Groups Dialog

    • Use this dialog box to grant users and groups access to SAS through DCOM. It is recommended that you enter the same values that you entered for the Custom Access Permissions. You should also give launch permission to System. (For field descriptions, refer to the Windows NT or Windows 2000 Help.) When you are finished, click OK.

      Note: If you grant launch permissions for an application to specific users and groups, then you might affect those users who previously had permission to the application through default permissions.

  13. Click OK in each of the open dialog boxes to save your selections and exit the dcomcnfg utility.