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 Copyright © 2009, SAS Institute Inc. , Cary, NC, USA All rights reserved. For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. [. . . ] 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). 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. 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. 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. If you do not select a folder, the library is automatically stored in the Shared Data folder. 3 Page 7 of the server lets you test the library definition on each server. If the library name or libref is not unique on all servers, the conflict is listed in the Status column. After you complete the wizard, the library is created and then displayed in the viewer under the client libraries for the specified servers. Creating an Output Library By default, SAS Enterprise Guide stores output data in the Sasuser, Work, or Egtask library, or a user-created output library on the SAS server. You can select Tools I Options I Output Library to change the default output library. [. . . ] The metadata engine retrieves information about a target SAS data library from metadata objects in a specified metadata repository. 54 Glossary metadata repository a collection of related metadata objects, such as the metadata for a set of tables and columns that are maintained by an application. A SAS Metadata Repository is an example. metadata server a server that provides metadata management services to one or more client applications. 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. [. . . ]