Cloning a Subsystem
53
3. Open the new instance URL, and go through the configuration wizard as described in
Section 2.6,
“Configuring the Default Subsystem Instances”
. Supply the security domain, CA, instance ID,
internal LDAP database, and agent information.
4. When the configuration is complete, restart the subsystem.
/etc/init.d/
instance_ID
restart
2.7.1. Cloning a Subsystem
For failover protection and for availability for high-traffic subsystems, it is possible to clone an existing
CA, DRM, TKS, or OCSP subsystem. To clone a subsystem, do the following:
1. Create a new instance using
pkicreate
.
2. Open the configuration wizard.
3. In the
Security Domain
panel, add the clone to the same security domain to which the master
belongs.
4. The
Subsystem Type
panel sets whether to create a new instance or a clone; select the clone
radio button.
Figure 2.16. Selecting the Subsystem to Clone
5. Give the path and filename of the PKCS #12 backup file which was saved when the master
instance was created. If a backup was not created at that time, use the
pk12util
utility to create
a PKCS #12 file.
Summary of Contents for CERTIFICATE SYSTEM 7.2 - MIGRATION GUIDE
Page 36: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Page 144: ...124 ...
Page 160: ...140 ...
Page 208: ...188 ...
Page 210: ...190 ...
Page 256: ...236 ...
Page 282: ...Chapter 12 Certificate Profiles 262 Parameter IssuerName_n IssuerType_n ...
Page 285: ...Freshest CRL Extension Default 265 Parameter PointName_n PointIssuerName_n ...
Page 362: ...342 ...
Page 376: ...356 ...
Page 436: ...416 ...
Page 490: ...470 ...
Page 504: ...484 ...