Using the steps provided, along with the Customizing SSL in CA WCC r11.3 Guide, WCC can be switched from non-SSL mode to SSL mode.
The installation of CA WCC on which this procedure is being performed must have had the Enable SSL option selected during installation.
Because your current install of WCC in non-SSL mode, you will need to re-install WCC and enable SSL mode. Any patches/maintenance you have in place may be wiped out. We recommend backing up WCC prior to completing the re-install.
Step 1: Back up your WCC prior to doing the reinstallation.
Step 2: Once you have backed up WCC, complete your re-installation, making sure you enable SSL mode.
Step 3: Generate a certificate for Secure Access to CA WCC
The procedures to obtain this certificate can be found in the Customizing SSL in CA WCC r11.3 Documentation.
This can be done in three different ways:
If you decide to use a certificate authority (C.A.), it may take hours or days to obtain the certificate. For a production environment, this is the recommended method to acquire the certificate.
If you want to generate a self‐signed certificate, no additional software needs to be installed. For the other two methods of changing the certificate (Generate a secret key and request a certificate, and Import an existing private key and certificate), OpenSSL must be installed on the CA WCC server before you perform either of those procedures. (See page 2)
The certificate you receive from your C.A. should be in PEM format. If it is in DER format, it needs to be converted to PEM. This can be done using OpenSSL.
What happens to the EEM Policies in place?
EEM policies are not affected by the WCC re-installation but you do have the option to overwrite them during the installation.
What happens to the AutoSys Server(s) in place?
The pre-existing AE server(s) will remain in place.