• In its default configuration, anyone can access your AppWave and run the applications broadcasted by it. To secure your AppWave, set Restricted Mode to On and Allow client to register user to off. You should also edit the All Users group and the folders this group has access to, and the user to limit the licenses available for that user. For more information, see "System Management", "Folder Management", "Group Management", and "User Management" in the AppWave Administrator Guide.
• AppWave does not work properly on Windows configurations using non-English characters in machine and file-system path names.

AppWave Browser

• AW-7327: Apps removed from Managed Apps will be removed from the hard disk sometimes are not removed from the display of Managed Apps. When you press Refresh or restart the Browser the removed app no longer displays in the Managed Apps display.
• AW-7304: You cannot add a review from Managed Apps in the AppWave Browser if the app is launched from the Store. In order to write or read a review you must search or navigate to the app in the Store. Once you have located the app, click the app icon to open the Details page and then click Reviews.
• AW-3917: AppWave Browser is not compatible with Fiddler Web Debugger, and possibly other packet sniffing applications. When an app is launched a content-length mismatch error occurs. To resolve this issue, quit the packet sniffing application and try again to run the app.
• AW-3634: Free Apps downloaded from the AppWave Store will not run if the connection to the AppWave Store is lost before the app is run and bookmarked. To use an app offline you must first run it and bookmark it in AppWave Browser.
• AW-3694: If while running an app such as DB Artisan, which requires the MSVC 2008 plugin, you locally install an application, such as ER/Studio Data Architect, the MSVC plugin ER/Studio DA requires is not installed. This prevents the natively installed application from launching when AppWave Browser is not running or if in AppWave Browser you remove the other apps which use the MSVC 2008 plugin. To resolve this problem, exit AppWave Browser so the MSVC 2008 plugin is not detected by the application installer and reinstall the application.
• AW-3701: A desktop shortcut to AppWave Browser is not retained or automatically created if you uninstall a previous version of AppWave Browser without deleting all the settings and internal data and then install the current version of the Browser. You can however create a desktop shortcut in the usual manner from the Windows desktop.
• AW-3752: While not connected to a Private AppWave, if you connect to the AppWave Store and then try to access a non-existent Private AppWave a connection failed page displays. This failure display persists when you again try to access the AppWave Store. You will not be able to see the content of the AppWave Store until you access another node, such as Notifications or Activity. Then, when you return to the AppWave Store node the AppWave Store content will once again display. The same problem occurs when you perform an invalid search such as entering only AND or OR as the search criteria.
• AW-3758: Reviews submitted from the channel of an app accessed through the Store Apps node are not accepted for moderation. To submit a review of an AppWave Store app, click the AppWave Store node and then click the app to access its channel.
• AW-3766: An error occurs when an unauthenticated user, not logged in to a private AppWave and not authenticated by the AppWave Store, creates a bookmark from an App Channel page of the AppWave Store and application launch fails if the unauthenticated user then tries to run the app. Restarting AppWave Browser corrects this problem. Bookmarks for AppWave Store apps should be created only for apps the user has been authenticated to run.
• AW-3794: Search results are not sorted by relevance when searching for apps by entering search criteria in the Search/Address bar. You may have to scroll through the results to find the app you're looking for.
• AW-4375: On systems running McAfee Enterprise, AppWave will not install in Turbo On mode and cannot be configured to use Turbo On. Works as expected. You must disable maximum protection form McAfee before installing and using AppWave Browser in Turbo mode.
• AW-4653: If you lose connection to your private AppWave and you previously launched Embarcadero apps while connected to both the AppWave Store and your private AppWave, then when you try to launch Embarcadero apps from the AppWave Store a licensing error message will display. Restart AppWave Browser when it loses connection to your private AppWave and you will be able to launch Embarcadero apps on the AppWave Store.
• AW-5038: On Windows 7, if the Microsoft Office 2010 is downloading new messages and you restart the system before the email synchronization is complete, the email download bar and download process starts again from the beginning and some emails are duplicated. Works as expected.
• AW-5111: Users running under a restricted user account (Turbo mode off) cannot increase the cache size when it is necessary to run more apps. Works as expected. Administrative rights are required in order to increase the cache size.
• AW-5479: In AppWave 3.2, if you change the Cache folder in the Options dialog to C:\NewFolder, the Cache folder would be configured to be C:\NewFolder\StreamingCore\Cache whereas in AppWave 4.0 and higher, the Cache folder is configured to be C:\NewFolder. Works as expected.
• AW-5486: The Search Engine does not return accurate results when searching on more than one term. Works as expected. You must separate search terms using "and."
• AW-5550: [Regression] Installing the AppWave Browser with -turbomodeoff parameter does not work.
• AW-5728: When you remove an app, file associations with that app are retained until you choose to open a relevant file type using the smart app link and then specify a new default app for that file type. Works as expected.
• AW-5779: [Regression] Unable to install the AppWave Browser on Windows XP when using a user with restricted rights. Works as expected. You must have adminstrative rights in order to install AppWave Browser.
• AW-5986: AppWave Browser does not create the icons when running the installer from the command line using the -silent parameter. The user can find AWB in the installation folder (by default C:\ProgramData\Embarcadero\AppWaveBrowser on Windows 7/Vista, and C:\Documents and Settings\All Users\Application Data\AppWaveBrowser on Windows XP). Works as expected.
• AW-6238: [Regression] On the App Channel Reviews tab, reviews are no longer categorized as Most Helpfule Favorable Review and Most Helpful Critical Review. Works as expected.
• AW-6248: [Regression] "F1" no longer works when the AppWave Browser is not connected to the private server; The Browser Help web page is no longer displayed. The work around is to select help from the context menu. The user must also have internet access in order to access the help content.
• AW-6392: Once you register a Retail version of the Microsoft Office 2010 app using a valid serial number, then you can launch either the Retail or Volume version of the app without needing to enter a serial number. Works as expected.
• AW-6596: When an app is upgraded on the private AppWave or AppWave Store, default file associations created are lost and must be specified again. Works as expected.
• If you are using a Proxy server to connect to the internet you must specify the proxy settings specified in
  • Internet Explorer [Tools\Internet Options\Connections\LAN settings] or in the
  • Internet Options applet of the Windows Control Panel
    • Windows XP: Start > Settings > Control Panel > Internet Options > Connections > LAN settings
    • Windows 7:Start > Control Panel > Internet Options > Connections > LAN settings
  Once proxy settings have been defined in the LAN settings dialog, you need to update AppWave Browser's Connect\Proxy Settings dialog to enable "Use Internet Explorer Proxy Settings".
• Some apps may not run if mastered in a Virtual Machine environment due to dependencies of DirectX or Video Card drivers. Works as expected.
• Existing ToolBox users should not run AppWave Browser and ToolBox at the same time. Works as expected.
• For some applications, if the application is already running, launching the AppWave equivalent or another version may just bring the currently running application into focus. Works as expected.
• Restarting the system is required when uninstalling or upgrading AppWave Browser. Works as expected.
• AppWave Browser must be restarted in order for changes to user privileges to take effect. Works as expected.
• AppWave Browser does not support Internet Protocol Version 6 (IPV6). Works as expected.
• Switching connection to multiple servers is not supported (user is allowed to change connection settings, but this may cause problems with license and apps management). Works as expected.
• Licensing and folder settings may not be all updated at refresh on AppWave Browser, sometimes reconnecting to AppWave is required. Works as expected.
• In some cases, AppWave Browser may become sluggish due to poor network performance. Works as expected. If this happens, changing the network connectivity option from wininet to HttpIndy may resolve the issue. This change may also remedy the "MS XML DOM parse error" and is required in order to configure AppWave Browser to use a proxy server to connect to AppWave. Since AppWave Browser requires authentication and Internet Explorer does not, AppWave Browser will not be able to connect to AppWave unless the proxy server settings in Internet Explorer are overridden. Add the following lines

  [InternetConnection]

  HttpTransportType=HttpIndy

  to the AppWave Browser configuration file, which is located at:

  • Windows Vista and Windows 7: C:\Users\\Local Settings\Embarcadero\AppWaveBrowser\Toolbox.ini
  • Windows XP: C:\Documents and Settings\\Local Settings\Application Data\Embarcadero\AppWaveBrowser\Toolbox.ini
• When uninstalling AppWave Browser, all data may not be removed. You will need to manually delete the dynamic cache folder, located at
  • Windows 7: C:\Program Data\Embarcadero\Product Repository\StreamingCore\Profiles\[user]\Applications.
  • Windows XP: C:\Documents and Settings\All Users\Application Data\Embarcadero\StreamingCore
• The AppWave Browser uninstaller may become unstable if a non-admin user attempts to remove an instance of AppWave Browser that was installed by an admin user. In this case, the admin user should uninstall AppWave Browser. Works as expected.

AppWave Studio

• AW-7233: Apps mastered with AppWave 4.1 cannot be broadcasted to an AppWave 2.0.1 server. Use AppWave Browser 2.0.1 to master and broadcast apps to the AppWave 2.0.1 server, or upgrade your server to the 4.1, which is the recommended solution.
• AppWave 3.0.1 or higher is required to master with the following templates: Adobe Creative Suite 5.5, Microsoft Project, and Microsoft Visio. Works as expected.
• AW-3727: Sometimes broadcasting an app results in an "Operation failed" error even though the application has been successfully deployed to the AppWave Server.
• Some applications that appear on the Embarcadero AppWave take advantage of Studio features in AppWave Browser 3.0 and later, such as multi-entry and complex scripting. To master this type of complex application, such as Microsoft Office, you need to update your AppWave (the host installation) and AppWave Browser to version 3.0 or later.
• Record and install is not supported on 64-bit systems. However, you can capture data from an existing installation using a template.
• When mastering large applications on Win 7 32-bit systems, Appwave Browser might enter into a non-responding state for a limited period of time. When this happens, the Mastering window will go to the background, behind the Studio window and it needs to be explicitly brought to the front.
• Sub-processes created during testing of an App will block AppWave Studio from overwriting the .app file if they are still running when you attempt to master.

App Specific

• Delphi and C++ Builder: Applications created using the Delphi or C++ Builder apps may not run outside of the Delphi or C++ Builder apps IDEs. This may be because the application you created is missing the required runtime libraries. You need to copy the required libraries from the virtual space in which the Delphi or C++ Builder IDE app runs, into the same folder as your application. This can be done in the Delphi or C++ Builder IDE by either of the following two methods:
  1. Select View > File Browser.
  2. Navigate to the files required and copy them into the same folder as your application.
  or
  1. Select Tools > Configure Tools > Add.
  2. Under Title, enter Command Prompt.
  3. Under Program, enter C:\Windows\system32\cmd.exe.
  4. Click OK.
  5. Click Close.
  6. Select Tools > Configure Tools and select Command Prompt.
  7. Use this command prompt window to copy all the files you need from the C:\XE3\bin folder in the virtual space into the same folder as your application.
• Change Manager: Command line invocation is supported with the App. Right-click the App icon and select Open Terminal. Command line terminal can be used only for the last App launched. Scheduler is not currently supported, so you will not be able to plan a script.
• .Net reliant Apps:
  • On Vista and Windows XP systems, to master applications that require .Net, make sure that captured application had the .Net runtime included during mastering. For the Apps mastered using templates, the correct runtimes are selected automatically.
• Toad: To use Toad for DB2, you must install the DB2 client from the operating system and connect to it outside of AppWave Browser.

Upgrading AppWave

• AppWave Host Upgrade Notes
• AppWave Browser Upgrade Notes
• Upgrading When You Have Internet Connection
• Upgrading Using the Media Kit
• Migrating ToolCloud Settings to AppWave
• Replacing Embarcadero License Center with AppWave

Upgrade Notes

AppWave is based on the Embarcadero ToolCloud technologies. If you are running ToolCloud and ToolBox, the following information will help you upgrade to the new system.

• AppWave Installer: The AppWave installer includes upgrade functionality.
• Backing Up: Before you upgrade to AppWave, make backups of your existing system. The install and upgrade process does not include undo functionality. Backing up AppWave is discussed in the "AppWave Administrator Guide.
• Importing Licenses: When upgrading from ToolCloud to AppWave, the AppWave installer will attempt to import licenses from an existing 1.x system. It will shut down the existing Embarcadero License Center (ELC) and remove the 1.x ToolCloud.
• InterBase Port: Upgrading from ToolCloud 1.x to AppWave will fail if the InterBase port number is changed during the upgrade process.
• Users and Licenses: Users and license assignments are automatically migrated to AppWave if you use the upgrade option in the installer.
• Running in Parallel: You cannot run ToolCloud and AppWave in parallel on the same machine.
• Migration Folders: If, for example, on ToolCloud 1.x you had a assigned a Silver license to a user then when you upgrade, there will be a folder called Migration_Silver, which will contain the user and all the applications corresponding to the Silver license level.
• All Apps Folder: When installation is complete, the All Apps folder will not contain the All Users group. AppWave Browser users will have access only to applications corresponding to the license level assigned on 1.x through the migration folder.
• Restricted Mode: In its default configuration, anyone inside your firewall can access your AppWave and run the applications broadcasted by it. Also, Apps broadcast from AppWave Studio will immediately be added to the All Apps folder and will be available to the All Users group. To secure your AppWave, set Allow client to register user to off. You should also edit the All Users group, the All Apps folder, and the user to limit the licenses available for that user. For more information, see Managing AppWave, Managing Folders, Managing Groups, Managing Users and Publish Applications.
• Embarcadero License Center: Embarcadero License Center (ELC) is integrated with AppWave and installs automatically when you install All-Access. ELC requires the Java Runtime Environment (JRE) on the same machine, which is also installed automatically by the AppWave installer.
• License Hosting: You use the Embarcadero License Hosting web site at members.embarcadero.com/login.aspx to create configuration files that let Embarcadero License Center track and control license distribution on AppWave. The site requires login and host server information. During AppWave installation, record the AppWave host name and IP address for later use on the License Hosting Website.
• Windows Services Registration: AppWave is automatically registered as a Windows service, therefore it will start when your machine starts. By default, the service is named Embarcadero AppWave. If you do not want AppWave to start as a Windows service, you can reset or otherwise change the service by selecting Start > Embarcadero AppWave X.X > Configure AppWave. In the Embarcadero AppWave Properties dialog, select the General tab and change the service parameters. For instructions on providing AppWave Browser to users, see "Providing Users with AppWave Browser" in the AppWave Administrator Guide.

Upgrade Instructions

The wizard-based installer guides you through the upgrade process. This section describes installation prerequisites and the Installation Wizard. It also provides information about decisions you must make during installation. You must have administrative privileges to run the install. To complete the installation, you need to complete each panel of the Installation Wizard.

Installation Wizard - License Agreement

To start the installation process:

1. Double-click setup.exe and the License Agreement appears.
2. Click I accept the terms of the License Agreement.
3. Click Next and the previous version detected panel appears.

Installation Wizard - Upgrade previous AppWave version

• Remove and install: If chosen, the ToolCloud or previous version of AppWave software will be uninstalled without backing up the previous version. All license files and binary files are not deleted when upgrading from AppWave 2.x to 3.x.
• Upgrade: If chosen, the data for the ToolCloud or previous version of AppWave will be backed up, the previous software will be uninstalled and AppWave will be installed. Data, such as users and groups from the previous ToolCloud or AppWave version will be imported into the new installation of AppWave.

Installation Wizard - Remove previous Embarcadero License Center

In ToolCloud versions 1.x, Embarcadero License Center (ELC) was installed as a separate application. In AppWave, ELC is more tightly integrated into the product. This screen will only appear if you are upgrading from ToolCloud to AppWave. When upgrading AppWave, you will not see this screen.

• Remove without import: If chosen, the previous version of ELC will be removed. License information is not retained. You will have to complete the License setup option on the AppWave Dashboard. For more information, see Set Up Licenses in the AppWave Administrator Guide.
• Remove and import: If chosen, licenses previously setup in ToolCloud are backed up, ELC is removed and then the licensing information is imported into AppWave. The licenses will be setup by the installer and there will be no need to set them up again.

Installation Wizard - Install Options

From this point onwards, the upgrade and install procedures are identical. For information on the options available, see "Installing AppWave" in the AppWave Administrator Guide.

AppWave Browser Upgrade Notes

• Download AppWave Browser from the upgraded AppWave Host and then run it. AppWave Browser will prompt you to upgrade the first time it runs. Your bookmarks, folders, and local app repository will be retained.
• Users running AppWave Browser 3.0 or 3.0.1 will not be able to upgrade the Browser from the AppWave Store if the Browser was installed by the administrator for all users on that machine, using the installer with the -a command line parameter. This prevents the user from running apps from the AppWave Store. In order to resolve this problem, the administrator should uninstall AppWave Browser and then the current user with administrative rights should install the most current version of AppWave Browser.

Upgrading Using the Media Kit

Upgrade ToolCloud 1.x to AppWave 3.x using the Upgrade instructions described above in Upgrade Instructions. For information on updating the product catalog and applications, consult the AppWave Quick Start Guide.

Migrating ToolCloud Settings to AppWave

If you have ToolCloud installed on one system and want to upgrade to AppWave and install AppWave on a different system, you can migrate your ToolCloud ELC settings such as licenses, users, and groups to the new AppWave by following these steps.

1. Install AppWave on the new system.
2. Backup the license files on the AppWave installation, so that if something goes wrong you can go back to previous settings. These files are located in …\[AppWave_install_dir]\elc\conf and include:
   • Licenses.zip
   • userlist_concurrent.txt
   • userlist.txt
   • iplist.txt
   • groups.xml
3. Backup the licenses zip files located in …\[ELC_install_dir]\conf (default: C:\Embarcadero\ELC4.2\LicenseCenter\conf).
4. In the MANAGE LICENSES area, click License Inventory and then click Import License. Browse to the license .zip file and then click Import License or you can copy the licenses to …\[AppWave_install_dir]\elc\conf on the system running AppWave .
5. Backup the licenses assignments files located in …\[ELC_install_dir]\conf. Copy them to …\[AppWave_install_dir]\elc\conf on the machine running AppWave .
6. Reload the license files, In the MANAGE LICENSES area, click License Inventory > License Files and then click Reload License Files.

Replacing Embarcadero License Center with AppWave

The Embarcadero License Center software has been integrated into AppWave. If you are upgrading your Embarcadero License Center (ELC) installation, you will set up licenses, users and groups. You do not have to cache products on AppWave if AppWave will only be managing your site licenses and you do not have an All-Access license.

Embarcadero Technologies Technical Support

If you have a valid maintenance contract with Embarcadero Technologies, our Support team will assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period.

Evaluators receive free technical support for the term of their evaluation. To download evaluations of Embarcadero Technologies products go to the www.embarcadero.com.

To contact Support, go to Support.

Comments: [email protected]