Change BWA connection to another BW system

Question

Hi,
We have a BWA that is connected to QBW system. We want (temporary) to disconnect it from QBW and connect it to TBW (Test system).
Do we have only to recreate the RFC connections to point to TBW ? are theres others steps  that have to done ?
Thank you for your help.
Sunny,

Answer 1

Hallo ,
Actually the process is so well described into  "Technical Operations Manual SAP NetWeaver BW Accelerator 7.20 for SAP NetWeaverBusiness Warehouse" at page 104 section :
Moving BW Accelerator Landscapes
Procedure
To move the box from one environment to another, proceed as follows:
1. Remove the test environment BWA indexes from the box. To do so, log on to the
development and/or test system, start transaction RSDDV, and delete all existing BWA
indexes. This step ensures that the queries in the development/test environment still
work, but are directed to the database.
2. Start transaction RSCUSTA and remove the RFC destination from the RFC BW
Accelerator entry.
3. Log on to one of the blades with the user <SAPSID>adm. Once you have deleted all
indexes from the previous systems, the index directory should be empty. Check that
the /usr/sap/<SAPSID>/TRX<instance_number>/index directory is empty. If
not, delete any remaining files and directories.
4. Start the TREX admin tool (stand-alone) [Page 137] on one of the blades by going to
/usr/sap/SID/TRX<instance_number> and starting TREXAdmin.sh or
TREXSetting.csh depending on your shell.
5. Go to the Connectivity tab page. Select the old connection and choose Remove
Connection. Select the checkbox for deleting the RFC destination in the old BW
system.
6. If RFCServer is on single threaded, select multi threaded in the combo box.
SAP NetWeaver BW Accelerator 7.20 November 2009
Administrating SAP NetWeaver BW Accelerator for Business Warehouse 105
7. Log on to all blades and check that the blades are all able to ping the new BW host by
name. If not, modify /etc/hosts/ accordingly.
8. Go back to the TREX administration tool (stand-alone) and go to the Connectivity tab
page. Configure the new connection by adding new logon information, and create an
RFC Destination in the new BW system. Choose Repair all and then Refresh until all
application servers have replicated the new configuration and everything is green.
9. Log on to the new BW system and start transaction RSCUSTA. Enter the RFC
destination in the RFC BI Accelerator field.
10. Go to /usr/sap/SID/TRX<instance_number> and call TREXSettings.sh or
TREXSetting.csh depending on the shell. Go to the exe/python_support
directory and start the BW Accelerator system check by executing the python
checkBIA.py script.
For more information, see BW Accelerator System Check [Page 119] and BW
Accelerator System Check Messages [Page 121].
11. Go back to the TREX administration tool (stand-alone) and go to the Configuration tab
page. Select Actions    Restart All Services & Delete All Indexes + Queues + Trace
Files.
12. Log on to the production system and start transaction RSDDBIAMON2
13. Choose BWA Connection Availability. The message in BWA Action Messages should
be BW accelerator services are fully available.
14. Start creating the BWA indexes using transaction RSDDV.
For more information, see Analyzing and Repairing BWA Indexes [Page 65] and
Using the BWA Index Maintenance Wizard [Page 39]
I did it for migrate one TREX/BWA 2 blades instance from QUAL to DEV and works ok.
Regards,
Paul