IBM MobileFirst Platform 7.0 - SQL Adapter deployment failure in remote server

0
votes

I have a simple SQL adapter, in a simple helloWorld application. All this app does is read a row from the database table and display it on the homepage. It works fine, deploys successfully in my local development server and I can see the data on my app homepage preview. However, when I try to deploy the adapter in a remote MobileFirst Server from the MobileFirst Console by uploading the ‘.adapter' file, it gives me the error:

FWLSE3064E: The "xml" file is missing

I have not been able to find what this error actually means and how can I fix it.

messages.log: http://pastebin.com/LqyRqid6
server.xml: http://pastebin.com/ZZy6Zkkv

1
ibm-mobilefirstmobilefirst-adapters
To further debug the issue, upload the full messages.log file from the remote server. – Idan Adar
Its a long error message, have edited the original message and pasted the actual error from the 'messages.log' file. I hope it gives a better insight to the problem. – A.K
Thanks, but I asked for the full messages.log file and not for an abbreviated version of it. Could you please upload the file as requested? Would also help to see your server.xml and well as information on the used application server - WAS/Liberty/Tomcat (full build number), Java version etc... – Idan Adar
its Liberty WebSphere Application Server 8.5.5.4 and java.version = 1.7.0. The file itself is 4Mb, wasnt able to paste and share through pastebin either, any suggestion on how to upload that file so you can view it? – A.K
You can use Dropbox, Google Drive, Mega and the like to host the messages.log and server.xml files. Also, what is the MobileFirst version (number + full build number). – Idan Adar

1 Answers

0
votes

The adapter you are trying to deploy is from MobileFirst Platform Foundation 7.0 (as can be seen in the supplied .adapter file), however the server version is Worklight 6.2.0.01 (as can be seen in the supplied messages.log), or at least the deployed project .war file.

Update the server installation to run v7.0.0.0 as well (or deploy the correct .war file). I suspect the deployment will then pass.