Transaction launcher in CRM Web IC

Question

Hi,
We are trying to use transaction launcher in the WEB IC to call an R3 transaction. We have successfully managed in DEV and now we want to move across to QA for transport. But the handler class and config is done for DEV so far. In order to work this in QA, should we create/define the R3 QA system as logical system + RFC in our CRM Dev box and then transport ? Will it be required to be done for Prod as well then from dev?  is there any other recommended way of doing this.
Regards,
Vin

Answer 1

Transaction Launcher handler class user mapped logical system to connect to R/3 environment.
I dont think you can transport Logical System,RFC Connections from Dev to QA or QA to Prod.
So before you start testing on QA,make sure that logical system for R/3 is already defined and RFC Connection is established.All you need to do is make sure that mapped logical system is created with the same name you have in DEV.To define the mapped logical system follow the path
Easy Access->Interaction Center->Interaction Center WebClient->Administration->System Parameters->Defined Tx Launcher Log Sys and URL's.This is the easy way without changing your code in Handler Class.
If you have already established a mapped logical system and you dont want to create another then you can do some code change in the below mentioned handler class methods
1. CONSTRUCTOR.
** In the Constructor methos replace the OWNLOGSYS with 
  ** the available mapped logical system in your QA env
  property-name  =  
  cl_crm_ic_abox_constants=>mapped_logsys.
  property-value = 'OWNLOGSYS'. "#EC NOTEXT
  append property to gt_properties.
2. CLASS_CONSTRUCTOR .
** In the Constructor methos replace the OWNLOGSYS with 
  ** the available mapped logical system in your QA env
  gv_mappedlogsys =
    'OWNLOGSYS'. "#EC NOTEXT
3.GET_ACTION_DEFINITION .
** In the Constructor methos replace the OWNLOGSYS with 
  **the available mapped logical system in your QA env
   concatenate cl_crm_ic_abox_constants=>bor_action
              'BUS1006005'  "#EC NO_TEXT
              'EDIT'  "#EC NO_TEXT
              'OWNLOGSYS'  "#EC NO_TEXT
         into rv_result.
The same applicable for QA to Prod too.
Hope this helps.
Thirumala.