Skip to main content

Hello,

 We have two K2 server installations using completely separate databases and hardware.  One is for development and one is for production. My first question is are we staging K2 the most ideal way or should we be utilizing development, training, production on one consolidated set of databases and hardware?

 The second question is given our current setup, how can we migrate service broker service instances (and changes to existing) from dev to production?  Do we simply need to go through the "Broker Management Console" and manually add the new instances or refresh the changed ones, or are the smart objects tied to them via guids making that process ineffective?  Is there a config file or set of tables we should replicate from prod to live?

There can be variety of different good ways to use K2. I think having K2 use separate database and hardware for development,staging and production is good option. This way you actually separate all the environments from each other and not making them dependent on each other.

 Migrating Service instance is very easy just make sure that you use the exact same Guid in production/staging/ which you use in development.Use the same Guid for Service Type and service instances. This way you do not need to reference your existing smart objects again.

 Use Broker Management Tool to register new services, just make sure you use the same Guid

Use Boker management tool to update existing service Types and instances, -> Restart the k2 service, copy new assemblies and open broker management tool.

Right click service type you need to update  and click on update service type.

 

 

 

 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings