We are wanting to connect to an external Database e.g. Oracle using the SQL Adapter in the Mobile Foundation service (not as the repository for the Mobile Foundation configuration).
As per:
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/adapters/javascript-adapters/js-sql-adapter/
And from that link:
dataSourceJNDIName: Optional. Connect to the data source by using the JNDI name of a data source that is provided by the application server. The adapter takes the connection from the server connection pool that is associated with the JNDI name. Application servers provide a way to configure data sources. For more information, see Installing MobileFirst Server to an application server. For example:
<connectionPolicy xsi:type="sql:SQLConnectionPolicy">
<dataSourceJNDIName>my-adapter-ds</dataSourceJNDIName>
</connectionPolicy>
During our implementation of the mobile application, we encountered SQL Adapter connectivity problems resulting in poor user experience and quality of service. We want to configure the SQL connection using a connection pool so we have greater control over the connection e.g. concurrency and timeouts.
| Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
There are two ways of connecting to SQL DB via SQL adapter:
1) Define the connection strings and credentials directly in the adapter.xml. Here there is no control over any tuning parameters.
2) Define a datasource in the application server and use it to connect. This allows applying all performance tuning parameters to the datasource ( outside MFP, at application server level) - connection pool, timeouts etc. Customer should adopt this approach. This is what customer mentioned above by setting dataSourceJNDIName