Previous Topic: Configure Policy Server ClustersNext Topic: Troubleshooting


Upgrading CA SSO Agent for Siebel

Use the CA SSO Platform Support Matrix available on the CA Support website to verify that both the previous and new versions of the product use the same operating environment. Upgrades are only supported if the operating environments for both versions are the same.

Upgrade the other CA SSO components (such as the Policy Server and Web Agent) in your environment first.

Note: For more information about upgrading the CA SSO components, see the CA SSO documentation.

Gather the information for the installer and run the installation wizard to install and configure the product.

This section contains the following topics:

Upgrade CA SSO Agent for Siebel on Windows

Upgrade CA SSO Agent for Siebel on UNIX

Upgrade and Enable the New Encryption Ticket

Upgrade CA SSO Agent for Siebel on Windows

Important! Before you start the upgrade process, verify that the services of the web servers are stopped.

Follow these steps:

  1. Double-click the following installation executable file:
    ca-erp-siebel-<version>-<operating_environmentprocessor_type>.exe
    

    For console-based installation, open a command line window and run the following command

    <executable_file_name>.exe -i console
    
  2. Click Next.
  3. Accept the License Agreement and click Next.
  4. Select the components that are already installed on the host where you are installing the product.

    Note: Depending on your configuration, whether the above-mentioned servers are located on the same or on different machines, you must run Installer once, twice or three times.

  5. Click Next.
  6. Click Continue with the UPGRADE and click Next.

    You are prompted to overwrite the existing file.

  7. Click Yes and click Next.
  8. Review your selections, and click Install.

    After the installation is complete, you are prompted to configure the agent.

  9. Select Yes, I want to configure now and click Next.
  10. Complete the configuration wizard using the information gathered previously for the installer.

Upgrade CA SSO Agent for Siebel on UNIX

Important! Before you start the upgrade process, verify that the services of the web servers are stopped.

Follow these steps:

  1. Run the executable installer file from the command line using the following command:
    <executable file name> -i console
    
  2. After selecting the relevant servers that are installed on the machine that you are installing the agent, the installer prompts you to confirm the upgrade.
  3. Enter Y.

    You are prompted to overwrite the existing file.

  4. Enter Y and follow the instructions to complete the installation.

    If you are running the installer on the host that has the Siebel server installed, then run the configuration script to configure the agent.

  5. Navigate to the following location:
    <Siebel_agent_install_folder>/siebel
    
  6. Run the following script:
    ca-siebel-config.sh
    
  7. Follow the instructions and complete the configuration.

Upgrade and Enable the New Encryption Ticket

Before upgrading to the latest release in a production environment, perform the installation in a test environment to make sure the upgrade does not have any adverse consequences.

Follow these steps:

  1. Run smobjexport command to generate a backup of the existing Policy Store.

    Note: For more information, see the CA SSO documentation.

  2. Stop one Policy Server.
  3. Replace the existing file, SiebelSSOAuth.dll, libSiebelSSOAuth.so, or libSiebelSSOAuth.sl with the file in the following location:
    <Siebel agent installation folder>\Siebel\bin
    
  4. Start the Policy Server.
  5. Wait several minutes to allow all agents to begin again using this Policy Server.
  6. Repeat Step 2 through Step 5 for each Policy Server in the environment.
  7. Open the CA SSO Administrative UI and find the response for the Siebel Ticket. Change the Function Name from GetSSOTicket to GetSSOTicketWithDN (you do not have to flush the cache manually, it happens automatically).
  8. Wait several minutes for every Policy server to detect the changed response and for the cache on every Web Agent to be flushed.

    Note: Manually flushing the cache does not accelerate this process.

  9. Test the environment to ensure that Siebel is working correctly.