Activity Logs
No subtopics in thissection
Information about all activities within IBM webMethods B2B such as, documents exchanged, deployment activities, and archival and purge changes are available on the Activity logs page. You can view and monitor the sequence of activities related to a IBM webMethods B2B account. Monitoring activity logs enables you to track the activities within IBM webMethods B2B, detect and analyze errors and thus work towards fixing them.
The Logs > Activity logs page includes the log records for:
- All deployment related activities. This includes actions related to asset movement such as, import or export of assets and creation of deployments.
- All general activities such as, updating the archival rule, and creating and deleting a purge rule.
- All transactional activities related to document submission and exchange.
- Any creation, or modifications of assets such as partner, document, processing rule, channel, partner user, document attribute, and field groups.
By default, Activity logs page displays information for Deployment logs.
For each of the logs, you can apply the following filters:
- 24H. Displays activities in the last 24 hours. This is the default option.
- 7D. Displays activities in the last seven days.
- 30D. Displays activities in the last 30 days.
- Set custom range. Provide a custom date range along with the timestamp to view the activities in the specified date and time range.
For each of the logs:
- You can sort the data based on the date and event.
- Use the search box to search for specific activity by the typing a keyword related to the required activity. For example, to view all the error logs, type error in the search bar. Similarly, to view all the successful events, type success in the search bar.
The color-codes to indicate activity logs entries are as follows:
- Red. Indicates an error in the activity logs. For example, if a partner configured as a receiver of a document is inactive.
- Orange. Indicates a warning in the activity logs. For example, when attribute transformation fails for extracted attributes which are not required to be defined in a business document.
- Green. Indicates an error in the activity logs. For example, if an archival process has completed.
Activity logs cannot be deleted.
Type of Logs
General logsTransaction logsDeployment logsAudit logsGeneral logs
Information about general activities of in IBM webMethods B2B is available in the General logs section of Activity logs page. This page displays general information such as, archival and purge related activities. For logs related to specific activities, see Transaction logs and Deployment logs.
The General logs section displays the following details:
Field | Description |
---|---|
Date | Timestamp when the action was performed on the deployment. |
Event | Message informing the action performed. |
Performed by | Name of the user who performed the action. |
Actions | Actions that you can perform. Click to view the details of the selected activity. |
Transaction logs
A global view of all transactions occurring in IBM webMethods B2B related all partners and document types, is available in the Transaction logs section of Activity logs page.
You can view available transactions of all partners.
The Transaction logs section displays the following details:
Field | Description |
---|---|
Date | Timestamp when the document was received. Click the timestamp to view the transaction status of the group to which the selected transaction belongs. Clicking the timestamp opens the Course of transaction section of the Transaction summary page. |
Event | Action performed on the document or the status of transaction. Some of the possible events are:
For details on possible events, see Viewing Transactions. |
Performed by | Name of the user who performed the transaction. |
Actions | Actions that you can perform. Click to view the details of the selected transaction. |
Deployment logs
You can monitor the status of deployments across all the users and roles that create them, in the Deployment logs section of Activity logs page.
The Deployment logs section displays the following details:
Field | Description |
---|---|
Date | Timestamp when the action was performed on the deployment. |
Name | Name of the deployment. |
Event | Action performed on the deployments. Some possible events are:
|
Performed by | Name of the user who performed the action. |
Source | Name of the environment from where the deployment set was published. Note
If you see (current) in the Source environment column, it indicates that the source environment is the environment to which you have currently logged-in to.
|
Target | Name of the environment to which the deployment was published. Note
If you see (current) in the Target environment column, it indicates that the target environment is the environment to which you have currently logged-in to.
|
Actions | Actions that you can perform. Click to view the details of the selected deployment. |
Click Inbound or Outbound tab to view the incoming or outgoing deployment details respectively.
Audit logs
You can monitor the creation and modification of assets and other activities performed by the users in your system.
The Audit logs section displays the following details:
Field | Description |
---|---|
Date | Timestamp when the user action was performed. |
Asset Type | Type of asset that participated in the activity. |
Event | Action performed by the user. Some possible events are:
|
Performed by | Name of the user who performed the action. |
Details | Details of the activity. |
Downloading Transactions and Other Activity Logs
SummaryBasic FlowNext StepsSummary
The Activity logs page lets you download the activity logs such as documents exchanged, the deployment activities, and archival and purge logs in your instance.
The logs are downloaded in a .csv file in compressed (.zip) format and for the duration of the download.
If you use Microsoft Excel to open the .csv file, to view the downloaded transactions, the leading zeroes are trimmed for the Document IDs column.
The size of each downloaded log file is limited to 25MB.
Basic Flow
To download logs:
- In IBM webMethods B2B, go to Logs > Activity logs.
Select the type of log you want to download and click
You can download audit logs, general logs, deployments, or transaction logs based on a date range or duration range such as 24 hours, 7 days, 30 days, or use a custom range as highlighted in the following image. You can also search for a string in the search bar within a specific date range and download only those transactions.
Next Steps
The downloaded file appears in the folder configured for all the downloads on your browser.
Managing Notifications
User PermissionsSearching for NotificationsSubscribing to NotificationsIBM webMethods B2B notifies you of activities or events occurring in the system, which may need your attention when you click on the on the upper-right corner of your screen. You can search for notifications that are not more than 30 days old. You can configure the notification retention in the Settings menu under Runtime options. For information, see Configuring Runtime Options.
You can subscribe to notifications of the following type:
- Alerts about the database storage limit you configured.
- Expiring subscriptions (applicable only to trial license).
- Alerts about transactions processed with errors.
- Any event-driven notification such as an integration being invoked.
- Expiring certificates.
You can subscribe to notifications of the following categories for any type of message severity:
- Transactions. Any message pertaining to transaction activity.
- Communications. Any message pertaining to establishing connections with other webMethods products, external, or third-party software.
- Systems. Any system message such as expiring licenses. You cannot unsubscribe alerts of this type.
- Assets. Any asset-related messages such as expiring certificates.
Each notification displays the date and time at which the event occurred. You can:
Expand the alert to get a detailed update.
Navigate to see the alert in the context of its occurrence. For example, automatically navigating to the transactions listing page for a failed transaction on clicking the alert.
Search for a notification using any word that occurs in its headline or description in the Notifications listing page.
Mark all notifications as read. When you click on the icon to see the notifications, these will be marked as read.
View similar alerts being grouped together. A count indicator appears for such alerts.
Identify the severity of the message with the color codes. Deep red for critical errors, red for errors, orange for warnings, and blue for information.
User Permissions
You must have administrator permissions to make the changes to the notification options in the Runtime options page.
Searching for Notifications
You can search for a notification on the Notifications listing page.
- In IBM webMethods B2B, go to Logs > Notifications.
Type a word in the headline or the description of the notification to search for it, using the following search filters:
Search Filter Description 24H Displays transactions in the last 24 hours. 15D Displays transactions in the last 15 days. This is the default option. 7D Displays transactions in the last seven days. Custom Provide a custom date range along with the timestamp to view the transactions in the specified date and time range. Category Search for notifications that belong to a certain category. The available categories are: Transactions, Communications, Systems, and Assets. Severity Search for notifications that belong to a certain severity. The available severities are: Critical, Error, Warning, and Information. Filters Apply filters such as category and severity. Mark as read Click on the mail icon to mark all the notifications as read.
Subscribing to Notifications
A few options allow you to customize the notifications you receive.
- In IBM webMethods B2B, go to Settings > Runtime options.
- In the Select type drop-down box, select General > Notifications.
- Configure the notification subscription and behavior. See Configuring Runtime Options for the description of each notification alert.