%META:TOPICPARENT{name="GlossaryEntriesD"}% ==Glossary of Technical Terms== [[GlossaryEntriesA|A]] [[GlossaryEntriesB|B]] [[GlossaryEntriesC|C]] [[GlossaryEntriesD|D]] [[GlossaryEntriesE|E]] [[GlossaryEntriesF|F]] [[GlossaryEntriesG|G]] [[GlossaryEntriesH|H]] [[GlossaryEntriesI|I]] [[GlossaryEntriesJ|J]] [[GlossaryEntriesK|K]] [[GlossaryEntriesL|L]] [[GlossaryEntriesM|M]] [[GlossaryEntriesN|N]] [[GlossaryEntriesO|O]] [[GlossaryEntriesP|P]] [[GlossaryEntriesQ|Q]] [[GlossaryEntriesR|R]] [[GlossaryEntriesS|S]] [[GlossaryEntriesT|T]] [[GlossaryEntriesU|U]] [[GlossaryEntriesV|V]] [[GlossaryEntriesW|W]] [[GlossaryEntriesX|X]] [[GlossaryEntriesY|Y]] [[GlossaryEntriesZ|Z]] [[GlossaryEntriesSymbols|#]] ===Domain Alias=== Domain Aliases may be found in the [Domain Aliases] section of the OpenLink Session Rules Book. You will also find Domain Aliases in the Edit Domain Aliases portion of the Administrative Assistant. The standard Domain Alias is a shortened form of a value passed in a DSN's Domain Name or Server Type field. For instance, Oracle 8 {{{=}}} ora8. However, you may create regular expressions, which map many values onto one Domain Alias. For instance, the following rule maps Progress 90A and 90B connections together: ^Progress 90A$|^Progress 90B$ {{{=}}} pro90b This allows you to create a single Mapping Rule, which applies in a variety of cases. This promotes economical and flexible security. If you do not employ regular expressions, you will need to create one Mapping Rule per each Domain. See Also: Domain, Mapping Rules, Server Type, SVT