Working on an isolated Linux machine, no internet access.
I am installing MobileFirst Server v7.0, WAS Liberty and IBM Java.
Having attached my repositories to Installation Manager I select an option to install. Click Next, and nothing further happens.
I see various solutions offered all of which are concerned with avoiding checking for update sites on the internet. I have followed all these, checked in the Installation Manager logs, see no error messages.
Any suggestions?
We were using v1.7 of Installation Manager, installed as adminsitrator.
We moved up to v1.8.2.1 installed as our user. It now works. Whether that's a version problem or an ownership problem I can't say.
javascript,mobilefirst,mobilefirst-server
WORKLIGHT_IS_CONNECTED and WORKLIGHT_IS_DISCONNECTED get fired only if the server state changes. So if you're sending requests to the server and then for some reason it's unreachable, the _DISCONNCETED event will get fired. If you then send a request and the server is successfully pinged, the _CONNECTED event will get fired....
mobilefirst,mobilefirst-adapters
you are missing an "item" in your javascript method. The code below should work properly. var param = [{ ....... "intestatari": { "item": children}, ....... }]; ...
worklight,mobilefirst,java.util.logging,websphere-liberty,mobilefirst-server
This is not related to MobileFirst but to the underlying application server that handles the logs creation. AFAIK not WebSphere full profile nor WebSphere Liberty profile provide the ability to separate logs based on their contents. What you could do is create your own tool/script that will go over the...
mobilefirst,mobilefirst-server,mobilefirst-console
Finally this issue was solved by setting max_allowed_packet = 30M and binlog_format = mixed in mysql's my.cnf file....
windows-phone-8.1,mobilefirst,weinre
With a new fresh application all worked fine. The investigation with console logs showed that the error came from WL.Client.connect() call. Anyway I deleted windowsphone8 enviroment, re-created and worked now it works. Also the line connectOnStartup: false, was commended I've reenabled but I don't think this was the problem.
Make use of adpaters in this Scenario. Have an HTTP adapter. In that use the adaptername.js file to create variable and assign your URL. Have a procedure which send these values to your client side. At the start of the application try to connect to your adapter and try to...
mobilefirst,mobilefirst-installation
We were using v1.7 of Installation Manager, installed as adminsitrator. We moved up to v1.8.2.1 installed as our user. It now works. Whether that's a version problem or an ownership problem I can't say....
mobilefirst,mobilefirst-adapters
This question is completely unrelated to your SQL adapter. The problem here is that you have used a href to navigate to another HTML file. By doing so you have exited the scope, or context, of the MFP framework, which is why you are unable to use MFP API methods...
Sorry For the Wrong answer first. You were using the wrong code to generate the .wlapp file the ant script is below. <project default="change"> <target name="change"> <taskdef resource="com/worklight/ant/defaults.properties"> <classpath> <pathelement location="worklight-ant-builder.jar"/> </classpath> </taskdef> <native-app-builder sourceFolder="C:\Workspace\Test\apps\Test" DestinationFolder="bin" worklightServerHost="http://111.111.111.111:10080"> </native-app-builder>...
mobilefirst,mobilefirst-server
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...
mobilefirst,mobilefirst-studio,mobilefirst-cli
Did you make sure to place a .gitkeep file in the java-adapter-folder\lib folder? The folder by default is empty and GIT does not preserve empty folders, and so when downloading this project from GIT the folder will be missing, but it may be required for the build process. Try adding...
mobilefirst,mobilefirst-appcenter
Finaly I got it working, the error was that I added the group name into <!-- Declare the IBM Application Center Console application. --> <application id="appcenterconsole" name="appcenterconsole" location="appcenterconsole.war" type="war"> but correctly is to add here: <!-- Declare the IBM Application Center Services application. --> <application id="applicationcenter" name="applicationcenter" location="applicationcenter.war" type="war"> So...
This problem was caused by referencing nonexistent adapter. I removed one of deprecated adapters from the project but forget to edit build.xml file.
It is not possible in MobileFirst Platform Foundation, and in general, to have an application uninstall itself. At the very least you could write a service in Android to do the timer, but not in iOS (maybe only in iOS 8 with app extensions), but still - your scenario is...
jquery,twitter-bootstrap,webview,mobilefirst,mobilefirst-adapters
I had similar issue and the problem was the Liberty profile configuration on my Windows 2012 server. The data returned by the SQL adapter was presented in the phone as gibberish (wrong characters). The data wasn't native english of course. I assume your production server is indeed Liberty profile v8.5+....
mobilefirst,mobilefirst-server
Only IBM Customers and Business Partners can download the server components. These components can be download from either the IBM Passport Advantage website or the IBM Fix Central website. Download IBM Installation Manager Download the GM version of the release you'd like to install Download the latest iFix version of...
Unfortunately no, the Studio/CLI tools do not provide the ability to not-rebuild certain artifacts in a build process. Each build request will re-request all artifacts and re-generate the resulting .wlapp/native folder. Sounds like a good feature request: developer.ibm.com/mobilefirstplatform/help On a personal note: I would just not use Sencha :-) in...
mobilefirst,mobilefirst-adapters
I think you are confusing how you invoke/test the adapter, with what verb it uses on the back-end system it is calling. You are testing/invoking it using GET, but the adapter is then calling your backend system - http://kenatibm.cloudant.com/backendsystem - using PUT. This is broadly the same explanation as Dave...
mobilefirst,mobilefirst-server,mobilefirst-studio
Edit: fix available starting iFix release 7.0.0.0-IF201506021502 This has been identified as a defect: 75848: PI42074 EXCEPTION WHEN DEPLOYING IOS ENVIRONMENT CONTAINING A SKIN Local workaround is as mentioned in the question. To receive a fix, please open a PMR (support ticket)....
worklight,mobilefirst,worklight-adapters,mobilefirst-adapters
In general the new RESTful JAX-RS (Java-based) adapters in version 7.0 operate independently of the old JavaScript-style adapters. I'm not aware of an in-process API to call them, so you would have to call them like any other RESTful service using WL.Server.invokeHttp (i.e. like how you might typically do this...
Read the help for this product: http://www-01.ibm.com/support/docview.wss?uid=swg24034222 The integration package includes sample applications and adapter to validate successful HTTP header or LTPA token integration, single sign-on to backend data sources using Worklight Adapters, OAuth authentication, context/risk-based access, Device Single Sign-On and MobileFirst Platform Foundation generated Certificate Authentication. The sample applications...
mobilefirst,mobilefirst-adapters
Edit: the fix for this issue is now available on IBM Fix Central - download the latest 6.3 iFix. I believe this is related to: APAR IBM PI39922 UNICODE PARAMETERS ARE ENCODED INCORRECTLY UPON BEING PASSED TO A MOBILEFIRST ADAPTER. This APAR fix is not available for MobileFirst Platform 6.3....
Its got fixed. I used below code to complete the objective. <target name="build-adapter-parallel"> <for param="check" parallel="true"> <path> <dirset dir="/Users/admin/Documents/workspace1/MyTime/adapters" includes="*"/> </path> <sequential> <echo> value of @{check}</echo> <adapter-builder folder="@{check}" destinationfolder="/Users/admin/Documents/workspace1/MyTime/bin" classpathref="base.path"/> </sequential> </for> </target> ...
mobilefirst,mobilefirst-adapters,mobilefirst-server
There is no built-in mechanism to cache an adapter response. Maybe this will give you a way to do it: use Java in order to "manage" the caching. You'll need to implement the logic to: Preserve the data in memory (in variables...) Decide when to return the cached data Decide...
mobilefirst,mobilefirst-server,mobilefirst-analytics
You don't mention what version of MobileFirst Platform Foundation you are using - for purposes of this answer, I am assuming 7.0. The way you set the JNDI properties on WAS is illustrated here. If you are in the "Environment entries for Web modules" section, you're in the right place...
If you use as-is the following function in iOSNativeiBeacons/iOSNativeiBeaconsLibrary/WLBeaconsLocationManager.m, then beacon-trigger's actionPayload can either be a local alert or a call to an adapter procedure. The details of adapter call are given next. -(void) fireTriggerAction:(WLBeaconTrigger *)beaconTrigger forWLBeacon:(WLBeacon *)wlBeacon { NSString *branchName = [wlBeacon.customData objectForKey:@"branchName"]; NSString *alertMessage = [beaconTrigger.actionPayload objectForKey:@"alert"]; if(alertMessage...
windows-services,mobilefirst,websphere-liberty
Here's our complete solution: 1. Start CMD as administrator and run this: sc create WASLibertyV85 binPath= "C:\Program Files\IBM\WebSphere\Liberty\bin\server.bat start worklight" DisplayName="IBM WebSphere Liberty V8.5 Worklight" start=delayed-auto 2. under Services.msc open the properties of the „IBM WebSphere Liberty V8.5 Worklight“ service and set this (if not already): Tab GENERAL -> Startup...
mobilefirst,mobilefirst-studio
There is no more Preview mode in a production environment, however there was a bug in the initial release of v7.0 where the preview button was still available while the underlying code is no longer there. Make sure you to apply the latest iFix release to your server installation. It...
https,certificate,mobilefirst,mobilefirst-adapters
The instructions you've followed are incorrect when using MobileFirst Platform. Follow the steps described in this user documentation topic (for Worklight 6.2, but valid for MFPF 6.3 and above as well). Do not export the certificate from a browser because this action adds browser metadata and other artifacts which shouldn't...
upgrade,mobilefirst,mobilefirst-adapters
By the description in the comments and the supplied messages.log, it is clear that you are attempting to use Application Authenticity Protection. This feature worked in a certain way in v6.2 and it works in a different way in v6.3 and above. From the comments it appears you are only...
mobilefirst,mobilefirst-adapters,mobilefirst-server
Starting MFPF 7.0 there are two authentication models: Classic: as you know it from pre-7.0 versions OAuth-based If your adapter is developed in the Classic way, it continues to work as before. If you want a procedure to have no security defined for it, not even the default internal one...
java,ant,mobilefirst,mobilefirst-adapters
You are correct that the JEE library is missing. Could it be that you did not declare it in the Ant task? See this user documentation topic: Building applications and adapters > Building an adapter building a Java adapter without libs <path id="my.path"> <pathelement path="/opt/IBM/Worklight/WorklightServer/worklight-jee-library.jar"/> </path> <adapter-builder folder="adapterRootFolder" destinationfolder="destination-folder" classpathref="my.path"/>...
This is happening due to recent changes Apple has done. To fix it: remove (do not delete) the buildtime.sh file from the target configuration in Xcode (in Build Phases > Copy Bundle Resources). Read the following for more information: Recent changes to Apple’s app submission review process IBM Worklight/MobileFirst 6.x/7.0...
ssl,https,mobilefirst,mobilefirst-server
You did not configure SSL between the adapter and the backend. The keystore that you should be looking at is defined in the worklight.properties file of the project (by default located like this: workspace\CustomLoginModule\server\conf). Make sure to follow the instructions provided here: https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_configuring_SSL_WL_adapters_backend_servers_certificates.html...
The MobileFirst Server that is installed in the Development environment (the Eclipse plug-in) uses a filesystem-based database (HSQL) by default. The MobileFirst Server that is installed in a QA/Production environment supports a database from these vendors: MySQL, Oracle, DB2. In both cases the the database that is created for the...
java,osx,mobilefirst,mobilefirst-cli
The best approach here is to have a simple wrapper script as mentioned previously. This keeps you safe from updates. Also, be sure to remove the PATH setting in "/etc/profile". Its quite simple... In Bash: #!/bin/bash #-------------------------------------------------------------------- # Simple multi-MFP launcher script # Karl Bishop <[email protected]> #-------------------------------------------------------------------- #-- Set specific...
The answer is no. The mainFile value must be the index.html that is placed in the common folder. Changing this value (which we would actually love to remove it from application-descriptor.xml so you won't ever see it and be able to touch it) is unsupported. The only other option for...
mobilefirst,mobilefirst-server
About the error message: /home/worklight/.worklight/server-configuration-tool/Configuration_MobileFirst_7/MobileFirst_7.xml:71: The element , is missing. A default user cannot be created for this server. This happens if your Liberty is configured for LDAP. In that case, the server configuration tool is not able to add a user (it can add users if Liberty has a...
mobilefirst,mobilefirst-server
Generally it means that the worklight-jee-library.jar shared library referenced in the server.xml (in each MFP runtime application) is not found. Check the path of this library in the server.xml and that the jar file is present in this path.
objective-c,cordova,mobilefirst
You cannot do this on your own with the supplied plug-ins. These warnings are issued by iOS but are harmless. We'll take a look, but this is harmless, unless you actually see a real problem (which I doubt right now that you do)....
soap,mobilefirst,mobilefirst-adapters
I examined the WSDL that you've provided and for the recuperaVariabili service the input parameter is defined as: <element name="recuperaVariabili"> <complexType/> </element> I believe that the empty complexType is what confuses that adapter generator as it might expect some elements/attributes to be defined for that complex type. I must say...
The logout is completed by calling WLAuthorizationManager.obtainAuthorizationHeader(); // no parameters My error was in thinking we could selectively be removed from a single Realm, instead we in effect remove our entire OAuth token....
cordova,windows-8,winjs,mobilefirst
Where are you calling the addEventListener ? Perhaps, the onactivated event has already been raised before you called the addEventListener. I was able to intercept the loading in the cordova.js file and added an event listener and the appropriate function was fired. ...
json,soap,mobilefirst,mobilefirst-adapters
Yes all the responses from Worklight adapter will be converted to JSON before reaching the Client device (Mobile,Web browser,etc) To understand the structure and working of adapters more clearly just read the link below Overview of worklight Adapters Next why Json always than XML ? JSON has several advantages...
mobilefirst,mobilefirst-server
No. As you mentioned, the server component is not free and you must purchase it from IBM. This is really not a question for Stack Overflow....
worklight,mobilefirst,worklight-adapters,mobilefirst-adapters
That is indeed one of the parameters that you cannot 'externalize' to worklight.properties in order to read its value from a variable. You can submit a feature request here: http://developer.ibm.com/mobilefirstplatform/help...
You could do something like this (very rough idea): As part of your authentication flow, if the user has passed the authentication - store in either localStorange or JSONStore a "token" that will basically state that the user has previously logged in. Also save in the server's database using userPrefs...
With OAuth, logout 'works' differently. See the following user documentation topic (search for "logout"): http://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.dev.doc/dev/c_oauth_security_model.html?lang=en The login/logout API: The WLClient login/logout API enables a user to log in to and log out of a specific realm, by updating the server side security state. However, in the new OAuth-based security model,...
timer,delay,mobilefirst,mobilefirst-adapters
You can't do this in the adapter logic, but you can do this in the client logic... Add the required delay implementation in the adapter procedure request's success callback function so that it won't get processed right away, if that's what you really want to do (which would be strange,...