3 BDI Job Admin

BDI Job Admin is a web application and services responsible for management of the receiving of data into OCDS from BDI. In as much as BDI Job Admin is a component of OCDS, it is also a component of the enterprise infrastructure that enables OCDS to receive Merchandising and Pricing data.

BDI Interfaces

OCDS (BDI) Job Admin is the interface between BDI infrastructure and OCDS, enabling BDI data to flow into the OCDS database. The following table lists the BDI Interfaces supported by OCDS for which data is exposed through REST web service resources.

Table 3-1 BDI Interfaces supported by OCDS

Interface Module	BDI Type
Clearance_Tx	Transactional
COFutureAvail_Tx	Foundational
DiffGrp_Fnd	Foundational
Diff_Fnd	Foundational
InvAvailStore_Tx	Foundational
InvAvailWh_Tx	Foundational
ItemHdr_Fnd	Foundational
ItemImage_Fnd	Foundational
ItemLoc_Fnd	Foundational
MerchHier_Fnd	Foundational
OrgHier_Fnd	Foundational
PriceChange_Tx	Transactional
PromotionOffer_TX	Transactional
RelatedItem_Fnd	Foundational
StoreAddr_Fnd	Foundational
Store_Fnd	Foundational
VatItem_Fnd	Foundational
Vat_Fnd	Foundational
WhAddr_Fnd	Foundational
Wh_Fnd	Foundational

Scheduling BDI Data

OCDS receives data from two sources, BDI and RIB. For data families where RIB messages trickle incremental changes to OCDS, a one-time BDI job provides OCDS with an initial load. For data families without RIB support, scheduled BDI jobs provide OCDS with recurring refreshes.

Table 3-2 Recommended BDI Refreshes for OCDS

BDI Family	BDI Refresh
Clearance Price	SCHEDULED
Diff Group	ONE-TIME ONLY
Diff	ONE-TIME ONLY
Inv Avail Store	SCHEDULED
Inv Avail Warehouse	SCHEDULED
Inv Future Available	SCHEDULED
Item Header	ONE-TIME ONLY
Item Image	ONE-TIME ONLY
Item Location	ONE-TIME ONLY
Item Supplier	ONE-TIME ONLY
Merchandise Hierarchy	ONE-TIME ONLY
Organization Hierarchy	ONE-TIME ONLY
Price Change	SCHEDULED
Promotion	SCHEDULED
Related Item	ONE-TIME ONLY
Store	ONE-TIME ONLY
VAT	SCHEDULED
VAT Item	ONE-TIME ONLY
Warehouse	ONE-TIME ONLY

Scheduled

BDI families not utilizing RIB for incremental changes should be scheduled using the BDI Scheduler at intervals appropriate for the BDI family.

One-Time Only

BDI families where initial load of data is provided by BDI, and incremental changes are provided by RIB, should not be scheduled using the BDI Scheduler. The only time OCDS should receive a subsequent BDI, after the initial load, is if the OCDS data is determined to be unreliable.

Important: Note that refreshing OCDS one-time only families may force downstream system, such as Xstore, to purge and completely refill all databases. Understanding how Omnichannel applications behave when OCDS is refreshed is extremely important when evaluating the decision to refresh "One-Time Only" data in OCDS from BDI.

WebLogic Users and Groups

WebLogic security realms provide a mechanism for protecting WebLogic resources. Users are entities that can be authenticated in a security realm. Users are organized into Groups that can have different levels of access to WebLogic resources.

This section lists the default security realm's Groups and Users used by the BDI Job Admin component.

See Monitoring Batch Jobs Using BDI Job Admin in Oracle® Retail Bulk Data Integration Implementation Guide for information about Job Admin User roles.

Groups

Table 3-3 WebLogic Groups

Name	Description	Component
BdiEdgeOcdsJobAdminGroup	User who can create, run and monitor Jobs	BDI Job Admin
BdiEdgeOcdsJobMonitorGroup	Users who can run and monitor jobs	BDI Job Admin
BdiEdgeOcdsJobOperatorGroup	Users who can monitor jobs	BDI Job Admin

Users

Table 3-4 WebLogic Users

Type	Group	Description	Component
Job Administrators	BdiEdgeOcdsJobAdminGroup	Job Administrators	BDI Job Admin
Job Operators	BdiEdgeOcdsJobOperatorGroup	Job Operators	BDI Job Admin
Job Monitors	BdiEdgeOcdsJobMonitorGroup	Job Monitors	BDI Job Admin

Changing User Passwords

A production OCDS should be integrated with IDCS or OIM. See the documentation for the integrated identity management solution for details on password management.

A non-production OCDS can simply use the WebLogic DefaultAuthenticator. The OCDS JobAdmin's user password is authenticated by the default Authentication Provider configured for the security realm of the WebLogic domain. When using the DefaultAuthenticator, a user password can be reset directly by accessing the Users and Groups tab of the security realm's settings in the WebLogic Admin Console.

Logging

Job Admin logs to multiple files, all located on the file system under the deployment path for the ocds-batch-job-admin.war. For more information, see Monitoring Batch Jobs Using BDI Job Admin in Oracle® Retail Bulk Data Integration Implementation Guide for additional details regarding Job Admin logging.

URL patterns

OCDS Job Admin uses the following URL patterns.

Table 3-5 URL Patterns

Type	User
Web Application User Interface	`http://<hostname>:<port>/ocds-batch-job-admin/`
REST services	`http://<hostname>:<port>/ocds-batch-job-admin/ocds-batch-job-admin/resources`

Job Admin User Interface

The OCDS BDI Job Admin UI is a web application that provides the GUI for managing batch jobs and runtime.

The User Interface provides ability to:

Start/restart, and track status of jobs
Trace data
View diagnostic errors
Manage options at job and system level
View the logs

Job Admin is a standardized framework component used by Oracle Retail BDI Edge Applications. Detailed documentation for the component is available in the Oracle® Retail Bulk Data Integration Implementation Guide.