User manual SAS ENTERPRISEGUIDE 4.2 ADMINISTERING

[. . . ] Administering SAS Enterprise Guide 4. 2 ® ® The correct bibliographic citation for this manual is as follows: SAS Institute Inc. Administering SAS ® Enterprise Guide ® 4. 2. Administering SAS® Enterprise Guide® 4. 2 Copyright © 2009, SAS Institute Inc. , Cary, NC, USA All rights reserved. Produced in the United States of America. [. . . ] If the check box is not selected, then all tables in the library will appear (even if you deny ReadMetadata permission for a table or the table is not registered in the metadata repository). Permissions are enforced if a user tries to open a restricted table. In this mode, the library is not read-only. This option is equivalent to the METAOUT=DATA option. 3 On page 4 of the wizard, you must specify the engine type for the library (file system, database system, or WebDAV) and specific information for the engine type that you select. If you are defining a file system or database system library, you must choose an engine. Select the SAS engine with which the data was created. For more information about engines, see the SAS documentation for your operating environment. See also the chapter that corresponds to your database management system in SAS/ACCESS for Relational Databases: Reference. 3 Also on page 4 of the wizard, you might have to specify the physical path where the library resides on the server. Depending on the value of the Engine Type field, Path might not be present. You can use the following wildcards in the Path field: <userid> substitutes a Windows user ID. For example, if a user logs on as ebeacon, then \\librarypath\<userid> becomes \\librarypath\ebeacon. Metadata Library Engine Managing Metadata Objects 4 Assigning Libraries 23 <sample> substitutes the SAS Enterprise Guide sample directory. For example, if you installed using the default directories, <sample>\data becomes C:\Program Files\SAS\Enterprise Guide 3. 0\Sample\data. If, however, another user installed in D:\EC, then <sample>\data becomes D:\EC\Sample\data. substitutes the server logon user ID. <serveruser> <serverpassword> substitutes the server logon password. <libraryuser> substitutes the library logon user ID. <librarypassword> substitutes the library logon password. Note: These wildcards might not work with client applications other than SAS Enterprise Guide and the SAS Add-In for Microsoft Office. 4 3 On page 5 of the wizard, you can specify library options and values. If wildcards are valid in the Path field, then you can also use them in the Options field. Avoid using prompting options such as DBPROMPT=YES. For additional options, see the chapter that corresponds to your database management system in SAS/ACCESS for Relational Databases: Reference. 3 On page 6 of the wizard, you must select the folder to which the library belongs. [. . . ] A SAS Metadata Server is an example. repository a location in which data, metadata, or programs are stored, organized, and maintained, and which is accessible to users either directly or through a network. See also metadata repository, SAS Metadata Repository. role a set of capabilities. In some applications, certain actions are available only to users or groups that have a particular role. SAS Metadata Repository a repository that is used by the SAS Metadata Server to store and retrieve metadata. See also SAS Metadata Server. SAS Metadata Server a multi-user server that enables users to read metadata from or write metadata to one or more SAS Metadata Repositories. [. . . ]