With PeopleTools you have the ability to create pagelets using the Pagelet Wizard. Pagelet Wizard pagelets, also known to the rest of the world as portlets, are small pages that provide display-only snapshots of applicable content which can be placed on the PeopleSoft Homepage. With the Pagelet Wizard you can create a variety of pagelets:

• HTML
• IB Connector
• Integration Broker
• Navigation Collections
• OBIEE Report
• PeopleSoft Query
• Rowset
• Search record
• URL

This post describes how you can get more control in formatting and setting up your HTML pagelets.

On 22 may 2011 Oracle released Oracle Fusion Applications R1 Beta version and was available for download from eDelivery. Yesterday (04 october 2011 ) at Oracle Open World 2011, Oracle announced general availibilty of Oracle Fusion Applications. This final version is now also available for download from eDelivery.

So what has changed from Beta to Final?

As a Peoplesoft developer (working with Peopletools-release 8.47.08), I have spent quite some time resolving issues caused by unexpected database-commits. As far a I know there’s no overall topic on this in Peoplebooks, therefore I will share my experience via this blog.

1) Database-updates via DML in a SQLExec-statement (e.g. INSERT INTO PS_TEST_TABLE VALUES(‘value_field_1′,’value_field_2′), triggered via an online component:
Peoplebooks states that DML in a SQLExec-statement is only allowed in FieldChange, SavePreChange, Workflow and SavePostChange events.
There’s a big difference in the outcome per event though; when this statement is put in a FieldChange-event, the DML is committed instantly, and this is something you probably don’t want!

2) Database-updates via DML in a SQLExec-statement (e.g. INSERT INTO PS_TEST_TABLE VALUES(‘value_field_1′,’value_field_2′), triggered via an Application Engine:
These updates are being committed according the AppEngine’s commit-settings.

2) Database-updates via a component interface, triggered via an online component (e.g. component A triggers component interface B_CI, triggering component B):
These updates are being committed as soon as the CI save-method is being invoked from the calling component (e.g. component A).

3) Database-updates via a component interface, triggered via an Application Engine (eg. AppEngine AE_1 triggers component interface B_CI, triggering component B):
These updates are being committed according the AppEngine’s commit-settings.
An exception to this rule I just recently encountered: the GetFile-statement leads to an immediate commit, even when used in an AppEngine-context!

In my previous post I described the steps needed to configure Oracle Virtual Directory for virtualizing LDAP. In this post I will describe the steps that need to be taken to configure Oracle Access Manager and Webgate.

Oracle Access Manager allows users to seamlessly gain access to web applications and other IT resources across the enterprise deployments. It provides a centralized and automated single sign-on solution. It also contains an authorization engine, which grants or denies access to particular resources based on properties of the user requesting access as well as based on the environment from which the request is made.

Oracle Access Manager consists of various components including Access Server, Identity Server, WebPass, Policy Manager, WebGates, AccessGates, and Access SDK. The Access Server and Identity Server are the server components necessary to serve user requests for access to enterprise resources. WebGates are web server agents that act as the actual enforcement points for Oracle Access Manager.

In my previous post, ODSM was configured to manage OID. In the post I will describe the steps you need to take to configure Oracle Virtual Directory (OVD) and create a connection in ODSM to manage OVD.

Oracle Virtual Directory is an LDAP version 3 enabled service that provides virtualized abstraction of one or more enterprise data sources into a single directory view. Oracle Virtual Directory provides the ability to integrate LDAP-aware applications into diverse directory environments while minimizing or eliminating the need to change either the infrastructure or the applications. Oracle Virtual Directory supports a diverse set of clients, such as Web Applications and portals, and it can connect to directories, databases and Web Services.