You want to create a Servicing Director test server with a copy of your production server data, and after making all the required changes, use the test server for testing and training.

The procedure below is for your local IT or system administrator familiar with Windows and Microsoft SQL server.

Note: Each Servicing Director system you have will need Servicing Director product licensing. For a test server, you can use the same license you have used for your production server. Your Servicing Director product licensing is stored in your production server. Therefore, when you move a copy of your production server data to your test server, your production server licensing will become effective on the test server.

Review the following:

• If you want to have a newer upgrade version of Servicing Director in combination with creating the test server, then use the newer upgrade version for all references in the following procedures.  For example, use the System Requirements for the upgrade version as the requirements for your test server.
• The Servicing Director System Requirements. Search the knowledge base for the system requirements that apply to your version. 
• Review Servicing Director SQL Server Required Configuration Settings 
• You'll find the Installation Guide on the Current Release Documentation page on Support Center. Review the related Upgrade Guide, if you are planning to use a newer upgrade version of Servicing Director.

 Make sure the test server computer meets the following Servicing Director System Requirements:

• The only versions of Windows supported for Servicing Director are listed in the System Requirements.
• The test server must be on a separate Windows server from the production server.

Install Microsoft SQL server on the test server:

• The only versions of Microsoft SQL server supported for Servicing Director are listed in the System Requirements.
• Review Servicing Director SQL Server Required Configuration Settings 
• Install Microsoft SQL server according to your Microsoft provided support instructions and apply or select the specific SQL settings.

Move the production server databases to the test server:

1. Have all Servicing Director users exist all applications, and end any other connections to the Service or SvcEventMgr databases.
2. Using backup methods appropriate for your production SQL server, create Production server database backups of the Service and SvcEventMgr databases.
3. Move the Service database and SvcEventMgr database backups to the test server using methods appropriate for your backup methods.
4. Restore the Service database and SvcEventMgr database backups on the test server.
5. Be sure the new databases created from restoring the backups have the required names Service and SvcEventMgr respectively.
6. Choose to overwrite the existing databases on the test server if your prior work on the test server has existing databases of the same name.

Create the SvcData folder on the test server:

1. Using Microsoft file system methods appropriate for your Windows servers, create the SvcData folder on the test server.
2. The primary or master SvcData folder is required to be a local folder on the test server.  Your institution might choose to create, update and otherwise synchronize a second copy of the SvcData folder, but these steps refer to the required SvcData folder on the test server.
3. Using Microsoft file system methods appropriate for your Windows servers, enable network sharing on the new SvcData folder on the test server.

Move the production SvcData folder to the test server:

1. Move the SvcData folder to the test server by using Microsoft file system methods appropriate for your Windows servers.
2. Copy the SvcData folder from the production server to the test server folder you created in the prior steps above.
3. Be sure to copy all files and subfolders from the production SvcData folder.
4. Use the new SvcData folder location when you install the database product in later steps.

1. Skip moving the archive if you have that option on your production system.
2. Remove the test server archiving configuration instead if you have that option on your production system.
3. Open SQL Server Management Studio on the test server. 
4. Open the New Query screen.
5. Enter the following SQL command in the New Query screen: Delete From Service..FolderFixed
6. Click the Execute button on the New Query screen toolbar to run SQL command. Note: Executing the SQL command should report several rows affected.

Install the Servicing Director database product on the test server:

1. Complete the Servicing Director Installation Guide procedures in the section titled "Installing the Servicing Director Databases". You are required to only install the Servicing Director database product on the test server, and the optional Servicing Director applications product is not required.
2. Locate the database installation program in Support Center .
3. Use the SvcData folder location created in the steps above when prompted for the SvcData folder during the database product installation.
   • If you wish to test a newer version of Servicing Director than you have on your production server, you can install the newer version of the Servicing Director database product at this point, upgrade the databases immediately to the newer version.  You will be required to upgrade the desktop applications to be on the same version.
   • This is a required step.  If the database product is not installed, your server will be missing required Servicing Director components.
   • If you have the Customer Self-Service add-on product, also install the Customer Self-Service database product. Only the Customer Self-Service database product is required, and use the current version of the Customer Self-Service Installation Guide to complete this step.

Reset the Servicing Director SQL Server login credentials:

1. Use the Servicing Director LSCNFG application to set new SQL Server login credentials on the test server.
2. On the LSCNFG application, clear the Default check boxes for the Loan Servicing and Reports SQL login section, and enter your choice of unique passwords.
3. You must use the LSCNFG run FixRights option by selecting the Run Fixrights checkbox.
4. Review Resetting the Servicing Director SQL Server Logins.

1. If you chose to upgrade the Servicing Director databases to a new version above by installed a newer version of the database product above, then skip these steps and upgrade the desktop applications to match the version on the databases. Use the matching version Servicing Director Upgrade Guide and use the procedures in the section titled Manually Upgrading Fusion Servicing Director Applications.
2. Reconfigure the selected desktop application if the version of Servicing Director is unchanged.
3. Change desktop applications only on the desktops you want to switch to the test server.
4. Consider which desktops you want to connect to the test server.  Any desktop connected to the test server should only connect to the test server, and you should avoid switching a desktop to test server and back to the production server to prevent accidental transactions on the wrong system.
5. Change the ODBC System Data Sources named Servicing and ServEM to connect to your test server using Mircrosoft procedures. 
6. Review Changing the Servicing Director ODBC Data Sources to Use SQL Server Authentication.

 Change the existing Servicing Director desktop applications to use the SvcData folder on the test server:

• If you upgraded the Servicing Director desktop applications above, skip these steps.
• Use the Servicing Director Change Reports Location application to browse to the RPT folder within the SvcData folder on the test server.
• Review Having the Servicing Director \SvcData Folder on a Server Other Than the Database Server

Prevent unwanted crossover to the original production server:

• The Event Manager database restored to the test server may have scheduled event data which includes file paths to the original production server.  To prevent unwanted crossover by these events to the original production server, the event criteria may need to change to update the file paths.
• Review Changing Event File Paths in the Servicing Director Event Manager Database.

Rename the test server Company Name:

1. Open the System Administration application from a Servicing Director desktop which has been redirected to the test server in the move data procedures,
2. Click Table Setup.
3. Select Company.
4. Change the Company Name on the Setup tab to a name of your choice to identify the test server.

Creating the test server is complete.

ArticleNumber:

000050073