Oracle ATG Web Commerce 10 Implementation Developer Essentials

Explanation:
Components are registered with the /atg/multisite/SiteGroupManager using the shareableTypes property.

References:

Explanation:
Auxiliary Tables
You can handle some data relationships using auxiliary attribute tables. For example, you could store users and their addresses in two related database tables, as described in the following piece of an XML repository definition:
<item-descriptor name="user">
<table name="dps_user" type="primary" id-column-names="id"> <property name="login" data-
type="string"/>
</table>
<table name="dps_address" type="auxiliary" id-column-names="id"> <property name="address1"/>
<property name="city"/>
<property name="state"/>
<property name="zip"/>
</table>

</item-descriptor>
Each user has a single address. For the purposes of this example, the user information is stored in a separate table from the user's address information.

Note: Primary and Auxiliary Tables

Each item descriptor must have one and only one primary table. The primary table is specified using the type="primary" XML attribute in a <table> tag. The primary table must define a column or columns that
store the repository ID. This column is specified using the id-column-names attribute. For example:

<table name="user" type="primary" id-column-names="id"> properties...
</table>

References:

Explanation:
Preserving request scoped objects on redirects
If a request results in a redirect to a local page through the method HttpServletResponse.sendLocalRedirect(), the ATG platform treats the redirect request as part of the original request, and maintains any request-scoped objects associated with that request. To implement this, the ATG platform adds an additional query parameter named_requestid to the redirected URL.

References:

Explanation:
allRootCategories lists of all the root categories in the catalog, including the allRootCategories in the rootSubCatalogs. This is used for display purposes.

Note: Displaying Root Categories

Typically, a catalog home page displays a list of root categories. Unlike other categories, root categories cannot be found through the childCategories property of other categories. Root categories are those that appear in the allRootCategories property of the user's catalog.

References:

Explanation:
Difference between Item Cache and Query cache

For each item descriptor, an SQL repository maintains two caches:

* Item caches
* Query caches

Item caches hold the values of repository items, indexed by repository IDs. Item caching can be explicitly enabled for each item descriptor.

* Query caches hold the repository IDs of items that match given queries. When a query returns repository items whose item descriptor enables query caching, the result set is cached as follows:

/ The query cache stores the repository IDs.
/ The item cache stores the corresponding repository items.

Explanation:
B (not A): You can limit the number of items that can appear in the slot at any one time.
E:
Note: The TargetingForEach servlet bean is a specialized version of the ForEach servlet bean that performs a targeting operation using the targeter component set by its targeter and sourceMap parameters. The TargetingForEach servlet bean displays every item returned by the targeting operation in the manner specified by its output parameter.

maxNumber
If the maxNumber property is set, the targeter only returns at most maxNumber items in the targeting result set. You can use this property as a precaution to prevent loading potentially large result sets into memory.

Explanation:

Preventing Inventory Deadlocks

InventoryManager includes the acquireInventoryLocks and releaseInventoryLocks methods. These methods can be used to prevent deadlocks in the database, especially if there are multiple ATG Commerce instances concurrently updating inventory.
References:

Explanation:
A: Nucleus performs one basic operation: resolving component names. Given the name of a component, Nucleus does its best to find or create that component and return it.

C: Name resolution is not a difficult task. Nucleus shows its real power by creating components and hooking them up to other components automatically. This function is invoked when Nucleus is asked to resolve a name of a component that does not yet exist. In this case, Nucleus looks for the appropriate configuration file that describes how to create that component and any other components that it requires.

Note: Nucleus is the Dynamo Application Framework's component model for building applications from JavaBeans. Nucleus lets you assemble applications through simple configuration files that specify what components are used by the application, what parameters are used to initialize those components, and how those components hook up to each other. The ATG Control Center Components window provides a handy way to create, modify, and manage Nucleus components.

Nucleus by itself provides no application-specific functions. The JavaBean components implement all of an application's functionality. Nucleus is the mechanism that gives those components a place to live, and a way for those components to find each other.

References:

Explanation:
For Ground the calculation is 4.50 (Price range is used) + 4.99 (the post calculator always gives this result)
-> 9.49
For Expedited the calculation is 10.00 (Weight range is used) + 4.99 (the post calculator always gives this
result) -> 14.99

Note 1: A ShippingPricingEngine implementation which computes the shipping price for an order. It accomplishes this task by invoking a series of ShippingPricingCalculators which incrementally compute the tax price:

The first step is to allow the preCalculators to manipulate the price. They are invoked in the order in which they appear in the preCalculators list.
The second step is to extract the calculators from any input PricingModels, and invoke them in the order in which they appear in the pPricingModels list.
The last step is to invoke the postCalculators in the order in which they appear in the postCalculators list.

Note 2: The ShippingPricingEngine is a structural component that does not actually calculate shipping prices itself. The actual price calculations are performed by the Pricing Calculator components that are configured as the preCalculators and postCalculators properties of the ShippingPricingEngine.

References:

Explanation:

Note: When you start the ATG Control Center, the following screen appears:

References: