Enterprise Guide shows a file folder under the SASApp (or SASMain) server in the EG Server list pane, which enables users to save their EG projects on the server.
By default this points to the users personal folder on the server (based upon their login name) and therefore other users can’t see any projects that are saved there.
Often you want to be able to see these projects easily, when you need to re-run one or if the user who created is away (yes Sam I am talking about you!).
On the SAS support site there is a SAS Note that outlines how to change this setting.
Basically you edit the definition for the workspace server, but the options are a little hard to find:
- In SAS Management Console, navigate to this location:
- Server Manager > SASMain – Logical Workspace Server > SASMain – Workspac Server.
- Right-click and select Properties.
- Select Options tab.
- Select Advance Options button.
- Select File Navigation tab.
- Select Specify Path and field, type the path.
- I.e C:\EGProjects
- Select OK and OK.
Then create separate folders under this location to enable the EG Projects to be stored by subject area.
Also don’t forget to change the file system security on these fodlers to allow users to read /write to it.
Of course the other option is to save the EG Projects in the Metadat tree / Webdav.
The benefit of this is that you are supposedly able to do impact analysis of these projects. (Has anybody tried this?)
I haven’t had a lot of luck getting the Webdav storage for EG working consistantly (and I like to be able to see the EG Projects in the file system for some reason as well)
Shane,
Thanks for this post. Many customers depend on the ability to store project files on their remote SAS server machine. It helps with collaboration as well as with content backup, migration, etc. As you mention, other than the tweak to the server definition to allow for the file navigation, there is no special setup required.
When you save a project into webDAV storage (into the SAS Folders tree), EG creates a metadata entry for the project. As part of that operation, it registers associations with other metadata items that are used within the project, such as information maps, stored processes, and metadata-controlled data libraries. This operation requires a configured content server that is defined in metadata.
The impact analysis feature is part of Data Integration Studio, where you can examine a change you are going to make to a table (for example) and see what that might affect downstream. When an EG project is registered in metadata like this, that project will show up in the impact analysis report.
Chris
Great article and input as well.
Two questions:
1. Is there a way to set as default path certain location created in metadata (/BIP Manager/Shared/region/dept for example) exclusively for EG stored Process Users who will only access STP via EG) by an admin? When EG is deployed the default path is the value set by admin.
2. If STP will only be accesses by EG, the folder for saving STP should still be under /BI Manager/BIP Tree or could be under any folder under BI manager?
Hi Shoin
1) Not that I know of. Unlike WRS, EG and AMO don’t have the ability to define a starting path for content.
So that means users will have to get use to clicking down the folder structure each time.
My preference is to place all content (WRS Report, Data Explorations, STP etc) in a folder by subject area rather than by content type, as the relevant SAS tool will filter the objects by its expected content type.
2) It can be stored under any folder the user has security to
So you could create a root folder called Stored Processes so the users don;t have to click to far down the folder structure to find the content.
Make sure you update your metadata security policies though, so you don’t introduce any security holes.