01-16-2018 03:19 AM
the quick answer is yes, you can, as long as:
- each Workspace server is on a different SAS application server (SASApps)
- the user has access/visibility on each SASApp and Workspace server.
When you create a new project, SAS Enterprise Miner will prompt you on what Workspace server you would like to work with along that project.
01-16-2018 03:55 AM
Thanks @JuanS_OCS. We have one Application server and both workspaces has been configured on it.
Somehow there is no way to access to the datasources on the other workspace?
01-16-2018 04:02 AM
I am not sure if there is a way for such kind of deployment. You can always ask SAS Technical Support, since they will give you the official statement, but I honestly would not investigate further on that direction.
It is a best practice to deploy only one IOM server (Worskpace server, StoreProcess server or PooledWorkspace server) per Application Server (SASApp), because when you connect to a SASApp, depending on the service requested, SAS Metadata will redirect automatically to one of those. If there is more than 1, the metadata does not have a way, initially, to know how to redirect to an alternative.
On one SASApp you can define more than one Batch server (because it is not an IOM server), but no more than 1 IOM server (per type).
If you need to have more than 1 IOM server of the same type (as Workspace server) you need additional SASApps.
01-16-2018 10:17 AM
Agreed with @JuanS_OCS that you can only define one "Logical" IOM server type (Workspace, Stored Process, Pooled Workspace) per server context (SASApp). However, you can define multiple server components within each Logical server definition. Based on what you have said, I'm guessing you have two Workspace Server components defined within the single Logical Workspace definition - is that correct? This type of configuration is generally performed to configure load balancing across multiple physical SAS servers and would require a shared file system between the two servers in order to have a shared location for data and program files. If you don't have a shared file system for your SAS servers, then you should define an additional server context (e.g. SASApp2) for the second Workspace Server component. You can control access to each server either through metadata permissions (by granting ReadMetadata access appropriately), or you can instruct your SAS users to select one server context vs. the other from within their SAS client application based on the type of work they are doing, or some other use case you may have.