Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Reporting Service

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:
  1. In the Project Explorer, create a new Orchestration project.
  2. Select
    File > New > BPEL Process
    .
  3. Name the process and click
    Finish
    .
  4. In the Participants view, select New Partner Service Provider.
  5. In the wizard, select System Services.
  6. Select
    Execute Report
    , and select
    Finish
    .
  7. From Participants view, drag the
    report
    operation to the canvas to create an invoke activity.
  8. Fill in the Input values as described below.
  9. 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.
  10. 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
<report></report>
element of the
reportMessageInput
variable.
To view a list of report design names, do the following:
  1. Ensure that the server is running.
  2. Open the Process Console.
  3. Select
    Catalog > Resources > Report Definitions
    .
  4. 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


Updated March 30, 2020