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.
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
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
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
this shows the B2B Viewer result set that displays explicitly restricted column data for a user group.
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
this shows the B2B Viewer result set for data specific to partner2 and zzpartner2 only.
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
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:
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:
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:
Modify Query window
Resending transactions To resend transactions, use the following procedure:
IBM Websphere Related Tutorials
|IBM DB2 Tutorial|
IBM Websphere Related Interview Questions
|IBM DB2 Interview Questions||Weblogic Interview Questions|
|IBM WebSphere Datapower SOA Appliances Interview Questions||IBM WAS Administration Interview Questions|
|IBM Websphere Application Server Interview Questions||IBM WebSphere MQ Interview Questions|
|WebLogic Administration Interview Questions||IBM DataPower Interview Questions|
|Ibm Websphere Message Broker Interview Questions||Ibm Websphere Cast Iron Interview Questions|
|Ibm Websphere Process Server Interview Questions|
Ibm Websphere Tutorial
B2b Technologies And Standards
B2b Deployment Methodology
Aspects Of B2b Security
Websphere Datapower B2b Appliance Xb60
Device Setup And Administrative Tasks
B2b Configuration Options
Troubleshooting The Appliance
Xb60 And Wtx Integration For Hipaa
Xb60 With Transformation
Trading Outbound Binary Documents Using The B2b Gateway Service
Trading Binary Documents Using A Multi-protocol Gateway Service
Handling Soap Messages With Attachments In A B2b Environment
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.