Step by Step migration to a new server using CA BSI 8.3.5
search cancel

Step by Step migration to a new server using CA BSI 8.3.5


Article ID: 10914


Updated On:


CA Business Service Insight


This document can be used as a guide on how to do the migration from an existing BSI installation to a new server, using the Best practices.

The object of this document is to change/move CA BSI from one server to another, but use all the same configuration and environment.

NOTE: you could change the Operating System version and the Oracle version on the new Server but you must keep in mind that they must be the same version or newer versions, they must be supported versions and in the number of Partitions and size they must be the same or larger. This also assumes the BSI version on both boxes is the same.


BSI 8.3.5

All Supported Windows OS and Oracle Databases

Document assumptions:

  • The APP, WEB and Database are on the same box. If they are not, then you may be able to ignore some of these steps.
  • You have already properly installed a new target installation of BSI. If you have a remote database which you are planning to reuse then you need to decide if you are going to  install a new DB with the new installation and then migrate your data over OR if you are going to install with a new DB but then point the new APP and WEB to your old database OR install the new APP and WEB while pointing to your old database which will bring your old installation down.


We first have to make sure that the new Server has all the Windows prerequisites as per the installation guide before installing BSI.

The new server must have the same Oracle version installed or newer. 

The new server must then have configured and installed the same BSI version, applying all the fixes that server could have had applied in the past. This server must be working without any problem before migrating anything.

Things to check:

  1. Install all the Microsoft pre-requisites
  2. Install Oracle same version and fix (Same sort order - very important)
  3. Verify Oracle configuration
    1. Oracle Listener
    2. Oracle Net service Name
  4. Install BSI same version and fix level (Same Org name and in the same Disk drive and path)
  5. Use the SAME dbowner name (such as oblicore) if you are replicating database information to a new DB
  6. Apply Windows Updates and verify that you apply the same fix on the other server

Before you start any migration it is highly recommended that the Server Source and Destination are backup in case anything goes wrong.

1.  Backup Recommended 

  • The Oracle Database (Oblicore)
  • The directory C:\inetpub\wwwroot\Oblicore
  • The directories where the Adapters are working such as %OG_HOME%\adapters
  • The directories where booklet templates are located such as %OG_HOME%\Booklet Templates

2.  Make sure that the new target BSI installation is working. Make sure you can login.

3.  Stop all of the adapters in your source BSI installation.

4.  Stop all of the BSI services on both the source and target installations

5.  If you are replicating the information in the database from the old installation to a new one, use a utility such as expdp/impdb to export the Oracle database from the old installation. You are better off having the DBA export the database with whatever they are most familiar with.

6.  Import the DB information with whatever Oracle command you use to backup. This is much easier when the two environments use the same Oracle database logins.

7.  If you are instead pointing the new APP and WEB to the old database and replacing the old APP/WEB, then instead you can edit the tnsnames.ora file and point your tnsnames entry to the old database.

8.  Check the %OG_HOME%\setup\config_init.ini on the new WEB server and then run %OG_HOME%\setup\config_init.bat. This should change most of the values in the T_SYSTEM_CONFIGURATIONS table to the new server name.

9.  Run: select * from t_system_configurations where upper(sys_config_value) like '%OLD_HOSTNAME%'; where OLD_HOSTNAME is your old WEB server name in uppercase. Then run the same command with the APP server name. These will return any entries which still need to be updated to the new server names. Run update commands to set them appropriately.

10.  If you are replacing an APP server with multiple instances of PSLwriter, then make sure you have installed all the additional instances. Also make sure MSMQ is installed properly in domain mode as this is a common sticking point.

11.  If you do not want to redeploy the adapters then copy over the %OG_HOME%\adapters folder from your old BSI installation. If you have any trouble with the adapters (due to security rights for example) then you can have them redeployed by deleting that adapters folder instead and letting BSI redeploy it from the config information in the database.

12.  Restart the BSI services