Transaction Viewer examples using RBM - IBM Websphere

Here, we show several examples of the RBM policies and their effect on the B2B Transaction Viewer.

XML Management Interface

Currently, there is no support for XML Management Interface support for the B2B Transaction Viewer.

Command line interface(CLI)

Currently, there are no active CLI commands for the B2B Transaction Viewer.

WebGUI interface

The following examples illustrate the functionality of the RBM policies and their effect on the B2B Transaction Viewer. The user will be able to view specific data for explicitly defined columns, partners, and actions.

Column visibility examples
Example below shows the policy string format for column visibility.

Column-visibility RBM access policy defines access to specific columns

the access policies for a user group that defines the columns available to partner2.

User group access policy that explicitly allows column visibility to specific column data

User group access policy that explicitly allows column visibility to specific column data

Columns can be explicitly set to be visible in the access policy. Columns not explicitly defined will not be visible. the B2B Transaction Viewer displays the columns for TransactionID, TransactionSetID, GatewayName, SenderID, and ReceiverID for Partner2 as defined.

B2B Viewer showing explicitly defined columns

B2B Viewer showing explicitly defined columns

the format for the B2B policy string that restricts column visibility for specific columns.

B2B policy string that restricts column visibility for specific columns

displays the user group with the access policy string in Example below that explicitly denies visibility to specific columns.

User group access policy that explicitly restricts access to specific column data

User group access policy that explicitly restricts access to specific column data

this shows the B2B Viewer result set that displays explicitly restricted column data for a user group.

B2B Viewer showing explicitly restricted columns

B2B Viewer showing explicitly restricted columns

Partner visibility examples
This section shows examples that use the b2b/partner-visibility access policy.

this shows the structure of the access policy string for the partner-visibility resource that gives access to users xxxxxx and yyyyyy.

B2B policy strings that grant specific partner visibility

this shows the access policies for the user group that define the data set specific to partner2 and zzpartner2.

User group access policy explicitly allowing access to all columns for partner2 and zzpartner2 data

User group access policy explicitly allowing access to all columns for partner2 and zzpartner2 data

this shows the B2B Viewer result set for data specific to partner2 and zzpartner2 only.

B2B Viewer showing result set for partner2 and zzpartner2

B2B Viewer showing result set for partner2 and zzpartner2

Controlling access to operations examples
This section shows examples that use the b2b/resend-transaction and b2b/get-document access policies.

this shows the access policy structure for defining the b2b/resend-transaction and b2b/get-document access policies.

B2B policy string that controls B2B operation

Limiting the access to various operations controls whether the user can perform specific B2B Viewer actions. Unless explicitly defined, the user cannot perform the action. this shows resend transaction access and get document access granted for the partners partner2 and zzpartner2. the B2B Viewer displaying Show Document and Resend Document actions.

User group access policy explicitly allowing resend transactions and get document actions

User group access policy explicitly allowing resend transactions and get document actions

B2B Viewer showing Show Document and Resend Document actions

B2B Viewer showing Show Document and Resend Document actions

Working with transactions in the B2B Viewer

After accessing the B2B Transaction Viewer, you can perform the following actions:

  • Control the number of transactions to display per page.
  • Define a query statement to filter which transactions to view.
  • Resend transactions that did not complete.

Controlling display limitsIn the viewer, use the Page Size list to control the number of transactions to display on each page. The default value is 50.Filtering transactionsTo display transactions that match a specific criteria, modify the query statement.

Modifying the query statement
To modify the query statement, use the following procedure:

  1. Click Modify Query.
  2. Use the fields to define the query statement, as needed. For information about the data, refer to “Data to modify the query statement”.
  3. Click Update Query.

The viewer refreshes to display only the transactions that match the criteria in the query statement.

Data to modify the query statement
The control at the top of the query page filters the query results based on the processing status of the transaction. You can filter based on all transactions, successful transactions, or failed transactions. The viewer shows the processing status for transactions in the Results Code column. Values used to modify the query statement are entered as string values:

  • Transaction ID: The identifier for a specific transaction. Specify the gateway-generated identifier as shown in the viewer to limit transactions to the specific transaction.
  • Sender Name: The name of a specific sender of B2B messages. The name is the name of the partner as defined in the B2B Partner Profile object. Specify the name of the partner as defined in the B2B Partner Profile object to limit transactions to the specific sender.
  • Receiver Name: The name of a specific receiver of B2B messages. The name is the name of the partner as defined in the B2B Partner Profile object. Specify the name of the partner as defined in the B2B Partner Profile object to limit transactions to the specific receiver.
  • Gateway Name:The name of a specific B2B Gateway object. Specify the name of the B2B Gateway object to limit transactions to the specific gateway.
  • MDN: The status of the MDN. Valid values are 0 or 1.
  • Input Timeframe: The time interval during which the gateway received the transaction:
  • Specify a start and end time to limit transactions to the explicit interval.
  • Specify a start time only to limit transactions from the start time onward.
  • Specify each aspect of the time frame using the format as shown in the viewer. You cannot specify an end time only.
  • Output Timeframe:The time interval during which the gateway sent the transaction:
  • Specify a start and end time to limit transactions to the explicit interval.
  • Specify a start time only to limit transactions from the start time onward.
  • Specify each aspect of the time frame using the format as shown in the viewer. You cannot specify an end time only.

Modify Query window

Modify Query window

Resending transactions To resend transactions, use the following procedure:

  1. Select the transactions to resend.
  2. Click Resend Selected.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Websphere Topics