Maximum users

[Hels Bells]

Hello,

Can anyone tell me if there's a maximum number of users that can be
created within OpenText Mgmt Server 10. I have a client who thinks
they'd like up to about 700 editors and I think that would be a BAD
idea.

And also that each editor would be responsible for a few pages (and
restricted access to all other) that need to be published out to
different directories so ....up to 700 publication targets, packages
and authorisation packages.

Can anyone give me any technical backup as to why this would be (and I
repeat here) a BAD idea aside from the cost of the licenses ....

Thanks in advance
Helen

[TonyGayter]

The maintainance alone would be almost unmanageble, publishing to sub
folders is a pain because if you want the main page in that folder you
have to have the foldername in the filename, and reddot doesnt see
this as a folder so they all need to be created before reddot would
publish to them, plus you cant apply auth packages to individual pages
only sub navigation, (which has cause untold problems in every single
project I have worked on, If I hear another client say 'Why cant you
do that, seems easy' I will punbh them in teh face lol).

Plus I woul dassume they would want workflows to go with that, The
time taken to do that woul dbe unbelievable. I would try creating a
small project and show them exactly what would have to happen etc..
then give them a quote for it and a quote doing it a better way. They
woul dprobobly be suprised with th edifferance.

[Stephane (SR Web Media)]

Hello,
We currently have over 600 editors spread out to I've 300 projects.
We are not with version 10 yet and still running version 6.5.

We have setup user groups for each different category and import user via LDAP. Managing the users themselves could cumbersome at times but doable.

I don't know you're project setup but for us we have a master project that contains all templates that we share to all projects. Then each user group is associate to the projects and then each projects have their authorization packages and publication packages.

In your case, I assume, they'll work on the same sites. So in your case, if you want to ease up the user management, you could separate your main or secondary navigation by projects and apply your different packages BUT doing this will bring some drawback like: you will not be able to use navigation manager as a whole, you might have some users working in different projects because of their role, you will not be able to use the automatic sitemap, so on so fourth.....

Hope this help in your reflexion !
Stephane

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
> To post to this group, send email to reddot-c...@googlegroups.com.
> To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
>

[RedDot in Toronto]

I've done both but not together... I worked on a project that had 700+
publication packages and roughly the same amount of folders/sub
folders in one project it'll work but opening the publication package
tab is extremely slow. If you're going to go down that route, I'd
suggest that you start a naming convention for your publication
packages. Is there any reason why you need a separate package for each
user? Also make sure you have all your variants planned out in advance
you don't want to be adding variants 700 times to each publication
package and assigning publishing folder.

700 users isn't a problem for one project it'll work, from a licensing
point of view it all depends on how many users are going to be logged
in at any given time concurrent licenses. We had a project where each
sales rep had a custom home page 700ish sales reps.

We were on version 7.5x I believe.

[Hels Bells]

Thanks guys for all the helpful information.

I think that's given me the confidence to recommend building a
solution with one project for the 700 editors.

Each of the "subfolders" that need to be published will have between
10 and 30 pages and there is only one level of navigation
(hallelujah!) so I wasn't intending on using nav man anyway. The small
size of each "subfolder" is als why I'm also a bit hesitant to do it
as separate projects as this does seem a bit overkill. Plus I thought
there was a restriction of 99 projects per server anyway ??

So my idea will to be to have a Plug-in that an authorised user will
run from a start page to create a publication target/package/workflow
and authorization package specific for that "subfolder". Then it will
create the "home" page for that subfolder (and assign the default
document name) and assign the relevant workflow and authorization. All
other pages created from these "home" pages will inherit the auth and
publication and workflow so I think this should work nicely now. I can
also create all of the other pages using the same plug-in and as crazy
as it sounds there won't be any internal links required. If they were
I could always bespoke the FCKEditor that I intend to use to modify
the connect to existing page option to provide only those pages
created in the current "subfolder"... It does seem quite a bit of
bespoking but certainly not undoable as the template setup is so
simple on this!

Obviously the fact that the packages/targets etc taking a long time to
open will have to be taken into consideration but I don't see this as
a huge problem as there will only likely be one CMS administrator (ie
me !!) and I've had worse frustrations within RedDot :-)

And again the licensing issue is something they'll have to deal with
depending on how much they want to pay to RedDot !!!

Again, if this does seem bonkers please feel free to set me straight!

Thanks again
Helen

[markus giesen]

What exactly is your client trying to do? I mean, what is the purpose
for this project?
I am also not sure if subfolders would be necessary...
Where do you publish to?
Maybe there is no need for a static folder and this could be managed
via URL rewriter?

700 Users are easy for RedDot CMS
Do you have different languages?
Do you have different project variants?

Instead of restricting access to each single page per user it might be
worthwhile setting up a workflow where every change needs approval.
Users rarely will mess around in other pages but if they do the
workflow can take care of it.
The time to manage this is likely to be less than the time to manage
groups/users/authentifications.

Users can get a startpage for the CMS, so the first page they would
see when they log in, that might be worthwhile looking into if each
user has only assigned one page.

[Hels Bells]

Markus,

The site is being published to IIS server as .aspx (There will be a
few user controls built into some templates) and SEO is important.

The structure for each subfolder is going to be almost identical so
that they want to have the published structure look like :

www.url.com/index.aspx

www.url.com/subfoldera/index.aspx
www.url.com/subfoldera/otherpage.aspx
www.url.com/subfoldera/differentpage.aspx

www.url.com/subfolderb/index.aspx
www.url.com/subfolderb/otherpage.aspx
www.url.com/subfolderb/differentpage.aspx

There will be user(s) who will manage the main top level page(s) and
then one or more users per subfolder to edit that content. They
haven't finalised workflow yet but it's likely that they each
subfolder will have a basic 2 step workflow - i.e. edit --> submit -->
approve --> publish. They're really quite insistent on one subfolder
user group not being able to edit other subfolders pages so I'm gonna
have to stick with authorization packages too.

I still think that I'll be able to do this in RQL as it will allow me
to get a new subfolder set up quickly but not by doing anything that
couldn't be done really easily by a RedDot administrator (The aim is
to make a non RedDot admin be able to get one of the subfolders set up
really quickly. But I like the idea of setting the start page for the
user too once I've created the subfolder home page so thanks for
nudging me about that one!