Nintex Connect

Hello,

in our SharePoint farm we have a single NINTEX database acting as configuration and content database for all consumers (i.e. site collections).

As you suggest one should have a 1:1 mapping for site collection and NINTEX content databases, which would also help us in backup- and restore-scenarios. While going through your documentation and forums we weren´t successful in finding a concise description for our purpose (which doesn´t mean it isn´t there, of course).

Would you please point us to a few locations which would help us in the following situations (we try to make clear what we want to do):

1) Adding a new site collection to a web application (1:1 mapping for a new site collection database and a new NINTEX content database)
- Adding a new site collection with its own content database
- Adding a new NINTEX content database via Central Administration
- Map the NINTEX content database to the site collection via Central Administration
- Activate the NINTEX features in the site collection
--> is that it regarding case 1)?

2) Extract and move site collection data from the current single NINTEX database to achieve a 1:1 mapping
- Create a new NINTEX content database via Central Administration
- Map the NINTEX content database to the site collection via Central Administration
--> now how to move the data from our current single NINTEX database?

3) Clone site collections between web applications
We have a production and a training environment represented by two different web applications. It would be nice to synchronise one way from production to training. Is that possible involving the steps described below?
- backup the production content databases (site collection and NINTEX)
- restore the production databases in the training environment
--> what else do we need to do to avoid interdependencies?

 Any help would be appreciated!

 Cheers,

 Gerald

Hello again,

let´s just pretend that situation 1) is described correctly. We are working on situation 2) at the moment:
We created a new NINTEX content database via Central Administration.
We mapped the existing site collection to this new NINTEX content database via Central Administration.
To migrate the workflow information from the existing single NINTEX database we try and use the NWAdmin-operation "-o MoveData".

As we are not willing to try and test this in our production environment (talking of a farm), we were "cloning" the environment and set up a test environment (Test farm):
Backup/Restore VM (web application server and application server).
New SQL server instance in the SQL server for the Test farm.
Fill the test SQL server instance with data from the production SQL server instance.
SQL server ALIAS in the Test farm pointing to the test SQL server instance.

The problem:
When executing the NWAdmin-operation like ".\NWAdmin -o MoveData -Url <sitecollection>", it seems like it receives the correct connection strings (NINTEX configuration database?), which both point to the production SQL server instance (which is ok, as the ALIAS should handle this).
Nevertheless we get prompted for a target database ID, and disregarding what we enter, we won´t succeed.

The question:
Does the NWAdmin-operation take into account that a SQL server ALIAS is set? The new NINTEX content database is not yet set up in the production farm, does the operation fail because it tries and connects to the production SQL server instance?
Any other ideas which would help us?

Thanks for any input!

Cheers,

Gerald

Hello again,

any help available? If we didn´t make ourselves clear, please ask for more information.

 Thank you,

Gerald

Hello again,

problem solved: if you get prompted for an ID, which is written directly above the prompt... just use it.

So now we created a 1:1-mapping for WSS Content Databases and Nintex Content Databases, which is what we aimed for.

Thanks for your patience,

Gerald

Hi swolfe,

basically follow these steps:
- create a new NINTEX Content Database via Central Administration (make sure the permissions are set on SQL-Server)
- bring down your farm (http://technet.microsoft.com/en-us/library/cc512725.aspx#Stop)
- NWAdmin.exe –o MoveData –Url http://yourSiteCollection
- bring up the farm
- map your NINTEX Content Database to your site collection via Central Administration
- perform an IISReset

This should be it. Good luck trying, come back with any questions!

Cheers,

Gerald