Installing CA Access Control Enterprise Management installs all the Enterprise Management Server components. You must prepare the Enterprise Management Server before you install CA Access Control Enterprise Management.
You must use console installation to install CA Access Control Enterprise Management on a Linux computer.
Follow these steps:
Note: In some releases of Linux, the operating system automounts the optical disc drive with the noexec option.
Note: The installer unpacks the installation files to the working directory. If you specify a working directory on the optical media, the installation fails because the installer cannot unpack the files.
/media/EnterpriseMgmt/Disk1/InstData/NoVM/install_EntM_r125.bin -i console
To use a custom FIPS key during installation, you must also specify the full pathname of the FIPS key in the command, using the format -DFIPS_KEY=path. For example, to install with a custom FIPS key located at /tmp/FIPSkey.dat:
/media/EnterpriseMgmt/Disk1/InstData/NoVM/install_EntM_r125.bin -i console -DFIPS_KEY=/tmp/FIPSkey.dat
Important! If you install CA Access Control Enterprise Management for High Availability, specify the same FIPS key on the primary and secondary Enterprise Management Servers. Specify a custom FIPS key if you install CA Access Control Enterprise Management for High Availability with FIPS support.
The InstallAnywhere console appears after a few moments.
Defines the location of an existing JDK.
Defines the JBoss instance that you want to install the application on.
You need to:
For example, /opt/jboss-4.2.3.GA
Note: The CA Access Control Enterprise Management installation program does not use the default JBoss ports but instead adds 10000 to the default JBoss port numbers. For example, the installation program uses port number 18080 rather than port number 8080 for HTTP connections. Ensure that you specify the ports that JBoss uses.
(Primary Enterprise Management Server Only) Defines the password used for CA Access Control Enterprise Management Server inter-component communication.
Note: CA Access Control Enterprise Management uses the communication password to manage the Message Queue keystore and administrator account, handle communication between CA Access Control Enterprise Management and the endpoints and manage the Java Connection Server.
Defines the connection details to the RDBMS:
Note: You granted this user the appropriate database permissions when you prepared the database.
The installation program checks the connection to the database before it continues.
Defines the user store type CA Access Control Enterprise Management uses. Select one of the following:
Note: To deploy login authorization policies to UNAB, you must select either Active Directory or Other User Store as the user store. If you select Active Directory or Other User Store as the user store, you cannot create or delete users and groups in CA Access Control Enterprise Management. For more information about UNAB and Active Directory restrictions, see the Enterprise Administration Guide.
Defines the Active Directory user store settings:
Note: Set the Search Root at least one node higher in the directory tree than the Distinguished Names (DNs) for the users specified for User DN and System User. Otherwise, Enterprise Management might launch without displaying any tabs.
Note: This user issues LDAP queries against Active Directory. You can choose to define a user with read-only privileges for this parameter. However, if you define a user with read-only privileges, you cannot assign admin roles or privileged access roles to users in CA Access Control Enterprise Management. Instead, you modify the member policy for each role to point to an Active Directory group.
The installation program checks the connection to Active Directory before continuing.
Note: You can use the DSQUERY directory querying utility to discover the user Distinguished Name (User DN). You must run this query on the Active Directory server. For example:
dsquery user -name administrator "CN=Administrator,CN=Users,DC=lab.DC=demo"
(Active Directory only) Defines the DN of the Active Directory user who is assigned the System Manager admin role in CA Access Control Enterprise Management.
Example: CN=SystemUser, ou=OrganizationalUnit, DC=DomainName, DC=Com
Note: By default, a user with the System Manager admin role can perform, create, and manage all tasks in CA Access Control Enterprise Management. For more information about the System Manager admin role, see the Enterprise Administration Guide.
(Embedded user store only) Defines the password of superadmin, the CA Access Control Enterprise Management administrator. Make a note of the password so you can log in to CA Access Control Enterprise Management when the installation is complete.
Note: In this step you create the superadmin user in the embedded user store. The superadmin user is assigned the System Manager admin role in CA Access Control Enterprise Management. You log in as superadmin the first time you log in to CA Access Control Enterprise Management. For more information about the System Manager admin role, see the Enterprise Administration Guide.
CA Access Control Enterprise Management is installed.
The installer closes.
You now need to configure CA Access Control Enterprise Management for your enterprise.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |