ERROR :: SponsorManager::submit :sponsor[ iRegistry] not found and invocation returned 404 error

Products

• SECURITY MISC CODES
• SINGLE SIGN ON - LEGACY
• CA Data Protection (DataMinder)
• CA User Activity Reporting

Issue/Introduction

Description:

This document explains how to prevent these errors from appearing in the igateway.log:

ERROR :: SponsorManager::submit :sponsor[ iRegistry] not found and invocation returned 404 error

Solution:

Even if these errors can be ignored, you can prevent them from appearing in the igateway.log
with the following steps:

1. Stop igateway ( S99igateway stop )
2. Edit the igateway.conf located in the folder /opt/CA/SharedComponents/iTechnology
3. Comment the <RegistryHostList> tag completely in igateway.conf as shown below
   ( add <!--  in front of these lines  and add --> after these lines )
   
   

   <!--                 <RegistryHostList name="RegistryHost-1">                             <host>localhost</host>                   </RegistryHostList>  -->

4. Start igateway ( S99igateway start ).
   After this the iRegistry error will not be logged in igateway.log.
    

 iRegistry is an optional iSponsor that is part of the iGateway install package.
 iRegistry provides iSponsor discovery and enumeration services.
 This iSponsor is not used with UARM.

If the problem persists or if you require any assistance, please contact CA Support.

Environment

Release:
Component: CAELM