Accéder au contenu principal

Installing Oracle Pagelet Producer (AKA Ensemble) on Windows


This post summarizes the steps for installing Oracle Pagelet producer (AKA Ensemble) 11g PS6 (11.1.1.6) on a Windows 2008 R2 platform.
Oracle Pagelet Producer acts as a proxy and allows to get HTML fragment from an existing application for reuse it in a different context (a portal for instance, or for syndication purpose in a B2B context).
This module is included in Oracle Webcenter Portal, and can be used in a standalone mode with a completely different technology than Java.

Prerequisites


Download the following pieces of software:


Product
File to download
Size
Download Launchpad
Oracle Database 11g Standard Edition 11.2.0.1.0

2 G
RCU 11.1.1.6.0 for Windows
(Repository Creation Utility)

Developper la partie Prerequisites & Recommended Install Process, puis telecharger le fichier Repository Creation Utility For Windows
335 Mo
JDK 1.6.0.29+ (32 et 64bits)
et JDK 1.7.0_02+ (64 bits)

·         jdk-6u32-windows-x64
·         Jdk-7u4-windows-x64
·         jdk-6u32-windows-i586


WebLogic Server 11gR1 (10.3.6)

Choisir la version 10.3.6 Generic (dans la colonne Additional Platforms)
1 G
WebCenter Portal 11.1.1.6.0

Choisir « Windows » dans la dropBox. C’est en fait un fichier générique qui est téléchargé
1,8 G

Certification matrix for WebCenter 11.1.1.6.0

Installation


The installation process is time consuming but quite straightforward.

Install database
  Important: choose an UTF8 embedded database
  Modify the processes parameter to more than 200:
     alter system set processes=220 scope =spfile;
  Restart database in order to take in account the new value parameter
Run RCU tool rcu.bat)
  choose, at least, the prortlet provider schema
Install JDK 7
Install WLS
Install Webcenter Portal
  Choose, at least, Portlet provider and pagelet producer (if asked)
Run config.cmd
  Choose a new domain (base_domain) and pagelet producer

Start the product
  Start database
  Start WLS Admin Server
  Start Managed Server for pagelet producer (WC_Portlet)

Check the port number used for Pagelet Admin console
  http://:7001/em
  go to webecnter detail about the Pagelet prodcuer in order to get the port number
Login on the pagelet producer Admin Console
  http://:/pagelets/admin

Documentation Links:





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...