Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Shut Down Target Site When Using Catalog Deployer?

Shut Down Target Site When Using Catalog Deployer?

Do I need to shut down the target site when transmitting a package using Catalog Deployer?

It is not necessary to shut down the target instance when deploying a package.  If you do not shut down the target instance there is a small possibility that a user would get timed out of entering a request if they happened to be ordering a service at the very instant that Deployer was attempting to update that service definition. In fact, you can't actually shut down RequestCenter when running Deployer, since Deployer uses the RequestCenter menus and screens, but if you do a large deployment, it is recommended to schedule it at off hours and to temporarily restrict end-user access to the site.


There is also a configuration parameter that can be adjusted to optimize Deployer performance, but at the expense of increasing the possibility of conflicts with end user requests, which also argues for scheduling large deployments ("large" subject to interpretation, but, say, 20+ services) at a time when users are not accessing MyServices to order a service.

Everyone's tags (1)