none
Oracle MA: Transition From Extensible Connectivity to Oracle Database Type Agent RRS feed

  • Question

  • This is a difficult question for me to come up with the correct title, but this is what I am trying to find out. We have an Oracle management agent that was initially set up as an Extensible Connectivity type agent. Some of the functionality in the code associated with that agent is not needed any longer, so Is it possible to switch/convert that connector to an Oracle Database type agent? And if so, how do I go about doing that?
    Thursday, November 21, 2019 9:46 PM

All replies

  • Install Oracle Client. Create the ORA File. Create new Oracle MA and map the functionalities you want.

    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Friday, November 22, 2019 9:55 PM
    Friday, November 22, 2019 9:55 PM
  • Are you referring to the .ora files like tnsnames.ora, sqlnet.ora, etc? If so, we already have those files along with Oracle client 11g installed with the administrator option since they were needed by this extensible connectivity based Oracle MA at the time of the original deployment. All the attribute mappings have since been changed to be handled bydeclarative sync rules since we only needed very simple data sync with no data transformation. The only part of the original code that is still being used is what handles the connection to the database and the data retrieval.
    Monday, November 25, 2019 3:29 PM
  • Ok, so what is the question now?

    Nosh Mernacaj, Identity Management Specialist

    Monday, November 25, 2019 3:32 PM
  • I was just providing additional information about my environment. That was all I was trying to do to make sure I got the correct answer from you. Wrong questions with missing information lead to wrong answers, right? Thus I am just making sure I provided all the information you might need to provide me the correct answer.

    I did have a question about the ORA files, and I asked you if you were referring to tnsnames.ora and/or sqlnet.ora. If so, then I already have those files.

    I need you to understand I don't have the experience with this product that you do! Thus I do need your help, but you can only help me if I give you all the facts. What I am still confused about is with the creation of a new connector and consequently connector space, and the implication of that to the data already in the metaverse since I will eventually end up deleting the original connector space. Is that the only route, or is it possible to simply change the connector type from extensible connectivity to Oracle Database and change the configuration parameters? I know the anchor attribute will be the same.

     


    Tuesday, December 3, 2019 5:29 PM
  • SHORT ANSWER YES.  It is as if this was another system like SQL, for instance.

    When you ask the queation you asked, people assume you know as much as connector space.

    I suggest that if you dont understand the basics, you should not attempt such task.


    Nosh Mernacaj, Identity Management Specialist

    Tuesday, December 3, 2019 6:01 PM
  • Thank you! I will follow your advice, and if I feel like I cannot handle this task, I will find someone else like a contractor to do it.
    Tuesday, December 3, 2019 7:32 PM