En vrac

Oracle Ensemble is a product which allows to build composite application from existing content. It falls into the category of mashup softwares , ans it’s included in the Oracle WebCenter Suite package. In the following exemple, we use it for injecting some web content from a blog site (realized with Wordpress ) into a Content System home page (provided by Typolight ). The goal, in our exemple, is to catch the list of categories (surrounded by the red line) and inject this fragment in the target application which is a site dedicated to a music academy This is the page generated by the CMS for a sample site. We want to amend this page, without modifying the original code First, it’s important to understand that Oracle Ensemble acts as a reverse proxy , and we need to call the target application through the proxy. We defined a new resource in the Ensemble Console, by mapping the internal URL with a new external one. ie: internal URL: http://localhost/typo External URL: http://l

In some situations, a FQDN (Fully Qualified Domain Name) machine can lead to problems after a fresh install of Oracle Webcenter Ensemble, when accessing to Admin console http://mymachine:20070/ensembleadminui/run/ensemble.faces The problems occurs on Windows XP or 2003 machines. Version of ensemble wich is concerned: 10.3.0j.0 and above In this case, have a look to the log into: <HOME_DIR>\ensembleadminui\10.3.0\wrapper.log If you get an error as following …<1.0.0-SNAPSHOT-SNAPSHOT nonfatal store error> kodo.jdo.DataStoreException: Syntax error: Encountered ")" at line 1, column 176. {SELECT t0.DOMN, t0.REALMN, t0.NAME, t1.URI FROM BEASAML2_SPPARTNER t0, BEASAML2_SP_AUDIENCEURI t1 WHERE (t0.DOMN = ? AND t0.REALMN = ? AND t0.NAME = ?) AND t0.DOMN = t1.DOMN(+) AND t0.REALMN = t1.REALMN(+) AND t0.NAME = t1.PARTNER_NAME(+) ORDER BY t0.DOMN ASC, t0.REALMN ASC, t0.NAME ASC} [code=-1, state=42X01…. then replace the FQDN by localhost into: <HOME_DIR>\settings

Using parameters with OmniPortlet within WebCenter Spaces is quite simple. The documentation about this feature is well done but an exemple will be useful. Version used : Oracle WebCenter 11g R1 (11.1.1.2) Let’s suppose we want filter a report with a specific currency setup at the page level. This is the original report. All the currencies are mixed First, we add a new parameter at the page level. Let’s name it pdevise and give a default value: EUR. Then, we add a filter at the Omniportlet definition level. In the second tab, we enter a new condition and the name of formal parameter, inside : ##Param1## The report is empty because the parameter Param1 is not wired. This is the last step: Wiring Param1 with the previous Page parameter pdevise . We must edit the component properties for the omniportlet (the yellow pen close to the view action menu icon) Finally, the report is displayed with the currency given at page level.