WebMethods Monitor User's Guide
WebMethods Monitor User's Guide
Cerebra, Glue, Infravio X‐Broker, Infravio X‐Registry, Infravio, My webMethods Server, My webMethods, webMethods Access, webMethods Administrator,
webMethods Broker, webMethods Central Configuration, webMethods Dashboard, webMethods Designer, webMethods Developer, webMethods Fabric,
webMethods Glue, webMethods Infrastructure Data Collector, webMethods Infravio X‐Broker, webMethods Infravio X‐Registry, webMethods Installer,
webMethods Integration Server, webMethods logo, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor,
webMethods Optimize for Infrastructure, webMethods Optimize for Process, webMethods Optimize, webMethods Portal, webMethods Process Engine,
webMethods Servicenet, webMethods Task Engine, webMethods Trading Networks, webMethods Workflow, and webMethods are either registered
trademarks or trademarks of webMethods, Inc.
Acrobat, Acrobat, and Reader are registered trademarks of Adobe Systems Incorporated. Amdocs and ClarifyCRM are registered trademarks of Amdocs.
Ariba is a registered trademark of Ariba, Inc. BEA, BEA WebLogic Server, Jolt, and Tuxedo are registered trademarks, and BEA WebLogic Platform is a
trademark of BEA Systems, Inc. Action Request System, BMC Software, PATROL, and Remedy are registered trademarks of BMC Software, Inc. BroadVision
is a registered trademark of BroadVision, Inc. Chem eStandards and CIDX are trademarks of CIDX, The Chemical Industry Data Exchange. SiteMinder and
Unicenter are registered trademarks of CA, Inc. PopChart is a registered trademark of CORDA Technologies, Inc. Kenan and Arbor are registered trademarks
of Alcatel‐Lucent. Data Connection and SNAP‐IX are registered trademarks of Data Connection Corporation. D&B and D‐U‐N‐S are registered trademarks of
Dun & Bradstreet Corporation. Eclipse is a trademark of Eclipse Foundation, Inc. Entrust is a registered trademark of Entrust, Inc. papiNet is a registered
trademark of the European Union and the United States. Financial Information eXchange, F.I.X, and F.I.X Protocol are trademarks of FIX Protocol Ltd.
UCCnet and eBusinessReady are registered trademarks, and 1SYNC and Transora are trademarks of GS1 US. Hewlett‐Packard, HP, HP‐UX, OpenView, PA‐
RISC, and SNAplus2 are trademarks of Hewlett‐Packard Company. i2 is a registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, ClearCase, DB2,
Domino, IBM, Informix, Infoprint, Lotus, Lotus Notes, MQSeries, OS/390, OS/400, RACF, RS/6000, SQL/400, S/390, System/390, VTAM, and WebSphere, and
z/OS are registered trademarks; and Communications System for Windows NT, DB2 Universal Database, IMS, MVS, and SQL/DS are trademarks of IBM
Corporation. InnoDB is a trademark of Innobase Oy. Itanium is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus
Torvalds. W3C is a registered trademark, and X Window System is a trademark of the Massachusetts Institute of Technology. MetaSolv is a registered
trademark of Metasolv Software, Inc. ActiveX, Microsoft, Outlook, Visual Basic, Visual SourceSafe, Windows, Windows NT, and Windows Server are
registered trademarks of Microsoft Corporation. Six Sigma is a registered trademark of Motorola, Inc. Firefox and Mozilla are registered trademarks of the
Mozilla Foundation. MySQL is a registered trademark of MySQL AB. nCipher is a trademark of nCipher Corporation Ltd. Eclipse is a trademark of Eclipse
Foundation, Inc. Entrust is a registered trademark of Entrust, Inc. papiNet is a registered trademark of the European Union and the United States. Financial
Information eXchange, F.I.X, and F.I.X Protocol are trademarks of FIX Protocol Ltd. UCCnet and eBusinessReady are registered trademarks, and 1SYNC and
Transora are trademarks of GS1 US. Hewlett‐Packard, HP, HP‐UX, OpenView, PA‐RISC, and SNAplus2 are trademarks of Hewlett‐Packard Company. i2 is a
registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, ClearCase, DB2, Domino, IBM, Informix, Infoprint, Lotus, Lotus Notes, MQSeries, OS/390,
OS/400, RACF, RS/6000, SQL/400, S/390, System/390, VTAM, and WebSphere, and z/OS are registered trademarks; and Communications System for Windows
NT, DB2 Universal Database, IMS, MVS, and SQL/DS are trademarks of IBM Corporation. InnoDB is a trademark of Innobase Oy. Itanium is a registered
trademark of Intel Corporation. Teradata is a registered trademark of NCR Corporation. Netscape is a registered trademark of Netscape Communications
Corporation. ServletExec is a registered trademark, and New Atlanta is a trademark of New Atlanta Communications, LLC. SUSE is a registered trademark
of Novell, Inc. Appia is a registered trademark and Javelin Technologies is a trademark of NYFIX, Inc. CORBA is a registered trademark of Object
Management Group, Inc. JD Edwards, OneWorld, Oracle, PeopleSoft, Siebel, and Vantive are registered trademarks; and Infranet, PeopleSoft Pure Internet
Architecture, Portal, and WorldSoftware are trademarks of Oracle Corporation. Perforce is a trademark of Perforce Software. JBoss and Red Hat are
registered trademarks of Red Hat, Inc. PIP and RosettaNet are trademarks of RosettaNet, a non‐profit organization. SAP and R/3 are registered trademarks
of SAP AG. PVCS is a registered trademark of Serena Software, Inc. SWIFT and SWIFTNet are registered trademarks of Society for Worldwide Interbank
Financial Telecommunication SCRL. SPARC and SPARCStation are registered trademarks of SPARC International, Inc. BAAN and SSA are registered
trademarks; and SSA Global is a trademark of SSA Global Technologies, Inc. EJB, Enterprise JavaBeans, Java, JavaServer, JDBC, JSP, J2EE, Solaris, Sun, and
Sun Microsystems are registered trademarks; and Java Naming and Directory Interface, JavaServer Pages, SOAP with Attachments API for Java, and SunSoft
are trademarks of Sun Microsystems, Inc. Sybase is a registered trademark of Sybase, Inc. VERITAS is a registered trademark, and VERITAS Cluster Server is
a trademark of Symantec Corporation. UNIX is a registered trademark of The Open Group. Unicode is a trademark of Unicode, Inc. VeriSign is a registered
trademark of Verisign, Inc.
Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Copyright © 2007 webMethods, Inc. All rights reserved.
Copyright © 2007 Software AG and/or its suppliers, Uhlandstrasse 12, 64297 Darmstadt, Germany. All rights reserved.
Contents
Appendix A. Archive and Delete Audit Data Stored Procedures Reference . . . . . . . . . . . 133
Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
This guide describes how to set up and use webMethods Monitor to monitor business
processes, services, and documents. Additionally, it describes how to work with process
models that are in your production environment, how to generate reports for logged
process instances and tasks, and how to archive data from the IS Core Audit Log and
Process Audit Log database components. webMethods Monitor functions are accessed
through the My webMethods interface.
Document Conventions
Convention Description
Bold Identifies elements on a screen.
Italic Identifies variable information that you must supply or change
based on your specific situation or environment. Identifies terms the
first time they are defined in text. Also identifies service input and
output variables.
Narrow font Identifies storage locations for services on the webMethods
Integration Server using the convention folder.subfolder:service.
Typewriter Identifies characters and values that you must type exactly or
font messages that the system displays on the console.
UPPERCASE Identifies keyboard keys. Keys that you must press simultaneously
are joined with the “+” symbol.
\ Directory paths use the “\” directory delimiter unless the subject is
UNIX‐specific.
[ ] Optional keywords or values are enclosed in [ ]. Do not type the [ ]
symbols in your own code.
Additional Information
The webMethods Advantage Web site at http://advantage.webmethods.com provides you
with important sources of information about webMethods products:
Troubleshooting Information. The webMethods Knowledge Base provides
troubleshooting information for many webMethods products.
Documentation Feedback. To provide feedback on webMethods documentation, go to
the Documentation Feedback Form on the webMethods Bookshelf.
Additional Documentation. Starting with 7.0, you have the option of downloading the
documentation during product installation to a single directory called
“_documentation,” located by default under webMethods installation directory. In
addition, you can find documentation for all webMethods products on the
webMethods Bookshelf.
Producing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Integration Server
webMethods components log
Logging data to the logging database.
Utility audit
subsystem
Monitor
Optimize for Process Process via
logging database
Tracker My webMethods
In addition to simply viewing logged data for documents, using Monitor you can
resubmit documents, and optionally edit the document before resubmitting it. Similarly, if
you have services and business processes set up to log the pipeline data, you can also
resubmit those services and business processes; optionally you can alter the pipeline
before resubmitting them. For more information about the actions you can take, see
“Monitor Actions” on page 12.
You can also use Monitor to remove data from the IS Core Audit Log and Process Audit
Log database components. You can have Monitor do either of the following:
Move data from the IS Core Audit Log and Process Audit Log database components
to an Archive database component, which is outside of the webMethods logging
database, and then delete the data from the IS Core Audit Log and Process Audit Log
database components
Delete the data from the IS Core Audit Log and Process Audit Log database
components without archiving it first
For more information about archiving and deleting data from the logging database, see
Chapter 7, “Archiving or Deleting Logged Data”.
Track when process instance and step status changes
Track whether process instances and steps completed successfully or failed
View values of logged fields and custom data logged for steps in the process
View error messages associated with a process
View the control actions (e.g., resubmit) taken against a process
Analysis data that Optimize for Process logs for process instances. If you have Optimize for
Process installed, you can set up analysis of your processes. Then you can view
metrics that relate to your business processes, such as the average time to complete a
process or the number of times a step was executed.
Data that a user-created service logged for integration processes:
Identify process instances
Track the status of a process and its steps
View values of logged fields and custom data logged for steps in the process
View error messages associated with a process
For more information about logging, see the webMethods Logging Guide.
Monitor Actions
When you have Monitor installed, you can do the following using the My webMethods
user interface:
Monitor and resubmit services. For more information, see Chapter 3, “Service
Monitoring”.
Monitor and resubmit documents. For more information, see Chapter 4, “Document
Monitoring”.
Monitor, suspend, resume, and resubmit process instances. For more information, see
Chapter 5, “Process Monitoring”.
Enable process models and define settings that are used by running process instances
of the models. For more information, see Chapter 6, “Working with Process Models”.
Generate reports about process instances, process models, task users, and task roles.
For more information, see Chapter 8, “Working with Reports”.
Archive and delete data from the logging database. For more information, see
Chapter 7, “Archiving or Deleting Logged Data”.
Resubmit process instances, services, and documents
Work with process models
Generate reports for process instances, process models, task users, and task roles
Archive or delete logged data from the logging database
Using My webMethods administrative functions, Monitor administrators can control the
the Monitor privileges that users and groups of users have. Granting or denying Monitor
privileges is based on the My webMethods roles to which the users and/or groups of user
belong. Using My webMethods you can control access to:
The Monitor pages that a role can access within the My webMethods user interface. For
example, you can configure My webMethods so that specific roles can view pages
related to monitoring process instances, but not allow those roles to view pages
related to monitoring services. For more information, see “Granting Users Access to
the My webMethods Monitoring Pages” on page 25.
The Monitor actions a role can perform. For example, you can allow specific roles to view
logged data about documents, but not resubmit the documents. For more
information, see “Granting Users the Ability to Perform Monitor Actions” on page 27.
The specific logged data (i.e., specific business processes, services, or documents) upon which
a role can act. This is referred to as content‐based access or data level security. For example,
you can allow specific roles to act upon only logged data associated with services that
you identify. For more information, see “Identifying the Logged Data Users Can
Perform Actions Against” on page 30.
You create roles in My webMethods that include the users and/or groups of users to
which you want to grant access. For example, you might create the Human Resources
role, and then assign users and/or groups of users who work in the Human Resources
department to the Human Resources role. You can then grant the Human Resources role
access to view Monitor pages to view and resubmit process instances, and content‐based
access to only view and resubmit process instances that are used by the human resources
department.
For more information about the My webMethods user interface and its administrative
functions, see Getting Started with My webMethods and the My webMethods Server
Administrator’s Guide.
Important! You should change the default password (manage) for the Administrator user
account.
For more information about logging in and logging out of My webMethods, see the
Getting Started with My webMethods guide.
1 Open a Web browser and enter the URL for the My webMethods Server.
2 On the My webMethods Login page:
In the User Name box, type your user name, for example, Administrator.
In the Password box, type your password, for example, manage.
Important! Before using Monitor, it is required that you configure the Central Users feature.
This feature allows Monitor to perform actions on the Integration Server using existing
My webMethods user accounts. This precludes any need to duplicate your My
webMethods user accounts in the Integration Server. The Central Users feature will use
the users and groups created in My webMethods to determine permissions when
performing Monitor actions. For details, see “Configuring the Central Users Feature for
Monitor” on page 21.
Click Logout at the top of any My webMethods page.
Important! Functionality available via the My webMethods user interface is based on the
privileges assigned to your My webMethods roles. If you do not have all privileges, My
webMethods might not display pages, buttons, and/or other user interface controls
required to perform the actions describe in this guide. If a procedure instructs you to use
an item that is not available, see your system administrator about acquiring the proper
privileges to allow you to perform the action.
Administration
Navigation Selections Use to...
User Management Define users, groups, roles and control access to Monitor
privileges.
For more information about defining users, groups, and
roles, see the My webMethods Server Administrator’s Guide.
For more information about controlling access to Monitor
privileges, see:
“Granting Users Access to the My webMethods
Monitoring Pages” on page 25
“Granting Users the Ability to Perform Monitor
Actions” on page 27
“Identifying the Logged Data Users Can Perform
Actions Against” on page 30
Business > Enable process models for execution and define settings that
Business Processes are used by running process instances of the models. For
more information, see Chapter 6, “Working with Process
Models”.
Administration
Navigation Selections Use to...
Business > Archive and delete logged data from the IS Core Audit Log
Data Management > and Process Audit Log database components. You can also
Archive Audit Data view the results of the archive or delete operation. For more
information, see Chapter 7, “Archiving or Deleting Logged
Data”.
My webMethods > Identify the Integration Server with which the My
System Settings webMethods Server is to interact. This is the server on which:
The WmMonitor package is installed
Contains the services and Integration Server documents
you want to monitor
Runs the Process Engine that executes process instances
For more information, see “Configuring Integration Servers in
My webMethods” on page 23.
Monitoring Navigation
Selections Use to...
Business > View the details about individual process instances, including
Process Instances drilling down to view information about the steps within a
process. You can also use this link to suspend and resume
process instances. For more information about using this
functional task, see Chapter 5, “Process Monitoring”.
Integration > Services View logged data that Integration Servers have logged for
services and to resubmit services. For more information about
using this link, see Chapter 3, “Service Monitoring”.
Integration > Documents View and resubmit documents that have been logged to the
logging database. For more information about using this link,
see Chapter 4, “Document Monitoring”.
Monitoring Navigation
Selections Use to...
Reports > Generate aggregate reports on process instances, process
Process Instances models, task users, and task roles. For more information
about using this link, see Chapter 8, “Working with Reports”.
Reports >
Process Models
Reports >
Task Users
Reports >
Task Roles
Producing Reports
You can generate reports that show aggregated data about process instances and tasks
that have executed. Monitor generates the reports using the Staging and Reporting
database components. The Staging database component holds process status data that has
been extracted from the Process Audit Log database component. The data in the Staging
database component is aggregated into daily statistics and loaded into the Reporting
database component.
For instructions on setting up the Staging and Reporting database components, see
“Setting Up to Generate Reports” on page 35. For instructions on creating and viewing
reports, including information about using third‐party reporting tools, see Chapter 8,
“Working with Reports”.
Note: Reporting is available only on data collected after January 1, 2003. Also, the reports
are only available in English. They are not localized and are not available in the language
packs.
Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuration Tasks
The following table lists webMethods Monitor configuration and setup tasks and where
to find information about each task.
1 In the Integration Server Administrator (of the supporting Integration Server):
Settings > JDBC Pools
2 Use the Create a new Pool Alias Definition link to create an MwS pool alias for My
webMethods Server. Use the portal database user ID and password.
Once you’ve created the MwS pool alias, you’ll see MwS show up as an option in the
Pool Alias Definitions list.
3 Assign the MwS pool alias to the CentralUsers functional alias definition. In the
Functional Alias Definitions list, click the Edit link in the CentralUsers row.
4 Select MwS in the Associated Pool Alias field.
5 Click Save Settings.
6 Click the Restart link in the CentralUsers row to restart the alias definition so the new
settings take effect.
7 Test the new alias definition by clicking the triangle icon (in the Test column) in the
CentralUsers row.
8 Restart the Integration Server.
9 In the Integration Server Administrator:
Security > ACLs
10 In the Select ACL field, select MonitorAdministrators ACL.
11 Click the Add button under the Allowed list to open the Select Role/Group dialog box.
The Select Role/Group dialog box shows the groups on the current Integration Server.
12 In the Provider field, select Central.
13 Type an asterisk (*) in the Search field and then click Go to get the list of roles and
groups to populate.
Note: The role and group list population might not work with Internet Explorer 6.x.
Note: The role and group list population might not work with Internet Explorer 6.x.
1 From My webMethods:
Administration > My webMethods > System Settings.
The System Settings page displays, with all currently configured Integration Servers
displayed in the System Settings panel.
2 Click Add to add a new Integration Server (or a combined Integration Server and
Analytic Engine host pair, if you are using Monitor with Optimize for Process).
3 Enter a name for your new server in the NAME column, and then do one of the
following:
To add an Integration Server for a BPM‐only host, enter the host name or network
address and port number in the INTEGRATION SERVER (MONITOR) HOST and PORT
columns, and select the check box in the USE SSL column if the server uses an SSL
connection.
To add a combined Integration Server/Analytic Engine pair of hosts, enter the
host names or network addresses and the appropriate port numbers in both the
INTEGRATION SERVER (MONITOR) HOST and PORT columns and the ANALYTIC ENGINE
HOST and PORT columns.
Note: Depending on the type of your installation environment, the Analytic Engine
fields might be missing from the System Settings page.
4 Click Save to save your configuration information.
5 Click Check Server Status to check the status of all configured servers.
6 Click the Delete button in the appropriate row to delete a server configuration row, or
click Add to configure another server.
Note: The default server or server pair cannot be deleted.
7 The default server or server pair has its radio button selected in the DEFAULT column.
To change the default server or server pair, select the radio button beside the server(s)
you want to make the default and then click Save. For any new My webMethods user,
the default server or server pair will be selected. Once a user selects a server or server
pair on a Monitor page, that server or server pair becomes that user’s default.
1 In the Integration Server Administrator (of the supporting Integration Server):
Packages > Management
2 In the WmMonitor row, click the Home icon.
3 Complete the first five fields in the Configuration Settings with the appropriate
information.
Note: The default MWS port number is 8585. If this port number was changed during
the My webMethods Server installation, the same port number specified during
installation also needs to be specified here in the MWS Port field.
4 Change any of the remaining configuration fields as desired.
5 Click Submit.
1 In the Integration Server Administrator (of the supporting Integration Server):
Packages > Management.
The Package List table displays the list of packages in the Integration Server.
2 Click the Home icon for the WmMonitor package.
3 In the Database Retries, specify the number of times Monitor should attempt to connect
to a database component. The default is 3.
4 Click Submit.
Note: To allow users to act on process
instances, for example, to resubmit process
instances, see “Granting Users the Ability to
Perform Monitor Actions” on page 27.
Note: To allow users to act on services, for
example, to resubmit services, see “Granting
Users the Ability to Perform Monitor
Actions” on page 27.
Note: To allow users to act on documents, for
example, to resubmit documents, see
“Granting Users the Ability to Perform
Monitor Actions” on page 27.
Model Models
Task Users
Task Roles
5 Click Apply.
To allow a user to perform Monitor actions, you grant functional privileges to roles to
which a user belongs. If a user belongs to more than one role, the user will have the ability
to perform a Monitor action as long as the functional privilege has been granted to at least
one of the user’s roles. For more information about defining roles, see the My webMethods
Server Administrator’s Guide.
Modify the pipeline for a
process instance and resubmit
it
Perform some, but not all types of Under Business Monitoring locate Processes.
actions for process instances. Under Processes, select the check boxes for
the actions you want the role to be able to
perform. Below shows a sample of granting
only the ability to resubmit process
instances:
Modify the pipeline for a
service and resubmit it
Modify a document and
resubmit it
5 Click Apply.
If you want to limit privileges, for example, give a user the ability to start and stop
instances of the newHire process, but only be able to view instances of the
ProblemReporting process, set up two user accounts. For example, you might set up user
account joeHR and assign it to the HR role and joeIntern and assign it to the Interns role.
As a result, when logged as joeHR, the user can view, start, and stop newHire process
instances. When logged in as joeIntern, the user can only view ProblemReport instances.
For more
Step Task Notes information, see...
1 In the Integration Server Administrator (of the supporting Integration Server):
Packages > Management.
The Package List table displays the list of packages in the Integration Server.
2 Click the Home icon for the WmMonitor package.
3 Select the Enable Data Level Security check box.
4 In the Data Level Security Administrator field, type the user name of a user who has
complete access to all My webMethods data and all pages of the My webMethods
user interface. By default, this field is set to Administrator, which is the webMethods
default administrator.
5 Click Submit.
5 To add additional processes that you want to allow the role to access:
a Click Add Processes.
b Use the Add Processes page to identify the processes to which you want the role
to have access.
c Click OK to save your changes.
6 Click Apply on the Edit Role page.
1 Install the Staging and Reporting database components, then connect Integration
Server to them. For instructions, see the webMethods Installation Guide.
2 Populate the Staging and Reporting database components using these services:
Service Description
pub.monitor.reporting.processDataMart: Copy logged data for process instances and
extract process steps from the Process Audit Log
database component into the Staging
database component.
pub.monitor.reporting.processDataMart: Accumulate the data and load it into the
transformAndLoad Reporting database component.
pub.monitor.reporting.processDataMart: Aggregate the data into daily metrics in the
aggregateDay Reporting database component.
webMethods recommends that you schedule the services to run automatically, at
specific times or intervals. Running the services regularly minimizes the time
required to process the data. For instructions on scheduling services, see the
webMethods Integration Server Administrator’s Guide. For instructions on using the
services, see the webMethods Monitor Built‐In Services Reference Guide.
Note: Do not run these services on Integration Servers that run process instances in
your production environment. These services consume large amounts of CPU and
adversely affect performance.
The Process Audit Log, Reporting, and Staging database components have a 1‐to‐1‐to‐
1 relationship. You cannot copy data from multiple Process Audit Log database
components into the same Reporting database component.
If the amount of data to process is very large, you can schedule the
pub.monitor.reporting.processDataMart:extract and pub.monitor.reporting.processDataMart:
transformAndLoad services to run more than once a day. Schedule the
pub.monitor.reporting.processDataMart:aggregateDay service separately, so it is run only a
single time per day. It is not useful to run this service more often.
3 The services that populate the Reporting database component use batch processing;
each service uses the same batches of data. The default batch size is 100, which
equates to about 100 rows from the WMPROCESS table. However, this number does
not represent exactly 100 processes per batch because the services take all rows
associated with a process from the WMPROCESS and WMPROCESSSTEP tables.
Multiple rows in the WMPROCESS table might apply to the same process, and all
rows with the same timestamp will be processed in the same batch. One row in the
WMPROCESS table might correspond to several rows in the WMPROCESSSTEP
table, depending on how many steps run in a process. You might want to adjust the
batch size after taking all these considerations into account. Configure the batch size
as follows:
a In the Integration Server Administrator (of the supporting Integration Server), go
to the Packages > Management page.
b Click the Home icon for the WmMonitor package.
c In the Reporting Batch Size field, specify the batch size to use.
d Click Submit.
1 Install the Archive database component, then connect Integration Server to it. For
instructions, see the webMethods Installation Guide.
2 Configure the Archive database component. To do so, run the
pub.monitor.archive:setOperationParameters service from Developer and specify the input
parameters described below. The setOperationParameters service sets the values that you
specify in the OPERATION_PARAMETER table of the Archive database component.
For more information about the setOperationParameters service, see the webMethods
Monitor Built‐In Services Reference Guide.
Parameter Entry
PROCESSAUDIT_DBLINK If you want to archive from the Process Audit Log
database component and it is installed on a different
database server from the Archive database
component, specify the name of the DBlink you
created for Archive to use to link to the Process Audit
Log database component.
ISCOREAUDIT_DBLINK If you want to archive from the IS Core Audit Log
database component and it is installed on a different
database server from the Archive database
component, specify the name of the DBlink you
created for Archive to use to link to the IS Core Audit
Log database component.
Parameter Entry
PROCESS_SCHEMA If you want to archive from the Process Audit Log
database component, identify it by specifying:
For Oracle, specify the database user
For SQL Server, specify the database name
ISCORE_SCHEMA If you want to archive from the IS Core Audit Log
database component, identify it by specifying:
For Oracle, specify the database user
For SQL Server, specify the database name
3 Set database permissions to allow the Archive database component to act on the IS
Core Audit Log and Process Audit Log database components. To do so, use the
GRANT command to give the Archive database user permission to select and delete
from the Process Audit Log database component, the IS Core Audit Log database
component, or both, depending on the data you want to archive.
4 Configure the number of days of audit information that Monitor should retain when
performing an archive operation. The default is 14 days.
a In the Integration Server Administrator (of the supporting Integration Server) go
to the Packages > Management page. The Package List table displays the list of
packages in the Integration Server.
b Click the Home icon for the WmMonitor package.
c Specify the number of days of audit information to retain using the Archive Results
Days setting.
d Click Submit.
Resubmitting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Note: Whether the search is case‐sensitive or case‐insensitive depends on how the
underlying database (for example, Oracle, DB2, or SQL server) handles the queries that
Monitor issues to obtain data.
4 In the text box, type the keywords that are contained in the service names of the
services you want to find. For example, you might specify:
The fully qualified name of the service (for example,
OrderPartner.Services:processOrder)
A partial service name (for example, processOrder) to select all services that
contain the specified keyword
If you leave the text box blank, Monitor searches for all logged service data that you
are authorized to view. For more information about how to specify keywords, see the
Getting Started with My webMethods guide.
5 Click Go to execute the search.
Monitor displays the search results below the search panel. For information about
how to work with the search results, see “Viewing Information for a Service” on
page 45 and “Resubmitting Services” on page 49. For information about saving the
search criteria to re‐use at a later time, see the Getting Started with My webMethods
guide.
Note: Whether the search is case‐sensitive or case‐insensitive depends on how the
underlying database (for example, Oracle, DB2, or SQL server) handles the queries that
Monitor issues to obtain data.
3 If Monitor is configured to use multiple Integration Servers, use the Server selection
box (above the Search tabs) to specify which server you want to search. The Server
selection box defaults to the last server specified by the currently logged in user. If the
current user has not selected a server, the default server set by the My webMethods
Server Administrator on the System Settings page will be used.
4 Fill in one or more of the following advanced criteria fields:
Filter By A date and time range to use to narrow the search
Range
Field Description
Filter By Type of date and time range you want to use:
Date Last Updated to search for services based on
the last date and time information was logged for
the service.
Start Date to search for services based on when the
service was started.
Range The dates and times for the range. You can either:
Click a predefined time period from the Range list.
Use the calendar picker to specify a Start Date and
End Date, then select the numbers for the hours
and minutes from their respective lists.
Note: If you want to add the search results to a My
webMethods custom page, it is recommended that
you use a predefined time period from the Range list.
When you do, the search results on the custom page
will be dynamic showing data relative to the current
date (e.g., yesterday). If you specify exact start & end
dates, the search results always contain data for the
specific dates you use.
Context ID The context ID of the service for which you are searching. You
must specify the full context ID.
Parent Context The context ID of the parent service that invoked the service(s) for
ID which you are searching. You must specify the full context ID.
Use this field to find all services invoked by the specified parent
service. You can find the context ID for a service by viewing the
Service Detail page. For more information, see “Viewing Detailed
Information for a Service” on page 46.
Activity Full or partial message entered into the Full Message field using the
Message pub.prt.log:logActivityMessages service. If you leave this field
blank, Monitor does not restrict the search by Activity Message
content.
5 Click Go to execute the search.
Monitor displays the search results below the search panel. For information about
how to work with the search results, see “Viewing Information for a Service” on
page 45 and “Resubmitting Services” on page 49. For information about saving the
search criteria to re‐use at a later time, see the Getting Started with My webMethods
guide.
Statuses for services
1 Search for the service you want to view. For more information, see “Searching for
Logged Service Data” on page 40.
2 In the search results, locate the service for which you want to view details and click
View Detail. Monitor displays the Service Detail page.
For a description of the information that Monitor displays on the Service Detail page,
see “Information Displayed on the Service Detail Page” below. For a list of the actions
you can take from the Service Detail page, see “Actions You Can Take from the Service
Detail Page” on page 48.
Tab Description
Service Information Monitor displays information that identifies the service on the
Service Information tab.
Field Description
Tab Description
Server ID The DNS name and port number of the
Integration Server on which the service ran or is
running.
User The user name of the client that invoked the
service.
Timestamp The date and time on which the activity indicated
by Current Status (for example, Failed) was logged.
Current Status The current status of the service. For more
information, see “Statuses of Services” on
page 48.
Duration The length of time the service took to execute or
has been active.
Error Message The error message associated with the service.
Monitor only displays the Error Message field
when the Current Status is Failed.
Root Service The fully qualified name of the root service of the
service whose details Monitor is displaying.
Child Services The fully qualified names of all services that the
service whose details Monitor is displaying
invoked.
History Statuses the service went through and the date and time each
status occurred. For a list of statuses, see “Statuses of Services” on
page 48.
Activity Messages If the service logged user‐defined messages by calling the
pub.prt.log:logActivityMessages service, this area shows the logged
messages, and dates and times on which the messages were
logged.
Control Actions If the service has been resubmitted, this area shows the user names
of the users who resubmitted the service, the Integration Servers
on which the service was resubmitted, and the dates and times
when the service was resubmitted.
Note: Each time a service is resubmitted, Integration Server assigns
it a new context ID.
Edit the pipeline for a root‐level service before resubmitting the service. For more
information, see “Resubmitting Services” on page 49.
Statuses of Services
Monitor displays statuses for services using both a status keyword (e.g., Completed or
Started) and also by using status icons. The following lists the location where Monitor
displays statuses and status icons for a service:
On the Services page, Monitor displays:
A status icon at the beginning of the row for each service. The icon is located after
the check box for the row.
The status keyword in the STATUS column.
On the Service Detail page, Monitor displays the status keyword in the Current Status field
on the Service Information tab.
The following table lists the possible service status icons along with their meanings:
The service is running; however, it has encountered errors.
Service completed, but it encountered errors.
The following table lists the possible service statuses along with their meanings:
Status Meaning
Completed The service has completed processing.
Failed The service stopped processing because it encountered an error.
Resubmitted Execution of the service has been resubmitted.
Started The service has started and is currently executing.
Resubmitting Services
You can resubmit root‐level services whose input pipeline was logged. The services can
have any status.
When you resubmit a service, Monitor changes the status of the service to Resubmitted. It
then starts a new instance of the service and sets its status to Started. Monitor uses the
context ID of the original service as the parent context ID for the new instance of the
service. All logged information for the original service (now in Resubmitted status)
remains unchanged. All information about the resubmission will be logged for the new
instance of the service.
If you want to edit the pipeline before resubmitting the service, you must resubmit the
service from the Service Detail page. After you update the pipeline, the changes you make
are only available while you are still on the Service Detail page. If you leave this page, the
changes you make are not maintained. As a result, if you want to edit the pipeline before
resubmitting, you must edit the pipeline and then immediately resubmit the service. The
pipeline for the original instance of the service is left unchanged. Monitor logs the
updated pipeline with the new instance of the service.
Resubmitting a Service
You can resubmit one or more services from the search results panel of the Monitoring >
Integration > Services page.
To resubmit services
1 Search for the services you want to resubmit. For more information, see “Searching
for Logged Service Data” on page 40.
2 In the search results, select the check boxes beside the services that you want to
resubmit.
3 Click Resubmit.
Important! The changes you make to the pipeline are only available while you are viewing
the Service Detail page. If you leave this page, the changes you make are lost. To resubmit
with the updated pipeline, you must resubmit the service immediately from the Service
Detail page, as described in the procedure below.
To edit the pipeline for a service and then resubmit the service
1 Search for the service whose pipeline you want to edit. For more information, see
“Searching for Logged Service Data” on page 40.
2 In the search results, locate the service that you want to resubmit and click View
Detail. Monitor displays the Service Detail page.
3 Click Edit Pipeline.
4 On the Edit Pipeline page, update the fields you want to change:
a Click the hyperlinked field value.
b Specify a new value for the field.
c Click OK.
5 After you have modified all the fields you want changed, click Save.
Monitor re‐displays the Service Detail page.
6 To resubmit the service, click the Resubmit button on the Service Detail page.
Resubmitting Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Note: You monitor Trading Networks documents from the Trading Networks Web
Manager.
For detailed information on setting up document logging, see the webMethods Logging
Guide. After document logging is setup, an administrator:
Must configure My webMethods to allow you to access the My webMethods pages for
viewing logged document data. For more information, see “Granting Users Access to
the My webMethods Monitoring Pages” on page 25.
Can also restrict the documents that you are able to view. For more information, see
“Identifying the Logged Data Users Can Perform Actions Against” on page 30 and
“Identifying Documents a Role Can Act On” on page 34.
Must configure whether you can resubmit documents or whether you can modify the
documents before resubmitting them. For more information, see “Granting Users the
Ability to Perform Monitor Actions” on page 27.
Note: Whether the search is case‐sensitive or case‐insensitive depends on how the
underlying database (for example, Oracle, DB2, or SQL server) handles the queries that
Monitor issues to obtain data.
4 In the text box, type the keywords that are contained in the document names of the
documents you want to find. For example, you might specify:
The full document name as it exists on the Broker (for example,
wm::is::OrderProcess::Implementation::CanonicalOrder)
The full document name as it exists on the Integration Server (for example,
OrderProcess.Implementation:CanonicalOrder)
A partial document name (for example, OrderProcess) to select all documents
that contain the specified keyword
If you leave the text box blank, Monitor searches for all logged document data that
you are authorized to view. For more information about how to specify keywords, see
the Getting Started with My webMethods guide.
5 Click Go to execute the search.
Monitor displays the search results below the search panel. For information about
how to work with the search results, see “Viewing Detailed Information for a
Document” on page 58 and “Resubmitting Documents” on page 60. For information
about saving the search criteria to re‐use at a later time, see the Getting Started with My
webMethods guide.
Note: Whether the search is case‐sensitive or case‐insensitive depends on how the
underlying database (for example, Oracle, DB2, or SQL server) handles the queries that
Monitor issues to obtain data.
3 If Monitor is configured to use multiple Integration Servers, use the Server selection
box (above the Search tabs) to specify which server you want to search. The Server
selection box defaults to the last server specified by the currently logged in user. If the
current user has not selected a server, the default server set by the My webMethods
Server Administrator on the System Settings page will be used.
4 Fill in one or more of the following advanced criteria fields:
Full name of an IS document, such as:
OrderProcess.Implementation:CanonicalOrder
Partial name of a document, such as: OrderProcess
If you leave this field blank, Monitor does not restrict the search
by document name.
Document ID The full or partial document ID of the document you are
searching for. The Broker or Integration Server that publishes the
document generates the ID when it publishes the document. If
you leave this field blank, Monitor does not restrict the search by
document ID.
Type The type of documents you are searching for (for example,
Broker, In Doubt, Retries). To select multiple types, click CTRL
while selecting each type. To specify all types, leave the field
blank, and Monitor does not restrict the search by type.
Client ID The client ID associated with the documents you are searching
for. Specify a partial client ID to search for documents associated
with multiple clients.
The format for:
Broker IDs is Broker@host:port (for example,
CustOps@qatest07:6849). To specify a partial client ID, you
might specify only CustOps.
The format for IDs of Broker clients is
clientprefix_folder1.folder2.foldern_trigger (for example,
smitha_documenthistory.history.triggers_MsgHistory
WithNoResServiceTrigger). To specify a partial client ID,
you might specify only smitha.
The value you specify for Client ID depends on the types of
documents you are searching for.
To search for this type of
document... Specify...
Broker IDs of the Brokers that logged the
documents
In Doubt IDs of the Broker clients associated
with the triggers that originally
processed the documents
Failed and Retries Exceeded IDs of the original destination
when failure/retries Broker clients
exceeded occurred during
delivery
Failed documents when IDs of the Broker clients associated
failure occurred during with the triggers for which
retrieval Integration Server originally tried to
retrieve the documents
Range A date and time range for the last date and time information was
logged for the document. You can either:
Click a predefined time period from the Range list.
Note: If you want to add the search results to a My webMethods
custom page, it is recommended that you use a predefined time
period from the Range list. When you do, the search results on the
custom page will be dynamic showing data relative to the current
date (e.g., yesterday). If you specify exact start & end dates, the
search results always contain data for the specific dates you use.
Search Whether you want Monitor to use an AND condition or an OR
Condition condition with the search criteria you specify.
Select AND if you want Monitor to find documents that match
all of the search criteria you specify.
Select OR if you want Monitor to find documents that match
any of the search criteria you specify.
5 Click Go to execute the search.
Monitor displays the search results below the search panel. For information about
how to work with the search results, see “Viewing Detailed Information for a
Document” on page 58 and “Resubmitting Documents” on page 60. For information
about saving the search criteria to re‐use at a later time, see the Getting Started with My
webMethods guide.
1 Search for the document you want to view. For more information, see “Searching for
Logged Document Data” on page 52.
2 In the search results, locate the document for which you want to view details and click
View Detail. Monitor displays the Document Detail page.
For a description of the information that Monitor displays on the Document Detail
page, see “Information Displayed on the Document Detail Page” below. For a list of
the actions you can take from the Service Detail page, see “Actions You Can Take from
the Document Detail Page” on page 59.
Tab Description
Document Monitor displays information that identifies the document on the
Information Document Information tab.
Field Description
Tab Description
Type The type of document, which will be one of the
following:
Broker
Failed
In Doubt
Retries Exceeded
Enqueued If the document was logged by a Broker, date
and time the Broker first enqueued the document
(that is, added it to the first subscriberʹs queue)
Timestamp The date and time the document was logged.
Control Actions If the document has been resubmitted:
User name of the user who resubmitted the document
Broker documents, the Broker to which the document was
delivered (always the Broker to which the Monitor‐equipped
Integration Server is connected)
For In Doubt, Failed, and Retries Exceeded documents, see
“Resubmitting Documents” on page 60
Dates and times the document was resubmitted
Resubmitting Documents
When you resubmit a document, Monitor logs a new instance of the document. All logged
information for the original document remains unchanged. All information about the
resubmission will be logged for the new instance of the document.
If you want to edit the fields in the document before resubmitting it, you must resubmit
the document from the Document Detail page. After you update the document, the
changes you make are only available while you are still on the Document Detail page. If
you leave this page, the changes you make are not maintained. As a result, if you want to
edit the document before resubmitting, you must edit the document and then
immediately resubmit it. The fields for the original instance of the document are left
unchanged. Monitor logs the updated document with the new instance of the document.
You can resubmit any type of document. The following table describes how Monitor
resubmits each type of document:
Document Monitor...
Broker documents Publishes the documents to the Broker to which the
Monitor‐equipped Integration Server is connected.
In Doubt documents Delivers the documents to the triggers that originally
processed the documents.
Failed documents
Failed during delivery Delivers the documents to the original destination
Broker clients.
Failed during publication Publishes the documents to the Broker to which the
Monitor‐equipped Integration Server is connected.
Failed during retrieval Delivers the documents to the triggers for which
Integration Server originally tried to retrieve the
documents.
Retries exceeded documents
Exceeded during delivery Delivers the documents to the original destination
Broker clients.
Exceeded during Publishes the documents to the Broker to which the
publication Monitor‐equipped Integration Server is connected.
Resubmitting a Document
You can resubmit one or more documents from the search results panel of the
Monitoring > Integration> Documents page.
To resubmit documents
1 Search for the documents you want to resubmit. For more information, see “Searching
for Logged Document Data” on page 52.
2 In the search results, select the check boxes beside the documents that you want to
resubmit.
3 Click Resubmit.
Important! The changes you make to the document are only available while you are
viewing the Document Detail page. If you leave this page, the changes you make are lost.
To resubmit with the updated document, you must resubmit the document immediately
from the Document Detail page, as described in the procedure below.
1 Search for the document you want to edit. For more information, see “Searching for
Logged Document Data” on page 52.
2 In the search results, locate the document that you want to resubmit and click View
Detail. Monitor displays the Document Detail page.
3 Click Edit Document.
4 On the Edit Document page, update the fields you want to change:
a Click the hyperlinked field value.
b Specify a new value for the field.
c Click OK.
5 After you have modified all the fields you want changed, click Save.
Monitor re‐displays the Document Detail page.
6 To resubmit the document, click the Resubmit button on the Document Detail page.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Overview
This chapter describes monitoring logged data for process instances.
In addition to monitoring data that has been logged for process instances, you can
perform some management tasks of process models. For more information, see Chapter 6,
“Working with Process Models”.
Note: Although you can view information about integration processes via Monitor,
integration processes are not eligible for stopping, suspending, resuming, or resubmitting.
1
2
Flow
Operations Description
1 To add a definition for the integration process, invoke the
pub.monitor.integrationProcessLogging:createProcessMetadata service. The process definition is
comparable to an entry for a process model that was created with Designer.
After you add a process definition, you can then add steps to the process.
2 To add a definition for a step that is part of the integration process, invoke the
pub.monitor.integrationProcessLogging:createStepMetadata service. The step definition is
comparable to an entry for a step added to a process model that was created with
Designer.
After you add a step definition, you can add definitions for one or more logged fields
that are associated with the step.
3 To add a logged field and associate it with a step, invoke the
pub.monitor.integrationProcessLogging:createLoggedFieldMetadata service. The logged field
definitions are comparable to custom data in a process model that was created with
Designer.
In the sample above, two logged fields are defined for and associated with the first
step of the integration process.
4 Continue using the pub.monitor.integrationProcessLogging:createStepMetadata service to add
additional steps and pub.monitor.integrationProcessLogging:createLoggedFieldMetadata service
to add logged fields for the steps. In the sample above, a second and third step are
added. One logged field is defined for and associated with the third step.
1
2
3
4
Flow
Operations Description
1 Each process requires a unique process instance ID. You can either create one on your
own, or use the pub.monitor.integrationProcessLogging:generateProcessInstanceID service to
generate a unique process instance ID.
Note: This service does not add data to the Process Audit Log database component.
That is, it does not start a new instance of the integration process.
2 To log a running instance of an integration process, create a process instance. To
create a new process instance, invoke the
pub.monitor.integrationProcessLogging:createProcessInstance service. As input to this service,
you must identify the process definition for which you are creating the instance. The
process definition must already exist in the Process Audit Log database component,
which you add using the pub.monitor.integrationProcessLogging:createProcessMetadata
service, as shown in the sample in “Defining an Integration Process” on page 67.
After you create the process instance, its process status is Started. Use the
pub.monitor.integrationProcessLogging:updateProcessInstanceStatus service if you want to
change the process status.
3 To start logging information about the first step in the integration process, create an
instance of the first step. To create a step instance, invoke the
pub.monitor.integrationProcessLogging:createStepInstance service. As input to this service, you
identify:
The process instance in which the step is running. You would specify the same
process instance ID that you specified as input to the
pub.monitor.integrationProcessLogging:createProcessInstance service in the previous
INVOKE flow operation.
The step definition for which you are creating the instance. The step definition
must already exist in the Process Audit Log database component, which you add
using the pub.monitor.integrationProcessLogging:createStepMetadata service.
After you create the step instance, the step status is Started. Use the
pub.monitor.integrationProcessLogging:updateStepInstanceStatus service if you want to change
the step status.
4 After the step instance is logged, execute the service(s) for the first step of the
integration process. The next flow operations are based on the outcome of this step.
Flow
Operations Description
5 This series of flow operations shows how the logic you might perform when a step
fails:
The step status is set to Failed using the
pub.monitor.integrationProcessLogging:updateStepInstanceStatus service.
The process status is set to Failed using the
pub.monitor.integrationProcessLogging:updateProcessInstanceStatus service.
An error message is logged for the process using the
pub.monitor.integrationProcessLogging:createProcessError service.
A service you code is invoked to exit the integration process.
6 This series of flow operations shows the logic you might perform when a step is
successful:
Values are set for logged fields that are associated with the step using the
pub.monitor.integrationProcessLogging:createLoggedFieldInstance service.
The step status is set to Completed using the
pub.monitor.integrationProcessLogging:updateStepInstanceStatus service.
7 This series of flow operations handles the second step in the integration process. The
flow operations are similar to those described above in 4 , 5 , and 6 .
8 This series of flow operations handles the third step in the integration process. The
flow operations are similar to those described above in 4 , 5 , and 6 .
Note: Whether the search is case‐sensitive or case‐insensitive depends on how the
underlying database (for example, Oracle, DB2, or SQL Server) handles the queries that
Monitor issues to obtain data.
Note: Whether the search is case‐sensitive or case‐insensitive depends on how the
underlying database (such as Oracle, DB2, or SQL Server) handles the queries that
Monitor issues to obtain data.
1 In My webMethods: Monitoring > Business > Process Instances.
2 Click the Advanced tab if it is not already displayed.
3 If Monitor is configured to use multiple Integration Servers, use the Server selection
box (above the Search tabs) to specify which server you want to search. The Server
selection box defaults to the last server specified by the currently logged in user. If the
current user has not selected a server, the default server set by the My webMethods
Server Administrator on the System Settings page will be used.
4 In the text box, optionally type the keywords that are contained in either the model
names used for the process instances or the instance IDs of the process instances you
want to find. For more information about how to specify keywords, see the Getting
Started with My webMethods guide.
If you leave the text box blank and specify no other search criteria, Monitor
returns data for all process instances that you are authorized to view, honoring
the maximum results search option. For more information about setting the
maximum results search option, see the Getting Started with My webMethods guide.
If you leave the text box blank and specify other search criteria, Monitor does not
restrict the search based on keywords.
5 Fill in one or more of the following advanced criteria fields:
Process The exact name of one or more models used for the process
instances you want to display. To select multiple entries, hold
down CTRL while you select each name.
For webMethods‐executed process models, the entries in the
Process list identify the model version, in addition to simply a
process model name. The entries have the following format:
processModelName ‐ modelVersion
where:
processModelName is the name of the process model.
modelVersion identifies the model version as it was
assigned in Designer.
If you want to search process instances based on specific
logged fields, choose from the Process list a process instance
that has logged fields. The screen will refresh and you will
now see the Filter section on the Search panel. In the Filter fields,
specify the desired criteria related to the logged fields you
want to search.
Status The status of the process instances you want to display.
To search for all statuses, select All.
To search for multiple, but not all, statuses, hold down
CTRL while you select each status.
For more information about statuses, see “Statuses of Process
Instances and Process Steps” on page 81.
Filter By The type of date and time range you want to use.
Choose Date Last Updated to search for process instances
based on the last date and time that information was
logged for process instances.
Choose Start Date to search for process instances based on
when process instances were started.
Range The dates and times for the range. You can choose either of the
following:
Click a predefined time period from the Range list. By
default, Monitor uses Today.
Use the calendar picker to specify a Start Date and End Date,
and then select the numbers for the hours and minutes
from their respective lists.
Note: If you want to add the search results to a My
webMethods custom page, it is recommended that you use a
predefined time period from the Range list. When you do, the
search results on the custom page will be dynamic showing
data relative to the current date (e.g., yesterday). In contrast, if
you specify exact start and end dates, the search results will
always contain data for the specific dates you use.
6 Click Go to execute the search.
Monitor displays the search results below the search panel. For more information
about how to work with search results, see “Viewing Information for Process
Instances” on page 76, “Stopping, Suspending, and Resuming Process Instances” on
page 86, and “Resubmitting Process Instances and Process Steps” on page 87. For
more information about saving the search criteria to re‐use at a later time, see the
Getting Started with My webMethods guide.
Statuses for process instances and steps within a process instance
Monitors associated with process instances
Detailed information for steps within a process instance
1 Search for the business process instance that you want to view. For more information,
see “Searching for Process Instances” on page 71.
2 In the search results, locate the process instance for which you want to view details
and click View Detail. Monitor displays the Process Instance Detail page.
For a description of the information that Monitor displays on the Process Instance
Detail page, see “Information Displayed on the Process Instance Detail Page” below.
For a list of actions you can take from the Process Instance Detail page, see “Actions
You Can Take from the Process Instance Detail Page” on page 81.
Tab Description
Process Monitor displays the following fields that identify the process instance.
Instance
Field Description
Information
Process The name of the process model associated with
the process instance.
Model Version The name of the model version used for the
process instance. This field is only applicable for
webMethods‐executed processes.
Tab Description
Start Date / Time The date and time the process instance started.
Last Updated The last date and time that information was
logged for this process instance.
Instance Id The unique identifier for the process instance. If a
process instance ID consists of multiple parts (for
example, order numbers from two or more
different order systems), Monitor creates one row
for each part.
Instance Iteration The number of times the process instance has
been submitted.
Status The status of the process instance. For more
information, see “Process Statuses” on page 81.
Duration The length of time a process instance has been
active.
For active process instances, the length of time
that this process instance has been executing.
Duration is calculated by subtracting the start
time of the process instance from the current
system time.
For inactive process instances, the length of time
the process instance was active. Duration is
calculated by subtracting the start time of the
process instance from the time the process
instance became inactive.
For timed out or stopped process instances, the
length of time the process instance was active.
Duration is calculated by subtracting the start
time of the process instance from the time the
cancel or timeout action occurred.
Note: For steps that execute in parallel, Duration
does not include the overlapping execution time.
Tab Description
Process An image of the process model as it was designed in Designer, if an
Diagram image is available for a webMethods‐executed or externally executed
process model. Because no model exists for an integration processes,
Monitor cannot display a process diagram for integration processes.
The image contains status icons next to steps that have executed or are
currently executing. For more information, see “Step Statuses” on
page 83.
For webMethods‐executed process models only, if transition logging is
enabled and your My webMethods Model Image Format user preference is
set to SVG, the transition lines along the path that the process took are
thicker than the transition lines along paths that the process did not
take. For more information about logging, see the webMethods Logging
Guide. For more information about setting your My webMethods user
preferences, see the Getting Started with My webMethods guide.
Step Summary Information about the execution of the steps within the process
instance.
Field Description
Tab Description
ACTION The action taken on the process instance
(suspend, resume, resubmit, or stop).
INSTANCE The instance ID for the process instance.
ITERATION
STEP NAME The name of the step.
STEP ITERATION The number of times the step executed.
USER The user associated with the process instance.
SERVER ID The server on which the process instance
executed.
Activity The Process Instance Detail page displays this tab only when the
Messages process instance ran a service that logged user‐defined messages.
Field Description
Tab Description
Process This tab displays error information for the process instance. Only errors
Errors for the entire process instance are shown here; step errors are shown in
the Process Step Detail page. For more information about step detail,
see “Viewing Detailed Information for Process Steps” on page 84.
Field Description
Actions You Can Take from the Process Instance Detail Page
You can perform the following actions from the Monitoring > Business > Process Instances
> Process Instance Detail page:
View detailed information about steps in the process instance. For more information,
see “Viewing Detailed Information for Process Steps” on page 84. From the Process
Step Detail page, you can perform the following additional actions:
Save the input pipeline for a process step to an XML file by clicking Save Pipeline to
a File.
Edit the pipeline for a process step before resubmitting the process instance. For
more information, see “Resubmitting Process Instances and Process Steps” on
page 87.
Restart a process step. For more information, see “Resubmitting Process Instances
and Process Steps” on page 87.
View monitors associated with steps in the process instance. For more information,
see “Viewing KPI Data That Is Associated with a Process Step” on page 85.
Stop, suspend, and resume process instances. For more information, see “Stopping,
Suspending, and Resuming Process Instances” on page 86.
Note: The meanings for each status that is described in this section are for webMethods‐
executed and externally executed processes. Although integration processes use the same
status keywords (e.g., Completed, Waiting, etc.), user‐created services set the statuses. As
a result, the user‐created services might use the status keywords differently than defined
by the webMethods product suite.
Process Statuses
Monitor displays process status information on the Process Instances page and also on the
Process Instance Detail page. The following lists the locations where Monitor displays
statuses and status icons for a process instance:
On the Process Instances page, Monitor displays:
A status icon at the beginning of the row for each process instance. The icon is
located after the check box for the row.
The status keyword in the STATUS column.
Either:
The process instance has been suspended.
The process is running; however, one or more steps might be
executing with errors.
Process completed, but one or more steps executed with errors.
The following table lists the possible process statuses along with their meanings:
Step Statuses
Monitor displays status information for the execution of steps within a process instance
on the Process Instance Detail page. The following lists the locations where Monitor
displays statuses and status icons for a process step:
On the Process Diagram tab, Monitor displays a status icon next to each completed and
currently executing step. The following table lists the status icons used on this tab and
their meaning:
The step has completed successfully.
The step failed.
The step is waiting, for example, to receive an external
document.
Either:
The step instance has been suspended.
The step is running; however, one or more errors might
have occurred.
Step completed, but with errors.
The following table lists the possible step statuses that Monitor displays on the Step
Summary tab along with the meaning of each status icon:
1 Display detailed information for the process instance that contains the step for which
you want to view information. For help with this step, see “Viewing Information for
Process Instances” on page 76.
2 On the Step Summary tab of the Process Instance Detail page, locate the step for which
you want to view detailed information and click Detail. Monitor displays the
Process Step Detail page.
If the status of the process instance is Resubmitted or Suspended and the input
pipeline for the step you are viewing has been logged, you can view the pipeline by
clicking View Pipeline. For more information about setting up logging data for process
instances, see information about setting the logging level in “Setting Up Logging for a
Process Model Version” on page 104.
Actions You Can Take from the Process Step Detail Page
You can perform the following actions from the Monitoring > Business > Process
Instances > Process Instance Detail page:
Save the input pipeline for a process step to an XML file by clicking Save Pipeline to a
File. You might want to save the pipeline for a step if you want to test the step or a
similar step and want to have actual data available for the test.
Edit the pipeline for a process step before resubmitting the process step. For more
information, see “Resubmitting Process Instances and Process Steps” on page 87.
Restart the process step. For more information, see “Resubmitting Process Instances
and Process Steps” on page 87.
1 Search for the process instance for which you want to view KPI data. For more
information, see “Searching for Process Instances” on page 71.
2 In the search results, locate the process instance for which you want to view KPI data
and click KPI Summary.
For more information, see the webMethods Optimize for Process User’s Guide.
To view KPI data that is associated with a step within a process instance
1 Display detailed information for the process instance that contains the step for which
you want to view KPI data. For help with this step, see “Viewing Information for
Process Instances” on page 76.
2 On the Step Summary tab of the Process Instance Detail page, locate the step for which
you want to view KPI data and click KPI Summary.
For more information, see the webMethods Optimize for Process User’s Guide.
1 Display detailed information for the process instance that you want to stop. For help
with this step, see “Viewing Information for Process Instances” on page 76.
2 On the Process Instance Information tab on the Process Instance Detail page, click Stop.
1 Display detailed information for the process instance that you want to suspend. For
help with this step, see “Viewing Information for Process Instances” on page 76.
2 On the Process Instance Information tab on the Process Instance Detail page, click
Suspend.
1 Display detailed information for the process instance that you want to resume. For
help with this step, see “Viewing Information for Process Instances” on page 76.
2 On the Process Instance Information tab on the Process Instance Detail page, click
Resume.
Completed Resumed
Failed Stopped
Note: From the Monitoring > Business > Process Instances page, you can only resubmit
process instances that have a Failed status. To resubmit processes in the other statuses,
you must resubmit from the Process Step Detail page
The input pipeline must be logged for at least one of the steps within the process. For
more information about setting up logging data for process instances, see information
about setting the logging level in “Setting Up Logging for a Process Model Version”
on page 104.
The step from which you want to resubmit the process instance must be enabled for
resubmission. For more information, see information about resubmit enabling in
“Setting Up Logging for a Process Model Version” on page 104.
You must have the authority to resubmit process instances. For more information, see
“Granting Users the Ability to Perform Monitor Actions” on page 27 and “Identifying
the Logged Data Users Can Perform Actions Against” on page 30.
If steps for referenced processes are downstream from the resubmitted step, the
Process Engine attempts to resubmit those referenced processes. The referenced
processes must also meet these requirements for resubmission.
In this situation, if data level security is enabled, in addition to having the authority to
resubmit the parent process, you must also have the authority to resubmit the child,
referenced processes. If you do not have this authority, the steps for the referenced
processes will fail. If you attempt to resubmit at the referenced process step and do
not have the authority to resubmit the referenced process, you will be unable to even
start the resubmission. For more information about data level security, see
“Identifying the Logged Data Users Can Perform Actions Against” on page 30.
Note: If you want to edit the pipeline for the start step before resubmitting or if you want to
resubmit a process instance from a step other than the start step, see “Resubmitting
Processes from a Step and Optionally Editing Pipeline Information” on page 89.
1 Search for the process instances you want to resubmit. For more information, see
“Searching for Process Instances” on page 71.
2 In the search results, select the check boxes beside the process instances that you want
to resubmit.
3 Click Resubmit.
Important! The changes you make to the pipeline are only available while you are viewing
the Process Step Detail page. If you leave this page, the changes you make are lost. To
resubmit a step with your changes, you must resubmit the step immediately from the
Process Step Detail page, as described in the procedure below.
To resubmit a step in a process instance and optionally edit pipeline information before resubmission
1 Search for the process instance that you want to resubmit. For more information, see
“Searching for Process Instances” on page 71.
2 In the search results, locate the process instance that you want to resubmit and click
View Detail. Monitor displays the Process Instance Detail page.
3 On the Step Summary tab of the Process Instance Detail page, locate the step that you
want to resubmit and click Detail. Monitor displays the Process Step Detail page.
4 To edit the input pipeline for a step:
a On the Step Information tab, click Edit Pipeline.
b On the Edit Step page, for each field value you want to change:
1 Click the hyperlinked field value that you want to change. If the value of a
field is not displayed with an active hyperlink, you cannot change that field
value.
2 Specify a new value for the field.
3 Click OK.
c After updating all the fields you want to change, click Save. Monitor re‐displays
the Process Step Detail page.
5 Click Resubmit.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Overview
In addition to monitoring process instances, you can perform some management tasks for
process models. The table below describes the tasks you can perform for process models:
1 In My webMethods:
Administration > Business > Business Processes.
2 Click the Keyword tab if it is not already displayed.
3 If Monitor is configured to use multiple Integration Servers, use the Server selection
box (above the Search tabs) to specify which server you want to search. The Server
selection box defaults to the last server specified by the currently logged in user. If the
current user has not selected a server, the default server set by the My webMethods
Server Administrator on the System Settings page will be used.
4 In the text box, type a keyword.
If you leave the text box blank, Monitor returns data for all models that you are
authorized to view, honoring the maximum results search option. For more
information about how to specify keywords and how to set the maximum results
search option, see the Getting Started with My webMethods guide.
5 Click Go to execute the search. Monitor displays the search results below the search
panel.
For more information about saving the search criteria to re‐use at a later time, see the
Getting Started with My webMethods guide.
1 In My webMethods:
Administration > Business > Business Processes.
2 Click the Advanced tab if it is not already displayed.
3 If Monitor is configured to use multiple Integration Servers, use the Server selection
box (above the Search tabs) to specify which server you want to search. The Server
selection box defaults to the last server specified by the currently logged in user. If the
current user has not selected a server, the default server set by the My webMethods
Server Administrator on the System Settings page will be used.
4 In the text box, optionally type a keyword. For information about how Monitor uses
the keywords, see “Performing a Keyword Search” on page 93. For more information
about how to specify keywords, see the Getting Started with My webMethods guide.
If you leave the text box blank and specify no other search criteria, Monitor
returns data for all models that you are authorized to view, honoring the
maximum results search option. For more information about setting the
maximum results search option, see the Getting Started with My webMethods guide.
If you leave the text box blank and specify other search criteria, Monitor does not
restrict the search based on keywords.
5 Fill in the following fields to specify additional search criteria:
Note: If you specify a keyword in this field, Monitor will not
return any externally executed or integration processes.
External to locate externally executed processes only
webMethods to locate webMethods‐executed processes only
Integration to locate integration processes only.
For more information about each process type, see “Types of
Processes You Can Monitor” on page 65.
Execution Whether the webMethods‐executed process models you want to
Enabled display have been enabled for execution. For more information
about enabling process models, see “Enabling and Disabling
Process Model Versions” on page 102.
Select this option... To display...
Yes Only enabled process models
No Disabled process models
All All process models regardless of whether
they are enabled or disabled
Note: If you select Yes, Monitor will not include any externally
executed process models and integration processes in the search
results because Execution Enable applies only to webMethods‐
executed process models.
Yes Only process models with analysis enabled
No Only process models with analysis disabled
All All process models regardless of whether
analysis has been enabled or disabled
Note: If you select Yes, Monitor will not include any integration
processes in the search results because integration processes
cannot be enabled for analysis.
6 Click Go to execute the search.
For more information about saving the search criteria to re‐use at a later time, see the
Getting Started with My webMethods guide.
1 Search for the process model you want to view. For instructions, see “Searching for
Process Models That Are Available for Monitoring” on page 93.
2 In the search results, locate the process model for which you want to view details and
click Edit Configuration Details.
Tab Description
Process Monitor displays the following fields that identify the process
Information model:
Field Description
Note: For integration processes, this is the value
specified for the processLabel input variable of the
pub.monitor.integrationProcessLogging:createProcessMeta
data service.
Tab Description
Created By User name of the person who created the process
model.
Note: For integration processes, this the user
name of the user that invoked the
pub.monitor.integrationProcessLogging:createProcessMeta
data service to add the integration process.
Tab Description
Analysis Whether the version of the process model is
Enabled enabled for analysis. This column is available
only when Optimize for Process is installed
because webMethods Optimize for Process
performs the analysis.
Note: This field is applicable only to
webMethods‐executed and externally executed
process models. You cannot enable an integration
process for analysis.
Analysis Specifies how long Optimize for Process waits
Process before it considers the instances that are based on
Timeout this process model version to be timed out. This
field is used by Optimize for Process during
process analysis.
Used Indicates whether the process model version has
been used for at least one process instance.
Yes indicates that the process model version
has been used at least once.
No indicates that the process model version
has never been used; that is, there have never
been any instances of this model version.
When a version of a model has never been
used, you can delete the model version. For
instructions, see “Deleting Unused Process
Models” on page 107.
Unavailable indicates that Monitor is currently
not able to provide use information because
the server used to log instances of the model
version is not available.
Process Diagram Monitor displays the model image as it was designed in Designer.
Note: Because integration processes are not modeled, Monitor
cannot display a model image for an integration process.
Tab Description
Process Quality of Monitor displays logging settings that the Process Engine uses for
Service Settings a webMethods‐executed process. For more information, see
“Setting Up Logging for a Process Model Version” on page 104.
Field Description
Note: These fields are applicable only to webMethods‐executed
processes. They do not apply to externally executed and
integration processes.
Important! If you disable all versions of a model that is called by
another process, the parent process will fail at the step that
calls the disabled process.
1 Search for the model version you want to enable or disable. For instructions, see
“Searching for Process Models That Are Available for Monitoring” on page 93.
1 In My webMethods:
Administration > Business > Business Processes.
2 Click the Advanced tab if it is not already displayed.
3 Select the name of the webMethods‐executed process model for which you want to
determine the enabled version from the Process Name list.
4 Click Go to execute the search.
In the search results, the enabled version (if any) has a check mark in the Execution
Enabled column.
Process Type Whether you can enable the process model for analysis
webMethods-executed Yes, you can enable webMethods‐executed process model
versions for analysis. You can only enable the version of the
process model that is execution enabled.
Externally executed Externally executed process models are always enabled for
analysis.
Integration process No, you cannot enable integration processes for analysis.
1 Search for the process model you want to enable for analysis. For instructions, see
“Searching for Process Models That Are Available for Monitoring” on page 93.
For each process model version, you specify the amount and type of data to log on the
Logging Level setting. If you want to be able to resubmit process instances from Monitor at
certain steps, you must set the logging level to a level that will log the input pipelines for
those steps, and you must enable resubmission for each of those steps using the Resubmit
Enabled setting.
Monitor shows all possible paths that process instances can take. If you want to see the
path the process instances actually took at run time, use the Log Transitions setting to
enable process transition logging for the process model version. The lines for the path that
was actually taken will appear in bold.
Important! If you regenerate a process model version, the logging settings return to the
default values, and you will have to reset them if you want different settings.
1 In My webMethods:
Administration > Business > Business Processes
2 Find the process model version you want to work with and then click Edit Configuration
Details.
3 On the Process Quality of Service Settings tab, click one of the Logging Level values
described in the table below. When choosing the logging level to use, consider what
you want to be able to do from Monitor later, as indicated by the table’s middle three
columns.
If a process instance will send data about its steps to Optimize, you must set the
logging level to 5 - Process and all steps.
You want to log... And you want to do this in Monitor... Set to...
View View
process step Resubmit a
status? status? process?
Nothing (that is, disable process No No No 1 - None
logging)
Process status when steps fail At No At failed 2 - Errors
failed step only
Input pipelines for failed steps step
Run‐time values for document
fields
Process status Yes No At failed 3 - Process
step only
Input pipelines for failed steps
Run‐time values for document
fields
Optionally, transitions
Process status and start step Yes For At start or 4 - Process
status start failed step and start
step steps
Input pipelines for start steps
and failed steps
Run‐time values for document
fields
Optionally, transitions
Process status and all step Yes For all At any 5 - Process
statuses steps step that and all
has logged steps
Input pipelines for every step input
Run‐time values for document pipeline
fields
Optionally, transitions
4 If you chose a logging level that allows you to log transitions, and you want to do so,
scroll right and select the Log Transitions check box.
5 If you chose a logging level that logs input pipelines for process steps, the Step Quality
of Service Settings tab lists those steps. Select the Resubmit Enabled check box for each
step at which you want to be able to resubmit process instances.
6 Click Save.
Note: When coordinating logging, keep in mind that when a service is run by a process
step, that service is actually called by a wrapper service, making it a nested service (as
opposed to a top‐level service).
For instructions on setting up service logging, and for complete information on logging in
general, see the webMethods Logging Guide.
Note: Before you can delete a webMethods‐executed process model version, you must first
disable that process model. For instructions, see “Enabling and Disabling Process Model
Versions” on page 102.
1 Search for the unused process models you want to delete. For instructions, see
“Searching for Process Models That Are Available for Monitoring” on page 93.
2 In the search results, select the check boxes beside the unused process models that you
want to delete.
3 Click Delete.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Overview
Software AG recommends that you remove data from the IS Core Audit Log and the
Process Audit Log database components on a regular basis to maintain your logging
database at peak performance. To remove data, you can either archive or delete it:
When you archive, the data is removed from the database components after it is moved
to the Archive database component.
When you delete, the data is removed from the database components, but not moved to
any other location.
Because Monitor reads the data that it displays from the IS Core Audit Log and Process
Audit Log database components, after you archive or delete data, you can no longer view
that data in My webMethods. However, if you archive the data, you can still query the
Archive database component using SQL statements.
The following table lists the methods that you can use to archive or delete document,
process, server, and service data from the IS Core Audit Log and the Process Audit Log
database components:
Archiving is an asynchronous operation and should have little system impact, but stored
procedures are especially useful for preserving Integration Server resources in
high‐volume situations.
Requirements
Before you can archive data, you must set up the Archive database component. For
instructions, see “Setting Up to Archive Data” on page 36.
To archive or delete from My webMethods, an administrator must configure:
My webMethods to allow access to the My webMethods pages for archiving and
deleting data. For more information, see “Granting Users Access to the My
webMethods Monitoring Pages” on page 25.
Whether you can archive data. For more information, see “Granting Users the
Ability to Perform Monitor Actions” on page 27.
Items to Consider
Optionally configure the number of days of audit information that Monitor should
retain when performing an archive operation. The default is 14 days. For instructions,
see “Setting Up to Archive Data” on page 36.
If you use an Oracle database, you can identify one or more people to receive e‐mail
alerts when the Oracle Purge operation completes. For more information, see the
webMethods Optimize for Process Administrator’s Guide
1 In My webMethods:
Administration > Business > Data Management > Archive Audit Data
2 Specify the age of the data that you want to retain in the IS Core Audit Log and the
Process Audit Log database components. Data that is older than the retention period
that you specify is archived or deleted.
Option Description
Note: Processes and services have a start timestamp and an end timestamp; Monitor
archives or deletes them based on the end timestamp. Documents and server data
have a single timestamp, and Monitor archives or deletes them based on that
timestamp.
3 Select the check boxes for the types of data to archive or delete.
Processes Process log entries, input pipelines, error data, and
run‐time values for user‐specified input and output
document fields.
Referenced processes, process‐related service data
(services, service error data, and user‐defined messages).
Process control data (resubmit, suspend, and resume
actions).
Services Service log entries, input pipelines, error data, user‐defined
messages, and service control data (resubmit actions).
Note: Monitor can archive user‐defined messages for a service
only if customized logging is set up for the service in
Developer. That is, if service logging is globally enabled in
Integration Server but customized logging is not set up for the
service in Developer, Monitor cannot archive used‐defined
messages written by the service.
Documents Logged documents for all Broker clients and document control
data (resubmit actions).
Server Data Integration Server server, session, and guaranteed delivery log
entries, and error log entries that are not associated with logged
processes, services, or documents (for example, errors that
occur during startup or during the run of unlogged processes,
services, activations, and documents).
4 Select the check boxes to indicate the status of the data that you want to archive.
Monitor will archive or delete only data with that status. The status check boxes are
available only for processes and services. Because documents and server data do not
have statuses, you cannot use status as a basis for archiving.
Option Description
COMPLETED Archives or deletes logged data for processes or services
whose status is Completed.
COMPLETED-FAILED Archives or deletes data for services whose status is
Completed, Failed, or Resubmitted, or for processes whose
status is Completed, Failed, Stopped, or Resubmitted.
5 Indicate the number of primary items and accompanying items to archive or delete at
a time in the Archiving Batch Size box. For example, you might want to archive or delete
100 processes and accompanying services, activity logs, and errors at a time. Choose a
number that takes the size of each record and other performance factors into
consideration. If the record size is large, consider reducing the batch size; if the record
size is small, increasing the batch size might increase the speed of the archive or
delete.
6 Indicate whether to archive or delete the data by clicking one of the following:
Option Description
Note: For Oracle, SQL Server, and DB2, the default values for all archive and delete service
parameters are stored in the OPERATION_PARAMETER in the Archive database
component. You can change the defaults in the table by running the
pub.monitor.archive:setOperationParameters service. You can override the defaults for specific
archive or delete actions by specifying values on the relevant parameters when you run
the archive and delete services.
Procedure Description
Oracle: Archives or deletes documents logged for
DOCUMENT_ARCHIVE.START_ Broker clients from the WMDOCUMENT table
DOCUMENTARCHIVE in the IS Core Audit Log database and
document control data (such as resubmit
SQL Server and DB2: actions) from the WMCONTROL table in the
DOCUMENT_ARCHIVE_START_ Process Audit Log database.
DOCUMENTARCHIVE
Oracle: Archives or delete process data and control
PROCESS_ARCHIVE.START_ data (such as resubmit actions) from the
PROCESSARCHIVE WMCONTROL,
WMCUSTOMFIELDDEFINTION,
SQL Server and DB2:
WMCUSTOMPROCESSDATA, WMPROCESS,
PROCESS_ARCHIVE_START_
WMPROCESSASSOC,
PROCESSARCHIVE
WMPROCESSDEFINITION,
WMPROCESSIMAGE, WMPROCESSRECENT,
WMPROCESSSTEP, WMSTEPDEFINITION,
and WMSTEPTRANSITIONDEFINTION tables
in the Process Audit Log database component,
and archives or deletes process‐related service
data from the WMSERVICEACTIVITYLOG,
WMSERVICE, and WMERROR tables in the IS
Core Audit Log database.
Procedure Description
Oracle: Archives or deletes server data from the
SERVER_ARCHIVE.START_ WMERROR, WMSESSION, WMTXIN, and
SERVERARCHIVE WMTXOUT tables in the IS Core Audit Log
database.
SQL Server and DB2:
SERVER_ARCHIVE_START_
SERVERARCHIVE Note: Archiving server data archives only
top‐level errors. To archive lower‐level errors
associated with services or processes, you must
first archive those services or processes.
Oracle: Archives or deletes service log entries, input
SERVICE_ARCHIVE.START_ pipelines, error data, and user‐defined
SERVICEARCHIVE messages from the WMSERVICE, WMERROR,
and WMSERVICEACTIVITYLOG tables in the
SQL Server and DB2: IS Core Audit Log database and service control
SERVICE_ARCHIVE_START_ data (such as resubmit actions) from the
SERVICEARCHIVE WMCONTROL table in the Process Audit Log
database.
Parameters
ARCHIVE Default. Copy the data from the source database
component to the Archive database component and
delete the data from the source database component.
DELETE Delete the data from the source database component.
2 Archive or delete data for processes or services whose
status is Completed.
4 Archive or delete data for processes or services whose
status is Failed.
1024 Archive or delete data for processes whose status is
Stopped.
32768 Archive or delete data for processes and services whose
status is Resubmitted.
32776 Archive or delete data for services whose status is
Activity.
p_batchsize String Number of primary items and accompanying items to archive or
delete at a time. For details, see step 5 on page 114 in “Archiving or
Deleting Logged Data from My webMethods”.
Usage Notes
p_batchsize parameter: Suppose you want to archive or delete 100 processes and
accompanying services, activity logs, and errors at a time. Choose a number that takes
the size of each record and other performance factors into consideration. If the record
size is large, consider reducing the batch size; if the record size is small, increasing the
batch size might increase the speed of the archive or delete.
Examples
p_retaindays parameter: Suppose today’s date is September 30 and you want to archive
or delete data for services that finished running more than 15 days ago (that is, before
September 15). You would specify this parameter as 15.
In My webMethods, go to Administration > Business > Data Management > Archive Audit Data
Results.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Overview
The following table lists the reports that you can view and where to find instructions for
how to generate each report:
Additionally, you can create reports using Third‐Party reporting tools. For more
information, see “Using Third‐Party Reporting Tools” on page 131.
See “Before You Can Generate Reports” on page 121 for information about setup that is
required before you can use Monitor to generate reports and the permissions you need to
generate reports from My webMethods.
Important! Report generation can be a processing‐intensive action. Depending on the
amount of data in the database, it can take several minutes to view the resulting report.
You might want to limit the requested data sets as much as possible.
The time period for which to generate the report
An aggregation period to identify how you want Monitor to summarize the process
instances, that is, daily, weekly, monthly, quarterly, or yearly
The generated report will include one section for each process model that you select. In
each section for a process model, each row represents a single aggregation period.
For example, if you select two process models, Model1 and Model2, a time period of a
year (e.g., January 1 to December 31), and a quarterly aggregation period, the generated
report would include two sections, one for Model1 and a second for Model2. In the
Model1 section, there would be four rows. Each row would represent a summary of all
instances that occurred during one quarter of the year (e.g., one row summarizing the
instances that occurred January through March, a second row summarizing the instances
that occurred April through June, a third row summarizing the instances that occurred
July through September, and a fourth row summarizing the instances that occurred
October through December).
Model The process models for the process instances to include in the
report. The list in the Model field contains all models that are
available for execution. You can select multiple models. If you do
not select any models, the report contains information for all
models.
Note: You cannot generate an Instance Summary Report for a
specific version of a process model. Monitor generates the report
for all versions of the selected models.
Aggregation The aggregation period for the report. You can set the aggregation
period to Daily, Weekly, Monthly, Quarterly, or Yearly.
Range The time period for the report. Specify the date and time
information was logged for the process instances you want
included in the report. To specify the range, you can either:
Click a predefined time period from the Range list.
4 Click Go.
For more information about saving the report criteria to re‐use at a later time, see
information about saving search criteria in the Getting Started with My webMethods
guide.
Note: Only the first iteration of a process instance is shown in the Instance Summary
Report.
To view a status-specific report for a process instances in a Started, Completed, or Failed status
1 Create a Instance Summary Report that includes the process instances for which you
want to view a status information. For instructions, see “Generating Reports about
Process Instances” on page 121.
2 In the results of the Instances Summary Report, click the value in a Started, Completed,
or Failed column to view all the instances in the aggregation period that have the
selected status.
Note: Search criteria that you selected when you created the Instance Summary Report is
still in effect for the status‐specific report. For example, if the Instance Summary Report
shows process instances from the last 7 days, the status‐specific report is also filtered by
the same criteria.
1 Create a status‐specific process instance report that includes the process instance for
which you want to view a detail report. For instructions, see “Viewing Reports of
Started, Completed, or Failed Process Instances” on page 123.
2 Locate the process instance for which you want to view a Instance Detail Report and
click the value in the PROCESS INSTANCE ID column.
Note: Search criteria that you selected when you created the Instance Summary Report and
status‐specific report is still in effect for the Instance Detail Report. For example, if the
Instance Summary Report and status‐specific report shows process instances from the last
7 days, the Instance Detail Report is also filtered by the same criteria.
Note: Only the first iteration of a process is shown in the Instance Detail Report.
Note: You cannot generate process model reports for specific model versions.
Number of automated steps, that is steps that require no human involvement, for
example a step that executes a service
Number of human steps, that is a step that represents a task, which a person must
perform
3 In the Model field, select the process models that you want included in the report. You
can select multiple models. If you do not select any models, the report contains
information for all models.
4 Click Go.
For more information about saving the report criteria to re‐use at a later time, see
information about saving search criteria in the Getting Started with My webMethods
guide.
1 Create a Process Models Report that includes the process model for which you want
to view a Step Report. For instructions, see “Viewing a Process Models Report” on
page 125.
2 In the results of the Process Models Report, locate the process model for which you
want to view a Step Report and click the value in the AUTOMATED STEPS, HUMAN
STEPS, or TOTAL STEPS column.
The generated report will include one section for each combination of a user and a task
within a process model. In each section for a user and task, each row represents the user’s
performance of that task during one of the aggregation periods.
For example, the report criteria might specify user Jill, the tasks ReviewOrder and
ApproveOrder that are both in the process model Model1, a time period of one month
(e.g., January 1 through January 31), and a weekly aggregation period. The generated
report would include two main sections, one for Jill’s performance of the ReviewOrder
task and another for Jill’s performance of the ApproveOrder task. Within each section,
each row shows the Jill’s performance of the task during one week of the month.
Note: As tasks are executed, the Task Engine logs information about the task to the Process
Audit Log database component. When the Reporting database component is populated
using the services in the pub.monitor.reporting.processDataMart folder, the services obtain
information that the Task Engine logged. For more information about the Task Engine, see
the webMethods Task Engine User’s Guide. For more information about populating the
Reporting database component, see “Setting Up to Generate Reports” on page 35.
Model The process models that contain the tasks to include in the
report. The list in the Model field contains all models that are
available for execution. You can select multiple models. If you
do not select any models, the report contains information for
all models.
Note: You cannot specify model versions. Monitor generates the
report for all versions of the selected models.
Aggregation The aggregation period for the report. You can set the
aggregation period to Daily, Weekly, Monthly, Quarterly, or Yearly.
Range The time period for the report. Specify the date and time
information was logged for the tasks you want included in the
report. To specify the range, you can either:
Click a predefined time period from the Range list.
Note: The Step field is populated with step names if you select a
model in the Model field.
User The users that you want included in the report.
If you do not select any users, the report contains all users that
are associated with the tasks identified by the report criteria.
Role The My webMethods roles to which the users you want
included in the report belong.
If you do not select any roles, the report contains all roles that
meet the other criteria you specify.
4 Click Go.
For more information about saving the report criteria to re‐use at a later time, see
information about saving search criteria in the Getting Started with My webMethods
guide.
Note: As tasks are executed, the Task Engine logs information about the task to the Process
Audit Log database component. When the Reporting database component is populated
using the services in the pub.monitor.reporting.processDataMart folder, the services obtain
information that the Task Engine logged. For more information about the Task Engine, see
the webMethods Task Engine User’s Guide. For more information about populating the
Reporting database component, see “Setting Up to Generate Reports” on page 35.
3 Define the report criteria:
Model The process models that contain the tasks to include in the
report. The list in the Model field contains all models that are
available for execution. You can select multiple models. If you
do not select any models, the report contains information for
all models.
Note: You cannot specify model versions. Monitor generates the
report for all versions of the selected models.
Aggregation The aggregation period for the report. You can set the
aggregation period to Daily, Weekly, Monthly, Quarterly, or Yearly.
Range The time period for the report. Specify the date and time
information was logged for the tasks you want included in the
report. To specify the range, you can either:
Click a predefined time period from the Range list.
Note: The Step field is populated with step names if you select a
model in the Model field.
User The users that belong to the roles that you want included in
the report.
If you do not select any users, the report contains all users that
meet the other criteria you specify.
Role The My webMethods roles to include in the report.
If you do not select any roles, the report contains all roles that
meet the other criteria you specify.
4 Click Go.
For more information about saving the report criteria to re‐use at a later time, see the
section on saving search criteria in the Getting Started with My webMethods guide.
Stored Procedures
The stored procedures for archiving data from the IS Core Audit Log database
component, Process Audit Log database component, or both to the Archive database
component are listed below.
Procedure Description
Oracle: Archives or deletes documents logged for
DOCUMENT_ARCHIVE.START_ Broker clients from the WMDOCUMENT table
DOCUMENTARCHIVE in the IS Core Audit Log database and
document control data (such as resubmit
SQL Server and DB2: actions) from the WMCONTROL table in the
DOCUMENT_ARCHIVE_START_ Process Audit Log database.
DOCUMENTARCHIVE
Oracle: Archives or delete process data and control
PROCESS_ARCHIVE.START_ data (such as resubmit actions) from the
PROCESSARCHIVE WMCONTROL,
WMCUSTOMFIELDDEFINTION,
SQL Server and DB2:
WMCUSTOMPROCESSDATA, WMPROCESS,
PROCESS_ARCHIVE_START_
WMPROCESSASSOC,
PROCESSARCHIVE
WMPROCESSDEFINITION,
WMPROCESSIMAGE, WMPROCESSRECENT,
WMPROCESSSTEP, WMSTEPDEFINITION,
and WMSTEPTRANSITIONDEFINTION tables
in the Process Audit Log database component,
and archives or deletes process‐related service
data from the WMSERVICEACTIVITYLOG,
WMSERVICE, and WMERROR tables in the IS
Core Audit Log database.
Procedure Description
Oracle: Archives or deletes server data from the
SERVER_ARCHIVE.START_ WMERROR, WMSESSION, WMTXIN, and
SERVERARCHIVE WMTXOUT tables in the IS Core Audit Log
database.
SQL Server and DB2:
SERVER_ARCHIVE_START_
SERVERARCHIVE Note: Archiving server data archives only
top‐level errors. To archive lower‐level errors
associated with services or processes, you must
first archive those services or processes.
Oracle: Archives or deletes service log entries, input
SERVICE_ARCHIVE.START_ pipelines, error data, and user‐defined
SERVICEARCHIVE messages from the WMSERVICE, WMERROR,
and WMSERVICEACTIVITYLOG tables in the
SQL Server and DB2: IS Core Audit Log database and service control
SERVICE_ARCHIVE_START_ data (such as resubmit actions) from the
SERVICEARCHIVE WMCONTROL table in the Process Audit Log
database.
Parameters
ARCHIVE Default. Copy the data from the source database
component to the Archive database component and
delete the data from the source database component.
DELETE Delete the data from the source database component.
2 Archive or delete data for processes or services whose
status is Completed.
4 Archive or delete data for processes or services whose
status is Failed.
1024 Archive or delete data for processes whose status is
Stopped.
32768 Archive or delete data for processes and services
whose status is Resubmitted.
32776 Archive or delete data for services whose status is
Activity.
p_batchsize String Number of primary items and accompanying items to archive or
delete at a time. For details, see step 5 on page 114 in “Archiving or
Deleting Logged Data from My webMethods”.
Usage Notes
p_batchsize parameter: Suppose you want to archive or delete 100 processes and
accompanying services, activity logs, and errors at a time. Choose a number that takes
the size of each record and other performance factors into consideration. If the record
size is large, consider reducing the batch size; if the record size is small, increasing the
batch size might increase the speed of the archive or delete.
Examples
p_retaindays parameter: Suppose today’s date is September 30 and you want to archive
or delete data for services that finished running more than 15 days ago (that is, before
September 15). You would specify this parameter as 15.
Index
A authorization
access privileges, description 15 accessing My webMethods pages 15
accessing Monitor via My webMethods 13
actions, Monitor C
documents 59 Central Users
list of actions 12 configuring 21
process instances 81 description 21
process models 100 enabling 21
process steps 85 configuring 25, 27
resubmitting documents 60 access privileges
resubmitting process instances 87 documents pages 27
resubmitting services 49 pages for archiving and deleting 26
resuming process instances 87 process instances pages 26
services 48 process model pages 25
stopping process instances 86 reports pages 27
suspending process instances 86 services pages 26
advanced search archiving and deleting data 17
documents 54 Central Users 21
process instances 72 data level security 31
process models 94 documents roles can act on 34
services 42 enabling 31
analysis enabling process models 104
processes roles can act on 32
Archive database component
services roles can act on 33
DBlink to IS Core Audit log 36
database component connection retries 24
DBlink to Process Audit log 36
functional privileges
setting database permissions 37
actions against documents 29
archiving and deleting data
actions against process instances 28
accessing tasks in My webMethods 16
actions against services 29
configuring 17
archiving and deleting data 30
allowing users to perform 30
Integration Server hosting WmMonitor package 23
allowing users to view pages 26
Integration Server My webMethods interacts with 23
Archive Results Day 37
My webMethods access privileges 25
from My webMethods 112
My webMethods functional privileges 27
methods 110
reason to 110 conventions used in this document 7
requirements for 111
setup before you can generate 17 D
using built-in services 114 data level security
using stored procedures 115 configuring Monfitor for 31
viewing results 117 definition 30
U
user interface, My webMethods 13
V
viewing
document details 58
Instance Detail Report 124
Instance Summary Report 122