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

Document ID : KB000010914
Last Modified Date : 14/02/2018
Show Technical Document Details

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 the 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.

This section contains the following topics:


  • Pre requisites on the New Server
  • General Best practices
  • Start the migration process

We first have to make sure that in 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. BSI 8.3.5 now support 32-bit or Oracle 12 if you install the cumulative 3 patch.

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 we start migrating anything.

In order to make this work, I will detail some of the things that you must have done:

  • Install all the Microsoft pre-requisites
  • Install Oracle same version and fix (Some Sort order on both server) Very Important!!!!
  • Verify that the same configuration:

    • Oracle Listener
    • Oracle Net service Name
    • Verify that under the HOST file you have the IP and Server name Install BSI same version and fix if it has applied (Same Org name, in the same Disk drive and path)
    • Use the SAME dbowner name (such as oblicore) if you are replicating database information to a new DB.
  • Apply the Windows Update and verify that you apply the same fix on the other server
  • Only !! when you have finish the entire process of installing (Oracle and CA BSI) you should change the regional setting of the Server to the one you usually use.
This document assumes that 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.At the time this was written, BSI 8.3.5 (with cumulative patch 3) support up to Windows 2012 and Oracle 12.This assumes 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:1) install a new DB with the new installation and then migrate your data over or 2) if you are going to install with a new DB but then point the new APP and WEB to your old database, or 3) install the new APP and WEB while pointing to your old database which will bring your old installation down.There are obvious benefits and drawbacks to each of these options we will not go into depth on here.

1) Before you start any migration it is very recommended that the Server Source and Destination are backup in case of anything, it is all ways a good start to have this done before any migration or change so we can go back in case you do have any problem in the process. 

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 installation is working. Make sure you can login.

3) Stop all of the adapters in your source 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. We have some older script examples which used emp/imp for this but 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 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 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 services.