Panel Customizable not showing Oracle BI under Mashups, when in Composer mode

Question

I had created a page with panel Customizable:
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
          xmlns:cust="http://xmlns.oracle.com/adf/faces/customizable"
          xmlns:pe="http://xmlns.oracle.com/adf/pageeditor">
  <jsp:directive.page contentType="text/html;charset=UTF-8"/>
  <f:view>
    <af:document id="d1">
      <af:form id="f1">
        <pe:pageCustomizable id="pageCustomizable1">
          <cust:panelCustomizable id="panelCustomizable1" layout="scroll"/>
          <f:facet name="editor">
            <pe:pageEditorPanel id="pep1"/>
          </f:facet>
        </pe:pageCustomizable>
      </af:form>
    </af:document>
  </f:view>
</jsp:root>
Earlier, I had installed all jDeveloper extensions
Business Intelligence ADF Task Flow
Business Intelligence ADF View Regions
Business Intelligence Composer
Business Intelligence Logical SQL View Objects
Business Intelligence Soap Connection
I followed the instructions given here
I had included library oracle.bi.jbips in weblogic-application.xml
I had included library oracle.bi.composer in weblogic.xml  (both of these steps are from the same instructions)
I have included the following libraries for BI in my Webcenter Portal project:
BI ADF Runtime
BI ADF Taskflow
BI JDBC
BI SOAP Connection Runtime
BI View Object Runtime
BI JIBPS
Then, I right-click on the jspx file shown above (from Application Navigator) and click Run.
After the page shows up, I press Cntrl + Shift + E.  Content Editor window shows up.
I select "Add Content".  In the popup that comes up, I select "Mash-Ups".  After that, "Oracle BI" should appear.  But it doesn't
Can someone please help me figure out why I am not seeing "Oracle BI" option in the popup after I select "Mash-Ups"?

Answer 1

Hi Vetsrini,
Many thanks for offering to help. It has just been solved. It was a typo in the XML of the name of the column.
Doh! Obvious now that I know!
- Jenny