Porting a BPC Application Set between two servers

Under normal circumsances, the application sets are copied between two servers via the BPC Server Manager Backup and Restore utility.

This document provides step by step instructions on how port an application set when the BPC Server Manager utility can not be used.

Overview

Steps to be performed on the Source server

Create a full backup of the Application Set SQL Database
Create an archive of the Application Set Analysis Services Database
Create a zip file containing the FileDb directory
Create a zip file containing the WebFolder directory

On the Destination server

Restore the Application Set SQL Database
Edit the AppServer table entries.
Restore the archive of the Application Set Analysis Services Database
Edit the application definition settings.
Extract the FileDB zip file containing the FileDb directory from the source server.
Extract the WebFolders zip file containing the WebFolder directory from the source server
Validate and Process Security using the BPC Administration client.
Save all Applications as part of the Application Set being restored

On the Source Server

Backup the Application Set SQL Database

1) Launch SQL Server Enterprise Manager and connect to the source server.

2) Right click on the Database folder.

3) Select All Tasks>Backup database.

4) The “SQL Server Backup” window will appear.

a) From the General tab’s Database dropdown list, select the Application Set SQL database you want to backup.

b) For Backup, select the Database – complete.

c) For Destination, select the Disk radio button. Then select the Add button to append a backup location to the Destination window.

d) In the File name dialog box, type in the name of the CPM Application Set you want to back up with a file extension of BAK (i.e. ApShellCopy.BAK).

e) Select OK to accept the file name.

f) From the “Select Backup Destination” window, select OK to return to the SQL Server Backup window.

g) Select OK to begin the SQL backup.

5) Exit SQL Server Enterprise Manager.

Archive the Analysis Services Database for the Application Set.

1) On the source server, open Analysis Services Analysis Manager.

2) Right click on the Application Set database and select Archive database…

3) Specify the folder where you want to archive the database.

4) Select Archive.

5) When the archive is complete, select Close.

6) Exit Analysis Services Analysis Manager.

NOTE: These steps must be performed on the AppSet_BPU if your Application Set includes an Insight Database. (ApShellCopy_BPU)

Create the FileDB Zip fileof the Application Set’s FileDB folder

1) Open Windows Explorer on the source server.

2) Navigate to the \FileDb\Application Set name.

3) Right click in this folder and select Add to Zip.

4) Name the file AppSetFDB.zip, where Appset is the name of the application set you want to port.

5) Click the Add button

6) Close the WinZip window once the process is complete

Create the WebFolders Zip file the Application Set’s Webfolder

1) Open Windows Explorer on the source server.

2) Navigate to the \WebFolder\Application Set name.

3) Right click on this folder and select Add to Zip.

4) Name the file AppSetWB.zip, where Appset is the name of the application set you want to port.

4) Click the Add button

5) Close the WinZip window once the process is complete

On the DESTINATION SERVER

1) Copy the Application Set SQL database backup file to a folder on the destination server.

2) Copy the Application Set Analysis Services Database archive file to a folder on the destination server.

Restore the SQL Database for the Application Set

1) On the destination server, open SQL Server Enterprise Manager.

2) Navigate to the Databases folder.

3) Right click the database and select All Tasks>Restore database.

4) The ‘Restore database’ window will appear.

a) From the General tab’s Database dropdown list, type the name of the Application Set SQL database you want to restore (i.e. ApShellCopy).

b) For Restore, select the From Device radio button.

c) For Parameters, select the Select Devices

d) The “Choose Restore Devices“ dialog window will appear.

i) For Restore, select the “Disk” radio button.

ii) Then click on the “Add” button.

iii) Browse to the location and file name for your Application Set SQL database backup file previously created. After the desired file is selected click OK.

iv) Click OK to return to the “Restore database” dialog window.

e) Select the Options tab.

i) Although not recommended, if you want to restore over an existing Application Set database with the same name select the checkbox “Force restore over existing database”.

ii) In the middle of the Options tab, review the information in the section entitled “Restore Database File As:”

(1) Ensure the drive letter and path information for the SQL database and SQL database log files are correct.

f) Click OK and the SQL restore procedure will start.

g) Click OK after the database has been restored. If you receive any errors during the restore process, please review the steps outlined above.

Editing the Application Set’s Defaults

1) Open SQL Server Enterprise Manager.

2) Navigate to the newly restored Application Set database and select the plus sign to display the database tables.

3) Navigate through the list to the tblDefaults table.

4) Right click on the table name and select Open Table>Return all rows.

a) Verify the drive letter and path for the following KeyIDs is correct. (Note: Review the tblDefaults table settings for the ApShell application sets for guidance.)

i) COLLABROOT

ii) FILESERVER

iii) FILESERVERLOCATION

iv) UPLOADTEMP

b) Verify the server name for the following KeyIDs is correct. (Note: Review the tblDefaults table settings for the ApShell application sets for guidance.)

i) FILESERVER

Editing the AppServer Database

If this is a new appset, you need to add some entries in the AppServer database.

1) Open SQL Server Enterprise Manager.

2) Navigate to the AppServer database and select the plus sign to display the database tables.

3) Navigate through the list to the tblAppSet table.

4) Right click on the table name and select Open Table>Return all rows.

5) Copy the ApShell Entry and Paste it in the last row.

a) For ID, type the name of the restored database (ApShellCopy).

b) Replace the name of the application set in the portion of the new DBConnectionString value that begins “Initial Catalog=XXX” (where XXX is the name of the prior application set) to the database name you just restored.

c) For the Description field, type in whatever you would like for the description for the database you restored.

d) Note the DBUSERID for use later.

e) Now that the entry is complete, close the tblAppSet table.

6) Navigate to the tblAppSetAccess table

7) Right click on the table name and select Open Table>Return all rows.

8) Move to the bottom of the table and create a new entry for the new Application Set.

a) For AppSetId, type in the name of the database you restored.

b) In the Userid field, type servername\userid where servername is the machine name of the server, and userid is the id of the installation id.

c) Specify a UserType value of 6. This will make the user a System Administrator & Application Administrator.

Restore the Application Set Analysis Services Database

1) Open Analysis Services>Analysis Manager and connect to the server.

2) Right click on the server icon and select Restore Database.

3) Navigate to the Application Set archive file copied earlier (i.e. *.cab) and select Open.

4) Select Restore to begin the restore process. This step may take awhile.

5) When the restore is complete, you may have to refresh the Analysis Services console so that the new database appears in the list.

6) Click on the plus sign next to the new database to expand it. This may take a while.

7) Then expand the Data Sources Folder

8) Under Data Sources, right click on appdef and select Edit.

9) Update 1 so it has the proper server name listed (i.e. the name of the destination server).

10) Update 2 so it contains the DBUSERID noted above (cpmsa ID), and type in the password.

11) Check the box for “Allow saving password”

12) Update 3, verify that the database listed in the dropdown box is the name of the Analysis Services database that was just restored.

13) Select “Test Connection”.

a) If the connection test is successful, click OK. Then click OK to close Data Link Properties.

b) If the connection test is not successful, review the preceding steps for Restoring Analysis Database. Make sure the SQL Server ID and password are correct.

14) Right click on the on the name of the database just restored and select Process Database.

15) Close Analysis Services.

NOTE: These steps must be performed on the AppSet_BPU if your Application Set includes an Insight Database. (ApShellCopy_BPU)

Copy FileDB and Webfolders

Unzip the FileDB and Webfolders zip files created above to the appropriate respective directories.

Example:

AppSetFDB.zip gets unzipped to [drive]:\PC_MS\FileDB folder

AppSetWB.zip gets unzipped to [drive]:\PC_MS\WebFolders

Create Virtual Directories

1. Open Server Manager

2. Click Appset/Create Virtual Directory

3. Check the box next to the Appset just restored and click create.

Validate and Process Application Set Security

1. Go through the connection wizard and enter the Admin module

2. Validate & Process Security

3. Optimize the application set with the Full Process option.

Rebuild Application Set Security