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

Editions Best Practices

rpjoseph

Hi again....

Could somebody please provide best practices or point me to documentation for creating daily editions. I am on TS 5.5.2 SP2B - Windows 2000.

Is it best to use OpenDeploy to schedule the submission? Or is Windows scheduler better?
Should we create an edition once per day - more often? less?
Do most of you create editions before your backup?
How do we customize the name of the editions?
How do we archive or remove editions so that they are easier to manage? It seems like it would be difficult after a couple of years with 700 some odd editions??
Anything else that we should know about would be appreciated

I have been making editions when I feel like it (probably not enough). I know that I need to automate this - I just want to know what others have done. It probably doesn't really require this much thought eh?

Also - I know that 'hidden' editions are created everytime a user submits content. Does anybody know how to get to those hidden editions?

Thank you again for your help.

Find more posts tagged with

Comments

MattP

So much of this depends on your needs, the volume of the site, how much you are willing to risk, etc etc. I am sure you will get a lot of varied responses.

I assume you mean scheduling a deployment, not a submit. I use OD for my deployment scheduling. Works fine. There are a few advantages a few disadvantages. You can add deployments with CLT if necessary. I think it is good to have all your deployment info in one place.

I create editions 3 times per week on a moderate volume site. Nothing wrong with once a day, some sites do more (multiple per day) others do less (once per week). Its value is really based onthe amount of change. I do this with a scheduled NT job.

We back-up everynight. Editions are created before the back-up. The backing-store needs to be frozen during back-up (at least for us...on windows).

The manual describes edition naming.

There are several posts of edition "pruning". Dave from Nike recently had some good insight.

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Edited by MattP on 05/07/03 01:13 PM (server time).

Migrateduser

For what it's worth...

We create editions on every submit for some of our sites (probably overkill and will be changed I think). And we create editions once per day on most of our sites, but only when a site has changed that day. This is scheduled via cron, which won't help you much with Wondows. We do delta backups every night and full backups once per week, and do not create editions based on any backup schedule. We don't bother much with customizing the name of an edition, but it would be easy enough if you wanted to. With TS 5.5.2 and above, deleting editions is a lot easier and faster than in previous versions. We have been able to delete lots of editions at once (how many is too many? good question) with no performance impact whatsoever. When we upgraded, we only brought over a few editions for each branch and set up an edition maintenance script (based on the publish trigger event) that limits each branch's number of editions. Like Matt said, this was brought up in some earlier post and if you want a copy of that script, I can send you one.

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

Adam Stoller

The one question I don't think was answered was the customization of the names of editions - for that, I suggest running iwpublish -h and looking at the usage (or if you're going through the GUI, you can supply your own name in the text field provided).

--fish
(Interwoven Senior Technical Consultant)

kellyrmilligan

I was wondering if I could get a copy of that script, I am looking to schedule cutting editions twice a week using cron.

Thanks,
Kelly

NathanW

We create an edition every day for all of our 25 web sites - provided there have been changes submitted to staging.

We run Windows servers and simply call a daily edition batch file from the task scheduler. Each line in the batch file looks like:

d:/teamsite/iw-home/bin/iwpublish -g -f //server/default/main/www.dotars.gov.au STAGING "This is an automated daily edition" adminuser

Nathan Wall
Department of Transport and Regional Services (Australia)

kellyrmilligan

is there a post that has this edition maintenance script attached?

thanks,
Kelly

Gregg Faus

I don't believe so. As NathanW eluded to, just create a .bat file and call it from Windows scheduler (or cron if you are using Unix). I do a similar thing, I have a nightly edition deployed to a website. My .bat looks like this:
@echo OFF
echo Creating Edition...
iwpublish -g //servername/default/main/projects/projectnamehere/ STAGING "Nightly Edition"
echo Done!

Then through the Open Deploy admin, I scheduled a "latest edition" config to run just after the batch file runs. That way the edition is created then deployed.

Migrateduser

I think Kelly was referring to the edition maintenance script, not the creation of editions. I would be happy to email my edition maintenance script to anyone who forwards me their email address. My email address is in my profile.

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