/iwmnt vs /.iwmnt

We are having an issue with the /iwmnt vs. /.iwmnt changes in 5.5.2. Our workflow cannot find the DCR when it is pointing to /.iwmnt, even thought the path to the file exists. The DatacaptureServlet is throwing an error:
Templating Error Page
Unable to find DCR : /.iwmnt/default/main/AGe-NET/WORKAREA/IES/templatedata/AGe-NET/Metadata/data/mm_tomorrow20031221437.datarecord

Can anyone help???? Anyone have any ideas? Is the problem within the servlet?

Find more posts tagged with

Comments

james1

What do you mean when you say that your "workflow cannot find the DCR"? Workflows do not natively look for DCR's. Are you using a cgitask to launch the DatacaptureServlet in edit mode?

What happens if you use "/iwmnt/default/..." or just "/default/..." instead of "/.iwmnt/default/..."?

-- James

--
James H Koh
Interwoven Engineering

Migrateduser

That little dot is a real pain in the ****. One of the negative things that came out of 5.5.2.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

tvaughan

I second Smitty's opinion about the pain-in-the-**** dot.

Basically, you gotta go through all your scripts that used to reference "/iwmnt" and make sure that the CGI parameters / IW variables you're getting are still producing "/iwmnt" and not "/.iwmnt"

For example, if you have a custom CGI and you used to say "$cgi->{form}{"directory_path"}" and expect to get back "/iwmnt/blah/blah" you will be disappointed with version 5.5 . . . .the "directory_path" now returns you "/.iwmnt/blah/blah"

Of course, if you sense bitterness, it is mostly because I was too retarded to think ahead and realize that "/default" is a better path to use if one must have absolute paths.

Tom

lnothaker

This particular problem ended up being related to using the directory path instead of the vpath with the iwextattr CLT. When I changed the call to pass it the vpath, iwextattr worked perfectly and the DCR was opened. The problem is, is that, how many other places are we using the directory path instead of the vpath with the other CLTs. Does anyone know if there is ever an instance when we want to use the path to /.iwmnt/default/main/yadayada? Would it be easier to use a regex at the very beginning of workflow and replace /.iwmnt with /iwmnt? Or will that break other things?

Thanks for all the replies!

tvaughan

My rule-of-thumb is to pretend as though the "/.iwmnt" doesn't even exist. It's used primarily as a cache for the IW web server (I think). I'm pretty sure you can't make any solid bets on the availability or currentness of stuff you find in /.iwmnt, but maybe some IW folks would like to chime in here.

Anyway, I can't recall all the changes I had to make to accomodate the 5.5 upgrade. I remember that diagnosing the problem was 1/2 the battle. Once you realize the environment has changed on you, isolating and fixing the problems becomes easier. In my case, I just slapped this code all over the place:

} elsif($directory_path =~ /.iwmnt(.*)/) {
$directory_path = "/iwmnt" . $1;

which is a pretty ****-poor continuation of the original problem, but I was in a hurry to get the upgrade done. . .

Tom

Migrateduser

What would be really nice, but one of my pipe dreams nonetheless, would be if I didn't have to ever care about what the **** a vpath or a full path was - if every stinking situation just used the same format. Then I wouldn't ever concern myself with dots and other such nonsense. In a perfect world...

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

There are specific times when you will want to use a direct file path over a vpath. For instance. pretty much any time you are passing a path to an interwoven command line tool you want to use vpaths (look at the -h output for the individual clt to find out for sure). There are some clt's that take a file path over a vpath (iwpt_compile.ipl wants file paths over vpaths).

An instance of where you would want to use file path would be if you want to read a file in a script/cgi. you would use the /.iwmnt path as opposed to /iwmnt. This is because you want to make your read happens through the non-cached nfs mount. You might ask, why not just use a vpath here as well? The first problem you may run into is with multi-store. While a link is made from /default to /iwmnt/default, the same sort of link for other stores is not created automatically (and therefore file paths starting with /somestorename may not exist). The only reason why /default works as a file path in most cases is because of the /default link.

tvaughan

You're dreaming yourself out of a job, Dave.

If it weren't for people like you and I to worry about vpaths and dots, how would the world continue to turn???

Tom

Migrateduser

We should start a support group...

Hi my name is Dave and I am a workflowaholic....

<from the croud: "HI DAVE!!!" >

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com