Registry Manager

The Registry Manager maintains a set of registries for caching WebSphere Commerce runtime data. Each registry provides methods to enable adding, deleting and refreshing of the registry content. These methods are available to the URL interface by means of the ListRegistry and the RefreshRegistry commands.

If the data in the tables associated with a registry is changed, you will need to refresh that registry for the change to take effect. For example, if a new entry is added to the Struts Configuring, the UrlRegistry has to be refreshed. Otherwise, the WebSphere Commerce runtime environment will not recognize the new URL.

The Registry Manager can manage any registries registered to it, including customer created registries.

There are two ways to register a registry with the Registry Manager:

1. Define a new registry:

   • In the WebSphere Commerce configuration file, in the <Registries></Registries> node, add a new <registry>. For example

     <registry initialCapacity="500" name="myStoreRegistry" regClassName="com.ibm.commerce.registry.StoreRegistry"/>
     
     
     

2. Explicitly call the addRegistry() method of the RegistryManager class.

The following is a list of registry components, their usage, and their associated tables:

Registry component	Usage	Associated table
AltLanguageRegistry	Alternative store language (used when the default store language is not available).	STORE, if the store group is changed or a new record is added to LANGPAIR If the AltLanguageRegistry is updated with new descriptions then the CurrencyManager and the QuantityManager should also be updated, because of the alternative languages specified.
BusinessPolicyRegistry	Business policies (sets of rules followed by a store or group of stores that define business processes, industry practices, and the scope and characteristics of a store's or group of stores' offerings)	POLICY, POLICYCMD
BusinessPolicyPriceListRegistry	Caches the relationship between TCs and their related policy IDs and price lists under a specified store.	TERMCOND, POLICYTC, POLICY
CalculationRegistry	Calculation rules, methods, ranges for coupon, discount, shipping, and taxes	CALRULE, CALMETHOD, CALSCALE, CALRANGE, CALRLOOKUP, STENCALUSG, and CALCODE (where only the default calculationCodes are cached), TAXCGRY, CATENCALCD CATGPCALCD CALCODEMGP, CALRULEMGP SHPJCRULE, TAXJCRULE CRULESCALE This registry needs to be refreshed whenever coupon, discount, shipping, or taxation configuration has been changed.
CommandRegistry	WebSphere Commerce commands, allowing the WebSphere Commerce Server to look up an implementation and default parameters for a command interface. ../../com.ibm.commerce.database.doc/database/cmdreg.htm	CMDREG
CampaignInitiativeCache	Campaign, Web activity, and e-Marketing Spot related information, including the rule that determines the marketing content to be displayed to customers and the conditions under which the customers are restricted.	CAMPAIGN, INITIATIVE, EMSPOT, and INTVSCHED
CurrencyManager	Store currency, including the customer or buyer preferred currencies and shopping currencies.	CURLIST, CURCVLIST, CURCONVERT, CURFORMAT, CURFMTDESC, STORELANG, NUMBRUSG, STOREENT (If the column SETCURR changes)
DeviceFmtRegistry	Device format algorithms, used to determine the appropriate JSP file to use as the response to a particular request for a message mapper. An adapter accepting requests and using the message mapper is given a device format ID.	DEVICEFMT
LanguageRegistry	Store language	LANGUAGE
QuantityManager	Quantities within orders, including the conversion format rules, quantity formats, and descriptions.	QTYCONVERT, QTYFORMAT, QTYFMTDESC, NUMBRUSG
SCFRegistry	Store configuration file	This registry caches the store configuration file (SCF) and needs to be refreshed whenever this file is updated. Tooling that modifies the store configuration file will automatically refresh this registry. The store configuration file for a given store is located in the path defined by the SCFFile variable in the instance configuration file.
StoreRegistry	Store information	STORE, STOREENT, and STOREGRP
TradingAgreementRegistry	Trading agreements. WebSphere Commerce supports several trading agreement types, including account, contract, RFQs, exchange, and auctions. The trading agreement types are defined in the TRDTYPE table.	TRADING
UrlRegistry	WebSphere Commerce controller commands (also called URLs)	Struts Configuring
UBFRegistry	UBF (universal business flow) for approvals, auctions, contracts, and trading	FLOWDOMAIN, FLOWDESC, FLOWTYPE, FLTYPEDESC, FLOW, FLDOMNDESC, FLSTATEGP, FLSTGPDSC, FLSTATEDCT, FLSTDCTDSC, FLSTATEREL, FLTRANSITN, FLTRANSDSC, FLCOMPOSE

Related tasks

Related Reference