How syclo will be integrated into SUP, it is a common question that every existing or potential SAP mobility customer will ask.

From a high level perspective, these two platforms will be integrated into a single runtime envionment, centralized administration and non-disruptive upgrade. Syclo server will be managed by SUP Management console with unified logging, Syclo will exposed services and be consumed by SUP. Anyway, this is a high level roadmap of integration at the moment of writing.

As we know, since SUP 2.1.3, iOS devices rely ultralite db (sql anywhere) to do synchronization with SUP cdb. Here is a useful article of how to open this database and inspect the content. It is often needed for developers to check the status and make troubleshooting of synchronization.

Reference

Sybase Unwired Platform Tutorials (scn.sap.com)

Sybase Unwired Platform Developer Center (scn.sap.com)

Here is the high level steps of android native development on SUP.

1. Generate Java Object API code. Be sure to use android.jar file with the correct level of SDK API

2. Create Android Project in Eclipse withe the correct level of Android SDK API and add the objectAPI library jar files into the build path.

3. Copy the generated code into the project source folder

4. Change the Android Manifest xml file and add the activity class.

5. Create User Interfaces, and java classes.

6. Run and test the application in the emulator with the correct version of OS.

The steps are based on SUP 2.1.3 version.

Tips:
1. If you use the sample code from the documentation, be sure to check the registration part, make sure to use correct server name, port, application id, username and password. Also change the mbo names to make the application run with no errors.

2. Make sure to generate, create and test the application in the same android api version.

3. Make sure the automatic registration is enabled on the target application in SCC.

4. Make sure the Java Compiler version is 1.6


Reference
Troubleshooting
Troubleshooting 2

During this initial phase of the partnership, SAP worked with Sencha to create a custom JavaScript library for Sencha Touch that allows a Sencha Touch application to work with an oData producer such as the SAP NetWeaver Gateway. Sencha Touch already provides web applications with data management capabilities through its Models, Stores and Proxies; this additional capability simply allows a Sencha Touch application to more seamlessly consume oData from an SAP data source.

This library will be developer community supported and available free of charge from Sencha.

Reference

Through this partnership, SAP will be enhancing its existing HWC to include support for the PhoneGap JavaScript API. What this means is that existing PhoneGap applications can be migrated over to the SAP Mobile Platform HWC and run without modification. Then, when updated versions of the application become available, they can be deployed into the container remotely using the management and provisioning capabilities of the SAP Mobile Platform. To make use of the secure, reliable synchronization capabilities of the SAP Mobile Platform, the existing PhoneGap application will need to be updated to access its data through the MBO. While this is extra work that must be done by a developer, one of the primary reasons you would move an existing application onto the SAP Mobile Platform and the HWC is to take advantage of the MBO, so it’s time well spent.

Reference

Here is the high level steps of installation and configuration of SAP Mobile CRM

1. Mobile CRM add-on installed on SAP CRM backend
2. Mobile CRM add-on installed on SAP ERP backend (optional for enabling ordering functions)
3. Deployed on SUP 2.1 and later.
4. Client software is installed on mobile devices.

Use SIMGH transaction to do custom configuration.

Reference Basic Tutorial Recording

There are four major components of Syclo Agentry Platform.

1. Agentry Server. Manages the communication between backend and devices and server-side functions.

2. Agentry Editor. Eclipse-based developement IDE.

3. Agentry Test Environment. Desktop-based test client to view object, emulate supported platforms or do debugging.

4. Agentry Client. Secure client installed on devices, consists of application definitions and master data.

Reference

Syclo has four major products released in the SAP Portfolio at the moment of writing this article.
1. Work Manager for SAP ERP - Mobile Enterprise Asset Management
2. Service Manager for SAP CRM - Mobile Field Service
3. Inventory Manager for SAP ERP - Mobile Inventory Management
4. Rounds for SAP ERP - Mobile Reading

Reference

Since 1995, Syclo has worked with over 600 organizations to create, deploy and manage a variety of mobile applications. Syclo’s software extends corporate systems and databases to a wide range of mobile devices and user types, helping companies cut costs, increase productivity and make better decisions across the board. Together, Syclo’s technology and prebuilt SMART Mobile Suite applications present a flexible, reliable and cost-effective framework for enabling the mobile enterprise.

This acquisition is the next step in delivering a fully-integrated mobile platform and enterprise application portfolio to both Syclo and SAP customers,” Syclo CEO Rich Padula said.

Reference

We often say we have to consider differently when building a complex mobile application. But what is complex?

• Asynchronous communication capabilities.
• Orchestration of many stateless service calls that are subject to a single transaction semantics. Example: Create a ServiceOrder with its Notifications.
• On device persistency and in particular keeping object state consistent with the server state.
• On device business logic such as a Pricing or a Configuration Engine.
• The ability to handle large data load. Example: equipments, material, products.
• Pushing data and updates to the mobile application.
• Support for complex data distribution rules (from server to device).
• Scalability in number of devices, requests, and data volume.

• Communication is request/response, stateless, un-buffered, http-based.
• Gateway exposes OData services for easy consumption.
• Routes requests 1:1 and changes protocol from http to RFC.
• Provides Push/Notification/Subscription capabilities for events and workflow.

• Connects devices from internet to intranet and routes requests to Gateway.
• Provides User Handling & Security (guards the Gateway).
• Leverages Push/Notification/Subscription (scalability of push for high volumes, planned).
• In contrast to Gateway no content development happens in this layer.

1 Alerts – Send assignment notifi cations that engineers view and accept or reject
2 Debrief – Empower engineers to debrief orders at the point of service
3 Mobile access – Give engineers access to service, customer, and product information in SAP CRM
4 Support for offl ine work – Enable field engineers to work offl ine and, when online,have data refreshed automatically
5 Google Maps integration – Let field technicians view assignments on a map, so they can plan visits
6 Map Integration
7 Calendar Integration
8 Dashboard – View and monitor status and progress of a service order in real time
9 Sybase? Unwired Platform – Take advantage of a prebuilt solution to mobilize SAP applications
10 Built-in security – Improve security by centrally managing, securing, and deploying devices

As we all know, Blackberry has it enterprise origins which offers key security capabilities and blackberry device management. Here is a brief summary of what we can refer when selecting or designing a mobile device security infrastructure.

1. Policies
Blackberry Enterprise Server which is a single point of management solution for blackberry devices offers over 450 IT related policies such as password, device wipe, etc.

2. Secure and Reliable data transfer
Data transfer across the intranet network is end-to-end AES-256 encrypted.

3. Firewall
This function which is common on PC operating systems also proves to be useful to handle attacks.

4. Email Security
Encryption of emails and attachments. Integrated Mobile email client can provide more security features.

5. SD Card
This removable card can be a source of intruders and security risks. Do not ignore.

6. Operators and Manufacturers
RIM is the manufacturer of Blackberry devices. Also there are operators with Blackberry infrastructure around the globe. The security policies can not work without the cooperation with devices makers and telco operators.

Mobile security should but not only include the following segments or aspects.

1. Mobile secure content and threat management (MSCTM)
MSCTM defends virus, spyware, spam, hackers, intrusions, and unauthorized use. This segments can be broken into three subcategories.
1a. Mobile threat management for antimalware, antispyware, firewalls
1b. Mobile IPC for file/disk encryption, data loss prevention
1c. Mobile VPN for mobile data transfer network security

2. Mobile security and vulnerability management (MSVM)
MSVM provides device wipe, lock, patching, password, policies and compliance.

3. Mobile identity and access management (MIAM)
MIAM offers authentication and authorization technologies like certificates, PKI, SSL. It is extremely important for users to access sensitive datas or to do ecommerce transactions.

4. GPS or location based awareness
This can be a complement for industries such as retail store, healthcare and government where users are mostly granted limited access in a certain range of areas.

Lastly the key thing is to always consider mobile security solutions before you are deploying your first enterprise mobile application, not matter whether it is Mobile CRM, Mobile BI, or even Mobile Email access. If you employ a BYOD roadmap, keep in mind the users' privacy.

If you have a large deployment, do engage with telco operators. Not only can they offer data plans, also they can provide enhanced features on network perspective such as APN etc. If your deployment is small, find some hosting or leasing solution providers to ensure cost effectiveness.

Just come across an article about SAP and Capgemini's partnership on developing a Direct Store Delivery mobile application in the next five years.
http://mobility.cbronline.com/news/sap-capgemini-sign-deal-to-co-develop-new-mobile-sales-execution-application-170512

This is part of the plan of SAP to provides hundreds and thousands of mobile applications for users, most of which are planned to be developed by partners.

As we all know, SAP has release Retail Execution Mobile Application. This application provides basic and general functions of data collection and store visits for merchandiser or sales people in retail and consumer products industries. It is simple and easy to use, however, it is far from the expectations of this industries users as it cannot fully provide end-to-end solution for roles other than merchandisers in the supply chain, for example, inventory management, delivery, etc.

This future killer app of Mobile Sales Execution together with Retail Execution App will change the way which the current store delivery operations are doing. From order to invoice, from route to transportation, from warehouse to stock, from reload to unload, from visits to audits, from master data to reporting, from barcode scanning to GPS locations, the information are all in one killer app. The brand new app will connect with backend ERP and CRM via Sybase Unwired Platform which is the SAP heavily invested mobile infrastructure.

What I think is the SAP and Capgemini do need to leverage strengths of each other to build this app. Five years seems so long, but it deserves to wait.

Mobile BI has been widely agreed as a second killer app for enterprises other than mobile email. Gartner has made analysis on this area and here is a quick summary from my side.

For end users,
1. small screen support is critical.
2. collaboration and exploration can be more intruitive to users.
3. offline reporting support
4. Multiple device support
5. Dashboarding

For Developers,
1. build once, deply many
2. transform desktop reports to mobile devices with less efforts.
3. Security
4. application development, integration with external, layout customization and development APIs are essentials

From my experiences, Mobile BI can be a evil devil for enterprises. It is fresh new at the first glance, but also can be of little interest to users several days later. Collaboration functions and email integration functions largly promote users sharing what they find in the reports. Also exploration functions can enable users discover datas and business insights with less limitation. Otherwise Mobile BI is only for a small group of executive users, rather than a killer apps that can be deployed more widely throughout different departments and organizatons.

I have been involved into a very interesting mobility case in china. We used to talk more about Mobile BI, Mobile for retail, Mobile EAM, Mobile Service, but what we find in this customer is the requirement of Mobile Time Management or Mobile Timesheet Application.

This customer is one the major auto manufacturer in China, as we all know Automobile industry is booming these years in China. However consumers become to have more options as all the global players are surging in. Auto manufacturers do have the requirement of improve efficiency especially on the streamlines.

If you have been to some auto factories to see the assembly streamline, you will find a huge rooms with all the workers on different duties. Team leaders will manage their performance and fill in the timesheet at the exact time when the workers are on duty.

There are 600 to 700 team leaders in this factory, each leader is in charge of a team of 10 workers. As the streamline room is so big, team leaders have to walk around, back and forth from the working sitepoint to the fixed PC workstation terminal. This does not look easy.

So mobility shows its value by providing possiblity of filling out timesheet, working status, worker's performance (ie. parts assembled per hours) anywhere anytime with a mobile device on hand. The armed team leaders, more probably will carry a pad, search the shifting schedule of his team members which is managed by HR time management specialist in backend system (SAP HCM), check it on site, and then sychronize the data back to the system. Worker's overall performance will be generated on a monthly basis and linked to the contribution of the individuals.

The project is led by the HR team. They found mobility is a reliable way to ensuring the capture of actual and accurate performance data, while they used to be in trouble of getting it. They found the worker's overall performance assessment will be more specific and show what the worker's strengths and weakness. Hopefully, the mobility solution can contributes to the success of a HCM system and improve the overall enterprise human resource efficiency.

I have never thought of virtual desktop is a good way of enterprise mobilization. However some of our enterprise IT still consider it as the temporary solution for the low level of mobilization requirement by end users.

Virtual desktop is a technology with a long history. Every Unix system administrators must be quite familiar with Xmanager or some tool like that. On mobile devices it could be a different story.

1. Virtual desktop on mobile devices provide users with no good UI experiences. UI Controls are nowhere like native ones. You have to wait for remote response of each actions you make on the devices. Right click hardly works like what you get with mouse on PC.

2. Performance can be bad due to slow network connections. Client crashes with no reasons and you have to log in again and again.

3. It works on Pad only, no phone users can endure working with PC desktop on a small screen.

4. Network Expense becomes out of control. Tests found the data volumes consumption is high because of the download and rendering of the remote desktop.

It is not to say that virtual desktop on mobile devices is of no use. IT persons can do administrative works with devices on their hands. But it can only be a temporary solution for some simple requirements such as office document manipulation. Enterprises with a clear mobility strategy and vision are still considering building native, web or hybrid application for mobile device workers.

Replication-based Synchronization Versus Message-based Synchronization
When choosing between generating code for replication-based synchronization or message-based synchronization, keep the following in mind:

A mobile application can be either message-based or replication-based, but not both at the same time. A package of mobile business objects can be deployed as either message-based or replication-based.

Replication-based synchronization
Supported on BlackBerry and Windows Mobile devices.
Data flow follows an upload/download pattern.
Data is synchronous (supports background synchronization).
Uses the "poke-pull" model of push, where a notification is pushed to the device (poke), and the device fetches the content (pull).
Best for mostly disconnected mode.

Message-based synchronization
Supported on iOS and Windows Mobile devices.
Uses an asynchronous messaging protocol.
Provides reliable messaging between the device and the server.
Provides fine-grained synchronization (synchronization is provided at the data level—each process communicates only with the process it depends on).
Best for always available mode.

Today SUP 2.1 ESD3 released, let us look into some details of the new features.

1. Security enhancement. For example, LDAP integration enhancement, https communications in all levels.

2. Platform support. New version supports iOS 5.1SDK latest update with XCode development tool 4.3.1. Also it supports Blackberry OS 7.

3. HTML Web container. New APIs from PhoneGap are announced and out-of-the-box. With the co-operation with PhoneGap and other partners, Hybrid Web container can be greatly improved when developers needs to talk with native device functions such as camera, GPS, file system, bar code scan etc.

4. Performance. New version of SUP now supports RBS(Replication based Synchronization) which is supported only on Blackberry and Windows Mobile before. This provides an superior option of optimizing data replication performance for iOS developers on SUP. See here for RBS and MBS(Message based Synchronization)differences.

5. Lastly，licenses audit engine, (maybe bad news for developers). The license management has and will be integrated into Solution Manager. However, it is possible to obtain from your regional SAP sales contacts.

Overall, SUP of the new version is part of the roadmap towards a more secure, scalable, and developer-friendly platform with cloud, B2E and B2C visions.

It is reported that, Samsung Galaxy devices have got U.S security clearance this year. The FIPS certification  takes Samsung mobile devices into a higher level and ensures Samsung to enter regulated industries such as government. It is a great step, I think, to the Korean company.

iCloud has been introduced as a major feature of iOS5 systems. iCloud can be used to backup and restore Apple devices, upload emails, contacts, calendars and applications. This sounds awesome to Apple and consumer users, however, to enterprise IT Administrators, it can be a disaster.

Take a look at the Terms and Conditions of iCloud which is normally ignored. This means never use iCloud to backup your sensitive and important documents or content.

Apple is unable to guarantee that any content you may store or access through the service will not be subject to inadvertent damage, corruption, loss or removal. Apple can also not be held responsible should damage, corruption, loss or removal of content occur. 

Also storing corporate data on iCloud can be a serious violator of corporate compliance. As in SAP, storing SAP data on iCloud would equate to storing it ‘outside of SAP’, which is strictly not allowed. Therefore, iCloud and possibly iOS5 are something which needs to undertake deep evaluation before they are corporate wide deployed.

Sybase Afaria provides a solution to disable certain build-in or user-installed application on mobile devices. For example, on corporate devices youtube and icloud can be disabled for security and compliance reasons. It is also meaningful to stop using dropbox or box.net services on coporate devices. (both are banned by Great Firewall of China, no more actions to take). Among these cloud storage services, icloud is the most integrated and transparent to unawared consumers. That is the dangerous point because consumer loses control of their privacy and is open to all kinds of phishing scams.