In my previous post I created the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. In this post I will configure Oracle Identity Directory (OID) and extend this domain with OID. Furthermore I will seed the Identity Store and Policy Store with data to be used by Oracle Access Manager.

As of August 15, 2011 Oracle PartnerNetwork provided hundreds of Oracle Fusion Applications self-paced learning assets to partners!

Yes, it is true, with this Oracle has shown to be commited to deliver Fusion Applications as a serious part of the Oracle stack and not just a hype as many skeptics would like to position a Apps wich they have not seen yet.

Fusion Learning Center can be accessed through the following link.

Way to go Oracle!

In my previous post I had configure Oracle HTTP server and an Apache LoadBalancer to handle all HTTP(s) traphic for IDM. In this post I will create the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. Later on we will extend this domain by adding Oracle Fusion Middleware components such as Oracle Identity Manager and Oracle Access Manager. Furthermore in this post we will configure Oracle HTTP server to handle HTTP(s) traphic for the Administration Server and Enterprise Manager through the loadbalancer.

In my previous post, I installed the components for IDM. In this post I will describe the steps to configure Oracle Web Tier.

Oracle Web Tier comprises of two components:

• Oracle Web Cache

A content-aware server accelerator, secure reverse proxy server that improves the performance, scalability, and availability of web sites

•  Oracle HTTP Server

Apache based web server that provides a HTTP listener for Oracle WebLogic Server and the framework for hosting static pages, dynamic pages, and applications over the web and includes all base Apache modules and modules developed specifically by Oracle.

In this post we will configure Oracle HTTP Server.

You can write the output of a PS Query to Excel simply by hitting the appropiate link:

You can also schedule the query and send an email. The email will then contain a link. When hitting the link the user is routed to the stdout-page of the process PSQUERY where he can hit the link to view the output if the query results in Excel.

Nevertheless it is possible that your client want to receive the Excel Sheet itself by mail, rather then an email with a link to a page with another link.

The problem could be solved by some simple lines of peoplecode in an application engine, in which a query is opened with the name: ”KP_AFWIJKENDE_ROLLEN”:

Local ApiObject &aRunQry;

&aRunQry = %Session.GetQuery();
If (&aRunQry.Open(“KP_AFWIJKENDE_ROLLEN”, True, False) <> 0) Then
   MessageBox(0, “”, 0, 0, “Error in opening query”);
Else
   If (&aRunQry.RunToFile(&aQryPromptRec, &aRunQry.Name, %Query_XLS, 0) = 0) Then
      MessageBox(0, “”, 0, 0, “Resultset saved into file successfully.”);
   Else
      MessageBox(0, “”, 0, 0, “Failed to save Resultset into file.”);
   End-If;
End-If;

On the application server appears a file KP_AFWIJKENDE_ROLLEN.xls, that you can send by sendmail. You could also include runtime parameters, that could be passed to the query.

The same method could also be used for writing all other output of an app. engine to an Excel Sheet as well. Much more elegant than a CSV I would say.