Quantcast
Channel: SCN : Popular Discussions - SAP NetWeaver Visual Composer
Viewing all articles
Browse latest Browse all 1353

System aliases and "destinations" in VC7.31

$
0
0

Hi,

 

We are trying to migrate from Visual Composer 7.0 system to Visual Composer 7.3. Our new VC system is currently 7.3 EhP 1 with SP 08 patch 2.

 

On our old VC system, we used a "System Alias" to connect to a backend "R/3" system (Netweaver AS ABAP).  The way the system alias worked, it was defined in the portal to point to a particular backend. This allowed for deploying the model on multiple portals that might have different backend systems - typically, to handle Development, QA, and Production. For example, in the dev portal, the alias "ABC123" points to the dev R/3 system, in the QA portal the same alias "ABC123" points to the QA backend system, and in the production portal the same alias "ABC123" points to the Production backend system.

 

In the new system, my Basis person says he's configured the RFC destinations and the aliases to match what we had in the old system. However, in the Visual Composer "seach" panel when I select the option "R3 Data Services" all I see is the destinations (the system id's of the development backends). I do not see the system aliases in the list. I see the term "system alias" used all over the documentation so I am expecting to see the aliases in the list, not the destinations. However Basis insists it is configured correctly, and that perhaps by "system alias" the documentation is only referring to a specific RFC destination. 

 

Shouldn't I be seeing the system aliases in the search panel, not the destinations? Can you suggest what might be wrong if I should be seeing the aliases but am not?

 

Thanks,

 

Margaret


Viewing all articles
Browse latest Browse all 1353

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>