Search Results register_service

Overview

FND_APP_SYSTEM is the registration layer of the Oracle E-Business Suite Applications technology stack. It belongs to the Oracle Applications Object Library (AOL) family of packages and exists to populate and maintain the topology metadata that defines an EBS installation: application systems, nodes, Oracle homes, application tier servers, database identities, and the Oracle Net connectivity artifacts that bind them together.

The package is catalogued in ETRM under classification OTHER, and its header carries the revision identifier AFCPSYSS.pls 120.2, unchanged since December 2005. Its 20 documented procedures mirror the administrative workflow followed when an environment is configured, cloned, or extended. Each procedure performs a narrow, atomic registration action against a single configuration entity in the FND schema.

Key Procedures and Functions

• REGISTER_SYSTEM — Establishes the application system record itself, capturing the system name, owner, CSI number, and an optional system GUID. This is the anchor row to which the remaining registrations logically attach.
• REGISTER_NODE — Registers a physical or virtual node. It accepts the node name, platform identifier, and tier flags for the forms, concurrent processing, web, administration, and database tiers, together with server identifier, network address, host name, domain, description, and an optional virtual IP.
• REGISTER_ORACLEHOME — Records an Oracle home, including its node, path, version, description, file system GUID, and an optional Oracle home identifier.
• REGISTER_APPLTOP — Registers an application top directory and its association with a node and product group.
• REGISTER_SERVER and REGISTER_SERVERMAP — Define application tier service processes and the mapping between those servers and the nodes hosting them.
• REGISTER_DATABASE and REGISTER_DATABASE_ASG — Create the database identity record and assign that database to an application system.
• REGISTER_INSTANCE and REGISTER_SID — Capture database instance and system identifier details used to resolve instance-level connectivity.
• REGISTER_SERVICE and REGISTER_SERVICE_MEMBERS — Describe database services and the instances that constitute each service.
• REGISTER_LISTENER and REGISTER_LISTENER_PORTS — Declare listener endpoints and their port assignments.
• REGISTER_TNSALIAS, REGISTER_TNS_DESCRIPTION, REGISTER_TNS_ADDRESS_LIST, REGISTER_TNSALIAS_ADDRESS, REGISTER_TNSALIAS_SETS, and REGISTER_ALIASSET_USAGE — Together these assemble the Oracle Net namespace: alias definitions, connect descriptions, address lists, the address entries beneath each alias, and the alias sets (such as PUBLIC and INTERNAL) that group aliases by purpose.

The specification exposes named constants that classify these registrations, including C_DB_SERVER_TYPE, C_APP_SERVER_TYPE, the FNDFS and FNDSM alias type identifiers, load-balancing and instance alias types, and the PREFERRED_INSTANCE and AVAILABLE_INSTANCE status values.

Tables Accessed

All access is performed through APPS synonyms over the FND configuration tables. FND_APPS_SYSTEM and FND_APPL_TOPS hold system and application tier directory definitions; FND_NODES, FND_ORACLE_HOMES, and FND_APP_SERVERS hold the node and process topology; FND_SYSTEM_SERVER_MAP links servers to systems. Database topology is held in FND_DATABASES, FND_DATABASE_ASSIGNMENTS, FND_DATABASE_INSTANCES, FND_DATABASE_SERVICES, FND_DB_SERVICE_MEMBERS, and FND_SIDS. Oracle Net metadata resides in FND_TNS_ALIASES, FND_TNS_ALIAS_ADDRESSES, and FND_TNS_ALIAS_ADDRESS_LISTS.

Usage Notes

The package is not exposed through a standard EBS form. It is invoked during installation, rapid clone, and AutoConfig-driven setup, where the configuration utilities call the register procedures to seed topology rows. ETRM records the package as referenced by one other package, indicating internal use by the technology stack rather than by application modules. Custom code should treat these procedures as privileged maintenance operations: they write directly to configuration metadata and are intended for use where the runtime has already determined the correct values, not for ad hoc execution against a running production environment.