I was reviewing Gartner magic quadrants related to enterprise mobility management (EMM) from 2011 to 2014.
On mobile applications time response is one of the key aspects of this ecosystem.
Some of the key points that influence on time response are:
1.- the type of application: native application or modified application from another application layer.
2.- The telecommunication channel used for the device (3G, 4G or Wifi connection).
3.- Testing of the solution: this is key for the solution, you not only need to test the functionality, you need to test Google web services, and other third party services to understand bottlenecks), test # of redundant users, etc… so many of the
4.- Architecture / platform decision, this will represent the main issue and one of the key decisions for the rest of the project. People working on robust business cases and a clear medium term road map do not use to fail on this point, but for the others the situation can be different.
If you are going to build a solution for mobile devices you will have to make so many questions about the type of user, #redundant people, peaks of use, look & feel. Sometimes the functional part is the easy part.
I need to remember this link, a good place for finding solutions for mobile issues.
I had an issue with the trackpad of the BB that I would like to remind (link).
I had the BB in the pocket and probably some keys + the trackpad was pressed in a sequence that I still do not know.
The issue was that the vertical move of the screen was stopped in some screens: an e-mail, main screen… and I was required to press the “alt” key to move on the screen. There were no physical issue, for instance on the e-mail inbox the move worked perfectly.
What I did to recover the initial configuration was to install an application and uninstall it. The complete reboot made the issue disappear.
Unfortunately for me I still do not know the sequence of keys I have to press to have the issue resolved.
- Allow the current users to access to their Web applications with the existing configuration pattern.
- Allow the mobile users to access to the WSDL elements using the Session Authentication = “Disable”.
With it, the access of the mobile users is done with the credentials entered when the user access to the application (an username/password screen is shown).
- How can I see an error on the mobile device?
- How can I measure the response time for each mobile action?
- Which actions do I need to check in order that the service support has visibility on the mobile errors?
With it, some of the answers are:
- The blackberry simulator has a lot of configuration options that allows you to simulate: Status of the battery, Quality of the signal… it will allow us to measure the response time in different conditions.
- We need to publish a method in the WSDL that allows us to log the mobile errors in a common database. The service support needs to know which errors are happening, the log of the mobile device seems to not be accessible by the service support in a centralized container.
We need to define it very well because this phase is going to be hard.
Yesterday I had the opportunity to assist to some sessions of the BlackBerry® Technical Seminar .
It’s a virtual conference hall where you can assist to different seminars. The seminars take 30 minutes or an hour.
1.- The Speed of Innovation: How IT is Driving Change in the Mobile Workplace.
A brief overview about how to prepare the Business Needs for Mobile Solutions. Too slight and not only by the 15 minutes of presentation.
2.- BlackBerry Enterprise Server Roadmap.
This has been an excellent revision of products, features and more.
Some things I learned from it:
- I didn’t know the product “Blackberry Unite!”.
- BES 4.1.6 has Certification on Domino 8.0.1 !!!
- BES 5.0 is named ‘Argon’.
- Blackberry MVS (Blackberry Mobile Services).
Today there are some other Seminars
I have been doing some Searchs on the Blackberry MDS Forum in order to get information about the problem of access to a secure WSDL published in Lotus Domino Server.
Some of the more interesting links for me are:
- This offers an easy way to fix it link,
- This other reminds us that we need to work at least with BES 4.1.2 link,
- This other is something I want to keep in mind when we deploy the application. This configuration problem is going to happen us, I’m sure. link,
- A little guide with the steps to follow, link,
Now it’s time to test all these suggestions and see what’s the solution.
Looking my previous post, it looks as the approach I suggested was not right at all. Let’s see what’s the right answer.
We are studying how to deploy lotus applications with MDS Studio & WSDL.
The starting was easy, but the real problem has started when we have tested the security of the Blackberry device to the Lotus Notes database.
We have been investigating about the Lotus Notes sessions creation and there is no easy way to get the session accesing with the the WSDL. I have done applications accesing using DIIOP and the NotesFactory object but this approach does not convince me at all.
Now we are thinking about to get the session using the POST method on the “?login” page of the Domino server and trying to use that session for the mobile user.
The questions that round my mind are:
– Is going to be possible to get the session with this method?
– Is able the Blackberry to store that session for next calls to the Lotus Domino Server?
– How is it possible that I have not found nothing about this problem on the Internet?
I hope to get some answers next week,
Today I have found a very interesting link: JavaOne Online Technical Sessions. After to do an overview on it I have found a technical session very interesting for me:
This technical session is a complete road map throw the different consideration you have to take into account when you develop a Mobile Application.
Another interesting aspect is how the analysis of each component is based in design pattern and combinations of it.
It also mention some issues related to the status of the mobile development, growth of the mobile tool kits.