Installation Guides › Upgrade Guide › Upgrading from r12 › How to Migrate from r12.0 › Upgrade r12.0 SOA Agents and SOA Security Gateways › Upgrade a SOA Agent to r12.1 on UNIX

Upgrade a SOA Agent to r12.1 on UNIX

The SOA Security Manager installer can upgrade existing SOA Agents to r12.1. The kit that contains the installer can be downloaded from the Technical Support site.

Note: if you have upgraded the web server associated with a SOA Agent for Web Servers since you last installed the SOA Agent, the Agent upgrade may not work. The upgrade is ensured only if the web server version has remained the same since the last SOA Agent installation. However, you can upgrade if you have applied a hotfix.

The installation executables are in the SOA Security Manager kit available on the Technical Support site. They are the following:

• Solaris—ca-soasm-12.1-cr001-sol.bin
• Red Hat Linux—ca-soasm-12.1-cr001-linux.bin

To locate installation kits on the Support site

1. Click Technical Support.
2. Log into CA Support Online.
3. Click Download Center.
4. Search the Download Center for the installation kit you need.

Note: Extract all files and directories in the SOA Security Manager kit to a common location on a local drive and keep them together—the SOA Security Manager installer cannot run without the included supporting files.

If you do not have sufficient rights, add executable permission to the install file by running the following command:

chmod+x ca-soasm-12.1-cr001-os_version.bin

• os_version

  Specifies sol or linux.

Important! If you execute the SOA Security Manager installer across different subnets it can crash. To avoid this problem, install the Policy Server directly on the host system.

Important! Remove any 5.x Web Agent Option Packs before upgrading to r12.1. 6.x Web Agent Option Packs do not need to be removed before upgrading to r12.1. For more information about removing and reinstalling Web Agent Option Packs, see the SOA Security Manager Web Agent Option Pack Guide.

Consider the following:

• If you have upgraded the web server associated with a SOA Agent for Web Servers since you last installed the SOA Agent, the Agent upgrade may not work. The upgrade is ensured only if the web server version has remained the same since the last SOA Agent installation. However, you can upgrade if you have applied a hotfix.
• If the installation program detects any locked Agent files, it prompts you to restart your system instead of reconfiguring it. Select whether to restart the system immediately or later.
• If you are upgrading an Agent on an Sun Java System web server, you may see an error message stating that the httpd.exe service is unable to locate the smconapi.dll. If this message appears, reboot your system before launching the Web Agent Configuration Wizard.

To upgrade a SOA Agent on UNIX systems

1. Exit all applications that are running and stop the web server.
2. Open a command window and navigate to where the install program is located.
3. Enter one of the following commands:

   GUI mode: sh./ca-soasm-12.1-cr001-os_version.bin

   Console mode: sh./ca-soasm-12.1-cr001-os_version.bin -i

   The SOA Security Manager installation wizard starts.

4. Proceed through the wizard to upgrade the SOA Agent. Consider the following when running the installer:
   • When prompted to select features to install, select CA SOA Security Manager Agents and then specify the SOA Agent types you want to upgrade.
   • When the wizard prompts you to confirm the upgrade, select one of the following option:
     • Continue with the upgrade—upgrades the SOA Agent to r12.1.
     • Abort the upgrade—exits the upgrade procedure without upgrading the SOA Agent.
   • If the installation program detect that newer versions of certain system .dlls are installed on your system and prompts you to overwrite these newer files with older files, select the No To All option.

   The new SOA Agent files are copied to the specified location.

5. Choose whether to restart your system immediately or later.
6. Re-configure the upgraded SOA agent with the SOA Security Manager Configuration Wizard.

   Note: You do not need to re-register your trusted host.