We are refreshing our database from production so the test environment is replica of production.
We export import the database and changed the storage path through PW admin in test environment. Is there anything else that we need to consider to have same projectwise as production?
we are seeing lot of workflow permissions are missing or they do not exist in production but shows up in test.
1) few security groups exist in test but they do not exist in production on folder level.
2) few exist in production but they were not copied to test
Do we need to do anything extra to copy the security otherwise why we have different groups between both environments?
Also, In test we are trying to remove the security group and it errors out "Cannot remove access control item"
when you say Export do you mean from ProjectWise or from SQL Server?
To make sure we have an exact copy of the database we have our database group take the latest backup of the database from and restore that on the dev database server. This gives us an exact copy of the database (at least as it was at last backup, hopefully just the night before) and it lets us test our backups to make sure they are working correctly.
we shut off the dev integration server while the restore is going on. after the restore is brought online I modify all the hostnames for the storage areas to servername that doesn't exist. Previously I would do this in SQL Server Studio, but i'll probably use powershell in the future. also need to modify indexing and thumbnails so they aren't submitted to the production indexing server.
We use Oracle so yes our steps
1) Dropped the test database2) Export production db3) Import into test DB4) change the storage area to point to new location via PW admin5) Changed User sync service, full text indexing, thumbnail to point to test server.
Looks like I followed all the steps but we seem to have problem with security group and access control.I will try another time with stopping the integration server services and provide an update if it makes any difference.
I would make step "0)" be "Stop the ProjectWise Integration service" on the test system.
Or, here's how I would order your list:
1) Get everyone to log out of the Production system (good luck!)
2) Stop the PW Integration service for the Production system (if users are transferring files then you might see some documents in "coming in" or "going out" as a result of stopping the service).
3) Export your Production database.
4) Optional: copy/sync your Production storage areas with your test storage areas if you need the files behind the documents.
5) Restart your Production PW Integration service and verify that all is well.
6) Delete your test datasource using ProjectWise Administrator (best to recreate it after the import)
7) Stop the PW Integration service on your test system.
8) Import your production database into your test database system.
9) Start the PW Integration service on your test system
10) Recreate your test datasource using ProjectWise Administrator and modify the storage areas to "point" to your test storage areas, or at least to somewhere different than the production areas!
11) Tweak your test datasource as needed for document processors, etc. so that there isn't any conflicts with your production system.
12) Verify that all is well, especially with your production datasource!
Dan WilliamsSolution ConsultantBentley Systems, IncorporatedPortland, OR, USA (Pacific Time UTC-08:00)
Answer Verified By: Rakhi Bhargava
thanks for detailed note. we are trying this in few hours and let you know how it went.