what all needs to be made sure or followed after renaming the repository and database

replied on January 7, 2022 • Show version history

Hi Sona

We do this from time-to-time and I made the following notes for our sys admin. It may not be perfect but it covers the issues we need to keep in mind.

This is for an on-premis application of Laserfiche v10.4.

Changing the name of a repository requires changing several integration values. Please follow the steps below.

In Administration Console, unregister the repository
In SQL Server Manager change name of database
1. In order to be allowed to change the DB name you must change the Restrict Access drop down to Restricted_User. This parameter is found in the State area (Database Properties >> Options >> State). Then change the name.
Back in Administration Console, re-register the repository with the new repository name and the new database name
1. When registering, watch out for the entry for File Server name. (If you have existing documents on the file server for this repository, the file server folder name cannot be changed. If you change it, you will lose access to the existing documents because the pointers in the database to the files on the file server are location paths - unless the location path is somehow updated they will still contain the old folder name on the file server. You can't change the file server folder name without changing the pointer values in the database. This is not covered in this document.
Go the Web Client configuration site and, in the Connections tab, add the new repository to the list. This will allow the newly named repository to be visible in the list for Web Access.
Once you set this up you will need to restart the Workflow Subscriber or it will continue to look for the old repository name.
If you have existing forms and workflows you will need to change all the connection profiles.
1. Also, if any of these workflows run a repository search tool, you need to update the query to show the new repository name.

Hope this helps. If any VARs or Laserfiche staff can add more I would be happy to read it.

1 0

replied on January 7, 2022

For Workflow and Forms, you want to worry about the stuff in flight. In Workflow, add redirects in the admin console so running instances won't be affected. For Forms, instances will suspend and you will need to fix the connection profile then resume them.

You will also need to update any Import Agent profiles, Quick Fields sessions, Connector profiles you may have.

For Audit Trail, I would just remove the existing repository registration and add the new one in and then let it re-import the audit data.

If you have any integrations connecting to the repository, they will also need to be updated.

2 0

replied on January 9, 2022

Thanks!!

0 0

Question

Question

what all needs to be made sure or followed after renaming the repository and database

Replies

Sign in to reply to this post.