Including sku attributes in product-sku-output-config.xml

Hello,
We have configured the product catalog integration between ATG and Endeca successfully and now I'm guessing how to expand/include other attributes of SKU into the Endeca Index, such as thumbnail and large Images which we are using as External Media Elements. I bet we'll have to customize product-sku-output-config.xml file, but how may this be accomplished?
Any tip or direction?
Thank you very much,
Rogerio Biondi
Discover Technology
Edited by: monotone on Dec 11, 2012 12:28 PM

Hi, monotone!
Yesterday I faced with this issue too and resolved it in such way.
1. Create product-sku-output-config.xml file in config folder of your module: config/atg/endeca/index/commerce/product-sku-output-config.xml
2. Extend it by adding needed properties. If property value is primitive type, you may just add property:
>
<item item-descriptor-name="product">
     <properties>
          <property name="displayName" output-name="product.displayName" type="string" />
     </properties>
</item>
>
If property value is Object, you must create property accessor that use custom logic for determining the values of properties that you specify. For example, the value of mediumImage is RepositoryItem of Media type. If you want to get medium image url (mediumImage.url), you may write so property accessor:
>
public class MediumImagePropertyAccessor extends PropertyAccessorImpl {
     private String mediumImagePropertyName = "mediumImage";
     private String urlPropertyName = "url";
     protected Object getTextOrMetaPropertyValue(Context pContext, RepositoryItem pItem, String pPropertyName, PropertyTypeEnum pType) {
          RepositoryItem externalMediaItem = (RepositoryItem) pItem.getPropertyValue(mediumImagePropertyName);
          String imageUrl = externalMediaItem.getPropertyValue(urlPropertyName).toString();
          return imageUrl;
>
After that you must specify this accessor in property-accessor attribute of your property in product-sku-output-config.xml:
>
<item item-descriptor-name="product">
     <properties>
          <property name="mediumImage" output-name="product.mediumImage"
               type="string" property-accessor="/com/something/endeca/index/accessor/MediumImagePropertyAccessor" />
     </properties>
</item>
>
3. Do baseline index via ProductCatalogSimpleIndexingAdmin component.
Refer to http://docs.oracle.com/cd/E35318_02/Platform.10-1-1/ATGEndecaIntegrationGuide/html/s0401configuringendecaindexingoutputc01.html for more information.

Similar Messages

Product-sku-output-config.xml - Is there a schema definition (XSD or DTD)?

For the product-sku-output-config.xml file (used to define the set of product and sku attributes that are sent to Endeca from ATG as part of the Baseline Index process, as defined in chapter 4 of the ATGEndecaIntegrationGuide.pdf, 10.1.2 version), is there a schema definition (XSD or DTD) available?
The format used by product-sku-output-config.xml seems similar to, but not the same as, the format described by http://www.atg.com/dtds/search/indexing-dependency-schema.dtd. For example, p35 of the ATGEndecaIntegrationGuide.pdf gives an example of a product-sku-output-config.xml with a "properties" child element of the top-level "item" element; per that indexing-dependency-schema.dtd, that isn't allowed. (Per that DTD, it should be either "meta-properties" or "text-properties", not "properties".)
More generally, I'm wondering if there's place that fully defines what can go into the product-sku-output-config.xml file.
I'm also interested this same question for the category-dim-output-config.xml file.
Thanks,
-Jon

For the product-sku-output-config.xml file (used to define the set of product and sku attributes that are sent to Endeca from ATG as part of the Baseline Index process, as defined in chapter 4 of the ATGEndecaIntegrationGuide.pdf, 10.1.2 version), is there a schema definition (XSD or DTD) available?
The format used by product-sku-output-config.xml seems similar to, but not the same as, the format described by http://www.atg.com/dtds/search/indexing-dependency-schema.dtd. For example, p35 of the ATGEndecaIntegrationGuide.pdf gives an example of a product-sku-output-config.xml with a "properties" child element of the top-level "item" element; per that indexing-dependency-schema.dtd, that isn't allowed. (Per that DTD, it should be either "meta-properties" or "text-properties", not "properties".)
More generally, I'm wondering if there's place that fully defines what can go into the product-sku-output-config.xml file.
I'm also interested this same question for the category-dim-output-config.xml file.
Thanks,
-Jon

Is it possible to have 2 different output config XML files and index the data into 2 endeca apps using the same indexing component ProductCatalogSimpleIndexingAdmin

Hi ,
We have a catalog that defines 2 types of products (they have too many different properties), so wanted to keep them on two different MDEX engines and serve the applications requests. Here DB catalog and front end ATG application is same for both the MDEX instances.
Is it possible to have 2 different output config XML files and index the data into 2 endeca apps using the same indexing component ProductCatalogSimpleIndexingAdmin?
Thanks
Dev

Hi, also have had some problem some monthes ago - I created separete component ProductCatalogSimpleIndexingAdminSecond. After that one of my colleage gave me some advice:
The creating separate component like ProductCatalogSimpleIndexingAdmin for the second IOC is possible way for resolving your situation. But I afraid that this way will be required creating mane duplicates for already existed components.
In my opinion the better way is the following:
starting from AssemblerApplicationConfiguration and ApplicationConfiguration component. It contains details for connecting between ATG and Endeca. Of course you should configure different components for different Endeca Apps.
After that:
Find all components that uses AssemblerApplicationConfiguration and ApplicationConfiguration. Customize these components for using one or another *Configuration component depending on what index works. (many variants released it: the most simple global custom component with flag.)
Then customize the existed ProductCatalogSimpleIndexingAdmin. Using one or another IOC and setting the flag in global custom component when index started. You can add some methods into your custom ProductCatalogSimpleIndexingAdmin like:
Execute baseline index for both IOC (one by one)
Execute baseline for IOC 1
Execute baseline for IOC 2.
Note: you should be afraid about incremental (partial) index in this configuration. But resolving conflicts in incremental index should be done after full implementation these changes.
Regards

How to include validation attribute (xmlns:xsi) into the resulting XML ?

Hi,
I'm having a problem including the validation schema attribute (xmlns:xsi) into the resulting XML.
For example, if I have the following schema:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="A" />
</xs:schema>
And I use the following code to get the XML:
XmlOptions ops = new XmlOptions();
ADocument ad = ADocument.Factory.newInstance();
ADocument.A a = ad.addNewSubscriptionNotification();
System.out.println(ad.xmlText(ops));
I will get something like:
<A />
I'd like to have:
<A xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://a.com/a.xsd"/>
How do I make this happen? Some xmlOptions, different kind of schema...?

Use
             <fx:resources>
                <fx:fileset dir="${basedir}/${dist.dir}" includes="*.jar"/>
                <fx:fileset dir="${basedir}/${dist.dir}" includes="lib/*.jar"/>
            </fx:resources>or simply
      <fx:fileset dir="${basedir}/${dist.dir}" includes="**/*.jar"/>Filed http://javafx-jira.kenai.com/browse/RT-24757 to update the docs.
Edited by: igor on Sep 5, 2012 2:23 PM

Can not find product , sku attributes data in database table

Hi there,
I find it really strange to find data in database related to product and sku. I set up the commerce reference store and store is up and running fine. Catalog is fine too. I am not able to find data related to sku attributes in database.
I have a product_id xprod2511 which has 11 child skus such as xsku2511_1, xsku2511_2 and so on. sku xsku2511_1 is blue color and size 4. When I search for this two sku attributes (color and size) information in dcs_sku_attr table with sku_id as xsku2511_1, no rows returned. In fact, I looked into few other sku tables but I am not able to find the information about color and size of a sku in any database table.
this is the query I am running:
select * from dcs_sku_attr where sku_id = 'xsku2511_1'
Can someone please let me know the table name where this information regarding color and size resides in?
Thanks a lot.

In dyn/admin If you try and view the definition file of ProductCatalog repository, then under sku item descriptor you would see the color and size property which would be under some table tag, that table tag table name should be the table holding these values.
the other question(may be silly) is that I hope that you are executing sql in correct schema, that is cata or catb schema (select * from catA.dcs_sku_attr) where the actual product catalog data resides.

Office 2013 Click to Run - VAMT error: product SKU is not found

We failed to install the retail key for Office 2013 Home and Business Retail through VAMT. Error is: The Software Licensing Service reported that the product SKU is not found.
VAMT key install and activation worked fine with other retail products. I believe it's somehow related to the click-to-run technology.
Any help would be appreciated.

Hi,
I'm not quite sure how exactly you did in VAMT, but usually, the error message will show up only if you are using a wrong product key.
Do you have any other product keys installed in VAMT? Make sure you are using the correct key. Also, which activation option are you using in VAMT?
http://technet.microsoft.com/en-us/library/hh825164.aspx
Regards,
Ethan Hua
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

How to work with SKU bundle with selectableSKU & SKU..?

Hi All, it is new version to my previous question..?
i have a SKU bundle with selectableSKU & SKU.. Here SKU price is not being included in to total product price..? and also the SKU is not included to Order..?
Thanks,
Vishnu

If we want the sequence table shall we have to create it seperately or will it creates directly?

XML/XSLT: Setting xsl:include href attribute with a variable

I have a main layout stylesheet and depending on which page the user selects I want to use xsl:include to display the selected information in the 'content' DIV. The process works fine if hardcode it like this:
<xsl:include href="welcome.xsl"/>
<div id="content"
<xsl:call-template name="welcome"/>
</div>
but, what I would like to do is have the name of the included template pulled from the xml file depending on which page was selected by the user. Something similar to this:
<xsl:variable name="ss">
<xsl:text><xsl:value-of select="root/stylesheet"/></xsl:text>
</xsl:variable>
<xsl:include href="{$ss}.xsl"/>
<div id="content">
<xsl:apply-template name="{$ss}"/>
</div>
So far I have tried using many different forms of code and have been unable to get this to work. Any ideas?
EDIT: Okay, I have it partly figured out, at least why it isn't working. As far as I can tell, the 'xsl:include' tag must be a child of the 'xsl:stylesheet' tag, and is thus declared before the <xsl:template match="/"> which means it can't read the xml element to even store it in the variable. I have an idea of how to accomplish what I need, though.
Last edited by munkyeetr (2009-01-28 03:29:58)

I have attempted the same thing before as well. The only way I was able to dynamically build the xsl:include was to declare a new namespace e.g xmlns:out="output.xsl" in my XSL file and do something like the following:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:out="output.xsl">
<xsl:namespace-alias stylesheet-prefix="out" result-prefix="xsl"/>
<xsl:varible name="xxx" select=" 'myFile.xsl' "/>
<xsl:template match="/">
<out:stylesheet version="1.0">
<out:template match="/">
<out:include>
<xsl:attribute name="href">
<xsl:value-of select="$xxx" />
</xsl:attribute>
</out:include>
</out:template>
</out:stylesheet>
</xsl:template>
</xsl:stylesheet>
When applied to any valid XML document this produces the XSL file you are after as the output.
To use this output against your intended XML source consider the following: A Java program can very quickly apply the above stylesheet to any XML source to get the output you want... then apply that XSL result to the actual XML document you are wanting to transform. From here you can do what you want with the transformed result.

XML element,if not including any attributes and/or child elements then

XML element in SQLX,if not including any attributes and/or child elements then the tag should not appear, how to achive this?
ex:Consider for <enumeration> tag where it is having some value.
<attribute>
<name>Ethernet Access</name>
<enumeration>
<StringValue>Bandwidth</StringValue>
</enumeration>
</attribute>
When <enumeration> tag is not have any Value in this, then output should be as follows.
<attribute>
<name>Ethernet Access</name>
</attribute>
But what i am getting is
<attribute>
<name>Ethernet Access</name>
</enumeration>
</attribute>
Please suggest me the solution for this.
I tried , but when xmlelement() is not having data it will display empty tag ie </enumeration>, If xmlforest() are null it wont show tag, But i have to use xmlelement only. how can that be achived using xmlelement .

Use a SQL case - when - else end construct to only execute the xmlelement if data is present. The SQL/XML standard is very clear, xmlElement will generate an empty element if no data is present. xmlforest will not.

Open fields PO Qty in SKU and u0093Order Unit - SKU to be changed at PO.

We put an breakpoint at function MEX_FEUSWAHL thru SE37 to get the screen control to PO, and the function return AKTH , ME21N , NBF and PT0F.
We need to set fields PO Qty in SKU and Order Unit <-> SKU to optional maintenance.
At tab Quantities / Weights on PO the fields are greyed.
We changed the screen control into the customizing to Optional , but fiels keeps greyed, and get the values from material master.
Does anyone knows a way to change it to Optional ? or does it fields are controlled by program ?
Best regards,
Ale

These fields are controlled by program, you can't change in the PO. you have to maintain the conversion in mateiral master and then use the appropriate order unit in the PO.

Error while converting planned order to production order for config materia

Hi experts,
While converting a planned order to production order for a configurable material.I am getting the following error meassage. Message No.CO684,
"You cannot make an assignment to make-to-order stock"
( DiagnosisThe component cannot be allocated to an individual stock because make-to-order production and engineer-to-order production cannot be executed with this order.
A possible cause is that you are trying to create an order with reference to a sales-order/project, where an account assignment to a sales order/project is not allowed in the settlement profile that is assigned to the chosen order type. This is inconsistant.
System ResponseThe following responses are possible:
Order processing is cancelled.
The system resets the special stock indicator back to the original value.
Procedure
Choose another order type).
I have checked some of the threads related to this error. But no where there is any solution.Please tell me if there is any settings to make so as to work on this scenario.
Thanks,
Sham

Hi,
This will be a MTO scenario. Please check your requirement type,Requirement class and strategy type config along with your Item category and schedule line category from SD.
Also check your Production order type config and settlement profiles.
I mean to say that you need new production order type to be configured for specific above mentioned combination.
Are you working on a production system..?? is it the first time you are creating the order for this config material..??
Regards,

Howto optionally include an attribute on an element in a JSP document ?

I cannot find a way to optionally include an attribute on an element in a JSP document (JSPX). My JSP document is used to create an XML according to an XML schema where some element are declared as optional by the schema (default for element attributes).
I've tried:
a)
<elem <c:if test="${!empty obj.attr}">attr=${obj.attr}</c:if>>
</elem>b)
<jsp:element name="elem">
   <c:if test="${!empty obj.attr}">
      <jsp:attribute name="attr">${obj.attr}</jsp:attribute>
   </c:if>
   <jsp:body>
   </jsp:body>
</jsp:element>And none of them work. Any ideas?

I cannot find a way to optionally include an attribute on an element in a JSP document (JSPX). My JSP document is used to create an XML according to an XML schema where some element are declared as optional by the schema (default for element attributes).
I've tried:
a)
<elem <c:if test="${!empty obj.attr}">attr=${obj.attr}</c:if>>
</elem>b)
<jsp:element name="elem">
   <c:if test="${!empty obj.attr}">
      <jsp:attribute name="attr">${obj.attr}</jsp:attribute>
   </c:if>
   <jsp:body>
   </jsp:body>
</jsp:element>And none of them work. Any ideas?

How to include a Attribute in a Navigation Block of a Web Report

Hi all,
I am trying to include an Attribute of an Infoobject in to a Navigation block. But the attribute is not appears in the list of navigation block objects inside the properties window of Web item (navigation block).
And one more thing how can we find a 25dizit number of a info object
Thank you
srini

Hi Fasttrack2,
According to your description, there is a main report with more than 100 rows of summary information, when users click the item of the row, the report need to jump to detail information shows as graph. The problem you are facing is that you are not sure
subreport, drilldown or drillthrough report should be used? You hope to set display detail information in the main report and keep high performance of report.
In Reporting Services, each subreport instance is a separate query execution and a separate report processing task. Subreports are recommended when there are just a few subreport instances. We should not use subreports inside a group when there are many
group instances, instead, consider using drillthrough reports. Drilldown reports process all data even when the data is first hidden. In order to improve the performance of the report, we can split drilldown reports into parameterized drillthrough reports,
because Drillthrough reports do not run until a user clicks the drillthrough link in the main report.
In this case, we can consider using drilldown or drillthrough report. In drilldown report, when we click a plus or minus button to expand or collapse a section of a report, the detail data will be displayed in place. By using drillthrough report, when we
click the link in the main report, the detail data will be displayed, we can come back to the main report by click return button in the drillthrough report.
Reference:
Troubleshooting Reports: Report Performance
Drillthrough, Drilldown, Subreports, and Nested Data Regions
If you have any more questions, please feel free to ask.
Best Regards,
Wendy Fu
If you have any feedback on our support, please click
here.

EEWB (attributes from product set type)

Hi gurus,
I have a question about EEWB. Could you please help me.
There is possibility to add components (attributes from product set type) at item level:
Business object - BUSINESS_TRANSACTION
Extension Type - ADD_NEW_ITEM_COMPONENT.
Ive created an extension with certain set type (it consists of 2 attributes). Everything was ok. New fields with 2 attributes have been added to new tab in a sales orders item.
But then Ive added 1 new attribute to the same set type. So I think this new attribute is to appear on the same tab with 2 other attributes. But it doesn'tt!
Ive regenerated my extension, Ive recalled wizard for this extension. Nothing has changed. There is still only 2 attribute in the tab.
So is it normal situation and is it necessary to create a new extension in order new fields to appear in a tab? Or I can do something else without creating the new extension?
So could you help me and give any solutions. Appreciate any help.
And thanks in advance.
Sunny.

It works already.

Can't create detail VO in one VO that including all attributes from M/D VO

Hi,
I have two EOs(BrFixreq/DafDefect) and two VOs(BrFixreqVO/DafDefectVO) based on the EOs, when create association between them I have selected "composition association" check box and "Cascade Update key Attributes" check box, and cardinality is 1 to 1.
And also another VO( TestViewObj) includes all attributes in BrFixreqVO and DafDefectVO, and set BrFixreq/DafDefect to updatable in TestViewObj definition , and add TestViewObj to an AM(AppModue).
When I run this AM in Oracle Business Component Browser, click "TestViewObj1" in left tab, and click the green plus sign on the toolbar, it only creates master VO attributes, not including detail VO attributes.
Any directions will be great help to me!
Thanks,
zeroxin

Hi,
I presume that your tables are associated "1 to 1".
This means that you could create your VO's and a viewLink and drop them in the page as Master(form)-Detail(form).
You would have to bind actions for both VO's in each CRUD button (ex. Insert should execute CreateInsertMaster and CreateInsertDetails).
Off course it would be better if things worked with a single VO because you would not have to do anything.
This is simply proposed as a workaround in case that you cannot make it work. More issues regarding the details of your implementation could occur that you would have to deal with.
Another way to handle this so that you have a single VO would be to create a database view that will handle insert, update, delete on both tables and create an Entity Object based on this view.
You can read more about this in the Fusion Developer's Guide For Oracle ADF (Chapter 37.5)
Gabriel.

Including sku attributes in product-sku-output-config.xml

Similar Messages

Maybe you are looking for