When Changing the Connect String in eapps.cfg File, the changes Still do not Take Effect.
(Doc ID 2522336.1)
Last updated on FEBRUARY 04, 2020
Applies to:Siebel CRM - Version 15.12 [IP2015] and later
Information in this document applies to any platform.
On : 15.12 [IP2015] version, System Admin
Cant direct Production eCustomer portal requests to the second portal Object manager server through the webserver .
Recently a second Object manager server was introduced into the Customer portal production environment. The server is successfully added to the enterprise and is visible in the enterprise and ready to take requests.
After updating the eapps.cfg config file on the webserver to point to the (new) second object manger server, the requests are still being routed to the first object manager server.
Requests should route to the new second server
The issue can be reproduced at will with the following steps:
1. Add server to the enterprise
2. Configure the connect string in the eapps.cfg to point to the new server in the enterprise.
3. Requests still route to the original server and not the newly added server.
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