Comments on: ExaCC OCI integration with OEM 13.5 Cloud Control installed On-premises. https://www.dbi-services.com/blog/exacc-oci-integration-with-oem-13-5-cloud-control-installed-on-premises/ Fri, 11 Apr 2025 09:38:02 +0000 hourly 1 By: Tomek Sikorski https://www.dbi-services.com/blog/exacc-oci-integration-with-oem-13-5-cloud-control-installed-on-premises/#comment-3895 Fri, 11 Apr 2025 09:38:02 +0000 https://www.dbi-services.com/blog/?p=35013#comment-3895 In reply to Wim.

Hi Wim
base on OCI documentation, https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/cliconfigure.htm
you can create another section as another profile for another tenancy :
[DEFAULT]
compartment-id = ocid1.compartment.oc1..
..
..
[ANOTHER_SECTION]
compartment-id = ocid1.compartment.oc1..
..
..
..
also create additional named credentials in OEM for this tenant, then during discovery choice this credentials.

]]> By: Wim https://www.dbi-services.com/blog/exacc-oci-integration-with-oem-13-5-cloud-control-installed-on-premises/#comment-3894 Thu, 10 Apr 2025 13:19:56 +0000 https://www.dbi-services.com/blog/?p=35013#comment-3894 Hi Tomec,

first thx for your post.
Works perfectly.

I do have a question though.
We have 2 different tenants.

How can I add a second tenant here, so OEM can read from 2 differnet ones?

>> from your example <<
oracle@agent1:~/# vi .oci/config
[DEFAULT]
user=ocid1.user.ooracle@agent1:~/#
fingerprint=.*********************************
tenancy=ocid1.tenancy..*********************************
region=eu-zurich-1
key_file=/home/oracle/.oci/oem_ro.pem

regrads
Wim

]]>