How to add Dimensions to the data in OEID

Question

Hi ,
I am relatively new to OEID with some background on Endeca web commerce.
We are trying to import the data from OBIEE server into the OEID . We are able to achieve this by using Load Data from OBI server option in Integrator.
The issue we are facing is that all the attributes are under navigation pane in studio when we load the data source in a studio application. What we need to have is to remove some of the attributes (that are not managed) and add some managed attributes (a.k.a dimension).I understand PDR and DDR need to be worked on . But my question is that how is the association of attribute to the PDR and DDR managed?
Any help would be appreciated. Or any pointer to the document that can help in this will also be great as I could not find documentation to add dimensions(managed attributes)
Version : OEID 3.0
Regards,
Mayank Batra

Answer 1

Mayank,
Is it mandatory that I have OUTER_TRANSACTION_ID (even if I try to run this current graph only) ? The OUTER_TRANSACTION_ID parameter is necessary if you want to run the graph as part of an outer transaction. Configuration graphs such as this one are often included in outer transactions used to refresh the data domain. You can omit it from the Web Service Client during development, but if you decide you want to include the graph in an outer transaction, you will need to add it.
I am adding a Web Services Client and linked to the input port of this WSC ,the output port of the transformer. Where does the code mentioned in the link goes?Do we need to keep the code in a file and pass the URL to the WSC because looks like that is what it takes. As stated earlier in the topic, graphs used to load the standard attribute schema generally follow a standard pattern. See http://docs.oracle.com/cd/E39272_01/integrator.300/integrator_users/src/ci_csv_based_configuration_graphs.html for details about these graphs.
You do not need to store the output of the Transformer as a file. The XML document output by the Transformer component is held in memory during processing.
Note, BTW, that your graph should also include a Denormalizer component between the Transformer and the Web Services Client.
Basically, once the input is read into the graph, it is processed by a Transformer component to create an XML document that can be incorporated into a Web Services request.
The XML document output from the Transformer component includes line breaks. The line breaks cause the input Web Services request to be terminated incorrectly. Therefore, the output from the Transformer should be fed into a Denormalizer component and converted into a single XML string. This string is then added to the Web services request in the Web Services client and submitted to the Endeca Server.
RLJII