Hi
I have to access a path that is in a different server than the OutSystems. We have this path mapped in OutSystems Server as the J: unit.
We also have a service user that has access to the OutSystems server and the mapping was made using this user.
In the FileSystem I’m passing this username, domain and password.
But I don’t know how to pass the correctly path to point to the mapping that was made.
Hi Julia,
If, on the OutSystems front-end server (the one where IIS runs), there's a network drive mapped as drive J, then you can access it the normal way you would in a Windows Explorer, e.g. "J:\somefolder\myfolder". Of course, instead of the J-drive reference, you could also use the full server path (e.g. "\\myserver\somefolder\myfolder").
That said, the service user must have access (at leat read access) to the server that the J drive points to, not just to the OutSystems front-end server, or access will be denied.
Hi Kilian,
Thank you for your answer! As "my server" you mean the external server that I need to access, right? Let's say that the external server that I need to access is "\\xx.x.xx.xxx\outsystem$" if I have this network drive mapped in my Outsystems server, I just need to pass the external server and folder as the path parameter, and if I have the correct permissions, it should work?
Yes indeed.
Ok! And since it’s a NAS server it can be accessed by the File System?
That's all Windows network configuration, and has nothing to do with OutSystems. If you can access (or at least the user that's used for the impersonation / Run As) the file share it's ok.
Julia,
check this other discussion:
https://www.outsystems.com/forums/discussion/64953/filesystem-is-filesystem-working-in-outsystems-cloud-to-on-prem-file-share-us/
Hi Diogo,
Why should the OP "check this other discussion"? How is it going to help her with her problem? Is what is described in that topic equal to or very similar to her problem?
Posting links to other topics is fine if they're very on-topic, but otherwise please don't do that!