nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

\\IWSERVER - How do I get this within Templating or CGI

Tim__D

Sometimes I need to get a vpath like y:\default\main etc..

Sometimes the documentation calls for vpaths like \\iwserver\default\main etc..

How do I get \\iwserver within templating or cgi?

Find more posts tagged with

Comments

Migrateduser

Take whatever you do have and regex it into the format that you do want, potentially either appending or de-appending either //IWSERVER or whatever the value of iwmnt is. I think most everyone has some version of these two functions laying around

[PHP]
sub vpathToPath {
my($vpath) = @_;
my $iwmnt = TeamSite::Config::iwgetmount();
my $path = "$iwmnt$vpath";
return $path;
}

sub pathToVPath {
my($path) = @_;
my $iwmnt = TeamSite::Config::iwgetmount();
my ($vpath) = ($path =~ m#$iwmnt(.*)#;
return $vpath;
}

[/PHP]

NOTE: I don't usually bother to put the //IWSERVER in my vpaths. I just start with /default (or whatever the archive is). Technically, that's wrong, but there are some of the CLTs (at least there still were in 6.1, last time I checked) that didn't honor properly formed vpaths. Also, depending on what you're doing, slash direction may be important, in which case you'll want to use the tr operator to flip it to the right direction for your platform.

Tim__D

Take whatever you do have and regex it into the format that you do want, potentially either appending or de-appending either //IWSERVER or whatever the value of iwmnt is. I think most everyone has some version of these two functions laying around

[PHP]
sub vpathToPath {
my($vpath) = @_;
my $iwmnt = TeamSite::Config::iwgetmount();
my $path = "$iwmnt$vpath";
return $path;
}

sub pathToVPath {
my($path) = @_;
my $iwmnt = TeamSite::Config::iwgetmount();
my ($vpath) = ($path =~ m#$iwmnt(.*)#;
return $vpath;
}

[/PHP]

NOTE: I don't usually bother to put the //IWSERVER in my vpaths. I just start with /default (or whatever the archive is). Technically, that's wrong, but there are some of the CLTs (at least there still were in 6.1, last time I checked) that didn't honor properly formed vpaths. Also, depending on what you're doing, slash direction may be important, in which case you'll want to use the tr operator to flip it to the right direction for your platform.

For example the windows CLT doc for iwextattr.exe states

"Full path to a file. Uses the form:
[//server]/archive{[/branch]+}
/{EDITION,WORKAREA}/dirpath"

My interpretation of this is that //server should be //teamsite or other server name not Y: which is returned by TeamSite::Config::iwgetmount();

Where I see //server in the 6.5 documentation should this be the server name? Currently for this particular CLT I'm using a full vpath including the IFS drive Y:\defualt\main etc..

How do I get \\servername? or does this information not exist.

Adam Stoller

For example the windows CLT doc for iwextattr.exe states

"Full path to a file. Uses the form:
[//server]/archive{[/branch]+}
/{EDITION,WORKAREA}/dirpath"

My interpretation of this is that //server should be //teamsite or other server name not Y: which is returned by TeamSite::Config::iwgetmount();

Where I see //server in the 6.5 documentation should this be the server name? Currently for this particular CLT I'm using a full vpath including the IFS drive Y:\defualt\main etc..

How do I get \\servername? or does this information not exist.

A vpath is constructed of:

my $iwmnt = TeamSite::Config::iwgetmount(); ...sub vpathToPath { my $path = shift; if ($path !~ /^$iwmnt/){ $path = "$iwmnt$path"; } return $path; } sub pathToVPath { my $vpath = shift; $vpath =~ s|^$iwmnt||; return $vpath; }

nipper

Otherwise know as Vpath 101 from Professor Ghoti

I *really* wish there was a devnet FAQ because this certainly belongs. Of course someone (who is motivated and wants to take credit) could take this and make a Tech Lib article out of it.

Tim__D

Thanks for such a thorough explanation.

So in short some functions within Teamsite like iwextattr in the context of FormsPublisher although documented as requiring vpaths actually require a file path which is comprised of the server mount not the server name concatenated with a file vpath to form a file path.

y:.* = File path
/archive/main/.* = vpath

Also y: and //iwserver are one in the same on windows

Please confirm the above so I get it straight Smiley Wink

I think I was confused because the documentation states that this CLT requires a vpath but at the top states "The file or
directory is specified with a vpath, including the server name." Then in the example the code reads:

iwextattr -l Y:\default\main\dev\WORKAREA\andre\products\index.html

Not

iwextattr -l \\teamsite\default\main\dev\WORKAREA\andre\products\index.html

Adam Stoller

Let me try again:

) as they are portable across platforms and do not need escaping or special manipulation.Okay?

Migrateduser

iwextattr will take either a vpath or a filesystem path. I agree that it's confusing that the manual says it takes a vpath and then gives a filesystem path in the example.

Tim__D

Got it thanks a lot for your response. I am now developing on windows but will be moving to unix at some point and make it a habit to now =~ s/\\/\//g; all paths. Thanks for the tip. I'll look into how to get //iwserver or //servername using built-in perl or CLT functions if I ever need to. If I cant get the info then I'll come back to this thread.

Adam Stoller

iwextattr will take either a vpath or a filesystem path. I agree that it's confusing that the manual says it takes a vpath and then gives a filesystem path in the example.

Interesting - I think that's one of the old "hidden features" of CLTs like iwextattr which allow you to provide a file system path when it really expects a vpath.

The examples in the Unix CLT manuals always use vpaths.
The examples in the Windows CLT manuals have been using file system paths since TS 4.0 if not earlier (I just checked)

This should probably be filed as a documentation bug - despite the fact that iwextattr apparently can handle a file system path, it is supposed to require a vpath.