iwsync a.d workareas problem

I have definetly misunderstood or missed something here but -

I have a branch that has several workareas with several DCT/DCR's in each. (Note the same DCT/DCR can occur in several workareas).

I have tested all my DCT/DCR's dbschema files with standalone deployments and they all wor´k fine.

I'm now trying to set up DAS.
The problem is that when I run iwsync in any form (validate, install etc) I get the same problem.

The problem is that iwsync is looking for ALLof the category/datatypes in ALL of the workareas (and some category/datatypes only exist in some workareas).

The kind of area I get is that <workarea>/<category>/<datatype>/datacapture.cfg does not exist. And it doesn't, that's because it's in another workarea !

Why is it trying to process all datacategory/types for the branch (defined in templating.cfg) when I am running iwsync on only one of the workareas where only certain of these datacategory/types exist ?

Am I missing some other cfg file somewhere ?
Do I have to define which datacategory/types are in which workareas somewhere ? In the templating.cfg maybe ?

Find more posts tagged with

Comments

Migrateduser

That's the default behavior of running iwsyncdb.ipl -initial command. It enumerates the category/type definitions in templating.cfg and initialize DAS for those types.

If you want to initialize DAS for just one data type, you must run:

iwsyncdb.ipl -initial <workarea_vpath> category/type

Remember, running -initial command does the following:

1. generate the _dd.cfg file: you must have setup ddhome/conf/ddcfg_uds.template if using UDS or ddhome/conf/ddcfg.template if using wide tables or ddhome/conf/ddcfg_uds_custom.template if using custom DCRs

2. submit the workarea ---> this may be a problem in your case because different workareas have different types configured. potential conflicts.

3. run the basearea and deltagen deployments

Migrateduser

"2. submit the workarea ---> this may be a problem in your case because different workareas have different types configured. potential conflicts."

Does this mean I have configured my types- workareas in a strange way ? Can I have only the same types in all workareas ?

Migrateduser

when you have multiple workareas in a branch and each branch has different category/type configured, you would have to run -initial command for each one of them with different catetory/type parameter to iwsyncdb.ipl -initial command. Now, you have all the base tables created for all the types but not all the delta tables. You will then have to do a GetLatest on each workarea for all delta tables to be created for each one of them. Depending on how each workarea is configured for category/types, when iwsyncdb.ipl -initial executes iwsubmit, there might be conflicts as well. That's what I meant.

Adam Stoller

In general - when you have multiple workareas on a branch - the workareas should all contain the exact same content except for files that are actively being modified within the workarea.

Thus - you should have all the same DCT types and all the same DCRs visisble within all the workareas - except for those DCTs that are being developed and/or those DCRs that are being created in one (or more) of the workareas.

Trying to set things up so that only *some* files show up in *some* workareas is generally a receipe for confusion (if not worse).

Remember - you are not "paying" for extra diskspace for versions of files in workareas that are in sync with staging - you only use additional diskspace for modified files.

Hope that helps...

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Thanks guys, I duplicated all my category/types sp that all work areas are identical and I now have no errors.
I feel a bit cheated though. The whole point of my workareas was so that users within those would onlt see the DCT's that they need to do their job, now they see them all regardless.

Migrateduser

In such a case you can create multiple branches?

Adam Stoller

I haven't tried it - but since you have a scenario where you'd easily be able to tell if it works ...

Despite the name of the element - you might be able to make the distinction within the templating.cfg file:

<locations>
<branch vpath-regex="..."/>
</locations>

Just a thought. If that doesn't work - I'd suggest (as I often do) contacting Interwoven Support and asking them to create a Feature Request for being able to define what templates are available on a more granular basis.

--fish
(Interwoven Senior Technical Consultant)