Process Developer

Back Next

Reporting Service

Process Server supports a reporting service. This means that you can create a BPEL process that sends a request to the server to take a snapshot of a deployed report, save the report as PDF, MS Word, or other format, and return it to the process. You use an invoke activity for this purpose. Within your BPEL process, you provide programming logic to email the report, use it in a People activity, or send it to an endpoint based on an invoked service. You can schedule the process to run daily (or other frequency) to have a daily report emailed.

Any BPEL process that implements report-based activities imports the WSDL provided with Informatica Business Manager
. The name of the WSDL is

reporting.wsdl

, and its port type,

reportingPT

, is in the Participants
view in the New Partner Service Provider
wizard under System Services
. The WSDL contains a report
operation.

<invoke
    inputVariable="reportMessageInput"
    operation="report" 
    outputVariable="reportMessageOutput"
    partnerLink="Provider" />

To create a BPEL process that requests a report:

In the Project Explorer, create a new Orchestration project.

Select
File > New > BPEL Process
.

Name the process and click Finish
.

In the Participants view, select New Partner Service Provider.

In the wizard, select System Services.

Select Execute Report
, and select Finish
.

From Participants view, drag the report
operation to the canvas to create an invoke activity.

Fill in the Input values as described below.

Add the additional activities and programming logic to copy the report to an email, People activity, or other service.

Tip
: Use the attachment function,

setAttachmentProperty

, to give the report a meaningful name when it is attached to an email.

Add fault handling by using the WSDL fault message fault name

reportFault

and variable as desired.

On the Process Console, go to the URN Mappings page and update the URL for Internal Reports, if needed. The default is localhost:8080.

Input Message for Reporting Service

The input message for the invoke activity has the following parts, as shown in the example.

<ns2:reportMessageInput xmlns:ns2=
    "http://schemas.active-endpoints.com/reporting/2009/05/reporting.xsd">
   <ns2:report>ServiceActivityDetail.rptdesign</ns2:report>
   <ns2:format>pdf</ns2:format>
   <ns2:parameters>
     <ns2:param name="Service_Name" value="OrderProcessSvc"/>
   </ns2:parameters>
   <ns2:otherOptions>
     <ns2:option name="BIRT Parameter" value="true"/>
   </ns2:otherOptions>
</ns2:reportMessageInput>

Specify the input parameters for the invoke activity as follows.

<report>	(Required). Name of the report design template. This is a report deployed to Process Server. The report names are visible in the Process Console Catalog
<format>	(Required). Format of the generated report. Valid formats are: pdf (default) doc (Word) xls (Excel) ppt (Powerpoint) ps (postscript)
<parameters>	Each report can have its own set of parameters that are input to the report. For example, specify the name of a deployed service to get a report about one particular running process. Parameters for the standard reports are described below.
<otherOptions>	Options for producing the report. There are many options, and they are documented in the BIRT documentation. For details, here is a link. http://www.birt-exchange.org/devshare/deploying-birt-reports/492-birt-viewer-2-3-user-reference/#description

Reports and Their Parameters

You can use the reporting service to access your own custom reports or the Informatica Business Process Manager standard reports that are displayed in the Process Console.

In the Process Console, you can view a list of Informatica Business Process Developer report designs. You can then select a report design to name in the

element of the

reportMessageInput

variable.

To view a list of report design names, do the following:

Ensure that the server is running.

Open the Process Console.

Select Catalog > Resources > Report Definitions
.

In the Filters table, disable the check box for Hide System and select Submit.

Some of the reports have parameters, and you can use them in the

<ael:param name="string" value="string"/>

element of the

reportMessageInput

variable.

The following reports contain parameters and valid values.

Active Tasks

RP_State - (To see a complete list of states, go to the Active Tasks page of Process Console and select the Run Report button. In the RP_State picklist, you can view the 14 different states.)

RP_CreatedAfter - Date

RP_CreatedBefore - Date

RP_CompletedAfter - Date

RP_CompletedBefore - Date

RP_Name - String

RP_Owner - String

RP_SearchBy - String

RP_OwnerType - integer

RP_IdentityType - integer

RP_NamesText - String

Server Log

RP_LogLevel VERBOSE = 1, INFO = 5, WARNING = 6, ERROR = 7 CRITICAL = 8

RP_LogSource USER = 8, MAINTENANCE = 9 and SYSTEM = 10

RP_LogService ENGINE = 3, ALERT = 4, MESSAGING = 5, TASK = 6, VERBOSE = 7, EVENTING = 8, EMAIL = 9, IDENTITY = 10

RP_LogEngineId integer greater than or equal to 1

Rename Saved Search

Table of Contents

Process Developer

Process Developer

Reporting Service

Reporting Service