Accéder au contenu principal

Oracle WebCenter Spaces Governance

 

Oracle WebCenter Space allows creation of Collaboratives areas. As it’s very easy to create a WorkSpace, it’s common to observe a workspace proliferation. So, it can be useful to check  the activity inside each of Spacers, and decide if it has to be archived depending the audience.

This post explains how to setup a very simple diagram which provides, inside WebCenter Space, an overall activity statistics for a given Workspace.The idea relies on the fact that activity is recorded in database Table.

Prerequisites

  • Oracle WebCenter Spaces is already installed
  • The schema which contains Spaces metadata is : DEV_WEBCENTER (or an other name) and the password must be known.

Steps

  • Create the following objects in DEV_WEBCENTER schema, with sqlplus or a similar tool

create type ext_array as table of number;

create function
  ext_gen_numbers(n in number default null)
  return ext_array
  PIPELINED
  as
  begin
     for i in 1 .. nvl(n,999999999)
     loop
         pipe row(i);
     end loop;
     return;
  end;

  • Create a diagramm with omniportlet tool (it’s a generic portlet which allows to create diagrams or lists based on SQL statements, XML, etc)

Along the wizzard, choose a SQL source, then enter the following statement:

select to_char(B.ti,'Month YY') month, nvl(A.nb,0) nb from (
select trunc(activity_time,'MONTH') ti, count(*) nb
from WC_SPACE_HEADER S,
WC_AS_ACTIVITY_ELEMENT A
where S.DISPLAY_NAME='ODrink'
group by trunc(activity_time,'MONTH')
) A,
(
select add_months(trunc(sysdate,'MONTH'),-column_value+1) ti
  from TABLE(ext_gen_numbers(12))
) B
where A.ti(+) = B.ti
order by B.ti

In the Layout tab, choose Line displaying:

image

After validating, this is the result which can be easily obtained:

image

 

By instancing the omniportlet multiple time, one can setup a complet dashboard: The following SQL provides Page activity for all the spaces (only three in our sample, but it’s just a demo):

select display_name, count(*) nb
from WC_SPACE_HEADER S,
WC_AS_ACTIVITY_ELEMENT A
where A.SCOPE_ID = S.SPACE_GUID and
service_id like 'oracle.webcenter.page%'
group by display_name, service_id

image

 

Version: 1.1 19-Aug-2010

Commentaires

Posts les plus consultés de ce blog

Auschwitz

 Quelques livres à propos des camps d'Auschwitz La mort est mon métier (Robert Merle) - 1952 Roman avec Rudolf Hoess (responsable camps d'Auschwitz) comme personnage principal Si c'est un homme (Primo Levi) - 1947 Témoignage de Primo Levi sur sa captivité à Auschwitz Les médecins d'Auschwitz (Bruno Halioua) - 2022 Etude sur l'organisation des services de médecine à Auschwitz Je me suis évadé d'Auschwitz (Rudolf Vrba) - 2004 Récit d'un captif qui a réussi à s'échapper d'Auschwitz Shoah  (Claude Lanzmann) - 1985 Dialogues du film "Shoah" Sonderkommando : Dans l'enfer des chambres à gaz  (Shlomo Venezia ) Entretien avec un ancien prisonnier qui a tenu le rôle de sonderkommando (manipulation des corps dans les chambres à gaz) Auschwitz I Birkenau Birkenau

Oracle Documents Cloud Service - Using Upload File REST API

If the Upload File sample given in ODCS documentation is used "as is", we get a http 400 error. The syntax is strict and every blank line must be empty (no space character for instance). If we cust and paste the sample, there are residual space characters which must be removed. So, use this pattern instead: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID": " " } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain Hello World! -----1234567890-- instead the original one: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID":"FB4CD874EF94CD2CC1B60B72T0000000000100000001" } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain -----1234567890-- Tests can be...

Oracle Sites Cloud Service - Apps

It's possible to add kinds of widgets (named APPS) inside any page of a site built with Oracle Sites Cloud Service (SCS). Any app is materialized by two URL: a Renderer Url which will render any HTML fragment inside an iframe tag at runtime a settings url which will be rendrered at design time in the settings menu. all URLs must be called through https (meaning that the called server has to be ssl enabled) In the following samples, we integrate: a dummy app (a simple html page produced with node.js) which demonstrates the parameteres caried by the Sites Cloud engine when calling the backend server,  a regular Apex report or form,  a custom report which calls a rest api generated by Apex /ORDS Sample node.js server.js below is a sample of parameter values get from a dummy node.js server Main call id=26e45e21-dbb6-4877-9886-482b37213d2f instance=eyJpbnN0YW5jZWlkIjoiQTI0NUNFNUNFNjA5MjE1REZBRTA2RTQyRjExOThBNThFNzc4RDc5NzFDMkIiLCJzaWduZGF0ZSI6IjE0NTAxMDg1M...