Welcome to Embarcadero AppWave™ 5.0

From AppWave
Jump to: navigation, search


EMBT Icon.pngAppWave Web SiteEmbarcadero Technologies Home Technical Support

ReadMe Last Updated: March, 2014.


Thank you for using Embarcadero AppWave 5.0.


AppWave works with all types of PC apps, applications that you have developed in house, and of course Embarcadero's own award-winning portfolio of tools for the developer, architect, and database professional.

AppWave comprises two primary components:

  • AppWave Enterprise Store - your Private AppWave runs inside your firewall, and provides a wide range of features around App and license management and assignment, app broadcasting (transmitting Apps to end user desktops, where they launch and run immediately with no hassle), App discovery (including search, rating & reviews, and more), and a variety of administrative options.
  • AppWave Browser - an easy-to-use desktop-based client that lets end users discover, run, and socialize Apps in your AppWave Private Store. On the Private AppWave, users can run only the Apps that they are authorized to run. The AppWave Browser includes certain administrative features available only to authorized users, as detailed in the product documentation. Additionally, but available only to users granted Admin or Author privileges, the AppWave Browser component also includes interfaces to the Administrator’s Console and the AppWave Studio. AppWave Studio facilitates the process of adding Windows software to the AppWave inventory as apps, also known as mastering.

And of course at the heart of the matter are the Apps themselves. Apps are housed in one place--inside of your own AppWave--and can be broadcast to users on demand, according to their assigned rights and license availability.

For more detailed information, see the documentation at http://docwiki.embarcadero.com/AppWave.

What's New in AppWave


What's New in AppWave 5.0


This section describes the new features of the various AppWave components in this release.


AppWave Enterprise Store

  • Enabling HTTPS setup utility for AppWave
  • AppWave now supports multi-language requests from AppWave Studio. Application details are shown in the current user's language (if available).
  • Minor improvements and bug fixes.


AppWave Browser

  • Multi-language support. The AppWave Browser UI now supports four different languages: English, French, German, and Japanese. The language changes depending on the language of the OS. English is the default language in case the OS is different from the four currently supported by AppWave.
  • Now it is possible to cancel the download process just by clicking the X in the upper right-hand corner of the progress bar.
  • Minor improvements and bug fixes.

What's New in AppWave 4.2


This section describes the new features of the various AppWave components in this release.

AppWave Public Store

  • The Public Store has now more stability with a better scalable and robust IT infrastructure to allow a large number of concurrent users.
  • More information to the customer with the necessary steps to be followed when launching the first app.
  • Email Verification for new and existing users: before an app can be launched by a customer, their email address needs to be verified.
    • New customers have to sign up and validate their email to launch apps.
    • Existing customers are prompted to validate their email when launching the first app.
  • Independent Software Vendor Portal: The Vendor Portal is the gateway to an easy-to-use app store for independent software vendors (ISVs). New functionality:
    • Master and license your apps as a vendor.
    • Add a price for your app and a Trial option if you want the customers to try your product before purchasing.
    • Payment process is handled by Cleverbrigde.
    • For the first product being purchased, the customer should fill out account/credit card information.
    • On subsequent purchases, the user will only need to confirm a password to purchase apps.
    • The customer can see a list of all the purchased apps in the account's dashboard.

AppWave Enterprise Store

  • Significant improvements have been done in this version to provide a more stable and robust product.

AppWave Studio

  • Mastering and Licensing of Apps by Vendors: Self-register as a vendor in order to be granted permission to master paid apps that will be available for the customers in the Appwave Store.
    • Download and set up the environment to master your paid apps. downloads.embarcadero.com/free/appwave
    • Define some fields to create a license for your app: Product Name, Product Version and Product Edition
    • Set up the Vendor Settings during the mastering process
    • Re-master the paid app if necessary and select an existing license, or update or create a new one.
  • Recommended Best Practices for Mastering Apps:
    • Always master on Windows XP SP3 (32-bit) to ensure the best compatibility with newer versions of Windows.
    • If possible, master in a Virtual Machine environment with a clean OS. Use the “snapshot” functionality to capture a clean state before mastering is begun. This makes it very easy to redo a mastering task or start the next mastering task from a clean state by reverting to previous snapshot.
    • Always test the app thoroughly on all supported Windows versions – especially if mastering is not done on Windows XP SP3. If known incompatibilities exist, resolve in the Advanced Configuration Options dialog in Step 4 (Test).
    • Make sure to include any runtime dependencies in the app mastering process to guarantee that the app runs across multiple Windows versions. Or you can describe the pre-requisites under the system requirements in Step 2 - the Launch & Brand page.
    • When using a zip file, browse to the path where the installer file resides. The executable must be on the root drive or the recording will not work.
      Note: You can install a custom app from a Zip file which contains the application’s executable. See Install Using a Zip File.
      • We don't recommend using a Zip file unless the application is an Installer, that means all the information is contained in the executable itself.
      • If we use an installation package compressed in a Zip file we can experience an unexpected behaviour. The reason is that AppWave Studio may need some extra files included in the Zip file.
      • When you select the executable from the Zip file only this file is unzipped and saved in a temporary folder, and AppWave Studio points to this folder during the process. If at some point AppWave Studio needs some extra file, as a DLL, it will not find the file at that location.

AppWave Browser

  • Improvement on the Progress bar adding new states giving more information to the customer when launching an app.
  • More usability and information for the listed apps in the Managed Apps menu: Version, Author, Provider, Size and Remaining (license expiration).

Release Notes


Additional Resources

Personal tools