In IBM bluemix, i basically have to use mobileFirst service to host my ios application being implemented in it. I have seen several tutorials and stack overflow search for that but didn't got any satisfactory answer from that. If you can provide any sequential tutorial for that will be very helpful.
Set up your Mobile Foundation service instance, as instructed in the following doc: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/bluemix/using-mobile-foundation/
Create an iOS application. It can be a native app or a Cordova app with the iOS platform.
Add the MobileFirst SDK to the application by following the instructions per the required platform, here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/application-development/sdk/
Register the application in the server. You can do this either via CLI or via a graphical interface. You can see a "quick start" way, here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/quick-start/
Basically, to register an app from the command-line, simply navigate to the app root folder and run the command: mfpdev app register.
To ensure the connection between the server and client, you can make a simple call to obtain a token. You can find this code in the Quick Start docs mentioned above.
For iOS, be sure to enable "Keychain Sharing" in Xcode.
Related
How to Manage app and data on a device (Block, Wipe and others) in ibm mobilefirst 8.0?
Following options are available in Mobilefirst 7.1:
Managing app distribution (using the Application Center)
Managing app versions (using the Operations Console)
Managing app access (using the Operations Console)
Managing usage, performance, warnings and errors (using the Analytics Console)
Managing data access
I suggest that you will take a tour of the MobileFirst Operations Console in MobileFirst Foundation 8.0. See here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/product-overview/components/console/
Managing data access / Managing app access
I assume you are referring to "remote disable". This is available from the application screen in the console. Select the desired registered application from the sidebar navigation and under the Management tab you will see a Application Access title.
Managing usage, performance, warnings and errors (using the Analytics Console)
Unsurprisingly, this is available from the Analytics console as before.
Learn more about Analytics console here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/analytics/console/
Managing app distribution (using the Application Center)
This has not changed and it not related to MobileFirst Foundation 8.0. You do this through the AppCenter console as before. AppCenter did not change between 7.1 and 8.0.
Managing app versions
In previous versions you would have upped the version value in application-descriptor.xml. In v8.0 instead whenever you want to release a new point release, i.e. 1.1 or 2.0 etc, you need to register another app versions, either using the MobileFirst CLI or directly via the console.
I suggest that you will start getting familiar with the product...
Product overview: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/product-overview/
Upgrading/Migrating: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/upgrading/
Application development: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/application-development/
We have develop a cross platform app with mobilefirst studio 7.0 and test it on production environment.
It was fine before we upgrade our project with mobilefirst studio 7.1.0.00-201510120-1525 and test it on clean staging server (7.1.0.0 20151012-1525).
It seems that the push notification functionality dedicated on mobilefirst 7.0 did not work properly on production server of mobilefirst platform version 7.1. The source code and configuration file of our mobilefirst push notifcation adapter and configuration files are here.
Inorder to fix the issue, we refer to official push notification tutorial which was documented here.
Surprisingly, although the source project in official tutorial looks fine on development server, it still not work on production server either.
We have test this project using iphone5s with ios 8.4 and HTC 816h phone with android 4.4.2, both of them fail to register push notification service after we login to the HybridEventSource sample application and tap the “Subscribe Notification” button.
The Mobilefirst server logs down internal server error message during the registration process of client devices.
I am wondering how to let the push notification mechanism work again on mobilefirst 7.1?
Either a valid push notification sample code of mobilefirst 7.1 or any fix pack which we do not know is welcomed.
Since we did not authenticate users via mobilefirst server, and devices were connected through vpn to server,
we prefer to have a solution which does not depends on particular mobilefirst server side authentication mechanism.
The server log message generated during this test is in this file.
The log file generated while we run EventSourceNotification app as xcode project is in this file.
For detail system log from ios device, please refer to device log file
And the Log message generated by HTC 816h android 4.4.2 phone is here
Information about our server environment:
Operating system : centos 5.8 linux
Java development kit : Oracle jdk 1.8 update 65 x86-64
Application server : Apache tomcat server 7.0.63
Worklight environment database : oracle database 11g.
Apple push notification service certificate : sandbox version
Well that's kinda suspicious, isn't it?
Since we did not authenticate users via mobilefirst server, and devices were connected through vpn to server, we prefer to have a solution which does not depends on particular mobilefirst server side authentication mechanism.
You are using the push mechanism provided by MFPF but you do not want to go through MFPF? You are required to go through MFPF if you want to use the push mechanism provided by MFPF... What did you mean by the above?
That said, did your DBA examine mf7-1-EventSourceNotifications-catalina.out.log? There are quite a few Oracle-related exceptions there that you should look at.
If you are still unable to resolve it I suggest to open a PMR instead so that the development team will be able to further investigate.
I Create the IBM Appcenter Installer for Iphone and deployed into the Appcenter and I access the appcenter console from the Mobile.
http://Honstname:9080/appcenterconsole/installers.html I am able to see the new installer(IBM App Center), When I click the install I am getting the error called.
cannot install application because the certificate is not valid.
I download the IOS enterprise development certificate from the developer.apple.com, I don't know where I can install this certificate in server or?, if mobile means how can I gave this certificate to every customer.
Please correct me if I am wrong.
For iOS, you must setup the server with SSL support.
There are too many steps to detail here, so it is based for you to review the full set of instructions in the following user documentation topic: https://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.installconfig.doc/appcenter/c_ac_ssl_config.html%23configuringsecuresocketslayerssl
I'm creating an app using Worklight. I need to show a Notification at specific time like an alarm clock. It'd work when offline so i cannot use Push Notification.
I need Notification like image below. Thanks.
iOS's Local Notifications feature does not have built-in support in Worklight.
One way to add Local Notifications support is by extending your application using a Cordova plug-in, which will allow you to run Native code.
This means that you will natively implement it by following Apple's APIs: to schedule the notification in the app and to then receive a notification locally via the OS, that will in turn allow you to open the app and execute an optional callback, etc...
You could either write a custom Cordova plug-in of your own,
Or find existing plug-ins on the web.
When adding an existing Cordova plug-in to Worklight (depending on your version of Worklight and version of Cordova), the instructions to do so are a bit different at this time.
This video demonstrates one instance of how to do add an existing Cordova plug-in: Integrating Cordova plugins into Worklight applications
I am trying to configure and upload the AppCenter installer app.
I already have our actual mobile project deployed on our Worklight Server (running on WAS Liberty profile). Now, we'd like to install AppCenter installer app in order to distribute our app for testing.
I've read through this article here: http://www.redbooks.ibm.com/redpapers/pdfs/redp5005.pdf, but didn't see any information on setting up the application descriptor file for the AppCenter Mobile Client.
Currently, my application descriptor file is pointing to localhost. Should this be pointing to our Application Center server URL or our Application Center console? Should it have the same configurations as our mobile app? And if I need to point it to our console, do I need another context set up for the AppCenter?
First thing first, I suggest that you take a look at the IBM Worklight Information Center topics for Application Center.
As for your questions:
You need not do anything to the AppCenter project (the AppCenter Installer app) other than:
Building it as-is (this varies depending on the platform you build it for) - this means not changing its worklightServerRootURL value, is it not required to connect to a Worklight Server (the apps you will install through it - will)
Uploading it to the Application Center management console
Downloading AND installing it to your device
Configuring it in-app to point to the Application Center server
As for after building your own Worklight project
Simply upload the .ipa, .apk or .cod file to the Application Center management console
Installing it via the previously-installed AppCenter Installer app
You will need to repeat downloading the AppCenter Installer app for each device you want to perform testing on.