Migration Options

Enterprise Browser 3.4


Enterprise Browser offers several options for migrating apps from different operating systems, competitive solutions and legacy systems so they can run on modern hardware and EB versions. Below is a summary of EB migration options with links to the relevant documentation for each.

From EB 3.2 and Older

Enterprise Browser 3.3 (and later) is delivered with a different package name than those that came before. Any previous version of EB must be uninstalled and all references to the former package name must be updated. Further, the new version targets Android API level 30, which imposes in-device storage restrictions and blocks access to external storage of any kind. The guides below explain how and why apps need to change.

The EB 3.3 Release Notes section of the Setup Guide lists the changes required to adapt to the package name change, and the Scoped Storage Guide will help with navigation through those changes.

From EB 1.8 and Older

Enterprise Browser 2.0 (and later) for Android supports the HTML5 ViewPort metatag and changes the way licensing is implemented. Apps running on older versions of EB might render improperly or display unexpected client certificate requests when launched with EB 2.x.

The Backward Compatibility Guide explains the minor changes that might be required to solve these issues.

From PocketBrowser

PocketBrowser is an app development toolkit for Windows Mobile/CE that's built on the mobile version of Internet Explorer. It enables developers to quickly build mobile apps for a wide range of functions, including barcode scanning, signature capture and printing.

In many cases, PocketBrowser 2.x/3.x apps can run within Enterprise Browser after just a few small changes. The PocketBrowser Migration Guide explains the changes that will always be required for migrating to EB from PB, and a few others that might be.

From RhoElements

RhoElements is an extension of the RhoMobile HTML5 development environment that enables connected and non-connected apps to perform seamlessly on Android and Windows Mobile/CE devices. Enterprise Browser supports RhoElements 2.x applications, which in many cases will run in EB with just a few small changes. The RhoElements Migration Guide explains explains the changes that will always be required for migration to EB, and a few others that might be.

From RhoMobile

The RhoMobile HTML5 development environment allows apps to target Android and Windows Mobile/CE devices using the same code. Enterprise Browser supports RhoElements 4.x Shared Runtime applications and HTML-based hybrid RhoMobile applications for Android and Windows Mobile/CE that use HTML and JavaScript. Ruby APIs and Ruby-language program code are NOT supported.

The RhoMobile Migration Guide explains the changes required for migrating RhoMobile apps to EB.

From SAP Console / TekTerm

For companies moving away from terminal-based mobile applications that use SAPConsole, Zebra TekTerm or similar character-based front-end solutions, Enterprise Browser should be considered for its simple means of developing portable UIs with industry-standard HTML, CSS and JavaScript.

Learn more about Enterprise Browser.

From Windows Mobile/CE

Enterprise Browser 2.5 (and later) supports meta tag filtering, which can be used to block meta tags or meta-tag properties from being applied if they're not supported on Android devices. Meta tag filtering supports whitelisting (allowing) and blacklisting (blocking) of meta tags as well as individual meta tag properties and is configured in the Config.xml file.

Go to the meta tag filtering section of the Config.xml Reference.

Related guides: