SAS® Integration Technologies: Administrator's Guide (LDAP Version)

More documents

Recommendations

Info

Setting Up a COM/DCOM Server: Introduction SAS can be configured to enable client access through Component Object Model (COM) interfaces. A COM connection can be established either locally (on the same machine) or remotely (on a different machine). For remote connections, the Distributed Component Object Model (DCOM) interface is used. Since COM launches the SAS object server, spawners are not used in the COM/DCOM server environment. However, you can (and should) use the Version 9 Object Manager (or Version 8 Workspace Manager) to obtain a DCOM server. The server definitions can be administered through LDAP or provided in a configuration file. Alternatively, you can imbed the server information in your application program. DCOM must be enabled on both the client machine and on the machine where the IOM server runs. The server machine requires additional configuration for DCOM object access and launch permissions. When to Use a COM/DCOM Server Configuration You can configure an object server as a COM/DCOM server if: • The object server will be installed on a Windows machine and will be accessed by Windows client applications running on remote machines. In this situation, the connection uses DCOM. • The object server will be installed on a Windows machine and will be accessed by Windows client applications running on the same machine. In this situation, the connection uses COM. If you use a Java client, you must use an IOM Bridge server configuration instead. Note: If your server or client machines run Windows XP Service Pack 2 or later, or Windows Server 2003 Service Pack 1 or later, you must change settings to enable DCOM functionality. See Configuring DCOM on Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1 for more information. COM/DCOM Setting Up a COM/DCOM Server: Introduction 42
Server and Client Requirements SAS supports Windows NT 4 (Server and Workstation), Windows 2000, Windows XP, and Windows 2003 as either client or server machines. Windows 98 is not supported. Server Requirements Install the following software on the server machine: • SAS 9.1 (or later) • SAS Integration Technologies • any other SAS products that your application will use COM/DCOM Server and Client Requirements 43
Page 1 and 2: SAS® 9.1.3 Integration Technologie
Page 3 and 4: SAS® Integration Technologies: Adm
Page 11 and 12: Setting up an LDAP Directory Server
Page 13 and 14: 10. You are asked whether you want
Page 17 and 18: sasDomainName eq, pres sasLogicalNa
Page 19 and 20: Adding Person Entries to the Direct
Page 21 and 22: Using the Integration Technologies
Page 23 and 24: saschannels sassubscribers Hardware
Page 25 and 26: If the value is set to none, the LD
Page 29 and 30: The command to start the SAS sessio
Page 31 and 32: Logical names All logical names ass
Page 33 and 34: Delete Help Server Wizard Set Acces
Page 35 and 36: Verifying IT Administrator Connecti
Page 37 and 38: Modifying Objects with IT Administr
Page 39 and 40: Searching for Objects Using IT Admi
Page 41 and 42: Reloading (Refreshing) IT Administr
Page 43 and 44: Choosing a Server Configuration Int
Page 47 and 48: Overview of Pooling A workspace poo
Page 49: Setting up Workspace Pooling You ca
Page 53 and 54: server and need metadata definition
Page 55 and 56: Creating the Metadata for a COM/DCO
Page 57 and 58: When you complete all of the steps
Page 59 and 60: ♦ Enter a unique name (sasServerc
Page 61 and 62: Configuration File Example: Minimal
Page 63 and 64: Enabling DCOM on the Server and the
Page 65 and 66: Configuring SAS for DCOM The COM Se
Page 67 and 68: Setting Default COM Security on Win
Page 75 and 76: Setting Default COM Security on Win
Page 79 and 80: Setting Permissions per Application
Page 81 and 82: ♦ SAS® Integration Technologies:
Page 83 and 84: left the Authentication Level on th
Page 89 and 90: where is the name of your machine
Page 95 and 96: Using the SAS Integration Technolog
Page 99 and 100: configuration file for a connection
Page 101 and 102:
SAS® Integration Technologies: Adm
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
3. Select the type of server to tes
Page 109 and 110:
• Make sure the permissions are c
Page 111 and 112:
Object Server Parameters The follow
Page 113 and 114:
Attributes for sasServer The sasSer
Page 115 and 116:
Page 117 and 118:
Attributes for sasLogicalNameInfo T
Page 119 and 120:
How an IOM Bridge Server Works In o
Page 121 and 122:
UNIX Note: When you install the spa
Page 123 and 124:
This completes the basic configurat
Page 125 and 126:
Spawner Requirements Hardware Requi
Page 127 and 128:
• Example UUID Generator IOM Brid
Page 129 and 130:
Using the IT Administrator Wizard t
Page 131 and 132:
◊ If you would like to add anothe
Page 133 and 134:
Using IT Administrator to Define a
Page 135 and 136:
Using IT Administrator to Define a
Page 137 and 138:
IOM Bridge Servers SAS® Integratio
Page 139 and 140:
the sasSpawner Attributes List will
Page 141 and 142:
Configuring a UUID Generator Curren
Page 143 and 144:
The following procedure explicitly
Page 145 and 146:
foundDashDash=1; fi args="$args$tmp
Page 147 and 148:
Invoking (Starting) the Spawner Aft
Page 149 and 150:
Starting the Spawner on Windows To
Page 151 and 152:
♦ ♦ −ldap_binddn "CN=John Doe
Page 153 and 154:
Method 1: Using SAS Setup 1. Log in
Page 155 and 156:
Spawner Invocation Options The foll
Page 157 and 158:
Note: If none of the spawner defini
Page 159 and 160:
Using the SAS Integration Technolog
Page 161 and 162:
Page 163 and 164:
configuration file for a connection
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Configuration File Examples: Server
Page 191 and 192:
Configuration File Example: Using L
Page 193 and 194:
Configuration File Examples: UUID G
Page 195 and 196:
Page 197 and 198:
Attributes for sasLogin A SAS login
Page 199 and 200:
Attributes for sasServer The sasSer
Page 201 and 202:
Page 203 and 204:
Object Server Parameters The follow
Page 205 and 206:
Server Startup Command You can spec
Page 207 and 208:
Attributes for sasSpawner The sasSp
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Creating a Stored Process Path A st
Page 215 and 216:
7. List the possible values for the
Page 217 and 218:
2. are discussed separately and in
Page 219 and 220:
6. After you define the subscribers
Page 221 and 222:
7. You cannot deliver information o
Page 223 and 224:
Creating Subscribers The publicatio
Page 225 and 226:
Creating Subscriptions When you ass
Page 227 and 228:
Entry Filters Publishers send infor
Page 229 and 230:
Creating Overrides An override is c
Page 231 and 232:
Creating a Library Data Source A li
Page 233 and 234:
Creating a Table Data Source A tabl
Page 235 and 236:
Adding Person Entries to the Direct
Page 237 and 238:
Page 239 and 240:
This example allows access to two g
Page 241 and 242:
Setting Access Permissions for an O
Page 243 and 244:
Specifying Bind Rules The bind rule
Page 245 and 246:
e before, after, or equal to the ti
Page 247 and 248:
Page 249 and 250:
Cn=sasArchivePaths,sascomponent=Arc
Page 251 and 252:
Page 253 and 254:
Page 255:
Your Turn If you have comments or s
show all

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?