Set System Properties
Go Up to AppWave Configuration and Administration
From the System Properties pages you can configure AppWave behavior.
System Properties tabs:
General Tab
From the SYSTEM MANAGEMENT menu, click System Properties. The System Properties pane appears.
Make the changes required on this page and then click Save.
Note: The AppWave process must be restarted before changes to the Proxy Server take effect.
General Properties fields.
| Field | Description |
|---|---|
| AppWave name | This is the name of AppWave as it appears to your AppWave Browser users. |
| Http Resolve | Auto resolve or manually set the http host. Auto resolve sets the Http Host value to be the host name of the system on which AppWave is installed. |
| Http Host | The host name of the system on which AppWave is installed. |
| Http Port | The default port number for AppWave is 80. You can accept or change the port number setting during AppWave installation. After installing, you can change the port number here. Changes to the port number will be in effect after AppWave is restarted. |
| Restricted mode | Restricts the reviews that users can see, also restricts availability of custom Apps broadcast to AppWave and affects how Apps are streamed. When running in Restricted mode, Apps broadcast will require Admin approval before release and will be in a Pending state. For information on publishing pending applications, see Publish Applications. If disabled, all newly broadcast Apps are automatically available to all users; they are published to the All Apps folder which is assigned to the All Users groups. If you want to monitor product reviews submitted by users and approve or reject their comments, select On. Reviews that contain questionable or inappropriate wording are automatically rejected. |
| User-initiated download | If set to On, when an AppWave Browser user runs an application that is internet available but not downloaded onto AppWave, downloading will be initiated. The application will be ready to run once it is downloaded to AppWave. |
| Auto deploy applications | If set to On, once applications have been cached to AppWave they are automatically copied to all streaming servers in order for the applications to be available when requested by the AppWave Browser user. |
| Auto stream applications | Once an application has been cached to AppWave, it is not automatically streamed. Setting this option to On automatically streams the application when it is added to AppWave. |
| Auto assign country group | This property works for EDN and LDAP users. If set to On, this creates groups automatically based on the AppWave Browser user’s location. This enables AppWave to restrict access to streamed applications based on the country, which is useful when export regulations dictate that certain applications cannot be used in specific countries. |
| Allow reviews update | If set to On, when updating the catalog, also allows reviews originating on the AppWave Store to be copied to AppWave. |
| Allow AppWave accounts | In environments where LDAP is integrated with AppWave, you can disallow local accounts, thus requiring all users to use their domain credentials to access AppWave. When this property is set to Off a local user cannot connect from the AppWave Browser or the AppWave console; the user needs to connect with a domain user name. |
| Allow Public Store to be visible | Set to off if you do not want AppWave Browser users to be able to access the AppWave Public Store via the internet. |
| Allow client to register user | Allows a new user account to be created when the AppWave Browser user attempting to connect to AppWave does not already have a user account. |
| Allow blank password | Allows new user accounts to be created that do not require a password. |
| Create user as author | Automatically assigns all new users to the Authors group which enables them to use AppWave Studio and master and broadcast applications through AppWave Studio. |
| Download pool size | Specify the maximum number of simultaneous downloads that can be initiated by AppWave users. |
| License Notifications | Specify thresholds for license pool usage levels. When usage levels grow above specified levels, notifications will be generated. When usage levels reach high or critical, the chance of users being denied licenses increases and you should consider adding more licenses. License notifications can be generated for all licensed products managed by AppWave. |
Email Tab
You can configure AppWave to send you email alerts in certain circumstances, for example when there are new or upgraded applications available; when a download has started, finished successfully or not; when the Embarcadero AppWave Store was checked for catalog updates and whether the catalog update was successful or not. If AppWave is configured to moderate reviewers comments you can also receive email notifications when new reviews have been submitted for your approval.
Follow these steps to access the Email tab:
- From the SYSTEM MANAGEMENT menu, click System Properties, and then click the Email tab. The Email tab appears.
- Select Enable sending email and then provide the particulars of your email server.
- In the Subscribed Users area, click the expand icon
and then enter the email address of the user to receive email notifications and then click the add icon 
.
Enter more addresses in the same manner if required. - In the Message Types area, select the types of messages for which AppWave should send out email notifications. By default, all message types are selected. Deselect the message types for which you do not want email notifications. You will still see all types of messages on the Notifications page but for only those selected will email notifications be sent.
- Click Save
Note: You can also configure AppWave to send out notifications when license usage has reached certain levels by specifying the high usage and critical usage levels on the General tab of the System Properties page. For more information, see License Notifications
Proxy Server Tab
Security in some environments requires the use of an internet proxy. You can configure AppWave to use a proxy instead of connecting to the internet directly for catalog updates and product downloads, and communications with AppWave Browser users. Proxy settings are automatically recognized during AppWave start up and after clicking the Refresh button if they are set in Internet Explorer, in the Windows Control Panel, or have been imported to system-wide level using netsh/proxcfg or the bitsadmin utility.
Access the Proxy Server tab from the SYSTEM MANAGEMENT menu. Click System Properties and then click the Proxy Server tab. The Proxy Server tab appears.
Note: If a proxy server has not been set, this page indicates that a proxy server was not used.
Possible scenarios:
- The system does not use a proxy. You will see this message: The prosy is not used.
- An anonymous proxy has been configured. You will not be able to change the User name and Password and these fields will not be available. You will see the proxy server name and port.
- A non-anonymous proxy has been configured. You must enter the User name and Password on this screen and click Save in order to connect to the proxy server once AppWave has been restarted.
- Note: To force AppWave to detect a change in the proxy settings, click Refresh .
App Repository Tab
Use the App Repository tab to specify the location of the repository where cached applications are stored on AppWave. The location of the Application Repository where products are cached, is specified during installation; however, if you want you can change the product repository to a different location here. This may be useful where there are several GBs of data to move which could cause network congestion or if you want to temporarily use another repository for testing. The repository can be a local directory or a network shared directory.
Follow these steps to change the path:
- From the SYSTEM MANAGEMENT menu, click System Properties, and then click the App Repository tab. The App Repository tab appears.
- In the Application Repository field, enter the location where you want the cached applications on AppWave to reside.
- To save the changes and later move the files to the new location, click Save.
Optimization Tab
Access the Optimization tab from SYSTEM MANAGEMENT. Click System Properties and then click the Optimization tab.
Java Options
- Initial memory pool: Initial amount of memory available for the Apache Tomcat web server.
- Maximum memory pool: Maximum of memory available for the Apache Tomcat web server.
Tomcat Configuration
The following descriptions for these Tomcat configuration parameters are courtesy of http://tomcat.apache.org:
- maxThreads: The maximum number of request processing threads that can be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. Tomcat default value for this attribute is 200.
- maxKeepAliveRequests: The maximum number of HTTP requests which can be pipelined until the connection is closed by the server./ Setting this attribute to 1 will disable HTTP/1.0 keep-alive as well as HTTP/1.1 keep-alive and pipelining. Setting this to -1 will allow an unlimited amount of pipelined or keep-alive HTTP requests.Tomcat default value for this attribute is 100.
- connectionTimeout: The number of milliseconds this Connector will wait, after accepting a connection, for the request URI line to be presented. The default value is 60000 (i.e. 60 seconds). Use a value of -1 to indicate no (ie.e. infinite) timeout.
- keepAliveTimeout: The number of milliseconds this Connector will wait for another HTTP request before closing the connection. The default value is to use the value that has been set for the connectionTimeout attribute. Use a value of 01 to indicate no (i.e. infinite) timeout.
Database Options
You can define the parameters of the interbase database.
- InitialSize: Initial number of connections in the database connections pool
- maxActive: Maximum number of database connections in the database connections pool. For unlimited connections, use -1.
- DATABASE_CACHE_PAGES: Number of database pages to allocate in memory per database. Default value is 20 48.
Note: See more information here Back Up AppWave.
Logging Options
In this section you can define the parameters involved in taking AppWave logs.
- Log4j rolling: Specify what determines when a new aaserver.log file should be created.
- Daily: A new log file should be created each day.
- By file size: When the log file reaches the maximum size, a new log file should be created.
- Maximum file size: Maximum size of the log file. This option becomes available and must be specified when you select By file size. The size of the log file, which when reached triggers the system to archive the current and to create a new log file and start logging to the new file.
- Maximum number of rolled files: Determines the maximum number of backed up aaserver.log files to retain before deleting the oldest log file. Specifying -1 indicates that the backup files should never be deleted by AppWave.
- Log4j level: Specify the level of information to retain in the aaserver.log file
- DEBUG: Records fine-grained informational events that are most useful to debug an application.
- INFO: Records informational messages that highlight the progress of the application at coarse-grained level.
- ERROR: designates error events that might still allow the application to continue running.
- WARN: Records potentially harmful situations.
Note: to collect the logs see Collect Logs.
Optimizing AppWave Performance
For an AppWave configuration involving multiple geographical sites and more than 100 users the following configuration parameters are suggested to optimize performance.
- Java Options:
- Initial memory pool: 512
- Maximum memory pool: 1230
- Tomcat Configuration:
- maxThreads: 250
- connectionTimeout to 6000
- Database Options:
- maxActive: 40
- DATABASE_CACHE_PAGES: 8192
Note: A Proxy server at each geographical location is also recommended. In the SYSTEM MANAGEMENT menu, select System Properties > Streaming and then select Allow web caching.
Streaming Tab
The Streaming Server is responsible for streaming an application requested by the AppWave Browser user.
Access the Streaming tab from from the SYSTEM MANAGEMENT menu. Click System Properties, and then click the Streaming tab. The Streaming tab appears.
Make the required changes and then click Save.
The following describes the options available on the Streaming tab:
- General:
- Repository cache: This is the directory where the applications that will be streamed are saved on the AppWave host. The primary purpose for the cache is to allow partial downloading of an application before showing the application to the user. This is especially important when working with large applications because caching the application allows the user to begin using the application sooner, before the entire application has been cached.
- HeartBeat period: Number of minutes between keep alive pings to the streaming server. The heartbeat maintains streaming server connectivity and alerts AppWave when the streaming server does not respond.
- HeartBeat grace period: The number of minutes to wait for the streaming server to respond to a heartbeat. If the streaming server does not respond within this period the streaming server is considered to be offline and a notification is generated.
- Web Caching: Web Caching configures a transparent proxy set up between AppWave and AppWave Browser. If this proxy is configured, AppWave would add special headers to streaming data sent to AppWave Browser. This allows the streamed data to be cached on the proxy server so that the next time an AppWave Browser user asks for the relevant application, the streamed data will be sent directly to AppWave Browser from the proxy. This ability may be useful when the communication channel between AppWave and AppWave Browser is poor.
- Allow web caching: Turn on or off the special header in streamed data blocks.
- Cache period: The time period the data block could be stored on the proxy server before it expires and is deleted.
- Offline Use: When enabled, all users can download and stream applications.
- Allow to download streamed applications: When enabled, allows the AppWave Browser user to download Apps to their desktop.
- Allow to stream and launch streamed applications: If disabled, allows you to restrict specific groups from downloading and streaming applications. Select Off to grant only select groups the permission to download and stream applications.
Switch to standalone streaming service mode
Click to convert an AppWave to a streaming server, which will work in conjunction with another AppWave to share streaming of applications to users. When you click this option, the following dialog appears where you can specify the properties of the master AppWave. For more information see Standalone Streaming Server.