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).
Related
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
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.
After installing a DB2 + WAS Liberty profile and the Mobile First server, we are trying to follow the Installing MobileFirst Server administration with the Server Configuration Tool steps.
At step 6, we're attempting to connect to a DB2 (v10.5) running on localhost:50000. After entering the hostname/port values - the message displayed in the panel is: "Invalid driver jar file name."
screenshot:
http://i.stack.imgur.com/LAoAx.png
DB2 V10.5
IBM MobileFirst Platform Server Configuration Tool 7.1.0.00.20150807-0630
IBM WebSphere Application Server Liberty Core - v8.5.5.7
IBM WebSphere SDK Java Technology Edition v7.0 for Libery 7.0.9.10
db2jcc4.jar was referenced during installation of the MobileFirst server components. Confirmed db2jcc4.jar and db2jcc_license_cu.jar exist in the WAS Liberty server profile
Anybody run into this?
Suspecting:
The Server Configuration tool isn't picking up the correct db2 jdbc jar file name .. bug?
The db2 driver jar name is misconfigured in a config file somewhere
Any pointers?
You need to re-enter the DB2 JDBC driver directory in the Server Configuration tool. Scroll down on the scren of the 'Database Settings' panel to have the text field to enter the directory.
I am trying to deploy multiple adapters to a Worklight Server in a production environment. When refreshing the console, the deployed adapters are missing.
What is the problem?
Can you please take a look at your Worklight Server log to see if any errors are displayed. I have seen in the past similar behavior when adapter procedures relied on security-tests, but the security tests were not defined properly in the authenticationConfig.xml file on the server side. In the server log I saw the following error:
"Failed to deploy adapter. This may be due to a JavaScript error in your adapter implementation"
If this is the case please update your authenticationConfig.xml on your production server to match the properties you have defined in your development environment. Also do these adapters deploy successfully in your development environment when running locally?
Make sure that the Studio the adapter was created in and the Server the adapter is deployed to are of the exact same build number
This is reason #1 for adapters to get deployed and then immediately get removed.
I have a Firebird 2.1.1 database deployed over a LAN. In a recent upgrade I used an FB internal function (COALESCE). When I was testing my Delphi app on my development machine there were no problems.
But when I tried to run a query on a production machine I received an error message telling me that the function (COALESCE) was unavailable.
Coalesce is a built in internal function in FB. It is not a UDF or a stored proc, it is built in.
Q: Why does a query using Coalesce work on my development machine but not a production machine?
Some more Info:
XP pro SP2 on both
My program is developed in Delphi 3.0 with BDE
BTW: I installed FB server on the workstation (production machine) and, low and behold, the query using Coaclesce works! I thought Coaclesce was an internal function?! I don't want to have to install FB Server on every machine. There are over seventy workstations in three different locations.
Normally I have FB (ver 2.1.1) installed on one machine running XP. This is my designated database server. All workstations running my app get their data from this server. I upgraded my app and changed the schema of the FB database that resides on my server that my client side app uses. One of the changes that I made was that I am using FB internal funcations for the first time. Specifically I am using function COALESCE. When I run my app on a workstation I get the following error message:
-SQL error code = -804
-Function unknown
-COALESCE
The app running on the workstation is running a select statement against the database on the server that uses COALESCE.
Here's the interesting part: The query containing COALESCE ran fine on my development machine (which is another workstation on our network) but not my users' workstations (production machines). So I asked myself "What's the different about my development computer?" Well it has FB server on it. So I installed FB server on a user's workstation (FB is now on our server + on the workstation running my app) and: I don't get the error anymore! My app is still using the server's database (not the workstation's) but it's as if by having a full FB server on the client workstation my app can now find the internal FB functions.
I have been assuming that FB internal functions are part of the server install. They don't need to be copied to workstations and they don't need to be declared. They are like SUM, MIN, MAX or AVG.
Q: Why don't Firebird Internal functions run on Firebird client conmputers?
The Firebird's client library "fbclient.dll" (or perhaps renamed as "gds32.dll") parse the statement and validates the SQL keywords that are used.
It is not necessary to install the server on the client machines.
What happened is that the machine was running with an old version of the client library (maybe BDE has been distributed with an old "gds32.dll") that not recognize the "COALESCE" keyword. When you installed the server version 2.1.1 it also install the updated client modules, and possibly replaced the old "gds32.dll" in the system directory for a "fbclient.dll" (option checked by default in the server installer) compatible with Firebird 2.1, renamed as "gds32.dll".
You can attempt to reproduce the problem, search for all copies of "fbclient.dll" and "gds32.dll" in the workstation, and then notice if they are really old version, and try replace only this specific files, without install the server in the client machines.