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.
Related
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
Worklight 6.2 on Liberty
Can I configure the AppCenter to use custom provisioning outlined in the GettingStarted material?
The server/conf folder is present in the AppCenter project, so it seems I could configure custom provisioning and build the war. The questions seem to be, will the appcenter client
access the new appcenter war like a normal worklight client with respect to the security mechanism, and will the new appcenter war respond like a normal worklight server to those requests?
No, IBM Worklight Application Center does not support the Worklight custom provisioning. The IBM Worklight Application Center server is no Worklight server (in the sense that it does not derive from the Worklight server classes).
The custom provisioning mechanism is often used to restrict the mobile devices that can connect to the Worklight server. However, for AppCenter, any device that runs the AppCenter client can connect to the server with a correct user and password. If restrictions are needed, they should be implemented in the mobile app, not in the facility that installs the mobile app.
After successfully building the AppCenter client application and launching it in an iOS device, my problem is that when I enter my Worklight Server credentials, the server URL and the port and with or without the applicationcenter context, the loading progress keeps running...
How to solve this issue?
I agree with Idan, first thing to do is to run the application center client on the iOS emulator and look at the device logs. I have seen the loading never ending when the client was not compiled correctly, note that the native folder of the application center client worklight project contains native code (a cordova plugin) that needs to be present in order for the application to run properly. If this is the problem you are facing, the cordova log will tell you that the plugin named 'com.ibm.mobile.InstallerPlugin' is missing.
I still no able to successfully download/install an app thru IBM app center to see what a new app looks like on a mobile device.
2 simple questions :
1) If an app, let's call it myapp, was download/install successfully thru IBM app center, then would myapp simply an independent new app on the device or myapp some how "embedded" in the worklight app center app?
2) If I deployed myapp to a Samsung tablet thru other means, that is not thru IBM app center, then would worklight serve has the knowledge of myadd install in this particular Samsung device?
The application would be independent. You could, for example, uninstall it either through the Application Center mobile client, or via the usual procedure the device OS allows you to.
Assuming the applications has connectOnStartup=true, and you deployed the app to the Worklight Server, the answer would be Yes. (the Application Center is not a substitute to the Worklight Server, you must still deploy it there if you intent for your application to use features such as Worklight Adapters).