1.5
Table Of Contents
- Installing Application Manager
- Contents
- Installing and Configuring Application Manager
- Introduction to Application Manager
- Security Considerations and System Requirements for Application Manager
- Preparing to Install Application Manager
- Installing Application Manager
- Configuring Application Manager with the Operator Setup Wizard
- Making Additional Application Manager Configurations
- Troubleshooting Application Manager
- Index
Prerequisites
Verify that a syslog server is installed, configured, and accessible from Application Manager.
Procedure
1 Access the Application Manager virtual appliance interface.
2 Select Login and log in to the SLES operating system.
3 Use the appropriate commands to access and configure the log4j.properties file to send logs to syslog
internally.
4 Use the appropriate commands to access and configure the syslog-ng.conf file to send logs to an external
syslog server.
5 Restart the Apache Tomcat server for the changes to the log4j.properties file to take effect.
a In the Application Manager virtual appliance interface, select Configure.
b Type the number to Manage Web Server.
c Type the number to Restart Tomcat.
After you configure the log configuration files, the new logging behavior takes effect.
Configuring SSL Connectivity to Application Manager
SSL connectivity to Application Manager and the Connector is disabled by default to simplify the configuration
of your Application Manager deployment during the proof-of-concept phase. Whether you configure a self-
signed certificate or a third-party CA certificate, you can implement the necessary tasks in phases.
Verify that the state of SSL, enabled or disabled, always matches between the Connector and Application
Manager. You can wait to enable SSL until you move Application Manager into production.
NOTE You do not need an SSL certificate if the Configure Web Server option of Application Manager and the
Connector are set to insecure mode. In secure mode, you can use either a self-signed or a third-party SSL
certificate. Typically, self-signed SSL certificates are used during pre-production testing, but you can use a
third-party SSL certificate during testing if you want. During production, the best practice is to use a third-
party CA SSL certificate.
For detailed information of the SSL-related tasks to perform during the recommended deployment phases, see
“Trial, Test, and Production Deployment Phases,” on page 7. The following bulleted items provide an overview
of tasks you should perform, if applicable, after you enable SSL for your Application Manager deployment:
n
Update each SAML application that you previously configured without SSL to now use SSL. In other
words, ensure that each SAML application now reaches Application Manager using HTTPS instead of
HTTP. This might involve working with account administrators for specific SAML applications. See
Application Manager Administration Help for information about configuring SAML applications.
n
If you are providing users with access to Windows Applications captured as ThinApp packages, reinstall
Horizon Agent on each user's system to update the Application Manager URL from HTTP to HTTPS. See
Deploy Horizon Agent.
Procedure
1 Enable Secure Ports for the Application Manager on page 37
To enable SSL for your Application Manager deployment, first enable secure ports for Application
Manager.
Installing Application Manager
36 VMware, Inc.