DataSource configuration in IBM Websphere used in application










0















My application is successfully deployed on test environment on IBM Websphere 6.1. I need to deploy the same application on my local machine. I am able to install my web application on IBM Websphere using admin console. But I am not able to configure datasource. Datasource is provided in the property file which is used successfully in test environment. Now, where do I configure datasource in IBM websphere, which will be used by my application. Datasource is not configured in web.xml or ibm-web-bnd.xmi. After deployment, I am getting following error in log files.




Connection Pooling Set up failed javax.naming.NameNotFoundException:
Context: 01HW357911Node01Cell/nodes/01HW357911Node01/servers/server1,
name: jdbc/SupplierNetDataSource: First component in name
SupplierNetDataSource not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0




I also created datasource in IBM Websphere admin console in resources successfully. But same is not used by my application.
I also created {Name Space Binding] in Environment->Naming path in admin console. But still same error is coming.



I also tried using tnsnames.ora file for datasource name, but was not successful.



Is there any way, to check the JNDI configured on test/dev unix server which can be replicated on local?










share|improve this question
























  • In your console, go to Resources, JDBC Providers and setup one. Inside the new provider, setup a JDBC DataSource, pointing to your database. Test the connection from the console, make that work first. Then make sure the JNDI name defined here matches what you declared in your EAR. The names must match. So it should be jndi/SupplierNetDataSource, not jdbc/SupplierNetDataSource I think (I can't see your EAR files).

    – Nic3500
    Nov 15 '18 at 13:01











  • I have setup a jdbc datasource pointing to my mb and tested successfully. Also, I changed dataSource name in property file as com.acg.dataSourceName = jndi/SupplierNetDataSource However, still same error is coming.

    – mahesh kumar
    Nov 15 '18 at 13:38
















0















My application is successfully deployed on test environment on IBM Websphere 6.1. I need to deploy the same application on my local machine. I am able to install my web application on IBM Websphere using admin console. But I am not able to configure datasource. Datasource is provided in the property file which is used successfully in test environment. Now, where do I configure datasource in IBM websphere, which will be used by my application. Datasource is not configured in web.xml or ibm-web-bnd.xmi. After deployment, I am getting following error in log files.




Connection Pooling Set up failed javax.naming.NameNotFoundException:
Context: 01HW357911Node01Cell/nodes/01HW357911Node01/servers/server1,
name: jdbc/SupplierNetDataSource: First component in name
SupplierNetDataSource not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0




I also created datasource in IBM Websphere admin console in resources successfully. But same is not used by my application.
I also created {Name Space Binding] in Environment->Naming path in admin console. But still same error is coming.



I also tried using tnsnames.ora file for datasource name, but was not successful.



Is there any way, to check the JNDI configured on test/dev unix server which can be replicated on local?










share|improve this question
























  • In your console, go to Resources, JDBC Providers and setup one. Inside the new provider, setup a JDBC DataSource, pointing to your database. Test the connection from the console, make that work first. Then make sure the JNDI name defined here matches what you declared in your EAR. The names must match. So it should be jndi/SupplierNetDataSource, not jdbc/SupplierNetDataSource I think (I can't see your EAR files).

    – Nic3500
    Nov 15 '18 at 13:01











  • I have setup a jdbc datasource pointing to my mb and tested successfully. Also, I changed dataSource name in property file as com.acg.dataSourceName = jndi/SupplierNetDataSource However, still same error is coming.

    – mahesh kumar
    Nov 15 '18 at 13:38














0












0








0








My application is successfully deployed on test environment on IBM Websphere 6.1. I need to deploy the same application on my local machine. I am able to install my web application on IBM Websphere using admin console. But I am not able to configure datasource. Datasource is provided in the property file which is used successfully in test environment. Now, where do I configure datasource in IBM websphere, which will be used by my application. Datasource is not configured in web.xml or ibm-web-bnd.xmi. After deployment, I am getting following error in log files.




Connection Pooling Set up failed javax.naming.NameNotFoundException:
Context: 01HW357911Node01Cell/nodes/01HW357911Node01/servers/server1,
name: jdbc/SupplierNetDataSource: First component in name
SupplierNetDataSource not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0




I also created datasource in IBM Websphere admin console in resources successfully. But same is not used by my application.
I also created {Name Space Binding] in Environment->Naming path in admin console. But still same error is coming.



I also tried using tnsnames.ora file for datasource name, but was not successful.



Is there any way, to check the JNDI configured on test/dev unix server which can be replicated on local?










share|improve this question
















My application is successfully deployed on test environment on IBM Websphere 6.1. I need to deploy the same application on my local machine. I am able to install my web application on IBM Websphere using admin console. But I am not able to configure datasource. Datasource is provided in the property file which is used successfully in test environment. Now, where do I configure datasource in IBM websphere, which will be used by my application. Datasource is not configured in web.xml or ibm-web-bnd.xmi. After deployment, I am getting following error in log files.




Connection Pooling Set up failed javax.naming.NameNotFoundException:
Context: 01HW357911Node01Cell/nodes/01HW357911Node01/servers/server1,
name: jdbc/SupplierNetDataSource: First component in name
SupplierNetDataSource not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0




I also created datasource in IBM Websphere admin console in resources successfully. But same is not used by my application.
I also created {Name Space Binding] in Environment->Naming path in admin console. But still same error is coming.



I also tried using tnsnames.ora file for datasource name, but was not successful.



Is there any way, to check the JNDI configured on test/dev unix server which can be replicated on local?







java websphere






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 15 '18 at 13:10







mahesh kumar

















asked Nov 14 '18 at 11:17









mahesh kumarmahesh kumar

13




13












  • In your console, go to Resources, JDBC Providers and setup one. Inside the new provider, setup a JDBC DataSource, pointing to your database. Test the connection from the console, make that work first. Then make sure the JNDI name defined here matches what you declared in your EAR. The names must match. So it should be jndi/SupplierNetDataSource, not jdbc/SupplierNetDataSource I think (I can't see your EAR files).

    – Nic3500
    Nov 15 '18 at 13:01











  • I have setup a jdbc datasource pointing to my mb and tested successfully. Also, I changed dataSource name in property file as com.acg.dataSourceName = jndi/SupplierNetDataSource However, still same error is coming.

    – mahesh kumar
    Nov 15 '18 at 13:38


















  • In your console, go to Resources, JDBC Providers and setup one. Inside the new provider, setup a JDBC DataSource, pointing to your database. Test the connection from the console, make that work first. Then make sure the JNDI name defined here matches what you declared in your EAR. The names must match. So it should be jndi/SupplierNetDataSource, not jdbc/SupplierNetDataSource I think (I can't see your EAR files).

    – Nic3500
    Nov 15 '18 at 13:01











  • I have setup a jdbc datasource pointing to my mb and tested successfully. Also, I changed dataSource name in property file as com.acg.dataSourceName = jndi/SupplierNetDataSource However, still same error is coming.

    – mahesh kumar
    Nov 15 '18 at 13:38

















In your console, go to Resources, JDBC Providers and setup one. Inside the new provider, setup a JDBC DataSource, pointing to your database. Test the connection from the console, make that work first. Then make sure the JNDI name defined here matches what you declared in your EAR. The names must match. So it should be jndi/SupplierNetDataSource, not jdbc/SupplierNetDataSource I think (I can't see your EAR files).

– Nic3500
Nov 15 '18 at 13:01





In your console, go to Resources, JDBC Providers and setup one. Inside the new provider, setup a JDBC DataSource, pointing to your database. Test the connection from the console, make that work first. Then make sure the JNDI name defined here matches what you declared in your EAR. The names must match. So it should be jndi/SupplierNetDataSource, not jdbc/SupplierNetDataSource I think (I can't see your EAR files).

– Nic3500
Nov 15 '18 at 13:01













I have setup a jdbc datasource pointing to my mb and tested successfully. Also, I changed dataSource name in property file as com.acg.dataSourceName = jndi/SupplierNetDataSource However, still same error is coming.

– mahesh kumar
Nov 15 '18 at 13:38






I have setup a jdbc datasource pointing to my mb and tested successfully. Also, I changed dataSource name in property file as com.acg.dataSourceName = jndi/SupplierNetDataSource However, still same error is coming.

– mahesh kumar
Nov 15 '18 at 13:38













2 Answers
2






active

oldest

votes


















1














WebSphere 6.1 reached end of service more than 5 years, do yourself a huge favor, move up to version 8.55 or 9, both of which are currently supported. When you said "datasource is provided in the property file...", I'm assuming you're referring to the procedure described in this IBM KnowledgeCenter topic. If so, you'll need to start the wsadmin command line tool and execute the steps indicated to create the datasource. Note, after running AdminTask.applyConfigProperties, you'll need to save the config using AdminConfig.save() and restart the server. As you mentioned, you can also create the datasource from the admin console, using the values in the datasource properties file as values, but you'll also need to create a JDBC provider to go with the datasource. If you're still having problems after applying the properties file, posting the contents of it here (less any userids/passwords) here would be the next step.






share|improve this answer























  • Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

    – mahesh kumar
    Nov 16 '18 at 7:33











  • That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

    – F Rowe
    Nov 17 '18 at 14:34











  • The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

    – mahesh kumar
    Nov 19 '18 at 12:23











  • From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

    – F Rowe
    Nov 19 '18 at 13:56











  • Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

    – mahesh kumar
    Nov 20 '18 at 15:04



















0














which scope did you created jdbc/SupplierNetDataSource data source ?






share|improve this answer






















    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298973%2fdatasource-configuration-in-ibm-websphere-used-in-application%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    WebSphere 6.1 reached end of service more than 5 years, do yourself a huge favor, move up to version 8.55 or 9, both of which are currently supported. When you said "datasource is provided in the property file...", I'm assuming you're referring to the procedure described in this IBM KnowledgeCenter topic. If so, you'll need to start the wsadmin command line tool and execute the steps indicated to create the datasource. Note, after running AdminTask.applyConfigProperties, you'll need to save the config using AdminConfig.save() and restart the server. As you mentioned, you can also create the datasource from the admin console, using the values in the datasource properties file as values, but you'll also need to create a JDBC provider to go with the datasource. If you're still having problems after applying the properties file, posting the contents of it here (less any userids/passwords) here would be the next step.






    share|improve this answer























    • Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

      – mahesh kumar
      Nov 16 '18 at 7:33











    • That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

      – F Rowe
      Nov 17 '18 at 14:34











    • The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

      – mahesh kumar
      Nov 19 '18 at 12:23











    • From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

      – F Rowe
      Nov 19 '18 at 13:56











    • Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

      – mahesh kumar
      Nov 20 '18 at 15:04
















    1














    WebSphere 6.1 reached end of service more than 5 years, do yourself a huge favor, move up to version 8.55 or 9, both of which are currently supported. When you said "datasource is provided in the property file...", I'm assuming you're referring to the procedure described in this IBM KnowledgeCenter topic. If so, you'll need to start the wsadmin command line tool and execute the steps indicated to create the datasource. Note, after running AdminTask.applyConfigProperties, you'll need to save the config using AdminConfig.save() and restart the server. As you mentioned, you can also create the datasource from the admin console, using the values in the datasource properties file as values, but you'll also need to create a JDBC provider to go with the datasource. If you're still having problems after applying the properties file, posting the contents of it here (less any userids/passwords) here would be the next step.






    share|improve this answer























    • Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

      – mahesh kumar
      Nov 16 '18 at 7:33











    • That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

      – F Rowe
      Nov 17 '18 at 14:34











    • The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

      – mahesh kumar
      Nov 19 '18 at 12:23











    • From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

      – F Rowe
      Nov 19 '18 at 13:56











    • Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

      – mahesh kumar
      Nov 20 '18 at 15:04














    1












    1








    1







    WebSphere 6.1 reached end of service more than 5 years, do yourself a huge favor, move up to version 8.55 or 9, both of which are currently supported. When you said "datasource is provided in the property file...", I'm assuming you're referring to the procedure described in this IBM KnowledgeCenter topic. If so, you'll need to start the wsadmin command line tool and execute the steps indicated to create the datasource. Note, after running AdminTask.applyConfigProperties, you'll need to save the config using AdminConfig.save() and restart the server. As you mentioned, you can also create the datasource from the admin console, using the values in the datasource properties file as values, but you'll also need to create a JDBC provider to go with the datasource. If you're still having problems after applying the properties file, posting the contents of it here (less any userids/passwords) here would be the next step.






    share|improve this answer













    WebSphere 6.1 reached end of service more than 5 years, do yourself a huge favor, move up to version 8.55 or 9, both of which are currently supported. When you said "datasource is provided in the property file...", I'm assuming you're referring to the procedure described in this IBM KnowledgeCenter topic. If so, you'll need to start the wsadmin command line tool and execute the steps indicated to create the datasource. Note, after running AdminTask.applyConfigProperties, you'll need to save the config using AdminConfig.save() and restart the server. As you mentioned, you can also create the datasource from the admin console, using the values in the datasource properties file as values, but you'll also need to create a JDBC provider to go with the datasource. If you're still having problems after applying the properties file, posting the contents of it here (less any userids/passwords) here would be the next step.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 15 '18 at 14:17









    F RoweF Rowe

    1,3891610




    1,3891610












    • Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

      – mahesh kumar
      Nov 16 '18 at 7:33











    • That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

      – F Rowe
      Nov 17 '18 at 14:34











    • The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

      – mahesh kumar
      Nov 19 '18 at 12:23











    • From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

      – F Rowe
      Nov 19 '18 at 13:56











    • Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

      – mahesh kumar
      Nov 20 '18 at 15:04


















    • Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

      – mahesh kumar
      Nov 16 '18 at 7:33











    • That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

      – F Rowe
      Nov 17 '18 at 14:34











    • The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

      – mahesh kumar
      Nov 19 '18 at 12:23











    • From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

      – F Rowe
      Nov 19 '18 at 13:56











    • Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

      – mahesh kumar
      Nov 20 '18 at 15:04

















    Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

    – mahesh kumar
    Nov 16 '18 at 7:33





    Following is property file values com.acg.productLibrary= ALSTOMDBA. com.acg.schemaName = ALSTOMDBA. com.acg.dbType = ORACLE com.acg.connectionStringDev = com.acg.oracleUserId = com.acg.oraclePassword = com.acg.dataSourceName = jndi/SupplierNetDataSource I have created a jdbc provider for datsource named SupplierNetDataSource using admin console. It is connecting successfully. However, same is not used by my application. In logs, getting null connection. On login page, I am getting following error: Error 500: com.andrewscg.frameworks.RTC_global (initialization failure)

    – mahesh kumar
    Nov 16 '18 at 7:33













    That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

    – F Rowe
    Nov 17 '18 at 14:34





    That's not a properties file that WebSphere can process to create a datasource. You said that you have created both a jdbcprovider and a datasource using the admin console, what's the purpose of the properties file then? I think you're getting confused by the sequence required to configure this, the properties file seems to be superfluous. 1) from admin console, create jdbc provider for Oracle. 2) from admin console, create a datasource that uses above jdbc provider, with jndiName of jdbc/SupplierNetDataSource. 3) save config, restart server

    – F Rowe
    Nov 17 '18 at 14:34













    The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

    – mahesh kumar
    Nov 19 '18 at 12:23





    The application reads datasource name from properties file. Now, IBM websphere will look for the database using data source name. Datasource name (containing values like url, id, password etc) is created using admin console in ibm websphere. But same is not used by the application.

    – mahesh kumar
    Nov 19 '18 at 12:23













    From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

    – F Rowe
    Nov 19 '18 at 13:56





    From the admin console, you've created a JDBCProvider for Oracle, and a Datasource with JNDI name " jndi/SupplierNetDataSource" using that JDBCProvider. You can press the "Test Connection" button on the datasource panel and the connection works? And your application is looking up "jndi/SupplierNetDataSource"?

    – F Rowe
    Nov 19 '18 at 13:56













    Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

    – mahesh kumar
    Nov 20 '18 at 15:04






    Application is looking for datasource named "jndi/SupplierNetDataSource". Error coming is "First component in name jndi/SupplierNetDataSource not found". logs are already present in the question. Same error is still coming.

    – mahesh kumar
    Nov 20 '18 at 15:04














    0














    which scope did you created jdbc/SupplierNetDataSource data source ?






    share|improve this answer



























      0














      which scope did you created jdbc/SupplierNetDataSource data source ?






      share|improve this answer

























        0












        0








        0







        which scope did you created jdbc/SupplierNetDataSource data source ?






        share|improve this answer













        which scope did you created jdbc/SupplierNetDataSource data source ?







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 9:02









        JosephJoseph

        113




        113



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298973%2fdatasource-configuration-in-ibm-websphere-used-in-application%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            這個網誌中的熱門文章

            How to read a connectionString WITH PROVIDER in .NET Core?

            Node.js Script on GitHub Pages or Amazon S3

            Museum of Modern and Contemporary Art of Trento and Rovereto