Installed IBM Mobilefirst 8 server with WAS 8.5.5.12 using Apache derby database.
Facing below error while checking connection of datasource which are created for mobilefirst server :
java.lang.Exception: DSRA8101E: DataSource class cannot be used as one-phase: ClassCastException: org.apache.derby.jdbc.AutoloadedDriver40 incompatible with org.apache.derby.jdbc.InternalDriver
Working fine with mysql database.
While this message would normally indicate that a data source implementation class was specified that does not implement javax.sql.ConnectionPoolDataSource, I don't believe that is the case here based on the classes identified in the exception message. Another possible cause is that multiple copies of the Derby JDBC driver are on the classpath at the same time. It should be noted that WebSphere Application Server traditional ships a copy of the Derby JDBC driver. If you do have two copies, is it possible to switch to only using the one that is shipped with the application server? If that is not possible, you might be able to work around this by selecting the option to isolate your JDBC provider.
For use with MFP 8.0 standalone server with Websphere Application Server 8.5.5.5, use DB2,MySQL or Oracle
Related
I use an online database which I am able to connect through altium or dbVisulizer. I want to add an instance to that database using ODBC Data source in windows, but it fails. The steps I followed are pictured below:
Any idea why is this happening?
Additional information:
Altium use the following information: ConnectionString = Provider=SQLNCLI11.1; User ID=alib_WFC5AKIMTQCL; Password="*********"; Initial Catalog=altium_library; Data Source=db.altiumlibrary.com,1433; Initial File Name=""; Server SPN=""
After connecting through dbVisulizer I have the following information: The server version is: Microsoft SQL Server 14.00.2027 Microsoft JDBC Driver 9.2 for SQL Server 9.2.1.0
I don't believe this is possible. However, in most cases, if you can connect to sql server via jdbc drivers, then you can connect to the same sql server with odbc.
Access does not support jdbc, and in most cases that driver is Java, and thus you would be talking about a java enabled client side software.
For example, I have a instance of SQL server. I direct connect from Access over the network to SQL server - using ODBC drivers.
However, my android phone? Well, I use jdbc type 4 drivers, and thus my android phone can also direct connect to that same instance of sql server on the network.
However, there is no support for Access to connect to SQL server using jdbc drivers, but then again, if that is SQL server in question, then both jdbc, and odbc should be able to connect to that running instance of SQL server.
Now, you might be able to setup and run what is called a jdbc "bridge" connection. This would require that you install + setup a bridge on your computer. (and that bridge runs like a mini web server - it is NOT just a driver, but a web like "service"/"server" that you have to have running. In fact, it quite much the reverse that such a bridge is for. So, for example, if you running that bridge, then it would be possible for jdbc drivers to in fact connect to the access database (this would be a type 2 (or 3???) jdbc driver/connection.
So, to be clear, a jdbc type 4 connection is NOT possible to Access, since they require a so called "socket" (tc/ip) connection. Access is file based, so you don't ever connect to a access database, but you OPEN IT as a file. However, as noted, you are talking about Access connecting to the server anyway.
However, Access does not support, nor use nor have any means to use and consume a jdbc driver. But then again, it stands to reason that any database from MySQL, Oracle, PostgrSQL, SQL server, and more ALL HAVE ODBC drivers.
So it begs the question, why a ODBC driver would not be used here?
But, as noted, since Access supports ODBC drivers, and not jdbc drivers, then the answer is no - Access cannot use such drivers.
We are unable to send the data to SQL database using SQL adapter in BizTalk.
The error we are facing is:
error in initializing provider [DBNETLIB]ConnectionOpen(SECCreateCredentials()]SSL Security error
We have recently enabled TLS 1.2 and disabled lower versions on both BizTalk and SQL servers.
We checked that SQL server native client version 11 was also installed in both servers.
We have tried creating ODBC connection using SQL serve native client 11 and that also didn't work.
Can you please suggest what is causing the issue and any other changes needs to be implemented.
I have WL6.0 project that contains SQL adapter. The adapter has procedure with requestTimeoutInSeconds="240" and I am trying to migrate that project to WL7.1.
As per Adapter timeout and concurrency article on IBM Knowledge Center, I have to use JNDI config instead.
The requestTimeoutInSeconds attribute of and
elements is ignored. Use JNDI configuration instead.
Can any one provide an example how to implement that?
I am working on MobileFirst Studio 7.1 and I imported the project with no errors.
Note that you are developing in MobileFirst Studio, which utilizes the Liberty application server as its underlying server.
Locally such changes are not required, since you're working locally...
This will become important once you start on moving to testing and production environments.
This means that you will need to update the server.xml of your WebSpher full profile/Liberty profile - not the server.xml of the server in MobileFist Studio.
You you can find documentation for this in the Liberty docs, here: http://www.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_dep_configuring_ds.html
Note that the setup you need to do differs based on your database type: MySQL, Oracle, DB2, ... You can find examples for each database type in the link above.
I am working with mobile first application and I have set it locally. I left server idle for about 15 minutes and then it is gives me configuration error.
When then I deploy adapter below error get started coming and not getting stop and adapter is not getting deploy.
Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
I tried clean the server, projects, restart studio every thing.
I have changed the workspace three time.
1) Eclipse - Version: Luna Service Release 2 (4.4.2) Build id: 20150219-0600
2) Mobile first : 7.0.0.00-20160307 - 1716
3) OS : Windows 8
Try killing the Java process or restarting the computer. You should then be able to successfully start the server and deploy the adapter.
Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
This is a common error or warning while server is downloading the artifacts(wlapp, adapter etc.) from database.
My actual problem was with database. WebSphere liberty with mobilefirst is giving derby as default database and My server was not working properly with it.
I changed it to MySQL database and it is working fine.
Successfully installed IBM MobileFirst 7.0 Server on following environment, and also, a runtime environment was created step by step and deployed successfully in this server (with GUI of MobileFirst Platform Configurion Tool shows deployed):
CentOS 6.4
MobileFirst Server 7.0
jdk-7u79
MySQL 5.6.24
Apache Tomcat 7.0.62
But I got a No runtime environment deployed in this server from worklightconsole.
I can't find any logs show the error messages. Also,the WL related tables was created automatically in MySQL databases and Worklight related folder generated in Tomcat path, too.
The GUI of MobileFirst Platform Configurion Tool shows deployed:
The cause to the failure may be due to an ssoExpiredLoginContextsCleanupTask error which can cause the server to not load:
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Cannot
execute statement: impossible to write to binary log since
BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine
limited to row-based logging. InnoDB is limited to row-logging when
transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
{prepstmnt 1015602967 INSERT INTO CLUSTER_SYNC (ID, hostVmId,
updateTimestamp, version) VALUES (?, ?, ?, ?) [params=(String)
ssoExpiredLoginContextsCleanupTask, (null) null, (long) 0, (long) 0]}
[code=1665, state=HY000]
To correct it, it is suggested to follow these instructions: http://www-01.ibm.com/support/docview.wss?uid=swg21695572, which are also relevant to MFP Server (and not just Application Center Server).