API Gateway: OAM Removal from Gateway

book

Article ID: 194103

calendar_today

Updated On:

Products

CA API Gateway API SECURITY STARTER PACK-7

Issue/Introduction

We are decommissioning OAM from gateway since we have migrated to Pingfed. For this, we need to clean up the OAM related packages.

[[email protected] ~]# uname -a
Linux host.com 2.6.32-642.11.1.el6.centos.plus.x86_64 #1 SMP Sat Nov 19 13:48:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] ~]#

[[email protected] ~]# rpm -qa | grep -i ssg
ssg-9.2.00-6904.noarch
ssg-oracle-access-manager-9.2.00-109.x86_64
ssg-nshieldpci-8.0-12.10.el6.x86_64
ssg-platform-1.6.00-97.noarch
ssg-appliance-9.2.00-6904.x86_64
[[email protected] ~]#

[[email protected] ~]# rpm -qa | grep -i compat*
xz-lzma-compat-4.999.9-0.5.beta.20091007git.el6.x86_64
compat-db43-4.3.29-15.el6.x86_64
compat-libstdc++-33-3.2.3-61.x86_64
MySQL-shared-compat-advanced-5.5.53-1.el6.x86_64
compat-readline5-5.2-17.1.el6.x86_64
[[email protected] ~]#

[[email protected] ~]# service ors status
ORS server running (pid 17488)
[[email protected] ~]#

Environment

API Gateway: 9.2

Resolution

If you're not using OAM anymore, from a functionality perspective, you don't need to delete it. The war file should not prevent you from installing another utility.