Why is a Foreign JNDI Provider Needed For the Multispeak Adapters Managed Server
(Doc ID 2074815.1)
Last updated on JULY 26, 2019
Applies to:
Oracle Network Management for Utilities - DMS - Version 1.11.0.4 to 2.3.0.2.0 [Release 1.11 to 2.3]Oracle Utilities Network Management System - Version 1.11.0.4 to 2.3.0.2.0 [Release 1.11 to 2.3]
Information in this document applies to any platform.
Goal
NOTE: This is no longer needed since version 2.4. It was replaced by the 'config.nms_url' configuration parameter.
When creating a managed server for the Multispeak adapters, the Adapters Guide states:
Adapter Installation Instructions for Oracle WebLogic Server
Topics
• Create a Managed Server (Optional)
• Create a Foreign JNDI Provider
Note: Creating a foreign JNDI provider is required when the
nms-multispeak.ear is on a different managed server than the cesejb.ear; if they
are deployed on the same server, skip this step.
What is not completely clear is why a Foreign JNDI provider is required, this article should provide more information on this topic.
Solution
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
Goal |
Solution |
References |