Best way to start over?

ECM
1

We’ve had DocStar installed for some time, but never connected it to our production environment. We did a bit of random testing with it attached to our test environment, then copied the production database over top of the Test database (wiping off any connections to DocStar again). We’d like to start over before we actually attach it to production and start using it for reals…

I’ve stood up a new VM for 3rd party software, and before I install ECM on the new server, I think I’d like to back-up, then blow away the current ECM databases to start fresh. Thinking it’s the AAAA0001, Astria_Host databases, is that correct? There’s also an EclipseSignalRBackplane database, is it related?

Is there anything I should collect beforehand?

2

You can get a second dev license and keep what you have built and use to develop and use your original license as production.

EclipseSignalRBackplane is related, but you may not need it in a future configuration.

1 Like
3

I do this all the time - Copying Kinetic Prod to Kinetic Test. Works fine, and like @gpayne mentioned, they will give you a Test/Dev license code so you can have the ECM and Kinetic environments in parallel.

Your workflows. If you export them, they will bring over all the additional pieces like datalinks, content types, fields, security, etc. But if you’re starting over, you might want to be more selective.

As far as I can tell, as long as the Kinetic DocType name and the ECM Content Type name remain the same, the “link” between them will still work. Has for me for the last 4 years.

2 Likes