Welcome to Embarcadero® AppWave™ 4.2
AppWave
Web Site | Embarcadero
Technologies Home | Technical
Support
ReadMe Last Updated: August, 2013.
Any updates to these ReadMe notes will be available at
docs.embarcadero.com.
Thank you for using Embarcadero AppWave 4.2.
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 - 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
Release Notes
Additional Resources
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. https://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).
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
- 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.
AppWave Browser
- Different progress alerts are displayed when launching an application.
- Applications are now organized in a more logical way, easier for the
user to manage. A new item has been included on the menu: Managed Apps. All the apps running on the system are listed here.
AppWave Studio
-
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.
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
AppWave Browser
- 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. Added
apps are automatically bookmarked and will appear in your AppBookmarks folder. 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.
AppWave Studio
- 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 Browser.
Release Notes
System Requirements
AppWave Public and Enterprise Store Requirements
The AppWave Store is supported on the following internet browsers:
- Internet Explorer, version 7 and later (8, 9, and 10)
- Mozilla Firefox, version 8 and later
- Google Chrome, version 15 and later
- Safari, version 3
AppWave Enterprise Requirements
AppWave 32-bit Minimum Requirements
- Intel Core i3 processor or higher
- 2 GB of RAM
- Basic install requires about 2GB with an additional 100 GB for the
repository of initial and future product downloads and 100 GB for cache.
- 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
- Windows 8, 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, with the following additions:
- AppWave is supported on the following operating systems:
- Windows 2003 64-bit
- Windows 2008 R2
- Windows 2012
- Windows 7 64-bit
- Windows 8 64-bit
General AppWave Requirements
- AppWave is supported on Mozilla Firefox, Google Chrome, 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
- Internal purposes: 61616
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.7 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
- Windows 8, 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:
AppWave
- For the AppWave 4.2 release the protocol has been changed from app:// to appwave://.
Because of this change, the user with the 4.2 release will not be able
to launch apps from a regular web browser navigating an older host. A
host earlier than the 4.2 release only uses the app:// protocol as
shown in the following screen shot. But because the 4.2 browser only
“listens” to the appwave:// protocol it cannot launch the app from the
older host.
AppWave Enterprise
- 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-7863: If AppWave is running, ADB (Android Debug Bridge) reports the emulator device -5566 is offline.
However ADB detects it and reports it as a device running on port 5567 (incorrectly). If you then run RAD Studio/HTML 5
Builder, and attempt to deploy an application to a running emulator device, it fails because there are certain ADB commands
that count on only one emulator device running. If there are multiple devices running, or if ADB thinks multiple
devices are running, an error is thrown.
This conflict is caused by AppWave. If the AppWave service is running,
ADB reports port 5566 [incorrectly] as an available Android emulator.
So the problem is with ADB which incorrectly reports our server, or in fact any server that listens to a
port in 5554-5584+1 range, as Android device. In case of multiple emulators, the option -s should be
used to specify what emulator to use.
NOTE: The issue of the ADB switches has been addressed in RAD Studio/HTML 5 Builder.
AppWave Admin
- AW-6186: Concurrent
licenses are automatically added when a new group of user is created.
If the admin wants to apply named licenses he needs to remove
concurrent licenses first.
AppWave Studio
- AppWave 3.0.1 or higher is required to master with the following
templates: Adobe Creative Suite 5.5, Microsoft Project, and Microsoft
Visio.
- AW-2883: When the user
is trying to master a custom app, sometimes AW Studio auto-detects and
applies an existing tempalte from a free app. For example application
using Ghostscript.
- 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.
- In order to master an application in Windows 7 or Vista, you
must launch the AppWave Browser as an Administrator, close the AppWave
Browser, and open it again by right-clicking the AppWave Browser
shortcut, and select "Run as Administrator."
- 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:
- Select View > File Browser.
- Navigate to the files required and copy them into the same folder as your application.
or
- Select Tools > Configure Tools > Add.
- Under Title, enter
Command Prompt.
- Under Program, enter
C:\Windows\system32\cmd.exe.
- 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.
Upgrading AppWave
This section contains the following topics:
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:
- 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:
- Licenses.zip
- userlist_concurrent.txt
- userlist.txt
- iplist.txt
- groups.xml
- 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.2 |
| AW-7689 |
Access violation when closing AwppWave Browser while streaming.
|
| AW-7663 |
Exception appears when there's no connection to the public host. |
| AW-7473 |
Cannot remove shell notification icon. When AWB (AppWave Browser) is running in tray mode, clicking on AWB shortcut on desktop or start menu appears to do nothing. |
| AW-7322 |
BSOD (Blue Screen of Death) :
- Because of kernel statck overflow during a failed app mount
- Win8 - after upgrading AWH (AppWave Host) from 4.1. to 4.1.1.
- When building cpp samples from RAD Studio XE4
- W7x64 -BSOD with Qihoo 360 anti-virus
- After launching 177 Apps.
|
| AW-7169 |
AppWave streaming crashes Symantec anti-virus. |
| AW-6187 |
Improve notification to the user when they have exceeded the number of allocated licenses. |
| AW-6162 |
Avast real-time file scanner causes machine to freeze when caching ER/Studio. |
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.