AEM 6 work with Oracle DB ? | Community
Skip to main content
S
srinivasan_m
October 16, 2015
Solved

AEM 6 work with Oracle DB ?

  • October 16, 2015
  • 12 replies
  • 7636 views

In AEM 6 upgrade document, I could able to see the information related to migeating to mongodb. Kindly confirm me that AEM 6 need mongo db only or will it work with Oracle DB also? As AEM 5.x is working with Oracle DB.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by smacdonald2008

    Out of the box - no - AEM does not work with Oracle. However - you can write a custom service (within an OSGi) that persists and queries data to and from an Oracle database.

    To do so - you have 2 choices:

    1 - you can use Java JDBC APIs to write an OSGi bundle to work with Oracle and write your own connection application logic. See these community articles (they use MySQL - but you can replace that with Oracle):

    http://helpx.adobe.com/experience-manager/using/persisting-cq-data-relational-database.html

    http://helpx.adobe.com/experience-manager/using/querying-persisting-cq-data-mysql.html

    2 - you can inject a DataSourcePool into an OSGi. Configure the DataSourcePool to work with Oracle. See this community article:

    http://helpx.adobe.com/experience-manager/using/datasourcepool.html

    Good luck!

    12 replies

    Show previous replies
    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    May 9, 2017

    HI,

    I would start with the documentation at [1], there another approach is choosen, see the "Usage" section.

    Jörg

     

    [1] https://sling.apache.org/documentation/bundles/datasource-providers.html

    therealsatz
    therealsatz
    Level 2
    May 9, 2017

    Jörg, I tried the other way as well to access the Datasource and even that method ends up having the Datasource as null. When the service event is getting registered without any errors when I click on save in the JDBC connection pool, it means that the JDBC connection is successful right? I'm still trying to figure what possibly is going wrong here. sad

    Terms & ConditionsAccessibility statement

    Loading footer...