C Business Mashup Examples

C.1.1 Creating a Graph to Display Page Hits

To create a graph that displays statistics for pages in your application:

1. Create a SQL data control, PageStats, using the ActivitiesDS connection. Specify the following SQL query and bind parameters:

   Query:

   SELECT space.name_ spaceName, page.name_ pageName, space.id, page.id, count(1), 
   fact.page_, page.resourceid_ FROM asfact_wc_pagevie_0 fact , 
   asdim_wc_groupsp_0 space , asdim_wc_pages_0 page, asdim_wc_applica_0 app 
   WHERE space.id = fact.groupspace_ and page.id = fact.page_ and app.id = 
   fact.application_ and fact.occurred between to_date(:startdate, :dateformat) 
   and to_date(:enddate, :dateformat) and app.name_ = :appname and page.personal_ 
   = :ispersonal and space.name_ is not null and page.name_ is not null and 
   space.id is not null and page.id is not null
   and fact.page_ is not null and page.resourceid_ is not null GROUP BY 
   space.name_, page.name_, space.id, page.id, fact.page_, page.resourceid_ ORDER BY count(1) desc
   

   Bind Parameters:

   startdate - 01/01/2008

   dateformat - MM/DD/YYYY

   appname - webcenter

   ispersonal - 1

   enddate - 01/01/2011

   For the detailed steps, see Section 25.2.1.2, "Creating the Data Control."

2. Expose the data control in the Resource Catalog by selecting Show from the Edit menu.

3. Create a task flow, Page Hits, based on the blank mashup style.

   For detailed steps, see Section 25.3.1, "Creating a Task Flow."

4. Edit the task flow, click Add Content, and in the catalog, locate the PageStats data control and drill down to the Analytics_PageViews_DC accessor.

5. Add the accessor as a graph. In the Create Graph dialog, select the following options:

   • Select the Bar graph type.

   • On the Placement page, select the Space Name, Page Name and Page ID data columns to be mapped along the X-axis, and Count to be mapped as Bars.

   • Accept the default values on all other pages of the dialog.

   For the detailed steps, see Section 25.4.1.3, "Adding a Data Control as a Graph."

   The graph is displayed as shown in Figure C-1.

   Figure C-1 Bar Graph Displaying Page Hits

   
   

C.1.2 Using a Parameterized Task Flow to Display a Graph of Page Hits in a Space

In the previous example, you saw how to view page hits in your WebCenter Spaces application. This section describes a similar example, but with the ability to display page hits for a specific Space only. In this case, the data control is added as a graph to a parameter form task flow. The input parameter allows users to specify a Space name and display statistics for that Space in the graph. This section includes the following subsections:

• Section C.1.2.1, "Creating the Page Hits Data Conrtol"

• Section C.1.2.2, "Creating a Custom Mashup Style with a Parameter to Specify the Space Name"

• Section C.1.2.3, "Creating a Task Flow Using the Custom Mashup Style"

• Section C.1.2.4, "Consuming the Data Control in the Task Flow"

C.1.2.3 Creating a Task Flow Using the Custom Mashup Style

In the Resource Manager, create a task flow, Top Five Page Hits for a Space, based on the new mashup style, as shown in Figure C-3.

Figure C-3 Create New Task Flow Dialog Displaying the New Mashup Style

For the detailed steps, see Section 25.3.1, "Creating a Task Flow."

From the Edit menu, select Show to include the task flow in the Resource Catalog.

C.1.3 Creating a Graph to View Portal Site Traffic

This section explains how to retrieve the site traffic data from the Analytics service and display it as a Pie graph.

To create a mashup with the portal site traffic data:

1. Create a SQL data control, PortalStats, using the ActivitiesDS connection. Specify the following SQL query and bind parameters:

   Query:

   SELECT 'Spaces' Name, count(1) Hits
   FROM asfact_wc_groupsp_0 fact , asdim_wc_groupsp_0 space , asdim_wc_applica_0 app
   WHERE space.id = fact.groupspace_ and app.id = fact.application_ and fact.occurred between
   to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and 
   app.name_ = :appname and
   space.personal_ = :ispersonal
   UNION ALL
   SELECT 'Pages' Name, count(1) Hits
   FROM asfact_wc_pagevie_0 fact , asdim_wc_pages_0 page , asdim_wc_applica_0 app
   WHERE page.id = fact.page_ and app.id = fact.application_ and fact.occurred
   between
   to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and
   app.name_ = :appname and
   page.personal_ = :ispersonal
   UNION ALL
   SELECT 'Portlets' Name, count(1) Hits
   FROM asfact_wc_portlet_0 fact , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate,
   :dateformat) and
   to_date(:enddate, :dateformat) and app.name_ = :appname
   UNION ALL
   SELECT 'Logins' Name, count(1) Hits
   FROM asfact_wc_logins_0 fact , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate,
   :dateformat) and
   to_date(:enddate, :dateformat) and app.name_ = :appname
   UNION ALL
   SELECT 'Searches' Name, count(1) Hits
   FROM asfact_wc_searche_0 fact , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate,
   :dateformat) and
   to_date(:enddate, :dateformat) and app.name_ = :appname
   UNION ALL
   SELECT 'Wikis' Name, count(1) Hits
   FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred
   between
   to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and
   app.name_ = :appname and
   doc.objecttype_ like '%WIKI%'
   UNION ALL
   SELECT 'Blogs' Name, count(1) Hits
   FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred
   between
   to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and
   app.name_ = :appname and
   doc.objecttype_ like '%BLOG%'
   UNION ALL
   SELECT 'Documents' Name, count(1) Hits
   FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred
   between
   to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and
   app.name_ = :appname and
   doc.objecttype_ like '%DOCUMENT%'
   UNION ALL
   SELECT 'Discussions' Name, count(1) Hits
   FROM asfact_wc_discuss_1 fact , asdim_wc_applica_0 app
   WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate,
   :dateformat) and
   to_date(:enddate, :dateformat) and app.name_ = :appname
   

   Bind Parameters:

   startdate - 01/01/2008

   dateformat - MM/DD/YYYY

   appname - webcenter

   ispersonal - 1

   enddate - 01/01/2011

   For the detailed steps, see Section 25.2.1.2, "Creating the Data Control."

2. Expose the data control in the Resource Catalog by selecting Show from the Edit menu.

3. Create a task flow, Portal Traffic, based on the blank mashup style.

   For detailed steps, see Section 25.3.1, "Creating a Task Flow."

4. Edit the task flow, click Add Content, and in the catalog, locate the PortalStats data control and drill down to the Site_Traffic_DC accessor.

5. Add the accessor as a graph. In the Create Graph dialog, select the following options:

   • Select the Pie graph type.

   • On the Placement page, select Name data column to be plotted as slices and Hits as the pie.

   • Accept the default values on all other pages of the dialog.

   For the detailed steps, see Section 25.4.1.3, "Adding a Data Control as a Graph."

   The graph is displayed as shown in Figure C-6.

   Figure C-6 Graph Displaying Portal Traffic Statistics

   
   

C.1.4 Creating a Mashup with Two Task Flows in a Master-Detail Relationship

This example describes how to wire two task flows in a master-detail relationship such that a selection in one task flow results in an action on the second one. This section illustrates how to do the following:

• Create a master task flow that displays page hits in a table.

• Hyperlink the user names column in the table.

• Create a details task flow that displays a graph of top five page hits for a user.

• On clicking a user name in the master, display the details task flow in a popup window.

C.2.1 Creating the SQL Data Control

Perform the following tasks to create a data control for the employee database:

1. Create a connection to the employee database. For the detailed steps, see Section 25.2.1.1, "Creating a Database Connection."

2. Create a SQL data control, EmpDetails, to retrieve data using this database connection. Use the following query to retrieve data:

   select ename, empno, mgr, deptno from emp where job in (:jobId) order by empno asc
   

   For the detailed steps, see Section 25.2.1.2, "Creating the Data Control."

   This data control returns records for all employees whose designation matches the value of jobId. The records are sorted by employee number.

3. Create a task flow, Employee Details, based on the Blank mashup style. For the detailed steps, see Section 25.3.1, "Creating a Task Flow."

C.2.2 Adding the Data Control and Binding Task Flow Parameters to Data Control Parameters

Perform the following steps to add the data control as a table:

1. Edit the Employee Details task flow in Oracle Composer.

2. In the Add Content dialog, navigate to the EmpDetails data control's accessor, click Add, and select Table, as shown in Figure C-12.

   Figure C-12 Employee Details Data Control Accessor

   
   Description of "Figure C-12 Employee Details Data Control Accessor"
   
   

3. Create an editable table, enable row selection, filtering and sorting, and select columns ename, empno, and deptno to be displayed in the table.

   For the detailed steps, see Section 25.4.1.1, "Adding a Data Control as a Table."

   The table displays with an empty field at the top of each column, as shown in Figure C-13. You can use those fields to specify filter criteria for the columns.

   Figure C-13 Table in the Employee Details Task Flow

   
   Description of "Figure C-13 Table in the Employee Details Task Flow"
   
   

4. Create a task flow parameter, designation.

   For the detailed steps, see Section 25.4.2, "Creating Task Flow Parameters."

5. To use the designation parameter to drive the data displayed in the table, copy the storage value of the parameter, #{pageFlowScope.designation}, and paste it as the value for the bind variable, jobId, on the Data tab of the table's Component Properties dialog.

   For the detailed steps, see Section 25.4.3, "Binding Data Control Parameters to Task Flow Parameters."

6. Create a page and add the Employee Details task flow to the page.

   For the detailed steps, see Section 25.4.5, "Consuming Task Flows that Contain Visualizations."

7. Edit the Employee Details task flow on the page, and on the Parameters tab, specify a designation to view corresponding details in the table.

C.2.3 Showing a Hidden Column in the Table

In your SQL query, you specified that the data control must retrieve the columns ename, empno, deptno, and mgr. However, you chose to display only the ename, empno, and deptno columns. In this case, the data control retrieves data from all four data columns, but displays only three. You can render the fourth column in the table but editing the table's source code. To do this:

1. On the Resource Manager - Task Flows page, select the Employee Details task flow.

2. Click Edit Source, then the Fragments tab, and locate the code for the hidden column. It would be similar to the code in the following example:

   <column sortProperty="MGR" filterable="true" sortable="true"
           headerText="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.label}" 
           id="column4" rendered="false">
     <af:inputText value="#{row.bindings.MGR.inputValue}"
                   label="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.label}"
                   required="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.mandatory}"
                   columns="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.displayWidth}"
                   maximumLength="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.precision}" 
                   shortDesc="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.tooltip}" 
                   id="inputText4">
       <f:validator binding="#{row.bindings.MGR.validator}"/>
       <af:convertNumber groupingUsed="false" pattern="#{bindings.accessor_gsrf2d136f7_d907_481d_ad3a_eb2b9dbe7c35.hints.MGR.format}"
                      id="convertNumber3"/>
     </af:inputText>
   </column>
   

3. Set the rendered attribute to true.

   The table now displays all four columns, as shown in Figure C-14.

   Figure C-14 Table Displaying Four Columns

   
   Description of "Figure C-14 Table Displaying Four Columns"
   
   

Similarly, you can hide a visible column by setting its rendered attribute to false.

C.2.4 Adding the Data Control in a Parameter Form Task Flow

The Parameter Form task flow provides an input text field where a user can specify a value. This value is passed to a data control accessor parameter so that the accessor displays data based on the user input.

You can add a data control as a table inside a Parameter Form task flow so that users can specify a value in the field to view corresponding details in the table.

To add a data control inside a Parameter Form task flow:

1. Create a task flow based on the Parameter Form mashup style.

   For the detailed steps, see Section 25.3.1, "Creating a Task Flow."

2. Edit the task flow in Oracle Composer and add the EmpDetails data control as a table inside the task flow.

   For the steps, see Section C.2.2, "Adding the Data Control and Binding Task Flow Parameters to Data Control Parameters."

3. Wire the jobId parameter on the data control to the Input Text component in the Parameter Form task flow, by specifying the jobId value to be #{pageFlowScope.bindVarId}.

   For detailed steps, see Section 25.4.4, "Wiring a Data Control to a Parameter Form Task Flow."

You can now specify a value in the input text field to view the corresponding records in the table, as shown in Figure C-15.

Figure C-15 Data Control in a Parameter Form Task Flow

Description of "Figure C-15 Data Control in a Parameter Form Task Flow"

C.3.1 Creating the Data Control

Create a data control, WebCenter Pages, to retrieve page-related data from the WebCenter Spaces data source. Use the mds-SpacesDS connection and enter the following SQL query:

select 'Home Space Pages' metric, count(*) value from mds_paths where path_type = 'DOCUMENT'
and path_name like '%.jspx' and path_high_cn is null and path_fullname like '%/user/%'
union select 'Business Role Pages' metric, count(*) value  from mds_paths where path_type = 'DOCUMENT'
and path_name like '%.jspx' and path_high_cn is null and path_fullname like '%/businessRolePages/%'
union select 'Space Template Pages' metric, count(*) value from mds_paths where path_type = 'DOCUMENT'
and path_name like '%.jspx' and path_high_cn is null and path_fullname like '%/spacetemplate/%'
union select 'Group Space Pages' metric, count(*) value from mds_paths where path_type = 'DOCUMENT'
and path_name like '%.jspx' and path_high_cn is null and (path_fullname not like '%/user/%'
and path_fullname not like '%/businessRolePages/%' and path_fullname not like '%/spacetemplate/%')

This query retrieves information about the different type of pages and the count of each page type, as shown in Figure C-16.

Figure C-16 Data Control with Page Information from the WebCenter Spaces Repository

Description of "Figure C-16 Data Control with Page Information from the WebCenter Spaces Repository"

This type of information can be represented either in a table or a graph. The following section describes how to add this data control as a graph.

C.3.2 Adding the Data Control as a Graph Inside a Task Flow

Create a blank task flow and add the data control as a Graph. Select the Pie graph type, and place the METRIC column as slices and the VALUE column as the Pie. The graph is added to the task flow as shown in

Figure C-17 Page Metrics Displayed as a Pie Graph

Description of "Figure C-17 Page Metrics Displayed as a Pie Graph"

C.4.1 Creating a Mashup to List the Spaces in the Application

This section describes how to create a mashup to display a list of Spaces. The Space names are displayed as hyperlinks so that a user can click a link to view the selected Space.

To create a data control and task flow to display the list of Spaces:

1. Create a Web Service data control, SpacesWS, (Figure C-18) using a WSDL URL with the appropriate machine name and port number, as shown in the following example:

   http://myserver.us.oracle.com:8888/webcenter/SpacesWebService?WSDL
   

   For the detailed steps, see Section 25.2.2.1, "Creating the Data Control."

   Figure C-18 WebCenter Spaces Web Service Data Control

   
   

2. On the OWSM Security page, apply the following additional policy, as shown in Figure C-19:

   oracle/wss11_saml_token_with_message_protection_client_policy
   

   Figure C-19 WebCenter Spaces Web Service Data Control - OWSM Security

   
   

3. Click Create.

4. Select the data control, and from the Edit menu, select Show.

5. Create a blank task flow, Spaces, to consume the data control.

   For the detailed steps, see Section 25.3.1, "Creating a Task Flow."

6. Edit the Spaces task flow and add the SpacesWS data control accessor as a table.

   For the detailed steps, see Section 25.4.1.1, "Adding a Data Control as a Table."

   To display the Space names as links, on the Columns page in the Create Table dialog, select Hyperlink in the Display As field. Then in the URL field (Figure C-20), specify the URL to which the Space name must be appended so that it opens the Space in a separate window, for example /spaces/#{row.item}.

   Figure C-20 Hyperlink Option on the Table Create - Columns Page

   
   

   The table displays as shown in Figure C-21

   Figure C-21 Mashup Displaying a List of Spaces

   
   

C.4.2 Creating a Mashup with a Form to Rename Spaces

This section references the SpacesWS Web Service data control created in the previous section and describes how to create a form that can be used to rename a given Space.

To create a custom form:

1. Create a task flow, Rename Space, using the Blank mashup style.

2. Edit the task flow and click Add Content.

3. Drill down to view the SpacesWS data control, and add the renameGroupSpace method.

4. Open the renameGroupSpace method and add arg1 and arg0 attributes as ADF Input Text w/Label, as shown in Figure C-22. This step adds two input text fields, where users can specify the old Space name and new Space name.

   Figure C-22 Options to Add renameGroupSpace Attributes

   
   

5. Save and close the task flow.

6. Change the labels for the input text fields:

   1. Select the task flow, and from the Edit menu, select Edit Source.

   2. Replace the label value for the first inputText component (#{bindings.arg0.hints.label}) to Old Space Name.

   3. Replace the label value for the second inputText component (#{bindings.arg1.hints.label}) to New Space Name.

   4. Click OK.

   The task flow now appears as shown in Figure C-23.

   Figure C-23 Task Flow to Change a Space Name

   
   

7. In the Resources Manager, select the task flow, and click Show from the Edit menu.

   You can now add this task flow to any page and provide the capability to change Space names.

C.5.1 Creating a Web Service Data Control

On the Resource Manager - Data Controls page, create a Web Service data control, CustData, using the WSDL for the Siebel Web Service.

For the detailed steps, see Section 25.2.2.1, "Creating the Data Control."

This example shows a connection to a Web Service that provides two methods, MyQueryById and MyInsertOrUpdate. MyQueryById takes a complex parameter, MyQueryById_Input, and MyInsertOrUpdate takes a parameter, MyInsertOrUpdate_Input. MyInsertOrUpdate_Input is an array parameter, which can be used to update multiple records in the table.

Expose the CustData data control in the Resource Catalog by selecting Show from the Edit menu.

C.5.2 Adding a Data Control Method as a Table to a Task Flow

To consume the CustData data control in a task flow:

1. On the Resource Manager - Task Flows page, create a task flow based on the Parameter Form style.

   For the detailed steps, see Section 25.3.1, "Creating a Task Flow."

2. Edit the task flow and click Add Content.

3. Locate the CustomerData data control and expand it to view its contents. Open MyQueryById, Return, then ListOfAccountInterface.

4. Add Account, shown in Figure C-24, as an editable table.

   Figure C-24 Table Option on the Account Method

   
   

5. In the Create Table dialog, select the columns to be displayed, as shown in Figure C-25.

   Figure C-25 Items Page in the Create Table Dialog

   
   

6. On the DC Parameters page of the wizard, from the context menu next to the MyQueryById_Input field, click Parameter Structure.

7. In the Parameters dialog, expand the complex parameter to view the PrimaryRowId parameter, specify the binding for this parameter as #{pageFlowScope.id}, as shown in Figure C-26, then click OK.

   Figure C-26 Parameters Dialog

   
   

8. Click Create.

   At this point, as the parameter passes a null value, the table displays all available records, as shown in Figure C-27.

   Figure C-27 Table Inside a Parameter Form Task Flow

   
   

9. As the table is inside a parameter form task flow, you must wire the task flow parameter to the data control parameter. To do this:

   1. From the View menu, select Source.

   2. In Source view, select the inputText component at the bottom of the page and click Edit on the toolbar.

   3. Change its Value attribute to #{pageFlowScope.id}, as shown in Figure C-28.

      Figure C-28 Component Properties Dialog for Input Text Field

      
      

   4. Click OK.

   5. Additionally, delete the commandButton component with the title GO.

      As an alternative to this button, you will learn how to use one of the Web Service methods to query the data source.

10. Switch back to Design mode of the page.

    As you deleted the GO button in the parameter form task flow, there is currently no way to query the data source from the task flow. Therefore, the next step is to add a Web Service method to query the data source.

C.5.3 Querying the Data Source

The Siebel Web Service in this example provides the MyQueryById method, which supports a single parameter, MyQueryById_Input. Add this method as a button to the task flow. As you already wired the MyQueryById_Input parameter to the task flow parameter in the previous step, the button is automatically wired to the task flow parameter.

To enable querying using the MyQueryById method:

1. Edit the task flow and click Add Content.

2. In the catalog, locate the CustData data control and expand it.

3. Add the MyQueryById method as an ADF Button.

   You can now specify an account ID in the parameter field to view details for that account in the table, as shown in Figure C-29.

   Figure C-29 Table and Query Button inside the Parameter Form Task Flow

   
   

C.5.4 Updating Data Source Records

If a data source allows writing into it, Web Service data controls provide array parameters to update multiple records simultaneously. The Siebel Web Service in this example allows writing back to the data source. It provides the MyInsertorUpdate_Input parameter, which is a complex parameter that can be used to populate multiple records at a time. This section describes how to use array parameters to update records in the table. Input Text fields added to the bottom of the page are used to update table columns.

To update records in the table:

1. Edit the task flow and click Add Content.

2. In the catalog, locate the CustData data control and expand it.

3. Add the MyInsertOrUpdate method as an ADF Button.

4. Switch to Source view of the page, select the new button, and click Edit to view its properties.

5. Click the Data tab, and from the context menu on the MyInsertOrUpdate_Input field, select Parameter Structure.

6. In the Parameter dialog, expand MyInsertOrUpdate_Input, ListOfAccountInterface, and Account.

   The Account parameter is an array type parameter and therefore displays an Add link.

7. In each row, define a bind parameter value for each column that you want to update, as shown in Figure C-30. For example, #{pageFlowScope.id1} and #{pageFlowScope.alias1} in the first row, and #{pageFlowScope.id2} and #{pageFlowScope.alias2} in the second row.

   Tip:

   To delete any of the columns you just added, leave the columns empty. Empty columns are deleted before passing the values back as Web Service parameter values.

   Figure C-30 Array Parameter Definition in the Parameter Dialog

   
   

8. You can update values for two rows, Account[0] and Account[1], by default. Click Add to add more rows.

9. Click OK in the Parameters dialog, then again in the Component Properties dialog.

10. Save and close the task flow.

11. To update values in the table, at the bottom of the page, add one Input Text field for each table cell that you want to update. To do this:

    1. Select the task flow in the Resource Manager and click Edit Source from the Edit menu.

    2. Copy the source code for the parameter form's inputText component and paste it four times.

    3. Change the id attribute value so that each ID is unique.

    4. Change the value attribute to contain the values you defined in the Parameters dialog in step 7, for example, #{pageFlowScope.id1}.

       Figure C-31 shows the source code for the new components.

       Figure C-31 Source Code of the New Input Text Components

       
       

12. Optionally, to organize the page components better, group the four inputText components in a Box component.

    The task flow is now wired to write back to the data source. Figure C-32 shows how the task flow appears. The first field is wired to the MyQueryById button and the remaining fields are used to provide values for the table. The new values are written to the data source when you click the MyInsertOrUpdate button.

    Figure C-32 Task Flow with a Table and Options to Query and Update

    
    Description of "Figure C-32 Task Flow with a Table and Options to Query and Update"
    
    

C.6.1 Building the Custom Mashup Style

As the Resource Manager does not provide a Create option on the Mashup Styles page, the only way to build a new mashup style is by copying an out-of-the-box mashup style and replacing its source code.

To build the custom mashup style:

1. Create a copy of the blank mashup style and name it PageHitsStyle.

2. Edit the source of PageHitsStyle and replace the code on the Fragment tab with the following:

   <?xml version='1.0' encoding='UTF-8'?>
   <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
             xmlns:pe="http://xmlns.oracle.com/adf/pageeditor"
             xmlns:cust="http://xmlns.oracle.com/adf/faces/customizable"
             xmlns:f="http://java.sun.com/jsf/core"
             xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
     <af:panelGroupLayout id="pgl1">
       <af:panelGroupLayout id="pg2" layout="horizontal" halign="center"
                            inlineStyle="padding-bottom:5px;">
         <af:inputText id="ip1" value="#{pageFlowScope.bindVarId}" label="Space Name" 
                       shortDesc="Enter A Space Name, by default it's all spaces"/>
         <af:commandButton text="#{dataComposerBundle.MASHUP_STYLES_GO}" id="cb1"/>
       </af:panelGroupLayout>
       <cust:panelCustomizable id="pc1">
         <table border="0" width="100%">
           <af:iterator id="i1" value="#{dataPresenter.dummyData.collectionModel}" var="row">
           <tr class="PortletText1">
             <td width="12px">
               <af:image id="img1" source="/adf/webcenter/star_sm_ena.png"/>
             </td>
             <td>
               <af:outputText id="otCol1" value="#{empty row.USERNAME ? '#{row.USERNAME}' : row.USERNAME}" 
                              inlineStyle="color:#333333; font-size:12px; font-weight:bold;"/>
               <af:spacer id="spacer1" width="5px"/>
               <af:outputText id="otCol2" value="viewed" inlineStyle="color:#333333; font-size:12px;"/>
               <af:spacer id="spacer2" width="5px"/>
               <af:goLink id="gl1" destination="{doc path pre fix}#{empty row.DOWNLOAD_URL ? '#{row.DOWNLOAD_URL}' : row.DOWNLOAD_URL}" 
                          targetFrame="_blank" text="#{empty row.DOCNAME ? '#{row.DOCNAME}' : row.DOCNAME}"/>
             </td>
           </tr>
           <tr>
             <td/>
             <td>
               <af:outputText id="otCol3" value="#{empty row.HITS? '#{row.HITS}' : row.HITS}" 
                              inlineStyle="color:#666666; font-size:12px;"/>
               <af:spacer id="spacer3" width="5px"/>
               <af:outputText id="otCol4" value="TIMES" inlineStyle="color:#666666; font-size:12px;"/>
               <af:spacer id="spacer4" width="5px"/>
               <af:outputText id="otCol5" value="in the last 7 days" inlineStyle="color:#333333; font-size:12px;"/>
             </td>
           </tr>
           <tr>
             <td/>
             <td>
               <af:outputText id="otCol6" value="Last Visit at " inlineStyle="color:#333333; font-size:12px;"/>
               <af:outputText id="otCol7" value="#{empty row.LASTVIEWED ? '#{row.LASTVIEWED}' : row.LASTVIEWED}" 
                              inlineStyle="color:#666666; font-size:12px;">
               <af:convertDateTime type="both"/>
               </af:outputText>
             </td>
           </tr>
           </af:iterator>
         </table>
       </cust:panelCustomizable>
     </af:panelGroupLayout>
   </jsp:root>
   

   where,

   #{pageFlowScope.bindVarId} is a reference that provides the input Space name

   #{dataPresenter.dummyData.collectionModel} is a dummy reference that gets replaced when you use the mashup style

   #{row.COLUMN} are placeholders that will reference data from data controls when the mashup style is used

   {doc path pre fix} is the prefix to be used for the document URL. To find the prefix for a document path, select a document on the Documents page and click Get a Link from the View menu. The first part of the Download URL (ending in path) is the prefix to be used. For example, http://my.company.com:8889/webcenter/content/conn/xyz18-ucm11g/path.

You can use this mashup style to build mashups that display page hits.

C.6.2 Creating a Task Flow Based on the Custom Style

This section describes how to use the PageHits mashup style to create a mashup that displays page hits in an Activity Stream layout. To illustrate this, you must create a SQL data control using the ActivitiesDS database connection, then consume the data control in a task flow based on the PageHits mashup style. However, to display the data from the data control in an Activity Stream layout instead of the typical table or graph layout, you must perform the following tasks:

• Create a SQL data control.

• Create a task flow based on the new PageHits mashup style.

• Add the data control as a table.

• Copy the data control's accessor ID from the table's properties.

• Hide the table.

• Wire the input text field in the task flow to the data control using the accessor ID.

To use the custom mashup style:

1. Creare a SQL data control, Top Five Viewed Documents in a Given Space, using the ActivitiesDS connection. Specify the following query:

   SELECT * FROM
   (SELECT users.userid  username, doc.name_  docname,doc.path_  download_url, count(1) hits,max(fact.occurred) lastviewed
   FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app,asdim_wc_groupsp_0 space , asdim_users users
   WHERE app.id = fact.application_
   AND app.name_ = 'webcenter' 
   AND fact.occurred BETWEEN (SYSDATE-7) AND SYSDATE
   AND fact.document_ = doc.id
   AND doc.name_ is not null 
   AND doc.id is not null 
   AND fact.document_ is not null 
   AND doc.resourceid_ is not null
   AND  fact.GROUPSPACE_ = space.id 
   AND  upper(space.name_) LIKE upper(:spacename) 
   AND space.name_ IS NOT NULL 
   AND fact.userid=users.id
   GROUP BY users.userid, doc.name_,doc.path_
   ORDER BY hits  DESC)
   WHERE rownum <= 5
   ORDER BY rownum 
   

   See Also:

   Section C.1.2.1, "Creating the Page Hits Data Conrtol"

2. Set the spacename bind parameter value to Home Space.

3. Select the data control in the Resources Manager and click Show on the Edit menu.

4. Create a task flow, Top Five Viewed Documents in a Given Space, using the PageHits mashup style, as shown in Figure C-33.

   Figure C-33 Create New Task Flow Dialog with PageHits Style

   
   

5. Edit the task flow and add the data control as a table, as shown in Figure C-34.

   Figure C-34 Top Five Viewed Documents in a Given Space

   
   

   Create a read-only table, and accept the defaults on Items and Columns pages of the Create Table dialog.

   On the DC Parameters page, specify the following as the parameter value for spacename:

   #{empty pageFlowScope.bindVarId ? '%' : pageFlowScope.bindVarId}

6. To get the accessor ID:

   1. Switch to Source view of the task flow, and select the Table component.

   2. Click Edit to view the table's properties.

   3. In the Component Properties dialog, copy the value of the Value attribute. This is the accessor ID for the data control. The value may be as shown in the following example:

      #{bindings.accessor_gsraffebf20_b500_480f_bf92_a9d33922a0a7.collectionModel}

7. Select the showDetailFrame component wrapping the table and click Hide on the context menu.

8. Right-click the iterator component, and click Edit.

9. Replace the value in the Value attribute with the accessor ID you copied from the table's properties.

   You now have a task flow with the Activity Stream-like seeded layout.

10. Save the task flow and exit Oracle Composer.

11. In the Resources Manager, select the task flow and click Show on the Edit menu.

12. Consume the task flow in a page. It appears as shown in Figure C-35.

    Figure C-35 Page Displaying Top Five Page Hits in a Space