VMware {code} Community
HRingersma
Contributor
Contributor

package Configuration contents(values) too?

HI, in my Orchestrator package, apart of workflow, webview, etc. I include the Configuration files too. However when I export and import the package into another system the values of the of the attributes in the configuration files have been losts. How to include those values too?

Reply
0 Kudos
3 Replies
Burke-
VMware Employee
VMware Employee

Hello there, what you are describing is by design. The Configuration Attributes are intended to be Organization specific settings that should not be stored in exported packages. This way, VMware PSO or your favorite partner can create a custom vCO solution that relies on some configuration settings for Infrastructure elements specific to the development environment. When you receive that package, if it had the developers settings, it would not work due to your infrastructure's unique settings and IDs.

If you really need to back up your settings, then please see the following thread (Last post by: cdecanini)

http://communities.vmware.com/message/1629233#1629233

Visit me at for vCenter Orchestrator tips and tutorials Smiley Happy

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
Reply
0 Kudos
stuartclements
Community Manager
Community Manager

Hi.

Please see http://communities.vmware.com/message/1628998#1628998.

Thanks,

Stuart

vCO documentation

Reply
0 Kudos
HRingersma
Contributor
Contributor

Thanks, all.

I use multiple configuration files for our workflows. E.g. one general configfile with setting to control the workflows and webviews, and another one for datacenter specific settings (servernames, db accounts, etc) , next one for dedicated Windows2008 sysprep settings, etc . Therefore it would be nice to add the default settings (not being developer settings) together with the package.

I solved it now by creating a workflow that sets all the values of the configElement attributes from a .csv file. This saves time during initial setup and prevents typing errors. :smileyblush:

Reply
0 Kudos