En vrac

in a fresh install of Oracle WebCenter, the OmniPortlet is deployed but not registered as a portlet producer. As mentioned in the documentation, it’s needed to do some extra setup either with the Fusion Middleware Control or with a WLST script. This post explains how to use the first option. Let’s suppose that the administration port is : 7001. Use a web browser for connecting to the Fusion Middleware control (Remark: it’s not the WebLogic console !) http:<hostname>:7001/em Connect as weblogic (or an account with administrative privileges) Choose Register Producer option in the WebCenter menu In the URL endpoint field, enter: http://<hostname>:7001/portalTools/omniPortlet/providers/omniPortlet In most of case, it will be useful to restart all webCenter, in order to see the new portlet displayed in the catalog (under Portlets folder) In order to  see the already registered portlets, choose Service Configuration

REST Apis are available with Oracle WebCenter R1 PS1 (Nov 2009). This post gives informations for installing samples on an existing WebCenter plateform. REST Samples which are provided on otn site can be installed either with Apache, or with WebLogic Server directly. Setup For Apache To avoid cross site scripting errors, you should proxy URL access to the REST service:   http://<hostname>:<WLSport>/rest/api/resourceIndex On Apache or Oracle HTTP Server Depending the current configuration of apache2.conf, it will be needed to setup the Proxy mod by updating the httpd.conf file, and by adding directives for proxying the target url dedicated to REST. In the lines below, replace the port 7001 by the port used by WLS. Modify httpd.conf by adding the following lines: LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so LoadModule proxy_balancer_module /usr/lib/apache2/modules/mod_proxy_balancer

This script is intended to those who use the Vmware WebCenter machine provided by Emiliano P. and need to use sqlplus or imp/exp modules. First, create a new file db.env in /home/wc directory, and add the following lines: #!/bin/bash # # description:  Environnement for SGBD # # change log: #       Pmonaco 09 Feb 2010 -  Creation # # Save LD_LIBRARY_PATH SAVE_LLP=$LD_LIBRARY_PATH ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server ORACLE_OWNER=oracle ORACLE_SID=XE LD_LIBRARY_PATH=$ORACLE_HOME/lib export ORACLE_HOME export LD_LIBRARY_PATH export ORACLE_SID export PATH=$ORACLE_HOME/bin:$PATH export NLS_LANG=American_America.AL32UTF8 Give execute permisions do db.env file: chmod +x db.env Then source the above file with the following command line : . ./db.env As from this point, it’s possible to use sqlplus or imp/exp executables.