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
If you choose to configure an additional Application Manager instance instead of cloning it, you must configure
the additional instance and fetch the master keystore from a previously configured Application Manager
instance.
Prerequisites
Have a plan for your Application Manager deployment that includes how you will handle load balancing and
high availability. Before you connect the Application Manager instances to an external database server, perform
the following:
n
Install and configure PostgresSQL 9.1 as the external database server, with the citext module installed.
The citext module supports the CITEXT data type, a case insensitive text type.
n
Install and configure the load balancing implementation.
n
Install and configure all the instances of Application Manager that you plan to use.
n
Consider the Connector in your deployment. You can use multiple Connector instances as well as multiple
Application Manager instances and should consider how you will use load balancing throughout the
Application Manager deployment.
Procedure
1 Access the Application Manager virtual appliance interface.
2 Select Configure and press Enter.
3 At the prompt, type the number to Database Key Management and press Enter.
4 At the prompt, type the number to Configure Database Connection option and press Enter.
5 Respond to the prompts about the database connection and press Enter after each response.
a Enter y to indicate that you want to connect to the external database server.
b Enter the IP address or the FQDN of the database server.
c Enter the name of the user with read and write privileges to the database.
d Enter the password of the user you just entered, the user with read and write privileges to the database.
6 Enter q when prompted to return to the Database Connection Configuration page.
If this Application Manager instance is the first in the cluster, the master key is generated automatically.
You do not need to fetch a master key store. You can exit the Database Connection Configuration page.
However, if this Application Manager instance is being added to a cluster where one or more Application
Manager instances already exist, continue to the next step.
7 If you plan to fetch a master keystore from a previously created Application Manager instance in the
cluster, on the system from which you will fetch the master keystore, enable root access to the ssh tool.
a On the Application Manager instance from which you will fetch the master keystore, log in to the
operating system and open the file /etc/ssh/sshd-config for editing.
b Locate the following line PermitRootLogin no and change it to PermitRootLogin yes,
c Restart the ssh tool with the following command /etc/rc.d/sshd restart.
8 Return to the Application Manager instance to which you want to copy the fetched master keystore and
complete the fetching procedure.
a Access the Change Application Manager Configuration screen, and if necessary, access the next page
of options, at the prompt, type the number to Database Key Management, and press Enter.
b At the prompt, type the number to Fetch Master Keystore and press Enter.
Installing Application Manager
42 VMware, Inc.