We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

BEst way to migrate through environments

Thread ID:

Created:

Updated:

Platform:

Replies:

130874 Jun 8,2017 03:50 AM Jun 9,2017 08:54 AM Report Platform 1
loading
Tags: Report Server
Patrick Graydon
Asked On June 8, 2017 03:50 AM

     Hello,

We have 3 servers (Dev, UAT and Production).

Can you please advise on the best way to promote reports/datasets/datasources through the environments please.

ie once UAT has passed how do we migrate the report to Prod?

Thanks

Patrick

Rajesh Rajendiran [Syncfusion]
Replied On June 9, 2017 08:54 AM

Hi Patrick,  

Thanks for contacting Syncfusion Support. 

To migrate the resources, you need to back up all the Report Server elements located in the following location of the UAT machine. 
%programdata%\Syncfusion\Report Server        
For Example : C:\ProgramData\Syncfusion\Report Server      
All the Resources and Logs will be in that “Report Server” folder.   

Case 1: If both the UAT and Production server point outs the same database means, please follow the bellow steps in Production server, 
1.            Go the folder %programdata% (For example: C:\ProgramData)    
2.            Create a folder “Syncfusion”.     
3.            Paste the backup folder “Report Server” in the newly created folder.     
4.            Install the same version of Syncfusion Report Server.  
 
If you follow the above steps, all data will be migrated to the production server as well. The users will not be affected. They do not need to change their passwords, etc. The Production Server ideally has the same categories, reports, datasets, and data sources.   

The above steps will back up and restore Resources and Logs folder.  

Case 2: If you want to keep separate database for both UAT and Production server, follow the steps mentioned in the Case 1. Additionally you need to change the database mapping based on the Database type you have chosen.  
 
For SQLCE: No changes required for the database mapping.  
 
For SQL Server, MySQL, Oracle follow the below procedure in the production server:     
The database configuration file will be in the below folder:     
%programdata%\Syncfusion\Report Server\Configuration    
   
Do the following changes in the production server:     
1.       Backup the schema and data. Restore it in a different DB server. This will copy all the user data to a separate DB server.    
2.       Form the Connection string for the production DB server as follows:     
   
SQL Server     
SQL Server Authentication:     
Data Source=”databaseCredentials.ServerName”;user id=”databaseCredentials.UserName”;password=”databaseCredentials.Password”;Initial Catalog=”databaseCredentials.DatabaseName”;    
Windows Authentication:     
"Server=”databaseCredentials.ServerName”; Integrated Security=yes;" Initial Catalog=”databaseCredentials.DatabaseName”;    
MySQL    
DSN="DSN name;"Uid="User Name";password="Password";    
Oracle    
master:DSN=DSN name;UID="Admin User Name";PWD="Admin Password";current:DSN=databaseCredentials.DSN;UID="Client User Name";PWD="Client Password";    
   
    
3.       Now encrypt the connection string of the production server using the utility:     

·         Run the Connection String Encryption.exe.     
·         Enter the above connection string and press Enter.     
·         You will get the encrypted connection string.    
    
4.       Replace the encrypted connection string in the Config.xml file of the production server.    
(%programdata%\Syncfusion\Report Server\Configuration\Config.xml)     
    
      

Thanks, 
Rajesh. R 


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;