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; } } }

Enterprise Structure of Callouts and Scripts

Tim__D

I was wondering how commom scripts, .pm's and callouts should be organized for a large ECM system. What are some best practices? Our other development processes use branching just as Teamsite does but Teamsite's most precious code does not live at the branch level? Can it?

Any help would be great,

- Tim

Edited by Tim__D on 02/02/05 11:04 AM (server time).

Find more posts tagged with

Comments

nipper

Use your directory structure to help.

i.e.

iw-home/custom/BUS_UNIT/PROJ/(bin,config,classes, etc), works for WFs as well. I did not do that for .pm's but you could.

Also, do your business units share one dev server or are there multiple ? Hope you have a config branch & tight controls
on the WF process to push from config branch to iw-home.

just a start

Andy

Adam Stoller

6.x and above - your .pm files should be stored in IWHOME/iw-perl/site/lib/ and you can make whatever structure you want down there (as per modular packaging)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gzevin

sometimes I create <iw-home>/custom/site_lib and the every script does 'use lib ...'.

it makes easier to move/archive all the custim stuff...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

Prior to 6.x - I'd agree.
As of 6.x, Interwoven has "promised" to not touch the iw-perl/site directory structure for any service pack, patch, or upgrade *and* iw-perl/site/lib is *in* the @INC list, so you don't have to use the 'use lib' directive -- and worry about specifying the full path through iwhome to where your modules live.
It's much more convenient.

For example, my customer now has a site/lib/ED/ directory with all the modules we developed for them - and soon (if I can get it to build) will have a site/lib/DBD/Oracle directory, etc. (i.e. - any modules that you download and build from CPAN will go into site/lib - and thus also will not be lost due to service pack, patch, or upgrade of TeamSite / iwperl)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Tim__D

Interwoven has all callouts in the following directories
\iw-home\httpd\iw-bin
\iw-home\custom\Company Name etc..\bin etc....

They placed any custom .pm files in
\iw-home\iw-perl\site\5.00503\lib\Company Name\Image etc..

Tim__D

We use a single production server for all business units

Tim__D

Can you elaborate on the concept of a config branch? I have long wondered if Teamsite could act as a versioning system to version itself or custom built components. Is that what your getting at? This is not a concept that I have seen in any Interwoven docs

Tim__D

Great that is how at least by .pm files are structured.

\site\5.00503\lib\

Adam Stoller

The 5.00503 structure is PRE TS6 - and as I said before it is TS6 and higher that provides the promise that Interwoven won't muck with the site/lib directory structure.

For earlier versions of TS you can put your stuff in the site/5.00503/lib directory but it is subject to being removed during an upgrade, service pack, or patch application.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com