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

More documents

Recommendations

Info

SAS® Integration Technologies: Administrator's Guide (LDAP Version) sas−RecycleActivationLimit In IT Administrator: Workspace Pool Recycle Activation Limit Optional COM/DCOM, IOM Bridge If you are using connection pooling, the number of times a server is used before the process is disposed of and a new process is used in pooling. A value of 0 indicates that the process will have no limit. sasRequiredEncryptionLevel In IT Administrator: Encryption Encrypt Optional COM/DCOM, IOM Bridge The level of encryption to be used between the client and the object server. None means no encryption is performed; Credentials means that only user credentials (id and password) are encrypted; and Everything means that all communications between the client and server are encrypted. sasServercn In IT Administrator: Name Required COM/DCOM, IOM Bridge The unique name for this sasServer object. sas−ServerRunForever In IT Administrator: Workspace Pool Server Process Shutdown Leave running when idle Optional COM/DCOM, IOM Bridge If you are using connection pooling, specifies that an idle server should always remain running. If the value of this attribute is true, the server always remains running. If the value is false, the idle server runs for the length of time specified in the sasServerShutdownAfter attribute. sas−ServerShutdownAfter In IT Administrator:: Workspace Pool Server Process Shutdown Minute until idle shutdown Optional COM/DCOM, IOM Bridge If you are using connection pooling, the number of minutes after which an idle server should be shut down. The value must be between 0 and 1440. The default value is 3. This attribute is ignored if the value of sasServerRunForever is true. sasService In IT Administrator: Connections IOM Bridge Service Optional IOM Bridge The service in which to connect to this object server. If you specify a value for both sasService and sasPort, then the value for sasService will be ignored. If neither sasPort nor sasService is specified, the spawner will attempt to use the service name sasobjspawn as the sasService. If sasobjspawn has been used already, the spawner will remove this sasService definition from its list. Note: If the server will have Java clients, specify a sasPort instead of a sasService. IOM Bridge Servers Attributes for sasServer 194
Object Server Parameters The following table lists the object server parameters that you can use to override or add to the object server parameters that the spawner uses to launch SAS. Object Server Parameter CLIENTENCRYPTIONLEVEL Alias: CEL Object Server Parameters Value none credentials everything Connection Type IOM Bridge JNLSTRMAX Numeric value IOM Bridge COM/DCOM LOGFILE Alias: LOG PORT PROTOCOL Path in which to create the IOM server trace log. TCP/IP port number bridge com (com,bridge) IOM Bridge COM/DCOM IOM Bridge IOM Bridge COM/DCOM SECURITY | NOSECURITY N/A IOM Bridge COM/DCOM Definition Specifies the degree of encryption to use when making outbound calls. This option is used only by the bridge protocol engine. Specifies the maximum length of string printed in the IOM server journal. This option can be used to adjust the amount of material included in an IOM trace. A value greater than 500 is recommended. Provides an alternative to the SAS Log for IOM server trace output. Note: The user who starts the server must have execute and write permissions for the log destination path. Specifies the value for the bridge protocol engine to use as the port in which to start listening for client connections. Specifies the protocol engine(s) to launch in server mode. Server mode indicates that the protocol engine(s) will listen for client connections. By default, Windows servers use the COM protocol engine and all other servers use the Bridge protocol engine.] It you specify (com, bridge) a multiuser server can simultaneously support clients using different protocols. Specifies whether client authorization is required. When security is enabled, the bridge protocol engine requires a username and password; the COM protocol engine is integrated with the single−signon security of the Windows networking environment. Authorization decisions are controlled by the server application. If "nosecurity" is Object Server Parameters 195
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 201: SAS® Integration Technologies: Adm
Page 205 and 206: Server Startup Command You can spec
Page 207 and 208: Attributes for sasSpawner The sasSp
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 253 and 254:
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?