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

More documents

Recommendations

Info

Important: For some SAS 9.1 hosts, IOM servers process a SAS autoexec file implicitly if the file is stored in the default location. This might cause compatibility issues for existing configurations because IOM servers did not process autoexec files in previous versions of SAS. You can suppress this behavior by specifying −noautoexec in the server command. For more information about the −AUTOEXEC system option, see the SAS documentation for your operating environment. • Logging Options (optional). To diagnose server problems, specify the −log and −logparm logging options on the server command line. You specify the logging options in the Command field or Object Server Parameters field of the server definition. For details about object server parameters, see Object Server Parameters. When you specify the logging options, you can also configure the server to create a different log for each process, or switch logs during execution. The following command (specified in the Command field creates a unique log file (in the server user's home directory) for each instance of this server definition. C:\Program Files\SAS\SAS 9.1\sas.exe −log "test%v.log" −logparm "rollover=session" For example, when the spawner starts the first server, a log named test1.log is created; when the spawner starts the second server, a log named test2.log is created. For information about system logging options, see SAS Language Reference: Dictionary. Note: Specifying logging options can cause performance degradation in your server; therefore, you should only specify logging options to diagnose problems with your server connections. Note: If you specify a log destination in the configuration metadata rather than the startup command, you might miss some messages that are generated before the log destination is set. IOM Bridge Servers SAS® Integration Technologies: Administrator's Guide (LDAP Version) Server Startup Command 198
Attributes for sasSpawner The sasSpawner object class contains information for an instance of a SAS spawner. The sasSpawner object class is defined using the attributes listed in the following table. For each option, the table shows: • The name that identifies the attribute on the LDAP server (or in the configuration file). Under each attributes name, the table shows the corresponding tab and field name in the IT Administrator application. • "Required" or "Optional" to indicate whether the attribute is required. • The type of server configuration for which the attribute is used. Note: Spawners are used only in IOM Bridge configurations. Therefore, IOM Bridge is listed as the server type for each option. • A definition of the attribute. Note: The following attributes which appear in the IT Administrator interface are not used in Version 9 of SAS Integration Technologies • sasEncryptionModulesPath • sasMasterPort • sasMasterService • sasLUName If you are using Version 9, do not use these attributes for your configuration. For step−by−step instructions on defining the metadata for a spawner, refer to Using the IT Administrator Wizard to Define a Server and Spawner or Using IT Administrator to Define a Spawner. If you are not using an LDAP server, you can use a configuration file to define a spawner. For instructions, see Using a Configuration File to Define the Metadata. Attribute Name description In IT Administrator:: Description objectClass In IT Administrator: N/A sasDomainName In IT Administrator: Connections Domain Required/ Optional Optional Required Optional sasSpawner Attribute Definitions Server Type IOM Bridge IOM Bridge IOM Bridge Definition Text to summarize why this object definition exists. This attribute is not used by the spawner. The object class identifier. For sasSpawner objects, this is always sasSpawner. If you use IT Administrator, this identifier is assigned automatically. The security domain in which the sasSpawner definition participates. The spawner definition must have the same domain name as the server with which it connects. The spawner uses the domain name, along with the machine name and logical name, to determine which server(s) it services. The lack of a domain is considered a domain; therefore, if the spawner definition has no domain name, it will be associated only with servers that have no domain name. Attributes for sasSpawner 199
Page 1 and 2:
SAS® 9.1.3 Integration Technologie
Page 3 and 4:
SAS® Integration Technologies: Adm
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Setting up an LDAP Directory Server
Page 13 and 14:
10. You are asked whether you want
Page 15 and 16:
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 27 and 28:
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 45 and 46:
Page 47 and 48:
Overview of Pooling A workspace poo
Page 49 and 50:
Setting up Workspace Pooling You ca
Page 51 and 52:
Server and Client Requirements SAS
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 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Setting Default COM Security on Win
Page 77 and 78:
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 85 and 86:
Page 87 and 88:
Page 89 and 90:
where is the name of your machine
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Using the SAS Integration Technolog
Page 97 and 98:
Page 99 and 100:
configuration file for a connection
Page 101 and 102:
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: SAS® Integration Technologies: Adm
Page 163 and 164: configuration file for a connection
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 197 and 198: Attributes for sasLogin A SAS login
Page 199 and 200: Attributes for sasServer The sasSer
Page 203 and 204: Object Server Parameters The follow
Page 205: Server Startup Command You can spec
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 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 249 and 250: Cn=sasArchivePaths,sascomponent=Arc
Page 255: Your Turn If you have comments or s
show all

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

Create successful ePaper yourself

Delete template?

Save as template?