- Review Section 3.0, Installing
the CA-Top Secret Driver and Section 5.0,
Configuring the CA-Top Secret Driver.
- Is this a new installation, or are you replacing
a Fan-Out driver Platform Services installation? For details about
upgrading from the Fan-Out driver, see Section 4.0, Upgrading
from the Fan-Out Driver.
- Consider where and how you will install each component.
- You must install the driver libraries
(samples library, load library, and REXX exec library) on a volume
that is shared by each system that shares the security system database.
- You must run the driver shim started task on only
one system that shares the security system database.
- You must create the change log data set on a volume
that is shared by all systems that share the security system database.
- You must run the change log started task on each
system that shares the security system database.
- You must install the exit routines on each system
that shares the security system database.
- Consider how you will respond to the installation
prompts and other installation decisions.
- You must provide a connected system schema file
during installation. A file with the required classes and attributes
is provided in the driver samples library member SCHEMDEF.
For details about the connected system schema file, see Section 6.2, The Connected System Schema File.
- You must provide a driver shim configuration file
during installation. A file that you can customize is provided in
the driver samples library member DRVCONF.
For details about the driver shim configuration file, see Section 5.2, The Driver Shim Configuration File.
- You must provide an include/exclude file
during installation. A file with basic suggested content is provided
in the driver samples library member INCEXC.
You can use the include/exclude file on the connected
system to limit your initial deployment to a small number of users
and groups.
For details about the include/exclude file, see Section 6.3, The Connected System Include/Exclude
File.
- How will you prototype, test, and roll out your
deployment?
- What user ID will you use to run the change log
started task? What user ID will you use to run the driver shim started
task?
For details about the requirements for these user IDs, see Section 2.4, Started Task User IDs.
- What are the host names or IP addresses of your
Metadirectory server and the system that will run the driver shim
started task?
- Will you use the default TCP port numbers?
Table 2-1 Default TCP Port Numbers
|
Driver shim connection to the Metadirectory engine |
8090 |
|
Driver shim HTTP services for log viewing |
8091 |
|
Secure LDAP port |
636 |
|
Non-secure LDAP port |
389 |