mkdir EM_Datamodels [notice the underscore]
mkdir "My Sample Report" [notice, the quotes are necessary since the directory name contains spaces]
The datamodel needs to go in the following directory:
-------------- "bipublisherreports/EM_Datamodels/My Datamodel.xdmz" [there is an underscore between EM & Datamodels]
The reports go in a report directory, for example:
--------------- "bipublisherreports/My Sample Report/My Report.xdoz" [use spaces here wherever you prefer]
Make sure your report refers to the datamodel in the right location. So, in BIP, when editing the report, use the above folder names, under the 'Enterprise Manager Cloud Control' shared folder.
For example, your BIP catalog will look like this:
---Enterprise Manager Cloud Control
-------------- My Datamodel
-------- My Sample Report
-------------- My Report
You then create a jar file with this:
jar cvf myemreports.jar bipublisherreports
Now, you need to make your bip reports part of your plugin source code.
You put your report.xml in your sysman/metadata/bipublisherreport [note the singular] directory.
<ReportFile relativePath="emreports" fileName="myemreports.jar"/>
You then create a subdirectory, sysman/metadata/bipublisherreport/emreports
And you put your myemreportrs.jar file here.
You then rebuild your opar using standard EM procedures.
When a customer later on instals your plugin, the BIP reports that go with the plugin are installed into the EM database repository automatically.
they can simply do this to deploy the bi publisher reports from em to BIP at any point:
emcli deploy_bipublisher_reports -plugind="my.sample.plugin" -pluginversion ="126.96.36.199.0" [-force]
The -force operation overwrites the reports.
See the complete help text like this:
emcli help deploy_bipublisher_reprorts
If they have not yet configured BIP with the configureBIP script, this deploy step happens automatically when they run configureBIP.
I think the problem you face is in your xml. The first attribute of the BIPublisher element must be the xml namespace which must match the target namespace outlined in the schema. During opar packaging you'll find that it extracts a schema to $TMP/BIPublisherReport.xsd_partner. Once it finds your report.xml it validates against this schema. To directly answer your question, the xmlns must be xmlns="http://www.oracle.com/DataCenter/BIPublisherReport". You can test the validation of your xml against the schema with Eclipse or because the xml and schema are so short you can use an online validation tool.