Results for “fnd_server”

2 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_NET_SERVICES is a server-side PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that governs the registration, maintenance, and inspection of the network topology underpinning an EBS environment. Its responsibilities span the definition of application-tier nodes, database-tier nodes, Oracle homes, TNS aliases, and the mappings that associate servers with systems and databases. In effect, the package is the programmatic interface through which EBS records the identity and connectivity details of the machines that participate in a multi-tier deployment.

The ETRM classification for this package is OTHER, indicating that it is not a published end-user API but an internal utility used by administrative and configuration tooling. The package body is dated with a header indicating a last modification in 2006, consistent with the long-lived nature of the AutoConfig and rapid-install infrastructure carried forward into EBS 12.1.1 and 12.2.2. Notably, the body employs dynamic SQL to query FND_NODES, a decision explicitly explained in the source comments as being necessitated by backward-compatibility concerns — the node_id column may not always be present or may have evolved across releases, so static references would risk compilation and runtime failures.

Key Procedures and Functions

  • REGISTER_DBNODE — Registers a database-tier node in the EBS network metadata, establishing the association between a database server and the system it belongs to.
  • REGISTER_APPNODE — Registers an application-tier node, recording an application server host within the EBS topology.
  • REMOVE_DBNODE — Removes a previously registered database node, reversing the effect of REGISTER_DBNODE.
  • REMOVE_APPNODE — Removes a previously registered application node.
  • REMOVE_SERVER — Deletes a server definition from the network configuration, typically invoked during decommissioning.
  • REMOVE_SYSTEM — Removes an entire system record, including its associated server mappings.
  • SHOW — Produces a formatted display of network configuration information, leveraging the formatting helper functions visible in the package body (fmtline, fmtuline).
  • SHOW_TNSALIAS — Displays TNS alias definitions and their associated address lists.

The body additionally contains internal helpers such as platformNameToNo, which maps a platform name (for example Solaris, HP-UX, Linux, or Windows NT) to a numeric platform code, and buildNodeName, which composes a node name from host name, domain, and platform inputs. These are supporting routines rather than documented entry points.

Tables Accessed

The package operates across a broad set of FND configuration tables, referenced through APPS synonyms. Node and server identity is held in FND_NODES, FND_APP_SERVERS, and FND_SYSTEM_SERVER_MAP. Database-side configuration relies on FND_DATABASES, FND_DATABASE_INSTANCES, FND_DATABASE_SERVICES, FND_DB_SERVICE_MEMBERS, FND_DATABASE_ASSIGNMENTS, and FND_SIDS. Connectivity information is stored in FND_TNS_ALIASES, FND_TNS_ALIAS_ADDRESSES, and FND_TNS_ALIAS_ADDRESS_LISTS. System-level and file-system metadata is drawn from FND_APPS_SYSTEM, FND_ORACLE_HOMES, and FND_APPL_TOPS. Collectively these tables describe where EBS components run and how they connect.

Usage Notes

Because the ETRM metadata records zero packages referencing this one, FND_NET_SERVICES is not a dependency of other PL/SQL units in the documented set; it is invoked directly by administrative interfaces and scripts. Typical callers include the EBS Autoconfig and rapid-install utilities, the OAM (Oracle Applications Manager) site-map and topology pages, and adadmin-style maintenance routines. A user searching for "fnd_server" is most likely probing the server-registration surface of this package, which corresponds to the REGISTER_APPNODE, REGISTER_DBNODE, REMOVE_SERVER, and SHOW routines. Custom code should treat these as internal interfaces: signatures and behavior are not guaranteed across patch levels, and the use of dynamic SQL against FND_NODES means output shape can vary with environment. Direct DML against the underlying FND tables is strongly discouraged in favor of these documented procedures.