Unable To Bring Up Weblogic Managed Server On Secondary Node
(Doc ID 2591977.1)
Last updated on FEBRUARY 17, 2023
Applies to:
Oracle E-Business Suite Integrated SOA Gateway - Version 12.2 to 12.2 [Release 12.2]Information in this document applies to any platform.
Symptoms
On 12.2.6 version, Installation Issues
Weblogic Managed server's unable to bring up on secondary node configuring ISG (Doc ID 1311068.1) on production.
This did not occur in test.
The Admin server is not starting. Forms server, OACORE server, OAFM cerver.
Nothing is starting on node 2. Following the note, ran the txkSoaConfigUtility.xml config file where this resulted. Some files are missing.
Errors in the log files:
ERROR
-----------------------
Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IsgAuthenticator is not specified.
The issue can be reproduced at will with the following steps:
1. Followed oracle standard DOC ID :- Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1)
Section 2: Configuring Oracle E-Business Suite Integrated SOA Gateway for REST Services
2. After configurated ISG setup using REST on PRODUCTION ENV. All services is up and running from Primary node but Secondary node Managed server is not starting.
The issue has the following business impact:
Due to this issue, users cannot make use of SOA Gateway.
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 |