The process completes key migration on the Secondary SAKA server for the new domain setup initiated in the previous step.

1. Login as strongauth on the secondary SAKA server.

2. Start up two shell windows.

3. In Window2, change the /usr/local/strongauth/glassfish/domains/domain1/logs directory.

   shell> cd /usr/local/strongauth/glassfish/domains/domain1/logs

   or use the shell-alias aslg:

   shell> aslg

4. In Window2, run the tail -f command on the server.log file so you can watch the output of the server application as it scrolls by.

   shell> tail -f server.log

   or use the shell-alias tsl:

   shell> tsl

5. In Window1, change directory to /usr/local/strongauth/bin.

   shell> cd ~/bin

6. In Window1, execute the Secondary-SAKA-Replication-Final.sh.

   shell> ./Secondary-SAKA-Replication-Final.sh

7. Follow the steps of the wizard, ensuring there are no errors in Window1 or Window2. If there are errors, contact StrongKey at This email address is being protected from spambots. You need JavaScript enabled to view it. and discontinue the new domain process.

8. In Window1, execute New-SKCE-Domain.sh to setup service credentials for the CEM. Specify the DID of this new domain and a password you would like to use to secure the CEM service credentials. These values must be the same as those supplied on the Primary SAKA server:

   shell> ./New-SKCE-Domain.sh <DID> <password>

9. Repeat steps 1–8 for all other Secondary SAKA servers in the cluster.

The new domain is now ready for configuration via DACTool. The DA must now choose to which domain to connect on the Systems panel. All administration functions described in this chapter continue to perform normally on the new domain.