Siebel Enterprise Discovery In Oracle Enterprise Manager Fails When Invoking The Discovery REST API
(Doc ID 3037410.1)
Last updated on JULY 30, 2024
Applies to:
Enterprise Manager for Siebel - Version 13.5.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to discover the Siebel application through Oracle Enterprise Manager, the following message is shown:
Enterprise Manager Agent Installed on Gateway Host :<Gateway Hostname>.
EM Agent for Gateway Host : <Gateway Hostname> is up and running.
Siebel Enterprise <Enterprise Name>_<Gateway Hostname>:<TLS Port> can be discovered since no target with specified name exists in Enterprise Manager.
Unable to Discover any Siebel Target
EM Agent for Gateway Host : <Gateway Hostname> is up and running.
Siebel Enterprise <Enterprise Name>_<Gateway Hostname>:<TLS Port> can be discovered since no target with specified name exists in Enterprise Manager.
Unable to Discover any Siebel Target
Agent log on the gateway server siebelremotelogging.trc records the following error message:
4-06-25 14:03:39,495 [main] DEBUG discovery.DiscovererBase logMsgInt.319 - getDir() return value is/app/siebel/ses/gtwysrvr/bin/
2024-06-25 14:03:39,501 [main] DEBUG lang.Class logMsgInt.319 - CheckDir - TLSListnerPort :<Port>
2024-06-25 14:03:39,501 [main] DEBUG discovery.DiscovererBase logMsgInt.319 - installDir isoracle.sysman.siebel.management.emagent.
discovery.DiscoveryResult@4034c28c
2024-06-25 14:03:39,501 [main] DEBUG discovery.DiscovererBase logMsgInt.319 - getDir() return value is/app/siebel/ses/gtwysrvr/sys/
2024-06-25 14:03:39,502 [main] DEBUG emagent.EMGatewayAgent logMsgInt.319 - gateway.properties exists, it is IP2017 or higher versi
on, get Siebel hierarchy by REST
2024-06-25 14:03:39,649 [main] ERROR emagent.EMGatewayAgent logMsgInt.319 - Exception when invoking Siebel discovery REST API: http
s://<Host>:<Port>/siebel/v1.0/cloudgateway/enterprises?expand=all
java.security.UnrecoverableKeyException: Private key not stored as PKCS#8 EncryptedPrivateKeyInfo: java.io.IOException: ObjectIdent
ifier() -- data isn't an object ID (tag = 48)
2024-06-25 14:03:39,501 [main] DEBUG lang.Class logMsgInt.319 - CheckDir - TLSListnerPort :<Port>
2024-06-25 14:03:39,501 [main] DEBUG discovery.DiscovererBase logMsgInt.319 - installDir isoracle.sysman.siebel.management.emagent.
discovery.DiscoveryResult@4034c28c
2024-06-25 14:03:39,501 [main] DEBUG discovery.DiscovererBase logMsgInt.319 - getDir() return value is/app/siebel/ses/gtwysrvr/sys/
2024-06-25 14:03:39,502 [main] DEBUG emagent.EMGatewayAgent logMsgInt.319 - gateway.properties exists, it is IP2017 or higher versi
on, get Siebel hierarchy by REST
2024-06-25 14:03:39,649 [main] ERROR emagent.EMGatewayAgent logMsgInt.319 - Exception when invoking Siebel discovery REST API: http
s://<Host>:<Port>/siebel/v1.0/cloudgateway/enterprises?expand=all
java.security.UnrecoverableKeyException: Private key not stored as PKCS#8 EncryptedPrivateKeyInfo: java.io.IOException: ObjectIdent
ifier() -- data isn't an object ID (tag = 48)
Steps to reproduce the issue:
1. Install the latest Siebel release
2. Install OEM 13.5 with the latest release update
3. Install the OEM Agent on the Siebel Server and Gateway instances
4. Log in to OEM console and attempt to discover the Siebel application
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |