New Content Store - Windows Explorer Path

We have just purchased a new content store and we are working through our code to make the appropriate changes to support the content that will move to this new directory.

We had initially begun sharing this space out as \\tshost\newstore. Support is indicating that the only supported model is \\tshost\iwserver\newstore. I could certainly write something that shares this location out upon reboot, my concern is that TS would not be fully initiated. Does anyone have experience with this dilemma?

Find more posts tagged with

Comments

Rick Poulin

What is your concern with this? The \\server\IWServer share will be available as fast as \\server\newstore. They both depend on iwserver to be running (as does the Y drive).

droog

Our custom code is tailored to point to \\server\store. Autonomy/IWOV uses this convention the default store, just looking for a similar approach with a second store. Adding in the IWServer piece will force us to change a lot of code.

Rick Poulin

I find it surprising that you have that much code relying on a network share.. but presumably you're already going through your entire codebase to find \\server\default and replacing it with \\server\newstore, so why not take the extra second to make it \\server\IWServer\newstore ? Yes, you could configure your own share but why bother venturing into unsupportedland when, as you've stated, you're already going through your code to update it.

Adam Stoller

Our custom code is tailored to point to \\server\store. Autonomy/IWOV uses this convention the default store, just looking for a similar approach with a second store. Adding in the IWServer piece will force us to change a lot of code.

Are you sure you're not confusing fully-qualified vpaths with network shares / mount points?

A fully-qualified vpath would be something like \\server\store\main\... - where this path only really has meaning when being evaluated on the actual TS server.

A network share would be something like \\server\\IWServer\store\main\... where "IWServer" is a named, shared, mount point on "server" that is accessible from remote machines (including client desktops).