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

More documents

Recommendations

Info

Deleting Objects with IT Administrator Note: Version 9 does not support dependent spawners. If you are using Version 9, do not configure a dependent spawner. Deleting an object (for example, a table) removes it from the LDAP server. Once an object has been deleted from the server, there is no way to restore it. You cannot delete any of the following nodes: • Publish Framework ♦ Publish Subscribe root ♦ Channels ♦ Subscribers • SAS Servers ♦ Dependent Spawners ♦ SAS Logins ♦ Servers ♦ Spawners • SAS Archiving ♦ Archive Paths • Applications ♦ Stored Process Paths • SAS Data Sources ♦ Libraries ♦ Tables Some channels may appear as folders because they contain overrides. To delete channels that contain subscription overrides, you must first delete all the overrides. Subscription overrides may be deleted by selecting them and clicking the Delete button. Deleting a subscriber's override does not delete the subscriber. See Overrides for more information. To delete an object from the LDAP directory: 1. Open IT Administrator. 2. In the manager bar, select the administration area in which you would like to delete an object: Publish Framework, SAS Configuration, SAS Archiving, Applications, or SAS Data Sources. 3. In the tree view, find the folder for the type of object you would like to delete. Then click the plus sign to open the folder. (For example, to delete a table object, you would open the Tables folder under SAS Data Sources.) 4. Select the object that you wish to delete. The object's current properties will be displayed in the property view in the right portion of the window. 5. Select the Delete icon ( ) on the toolbar; or select File Delete from the menu bar. 6. Select OK in the confirmation dialog box. The item is deleted. Getting Started Deleting Objects with IT Administrator 30
Searching for Objects Using IT Administrator You can use the search tool in Integration Technologies Administrator to locate specific objects in the LDAP directory that meet your search criteria. You can search for the following types of objects: Note: Version 9 does not support dependent spawners. If you are using Version 9, do not configure a dependent spawner. • Channels • Subscribers • Servers • Spawners • Dependent spawners • SAS logins • Logical names • Archives • Archive paths • Stored processes • Stored process paths • Tables • Columns • Libraries The search tool consists of a text field in which you enter words to search for, and three tabs to specify the conditions of the search. To perform a search: 1. Select the Search button ( ) on the toolbar; or select Edit Search from the menu bar. 2. In the Search For field, enter one or more words. By default, multiple words are interpreted as a collection of separate words. You can use the Advanced tab, as described below, to specify that multiple words are to be interpreted as a phrase. Searching is not case sensitive. 3. On the Search In tab, select the administration area in which you want to search (Publish, Server, Archive, Applications, or Data Sources). You can search in only one administration area at a time. Then select the types of objects that you want to search for. If you search across multiple object types (for example, servers and spawners), the search results will be displayed together in a single list. 4. On the For Attributes tab, select the properties for the search tool to examine. By default, the search tool searches in the Name field. 5. On the Advanced tab, select the match criteria. The default match criterion is "Contains one of the words". The match criteria are explained in the following table. Match criteria Contains one of the words Contains the phrase Explanation Finds objects in which at least one of the fields specified in the For Attributes tab contains at least one of the words specified in the Search For field. Finds objects in which at least one of the fields specified in the For Attributes tab contains the entire phrase specified in the Search For field. Searching for Objects Using IT Administrator 31
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: Modifying Objects with IT Administr
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 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 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 91 and 92:
SAS® Integration Technologies: Adm
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:
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)

Create successful ePaper yourself

Delete template?

Save as template?