Deployment

["Coco, Christopher" <Christopher.Coco@vignette.com>]

Is it thought that the corresponding producer use cases would have to handled out-of-band?

The corresponding use case being as follows:

1. Producer "Publishing" - in the case of the controlled environment, it is very possible 
that there exists both a portal consumer and a wsrp producer that both need to be moved 
from a staging to a production deployment. The consumer "publishing "use case covers the 
assumption that the consumers (both the staging and production) are pointing to the same 
physical producer(s), but what happens in the case where the producer(s) need to be moved to 
another deployment? It is assumed that producer will have to maintain the same url?

2. Producer Deployment - how does the producer handle the importing/exporting of portlet assets
and consumer metadata (registration contexts) from one producer deployment to another? It would
seem just as likely for a producer to want to import/export applications which contain wsrp
producer offered portlets from one producer deployment to another (along with all consumer 
configured portlets and the corresponding consumer metadata). Is it thought that the producer
will maintain registration context across imports, or do a mapping of imported registration
contexts to existing registration contexts on the target deployment, or neither? Off the top of
my head it would seem that there are several reasons that would precipitate moving portlet/consumer
assets from one producer deployment to another.

Thank you,
Christopher

Christopher Coco
Senior Software Engineer
Vignette Application Builder
p. 415.995.3534 | f. 415.975.9801

Vignette's software and expertise help organizations harness 
the power of information and the Web to deliver measurable 
improvements in business efficiency. Vignette is the efficiency 
expert. Visit http://www.vignette.com/ to learn more.