Results for “wbsvr_id”

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

Overview

The IEB_WB_SERVERS table resides in the IEB schema and belongs to the Oracle Interaction Blending (IEB) product family. It stores summary information about IEB servers — the Workbench (WB) server instances that host the interaction blending runtime engine used for agent, skill, and routing configuration distribution to telephony and CTI layers. Each row represents a single configured WB server, capturing identity, communication endpoints, scheduled maintenance behavior, and operational tuning parameters. In Oracle EBS 12.1.1 and 12.2.2, this table is a configuration master: it is populated during implementation and referenced by subordinate IEB tables that bind agents, service categories, and multimedia servers to a specific WB server instance.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as hub-leaning. This is a heuristic suggestion rather than a physical statement: the table behaves as a durable business entity keyed on a stable server identity, with the surrounding descriptive and scheduling columns operating as type-1 attributes of that entity.

Key Information Stored

The 41 documented columns fall into identity, operational, and connectivity groups. The most significant include:

• WBSVR_ID — surrogate primary key of the table, enforced by the unique index IEB_WB_SERVERS_PK_U and the constraint IEB_WB_SERVERS_PK. This is the column referenced by all dependent child tables.
• WB_SERVER_NAME — the business-key candidate, enforced by the unique constraint IEB_WB_SERVERS_NM_UK. It provides the human-readable server identity used by administrators.
• WB_SERVER_TYPE and DESCRIPTION — classify and describe the server instance.
• COMMUNICATION_METHOD, COM_OBJECT_NAME, COM_DNS_NAME, COM_IP_ADDRESS, COM_PORT_NUMBER — define how the EBS application tier reaches the WB server, including the transport method and network endpoint.
• COM_PARAM1 through COM_PARAM4 — parameterized connectivity options consumed by the communication layer.
• LOG_FILE_NAME, LOG_DBC_FILE_NAME, CCI_DBC_FILE_NAME, TRACE_FILE_NAME — file locations for logging, statistics, and trace output.
• STAT_DUMP_SUNDAY_Y_N through STAT_DUMP_SATURDAY_Y_N, STAT_DUMP_BEG_TIME_HHMM, STAT_DUMP_END_TIME_HHMM — per-day scheduling flags and the daily start/end window for statistics collection.
• DAILY_CLEANUP_Y_N, CLEANUP_TIME_HHMM, AUTO_SHUT_DOWN_Y_N, AUTO_SHUT_DOWN_TIME_HHMM — maintenance automation settings for queue cleanup and server shutdown.
• VIRTUAL_Q_CLEANUP_SIZE, WORK_QUEUE_CACHE_SIZE — tuning thresholds for the virtual queue and work-queue cache.
• SECURITY_GROUP_ID — multi-tenant security grouping, joined to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF framework.
• IEO_SERVER_ID and CHECK_NEW_SC_ENTRY — cross-reference to the IEO server and validation control for new service-category entries.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide the audit trail.

Common Use Cases and Queries

Administrators and developers query this table to validate server configuration, audit scheduled jobs, and drive status reports. Typical patterns include:

• Retrieving all active WB servers and their endpoints for connectivity troubleshooting.
• Reporting which servers have daily cleanup or auto shutdown enabled and at what time.
• Joining to child tables to count how many agents or service categories are bound to each server.

A representative query:

SELECT s.wbsvr_id, s.wb_server_name, s.wb_server_type, s.com_ip_address, s.com_port_number, COUNT(a.wbsvr_wbsvr_id) agents
FROM ieb.ieb_wb_servers s
LEFT JOIN ieb.ieb_agent_indexes a ON a.wbsvr_wbsvr_id = s.wbsvr_id
GROUP BY s.wbsvr_id, s.wb_server_name, s.wb_server_type, s.com_ip_address, s.com_port_number;

Related Objects

IEB_WB_SERVERS is referenced by three dependent IEB tables through the WBSVR_WBSVR_ID foreign key, and itself references a security lookup:

• IEB_AGENT_INDEXES — join on IEB_AGENT_INDEXES.WBSVR_WBSVR_ID = IEB_WB_SERVERS.WBSVR_ID.
• IEB_WB_SVC_CATS — join on IEB_WB_SVC_CATS.WBSVR_WBSVR_ID = IEB_WB_SERVERS.WBSVR_ID.
• IEB_WB_SVRS_MMS_SVRS — join on IEB_WB_SVRS_MMS_SVRS.WBSVR_WBSVR_ID = IEB_WB_SERVERS.WBSVR_ID.
• FND_SECURITY_GROUPS — referenced via IEB_WB_SERVERS.SECURITY_GROUP_ID for security group resolution.

Together these relationships make IEB_WB_SERVERS the central configuration anchor for the Interaction Blending server topology in Oracle EBS.