Welcome to Embarcadero® AppWave™ 4.1
Web Site | Embarcadero
Technologies Home | Technical
ReadMe Last Updated: January 30, 2013.
Any updates to these ReadMe notes will be available at
Thank you for using Embarcadero AppWave 4.1.
Based on Embarcadero ToolCloud technology, AppWave is a Private PC App Store that takes the friction out of traditional software applications, boosting user and organizational productivity by converting applications into AppWave Apps.
AppWave works with all types of PC apps, including software applications that you may have purchased, 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. You may also find certain free apps available to you through Embarcadero's own AppWave Store, that will help you explore AppWave, discover new apps, and experience the power of AppWave.
AppWave comprises three 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 Public Store - hosted by Embarcadero, the AppWave Store provides fast and easy access to hundreds of desktop applications. When an AppWave Browser user connects to the AppWave Store, they can browse, explore, and run these free apps using technology that encapsulates and streams applications without requiring installation.
- 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 docs.embarcadero.com.
What's New in AppWave
What's New in AppWave 4.1
This section describes the new features of the various AppWave components in this release.
AppWave Public Store
- Public Store Set Up and Use. The process of setting up and using apps in the Public Store has
been streamlined so you can get up and running quickly.
- Open the Store and create an account. Once you complete the required information you
just have to click Sign Up and your account is created.
- In the Public Store, select an app you want to run and click Free.
- The first time you run an app in the Store, you are prompted to install the AppWave Browser.
The Splash Screen installer appears and you can follow the installation progress.
Once complete, the AppWave icon is placed in the System tray.
- The End User License Agreement of your selected app opens. Just click Accept and the selected app runs on your desktop.
AppWave Enterprise Store
- AppWave Admin User Interface Customization:
- Automatic Proxy Server Usage Detection:
- Independent Software Vendor Portal: The Vendor Portal is the gateway to an easy-to-use app store
for independent software vendors (ISVs). The ISV can:
- Self-register as a vendor.
- Set up your financial account with payment information.
- Add and manage your products.
- Access and view summary reports of your sales and downloads.
- Provide End User Support for your customers.
- Improved Progress bar provides more information, such as the operation being performed, downloading, streaming, starting, and the percentage complete.
- Apps you run are automatically bookmarked and appear in your Managed Apps tree.
Adding Native Installer to AppWave Catalog: You can now add a Native Installer to the AppWave Catalog with the required metadata.
- It delivers software that cannot be easily mastered. Some examples of this are: Native 64-bit, printer drivers, and software establishing Windows services.
- It also distributes data and media content packaged up as installers. Examples of this type of content would be: data models, training materials and manuals, and data sets.
- The mastering steps in the AppWave Studio require you to provide key information needed to complete the mastering successfully:
- Provide the install location, launch executable, and an un-install registration key.
- You also need to complete all required fields in the Launch & Brand step such as working folder, product name and version, and publisher.
- 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.
What's New in AppWave 4.0
This section describes the new features of the various AppWave components in this release.
AppWave Public Store
- Usability Update : Many improvements to the user interface have been made. These changes are:
- New AppWave Store design.
- App listings are now displayed in a grid view.
- Hovering the mouse over an app listing displays expanded app details.
- The product page for an app now includes three tabs:
- Overview: When clicked, the screen shot expands in an overlay showing the app and the app description.
- Details: A description of the app, including app details, version, and requirements.
- Review: Reviews for the app as well as the ability to create a review.
AppWave Enterprise Store
- New Reports: New usage reports allows you to monitor usage of streamed apps, including free apps that use workstation licensing. AppWave does not monitor the use of locally installed apps such as those used offline. These new reports include the following:
- Streamed Application Usage Frequency Report: Number of times each streamed application was used by a specified user or group of users during the specified time range.
- Streamed Application Usage Duration Report: Total number of hours each streamed application was used for the specified period. Streamed application that were not used are excluded.
- Streamed Application Usage Duration by User Report: Total number of hours a streamed application was used by each user and group for the specified period.
- Display of Apps:The apps are displayed in the following categories:
- Average Rating (from highest to lowest) of apps available on the Enterprise Store
- Download Popularity (from most downloaded to least) of apps available on the Enterprise Store
- Time on System (from newest to oldest) of apps available on the Enterprise Store
- The home page consists of alternating scrollable "top 10" sections interleaved with advertising banners
- Viewing Featured Banner Placements Promoting Specific Apps:
- The administrator has access to an interface that allows him to select which apps within
the Enterprise store to promote
- The apps will have, as part of their metadata, pre-built ad banners that will be displayed on the home page
- Smart App Links: Smart App Links allow you to right-click a document and open the app associated with that document type. It also lets you, for example, from a Microsoft Outlook app email, double-click the Microsoft Word file attached and open the document in the Microsoft Word app. When you try to open a file, AppWave cross references the file type with a database, retrieves a list of appropriate apps that can open the file, retrieves a list of already installed apps that can open the file, and presents a list of appropriate apps to you. This gives you the ability to immediately open the file and set a default within the same workflow regardless of if the application is already installed or not. AppWave Studio now includes the ability to include file type associations (FTA) information inside the mastered app. There is also a tool available for updating already mastered apps with the new FTA information.
- WebApps Support: WebApps are applications that are accessible via an Internet Browser, typically executed on an application server either hosted by the enterprise customer directly or accessed as a "cloud" service that is hosted externally. Popular business-related WebApps include, Salesforce.com, Office Live, Microsoft Exchange (via OWA), Eloqua, and IBM/Lotus Connections. WebApp support allows your organization to provide a catalog of both internally available WebApps as well as controlled access to external WebApps. AppWave provides single click access for easy and transparent access to WebApps. The AppWave catalog and its integrated licensing and reporting capabilities makes:
- AppWave an ideal platform for distributing, monitoring and controlling access to WebApps for your IT department.
- AppWave Browser an ideal catalog, discovery and rating/review interface for WebApps for users.
- AppWave Studio the ideal mastering tool for defining the parameters for the display and execution of WebApps from within AppWave Browser.
- Progress Feedback: The Progress bar displays meaningful status text during app streaming and launch. The bottom
of AppWave Browser now contains an app status bar, displaying the app name, a progress bar,
and the percentage streamed. If more than one app is streaming, the progress for the app
selected and displayed in the application window displays.
- Colored and Labeled Buttons: New colorful buttons with meaningful labels display in the Application window.
- Run: Launches an app that has been cached on your private AppWave
- Install: Launches the app installer. Installed apps run faster on your system and can be run
when not connected to the private or public AppWave when offline license usage privileges
have to been granted to the user.
- +Add: Add an app that is not currently available on your private AppWave but can be to
downloaded from the Embarcadero pubic AppWave to your private AppWave. Once
available on your private AppWave, any user can then run or install the added app. A Once
AppWave finishes broadcasting the app to your system, it will launch automatically and the
+Add button for the app will change to Run.
- Downloading: App that you have chosen to +Add is being broadcasted to your system.
- Master: Opens this mastering template in AppWave Studio, so you can then complete the
mastering process for this app.
- Information Displayed on Hover: When you hover your mouse over an app in the Application window, more detailed app
information displays. Clicking More displays the product channel.
- Open for Upgrade: This command, available under the Gear command,
takes an existing .app file and extracts it onto your machine. Once it is extracted you
can make changes and then remaster it. It is a very powerful tool when you want to apply a
service pack or add some files to an existing mastered app.
- Smart App Links: Smart App Links allow you to right-click a document and open the
app associated with that document type. It also lets you, for example, from a Microsoft Outlook app email,
double-click the Microsoft Word file attached and open the document in the Microsoft Word app.
When you try to open a file, AppWave cross references the file type with a database, retrieves a list of
appropriate apps that can open the file, retrieves a list of already installed apps that can open the
file, and presents a list of appropriate apps to you. This gives you the ability to immediately open the
file and set a default within the same workflow regardless of if the application is already installed or not.
AppWave Studio now includes the ability to include file type associations (FTA) information inside the
mastered app. There is also a tool available for updating already mastered apps with the new FTA information.
- WebApps Support: WebApps are applications that are accessible via an Internet Browser,
typically executed on an application server either hosted by the enterprise customer directly or
accessed as a "cloud" service that is hosted externally. The AppWave Studio now provides the ideal
mastering tool for defining the parameters for the display and execution of WebApps from within
AppWave Public and Enterprise Store Requirements
The AppWave Store is supported on the following internet browsers:
- Internet Explorer, version 7 and later (8 and 9)
- Mozilla Firefox, version 8 and later (9 and 10)
- Google Chrome, version 15 and later (16 and 17)
- Safari, version 3 and later (4 and 5)
AppWave Enterprise Requirements
AppWave 32-bit Minimum Requirements
- Intel Pentium III 1.2 GHz processor or higher
- 2 GB of RAM
- Basic install of 650 MB with an additional 100 GB for the repository of initial and future product downloads. (Current app inventory of all apps requires 53 GB of disk space.)
- High resolution monitor (1024 x 768), 16-bit display or greater
- AppWave is supported on the following operating systems:
- Windows XP SP3, 32-bit
- Windows 2003, 32- and 64-bit
- Windows 2008 R2
- Windows 7, 32- and 64-bit
AppWave 64-bit Minimum Requirements
Requirements for the 64-bit version of AppWave are the same as for the 32-bit version, except for the following:
- AppWave is only supported on the Windows 2008 R2 operating system
General AppWave Requirements
- AppWave is supported on Mozilla Firefox, or Internet Explorer 7 or later
- AppWave uses the following ports by default, and can be modified by the administrator at the time of installation:
- Tomcat and other internal processes: 8009
- AppWave server port: 80 (This can be modified in AppWave System Properties after install.)
- Shutdown port: 8082
- Database port: 3052
- Licenses port: 5567
So do not use these ports as the communication port or for other applications.
Note: You may choose to allow your AppWave Private Store to communicate with Embarcadero, in order to automatically receive product and license updates. Following is a list of Embarcadero servers that are accessed, which may need to be added to your trusted list within your firewall: appwave.embarcadero.com, AppWave Store; license.codegear.com, All-Access license hosting; reg.codegear.com, AppWave registration; cc.codegear.com, auto update; and altd.embarcadero.com.
- You require Embarcadero license certificates for the Embarcadero products you purchase.
- All products that you share through AppWave reside in the repository. Ensure that you have enough hard disk space to accommodate all of the products prior to defining the location of the repository directory. Individual space requirements can be found in the individual product documentation at docs.embarcadero.com.
- AppWave ships with JVM 1.6 embedded.
- AppWave ships with InterBase XE3 embedded.
AppWave Browser Technical Requirements
- AppWave Browser is a Windows application that supports 32-bit applications on the following operating systems:
- Windows XP SP3, 32-bit
- Vista SP2,32-bit
- Windows 7, 32-bit and 64-bit
- AppWave Browser installer is 50 MB in size and AppWave Browser requires a minimum of 512 MB of memory to start. More memory will be consumed based on usage, as apps are launched.
- Default cache size for AppWave Browser is 512 MB.
- Products available in the AppWave Browser have the same approximate memory and disk size requirements as they do independent of AppWave. For the requirements of individual Embarcadero products, consult the product documentation at docs.embarcadero.com.
- AppWave Browser supports 32-bit applications on 32-bit and 64-bit operating systems.
AppWave Studio Technical Requirements
- Mastering is supported currently only on 32-bit operating systems.
- Mastering of 64-bit applications is not supported.
Limitations of Application Virtualization
Some apps in AppWave will perform automatic updates from vendor websites. Such in-app auto-updates will generally not work in a virtualized app. Should such an auto-update happen when running an app from AppWave, AppWave Browser users should cancel the update operation as it is likely to fail. Similarly, users should not select menu items within an app that aims to update from vendor website. The solution is to apply updates for existing apps once for all users via the mastering process using AppWave Studio. The most recent versions of Embarcadero XE apps are always available on the AppWave Store and are made available to Embarcadero users with maintenance contracts. Embarcadero also updates third party apps on the AppWave Store regularly.
Known AppWave Issues
Known AppWave issues are divided into the following categories:
Public AppWave Store
- AW-3572: AppWave Store does not detect AppWave Browser when the Browser was installed by an administrator for all users, using the command line -a parameter, and another user logs in to the AppWave Store and tries to run an application from the Store. The user will be prompted to install AppWave Browser, which requires administrative rights to perform. However, all users will be able to access and run apps from the AppWave Store node in AppWave Browser.
- AW-3672: AppWave Store does not recognize the AppWave Browser installation if the current user is not the user who first installed AppWave Browser from the store. Users, other than the user who first installed AppWave Browser, will need to run the Download Manager and install AppWave Browser every time they launch an app from the AppWave Store.
AppWave Enterprise Store
AW-7290: After upgrading, for complex applications such as Microsoft Office, the number of seats available will be set to unlimited. You will need to reset the number of seats licensed in the License Automation pages for the application.
- 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.
- 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
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".
- 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
- 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
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.
- 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.
- 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:
- Select View > File Browser.
- Navigate to the files required and copy them into the same folder as your application.
- Select Tools > Configure Tools > Add.
- Under Title, enter
- Under Program, enter
- Click OK.
- Click Close.
- Select Tools > Configure Tools and select Command Prompt.
- 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.
This section contains the following topics:
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.
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:
- Double-click setup.exe and the License Agreement appears.
- Click I accept the terms of the License Agreement.
- 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.
- Install AppWave on the new system.
- 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:
- Backup the licenses zip files located in …\[ELC_install_dir]\conf (default: C:\Embarcadero\ELC4.2\LicenseCenter\conf).
- 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 .
- Backup the licenses assignments files located in …\[ELC_install_dir]\conf. Copy them to …\[AppWave_install_dir]\elc\conf on the machine running AppWave .
- 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.
|Bugs Fixed in AppWave 4.0
||[Regression] "An outgoing call cannot be made since the application is dispatching an input-synchronous call" error displayed.
||When you search for a product and multiple results are found, their icons are not properly listed.
||Launching Performance Analyst from DBArtisan 9.1.1 app does not work.
||Relation between LDAP user and group is not imported when group name is different than pre-Windows 2000 group name.
||Error message is returned after turbo mode is disabled.
||[Regression] When switching to User Mode, Driver is not uninstalled after reboot.
||Browser displays offline warning for dummy app.
||Browser occasionally displays RES_E_ITEM_NOT_FOUND error on start.
||Excluded registry keys still be capture by StreamingFSD.
||Unable to create instance of StreamingCore: unable to get error message error message is returned.
||Research - Longer the streaming performance test results in a sizable increase in the time to stream an app.
||Research - Linear increase in time to stream an app related to number of threads used..
||Reconstructing an App from AppWave Studio returns Quit ReconstructAppToMachine. Status: 0.
||[Regression] AppWave Browser fails to display Edition on Overview Page and Versions Page.
||[Regression] Increased timing for record and install, master and broadcast processes.
||IBM Rational Application Developer fails to run on Win 7 64.
||[Regression] Unable to launch SAP Crystal Reports after the app was broadcasted.
||The results from "View All", after search, are not accurrate.
||Tab buttons in Store App Channels are not displayed properly in IE8, 9 and on AWB running on a Windows XP machine.
||Win7 (x64) registry issues.
||[REGRESSION] Some apps like Adobe Audition and Dreamweaver fail to launch at prefetch and launch after broadcast.
||[Sometimes 1 out of 10] Uninstall and reinstall leave the system in bad state.
||"Streaming player failed to initialize properly" error is returned when launching apps with turbo mode disabled.
||Visio/Project/ Office .app fails to launch with error "AppWave Streaming Server timeout".
||Search word is missing from Store search field with IE (9.0, 8.0, 7.0).
||Sign Up form validation is performed when searching on Store.
||Adobe® Audition® blocks when trying to browse on the disk for saving a file on Windows 7 x64.
||When using two apps that have connection to Microsoft SQL Server (ADO), the provider list it's not displayed and you are not able to establish a connection to a database.
||Visio .app (installed on C:\Program Files) failes to launch on Win 7 64 bits only.
||BSOD appeared after closing LibreOffice 3.3 on Windows 7x86.
||Microsoft Project and Microsoft Visio fail to launch when Norton Internet Security 2012, McAfee Total Protection or Avast Internet Security 7 anti-virus programs are installed on the machine running AppWave Browser.
||[Sometimes] [Once] Access violation appears when trying to load Store page.
||[SOMETIMES -rare] When upgrading from 3.0.1 to 3.1 Browser (build 81) using DM from Production Store, after OS reboot Mad Except appears.
||Cannot search for 0 (zero) on production store.
||AppWave Browser becomes unresponsive if the user does not choose one of the options from EULA dialog for a few hours (after launching an app from store).
||From the Account Dashboard in the AppWave Store, you cannot change your contact details, password, and Newsletter preference if you have an EDN account that was created before accessing the store and your EDN details are missing some attributes that are now required, such as language, company, phone, and state. You will first need to provide these details on the Member Services page of the Embarcadero Developer Network Website, edn.embarcadero.com.
||[Regression]Unable to launch OpenOffice after Record an Install.
||AppWave Browser crashes upon pressing cursor up or down key while the focus is on the address bar.
||Apps launched from the Store provide feedback only at the beginning of the launching process. You may think the app has hung but should just wait a little while for the app to run.
||Rapid SQL could not be started on Windows 7x64.
||IBM Rational Application Developer .app fails to launch from Start menu, launch process enters in a loop - 32 bits VMs.
||Upgrade of the AppWave browser takes several minutes with no feedback to the user.
||When AppWave Browser is installed by a non-administrator user who is running the installer as an administrator, AppWave Browser should be installed for all users on the machine.
||[Regression] Some products launched on 2.0.1 AWB version return "Failed to launch"/"License server does not have license for this product" error after AWB is upgraded.
||The Register and Forgot Password links are not highlighted if you use TAB control.
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.