Activate CHaRM using Virtual Systems in Landscape

[former_member207465]

Is it possible to activate a CHaRM project against a landscape that

contains virtual systems?

We currently have a Development system (DEV) with a virtual Test system

(QAS) and virtual Production system (PRD). These systems are marked as

Virtual in TMS and SMSY System Landscape. We have added these systems t

o

the Logical Components and created a new Solution Manager project and

want to activate CHaRM against this scenario. .

The TMS routes are defined with Dev -> QAS(virtual) -> PRD(virtual). Is

this scenario possible? Do the standard CHaRM activation checks (RFC's,

Authorizations, etc) get bypassed because these systems are virtual?

When activating CHaRM, we still receive the error that no consolidation

system exists for our Dev system even though the TMS routes have been

defined properly. However, since these systems are virtual, we cannot

add client information to them.

Thanks

[raguraman_c · Accepted solution]

Hi,

>

> Is it possible to activate a CHaRM project against a landscape that
> contains virtual systems?
> The TMS routes are defined with Dev -> QAS(virtual) -> PRD(virtual).  Is
> this scenario possible?  

A virtual system cannot export any TR. So any request imported to QAS cannot be exported

So

>

> The TMS routes are defined with Dev -> QAS(virtual) -> PRD(virtual).  Is
> this scenario possible?  

is not possible.

Hope this answers your question.

Feel free to revert back.

--Ragu

[Miguel_Ariño]

Please check How to create a virtual system in SAP Solution Manager 7.2 | SAP Help Portal , for details about the setup involved.

[debosmita93]

Yes this is in fact possible. I have built a similar Solution for Charm with 2 virtual system. As per the 2811220 note we can deploy charm on a landscape having 2 Virtual systems. But the Dev system HAS to be a live system. I faced the same issue while building this solution. The resolution is stated below:

1. Make sure the Virtual systems created have Client mentioned in the LMDB.

2. Maintain the same Client numbers in the STMS transport teack for both Qas and Prd Virtual system. Activate and distribute the settings and your issue will be resolved.