Skip to main content
H
harshav
December 24, 2021
Solved

New MariaDB Connected System Data source Name Not available !!!

  • December 24, 2021
  • 3 replies
  • 0 views

Hi Team,

We started to create a new Database schema using the Connected systems concept introduced in 21.3

However we have to use the Execute Store Procedures we need to provide the Data source Name : For example like jdbc/Appian

Like this i am unable to find out the Data source/JNDI Name for the Seperate schema which is created.

Could someone help me out with the datasource name of my schema created.

For Example the Data source Name / Schema name created in the DB is SchemaOne.

    Best answer by harshav

    Hi [mention:033c04acf46b4894b99c5553f35c56e0:e9ed411860ed4f2ba0265705b8793d05],

    We resolved this issue by calling the same schema credentials in Admin console and created a data source under data sources tab in integration section. Later i used that for plugins where the data source name is expected. This solved my issue of using a separate schema and the data source name.

    3 replies

    vincenzor8745
    vincenzor8745
    December 29, 2021

    Step are these:
    1. Create new schema (it seems you have already done) --> please annotate the string connection!
    2. Create new connected system for database and fill the string connection obtained at step 1.
        in this step you have to create a name for connected system.
    3. Using the connected system created at step 2 into a new Datastore (select connected system in datastore in high left listbox) and work as usual.

    you have done all of these step?

    C
    craigf603812
    December 31, 2021

    I too am currently facing this problem. I have followed the steps to set up a schema, and to create the connected system. If I use the name given to the connected system as the dataSourceName, i get an error in tomcat log saying 

    Name [XXX Data Source] is not bound in this Context. Unable to find [XXX Data Source].
    H
    harshavAuthorAnswer
    December 31, 2021

    Hi [mention:033c04acf46b4894b99c5553f35c56e0:e9ed411860ed4f2ba0265705b8793d05],

    We resolved this issue by calling the same schema credentials in Admin console and created a data source under data sources tab in integration section. Later i used that for plugins where the data source name is expected. This solved my issue of using a separate schema and the data source name.

      Terms & ConditionsAccessibility statement