JCO Destination Creation

[Former Member]

Hi,

Another question when creating JCO destination:

When creating JCO destination for RAR, is it possible to specify a new name for it OR shoul we keep the name provided (i.e: VIRSAHR_MODEL & VIRSAHR_METADATA)?

The process for creating a JCO destination for ERM, CUP and SPM, is it the same as for RAR?

In the SPM Post-Installation guide it is said that use as "JCO Destination Name the Connector ID weu2018re using in RAR". What about this requirement?

Many thanks in advance. Best regards,

Imanol

[Former Member · Accepted solution]

And why within some PDF documents related with the post-installations steps, we can see the JCO destination renamed?

For example within RAR Post-Installation steps we can see the name "grc-rig-03_AR1_001" in the JCO Destinations list.

Many thanks in advance. Best regards,

Imanol

[Former Member · Accepted solution]

That is not renaming of the JCo destination. SAP NW converts the JCo name and then displays it in RAR when you create connector.

Regards,

Alpesh

[Former Member]

So, under a four GRC capabilities to be implemented scenario, do you mean that JCO destinations needs to be defined just once?

Thanks in advance. Best regards,

Imanol

[Former Member]

Hello Imanol,

Yes, you can use the created JCO destination in all 4 capabilities and this will enable your connectivity of backend to GRC components. Just like Alpesh mentioned, do not change the JCO names as then the integration will not work.

Regards, Varun

[Former Member]

Inamol,

Do not change the name of the JCo destinations as these names are being reffered inside RAR. SPM will use the same JCo destination as RAR so you won't have to create any new JCo destinations.

I do not recommend using any JCo destinations in CUP and ERM. Make sure to keep connector names in RAR, SPM, ERM and CUP exactly same otherwise the integration between all these modules would not work.

Alpesh