Updating Connection Details

FlexNet Manager Suite 2022 R2 (On-Premises)

You can change all details and credentials for connection to the Oracle Enterprise Manager instance.

When the OEM adapter is first run, it encrypts the connection details used to access the Oracle Enterprise Manager implementation. Therefore, the process to edit the connection details is different, based on whether the OEM adapter has been run since the connection details were last recorded. You can tell whether this is so by looking in the configuration file.

The details are all stored in the <connectionStrings> element of the configuration file.

1. If the OEM adapter has been run since the details were recorded in the configuration file, the encrypted <connectionStrings> element appears similar to this:

   <connectionStrings configProtectionProvider="DataProtectionConfigurationProvider">
       <EncryptedData>
         <CipherData>
           <CipherValue>AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAeNhcGMAVK0uVGNTqOg/WbQQAAAACAA
              AAAAADZgAAwAAAABAAAACTO9kpn6BptpLvsXExg1UBAAAAAASAAACgAAAAEAAAAELCyiwz5A
              XZw9xZXfEPiAAAAgAAPJQYe+G9AfScFMJTYgA0NDbAgZdRA9nB91DN42A1xjeCskUs9+KNjV
              U1PSFRV4ujta40evf3IOZy5odyHsIrJRCKOOGdhDb1wh4ISEkpJk/QDna6LeCbbtXXsQK2Lo
              AHQc/plz77UkQZxnxkL5ElPIGHl6AojEXT2F5NGjElJX6GXbUXQDkNnDfi2o6XI/CDbX8gCu
              MonY1cTLYGe6+AQPpDgcY3rA02ZFOs7/Zb0cKOw7IoZdB6H8OIvrClSzqNkVBd3YfLhP/KOr
              kQFP8orqj54BJW74E1v3VUZnte1ESgLA5MYb/F9Ah3M5xi2Q6ITXOQmVRGESrivsdqr6nyGz
              5APx2yVBuEcoVhpOMYURbEbBSW+6/aydg8nY1DrcMzkPlXiZ0CQs4yZYHSWt3+bFEN30xh6X
              KFH7Tpc8e5y9Tq1Bhwk+Kw6AFfZhcdewApJ4ZkGAr4ixE6gNqWXnomk2puKNFImhJfqLLIuQ
              x9T00Uu2bjJ9Y+dUlrcuov12hQXOCh9nqOdmeIQHPXgw8//eHYOzwy2TgMcq2M2LxXRbQqCT
              eWtlP1ucJVyct9gnJlk2L3FSBNgMu1C9mncR7MsGDBWoQMXnwC5+Y6P1GT45sPOedBQvIQIT
              j7MCuzfgDD1R9c7w1gejTGmrl3Kmf33tGPMRYPV7CPNET3DUV9AGQUAAAAaIEkjyqfExrbei
              YJvG2usqYO3Nk=</CipherValue>
         </CipherData>
       </EncryptedData>
     </connectionStrings>
   

   In this case, delete the entire element and replace it with a plain text version as shown below.
2. If the OEM adapter has not been run since the configuration file was changed, it has a plain text form similar to this (line wrapping has been added here for legibility). Replace the italicized placeholders with your own values, as described below. Keep the connectionString attribute all on one line.

   <connectionStrings>
       <add name="OEMConn" 
           connectionString="Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
                            (HOST=HostIPAddress)
                            (PORT=PortNumber))
                            (CONNECT_DATA=(SERVICE_NAME=ServiceName)));
           User Id=AccountName;Password=UnencryptedPassword;"></add>
       </connectionStrings>
   

   where the following details should be confirmed with your Oracle administrator:

   • HostIPAddress is the IP address of the Oracle server hosting Oracle Enterprise Manager
   • PortNumber is the port that the OEM adapter should use to query Oracle Enterprise Manager
   • ServiceName is the service name established when Oracle was installed on the Oracle server
   • AccountName is the account (user name) that the Oracle administrator has established for accessing Oracle Enterprise Manager
   • UnencryptedPassword is a plain text rendition of the password for the same account (remembering that all the connection details are encrypted together as soon as the OEM adapter runs next).
3. Save the amended configuration file.
   The Password Store: Password Filter dialog displays.
4. Use the Windows schedule task interface to run a test of the OEM adapter to confirm that the connections details were correctly entered.