Error: Unable to find asset type in OER: ed1ed5 34-39b8-11de-bee0-79d657a0a2b0

I was trying to submit a project from Jdeveloper in Oracle enterprise repository and i got below error

NOTE: To harvest Oracle Service Bus 10 projects, please use osb10harvest.bat
com.oracle.oer.sync.framework.MetadataIntrospectionException: com.oracle.oer.syn
c.framework.MetadataIntrospectionException: com.oracle.oer.sync.framework.Metada
taIntrospectionRuntimeException: Error: Unable to find asset type in OER: ed1ed5
34-39b8-11de-bee0-79d657a0a2b0. Please make sure that the Harvester Solution Pa
ck is installed in OER.
at com.oracle.oer.sync.framework.MetadataManager.init(MetadataManager.ja
va:317)
at com.oracle.oer.sync.framework.Introspector.(Introspector.java:2
61)
at com.oracle.oer.sync.framework.Introspector.main(Introspector.java:537
)
Caused by: com.oracle.oer.sync.framework.MetadataIntrospectionException: com.ora
cle.oer.sync.framework.MetadataIntrospectionRuntimeException: Error: Unable to f
ind asset type in OER: ed1ed534-39b8-11de-bee0-79d657a0a2b0. Please make sure t
hat the Harvester Solution Pack is installed in OER.
at com.oracle.oer.sync.framework.impl.DefaultPluginManager.processIntros
pector(DefaultPluginManager.java:157)
at com.oracle.oer.sync.framework.impl.DefaultPluginManager.(Defaul
tPluginManager.java:99)
at com.oracle.oer.sync.framework.MetadataManager.init(MetadataManager.ja
va:315)
... 2 more
Caused by: com.oracle.oer.sync.framework.MetadataIntrospectionRuntimeException:
Error: Unable to find asset type in OER: ed1ed534-39b8-11de-bee0-79d657a0a2b0.
Please make sure that the Harvester Solution Pack is installed in OER.
at com.oracle.oer.sync.framework.MetadataManager.putAssetType(MetadataMa
nager.java:220)
at com.oracle.oer.sync.framework.impl.DefaultPluginManager.processIntros
pector(DefaultPluginManager.java:130)
... 4 more


The solution for this issue is to import the harvest solution pack in OER.

Login to OER

go to admin and import export tab



once the gui comes up.

Go to import tab and locate the zip file.

For a 12c installation it should be in following location

SOA_HOME\oer\modules\tools\solutions

Say import and finish the wizard.



Once completed try to resubmit the data and see if you get any issue.

Disable auto built in Jdeveloper 12c on Saving project

I was quite annoyed with this feature of Jdeveloper 12c as whenever i save the project it tries to compile the project.

This is a default feature in Jdeveloper 12c.

It is good if you are working in a local machine

But if you are working in a remote machine which is already very slow this feature is quite annoying.

Luckily you can remove this feature.

In order to remove this

Go to Jdeveloper

Tools--->Preference

Go to Code Editor --> Save action.

there by default "Build project after save" option is added.

Select that option and remove it.



Say ok and restart Jdeveloper.

Now you should not face this issue.

Upgrade BAM 11g to BAM 12c-Issues in BAM 12c

If you are working in a project where there is a requirement to upgrade BAM 11g artifacts to BAM 12c.

Be very careful while giving the estimates to client for the migration.

Make sure you know some facts on BAM 12c before you make any commitment or provide estimates.


1> Only data source and EMS can be migrated in BAM 12c

Oracle has published a very nice document on how to upgrade these artifacts

http://www.oracle.com/technetwork/middleware/bam/learnmore/bam11g-12cmigration-2389379.pdf


2> BAM reports is no longer existing in BAM 12c. We have a dashboard now.

So all the BAM reports now needs to be recreated in BAM dashboard.
This again involves a lot of steps as now we have Business query-->Business View and then dashboard.

3> ALerts can also be not migrated as alerts might have reference to BAM 11g report and now in BAM 12c we can send the BAM dashboard link.


4> Most important BAM 12c has lot of bugs

Batch parameter does not work

Null parameter can not be inserted in BAM

parameter does not show up in business query.

Further a lot of patch needs to be applied in the BAM 12c.

So make sure you are taking more than enough buffer time for the development.

BAM 12c needs to be more stabilized.

Getting issue in JDeveloper 12c while creating a connection with BAM server

I tried to create a connection to BAM server from JDeveloper 12c and i got below error



The reason for this error was that i was using JDK 1.8 and after i changed my JDK to 1.7 it worked fine.

There are some patches that needs to be applied on Jdeveloper and you can eaily get the list of

patches from Metalink