Each of the DataPower services available in the XB60 device has built-in features andfunctionality to handle many types of transactions and protocols that can be used to route data. Because the XB60 was built on top of our core Application Integration appliance, the XB60 has many services that are application integration services in nature. We only discuss the B2B-specific services and objects.
From the Control Panel under B2B, there are three shortcuts specifically for B2B:B2B Partner Profiles, B2B Gateway Service, and B2B Transaction Viewer. This section will briefly describe each function.
Control Panel view of B2B objects B2B Partner Profiles
The B2B Partner Profile is the configuration object where the trading partner information is defined. This information includes the profile name, profile type, business IDs, AS security, destinations for document routing, and contact information.
A trading partner is either an internal or external trading partner based on the understanding that an internal trading partner exists within the corporate enterprise and an external trading partner exists outside of the enterprise.
Trading partners have unique business IDs. However, if a profile is defined as internal, that trading partner might also have the same business ID defined in their external definition, because an internal trading partner and an external trading partner are different objects.
Whether a trading partner is internal or external also affects the options under the AS Security tab. Internal profiles will only use private security credentials, and external profiles will only use public security credentials. When you trade documents between two hubs, the internal profile is the private side of the profile and contains private keys, and the external profile is the public side of the profile and contains only public certificates. depicts how the hub owner’s private side of the profile is stored on the owner’s B2B hub and communicates with the public side of the owner’s profile, which is stored on the partner’s B2B hub. The partner’s B2B Gateways will also work in the same manner.
Internal and external profile linkage
The B2B Partner Profile contains four tabs that are used for service configuration: Main, AS Security, Destinations, and Contacts tabs.
The Main tab
The main tab identifies the name of the profile, the Admin State (enabled or disabled) that allows the profile to be used in a B2B Gateway object, the Profile Type (internal or external), and the Partner Business IDs associated with the profile.
The Business IDs must be equivalent to identifiers that are expected in the transactions, such as:
Main tab: Internal partner profile
The AS Security tab
Internal profile AS Security tab
For external profiles, AS security is optional, but if used, the AS Security tab contains a place for credentials to be used to verify signatures and validate signature certificates from the partner. External profiles use public certificates:
Note:Although this setting controls whether to sign outbound messages, the Send Messages Unsigned property in the Partner Profile Destinations tab can override this setting. You override this setting if you have selected partners who do not require signatures.
External profile AS Security tab
The Destinations tab
Message destinations define the routing information for the partner. The first destination is the default destination. The gateway uses the default destination when no specific destination is selected from within the B2B Gateway. If the destination protocol is AS, AS attributes can be configured to support security, MDNs, transaction time to live, and resend logic. B2B partner profiles can have multiple destinations. For those individuals familiar with DataPower terminology, it might be helpful to think of internal partner destinations as a “Backend URL. ”
Tip: An internal partner profile can have multiple destinations defined, but the first entry in the list will be the default destination. To change the default destination, move the desired destination up to the first position.
When you select the Destinations tab, you will be presented with the Destinations list view as seen in Figure below. From this view, you can create a new destination by clicking Add or by editing an existing destination by clicking the pencil to the right of the destination.
Destinations list view
When you click Add, you are presented with a Destinations detailed view where you can configure attributes related to your destination of choice (refer to Figure below). The XB60 provides a wide range of destinations from which to select. Supported destinations are:
In addition, you must provide:
Destinations detailed view
The Contacts tab
The contacts section allows contact information to be entered for the profile. To create one or more contact records, enter information into the the provided fields. The Contact tab is optional; it is not meant to be treated as a contact manager but rather to provide the users of the system with the ability to store contact information about key technical people who are responsible for data that is sent or received to that profile.
B2B Gateway Service
A B2B Gateway Service is an object that defines the characteristics of B2B transaction processing and the association of trading partners allowed to trade data with the B2B Gateway. The B2B Gateway Service includes handling AS2 and AS3 data flows as well as the generation and consumption of the MDNs that are associated with each transaction. If you click B2B Gateway Service → Add, a new B2B Gateway template is displayed.
An example of the new service is depicted.
New B2B Gateway Service
The B2B Gateway Service contains four tabs that are used for service configuration: the Main, Archive, XML Format, and Advanced tabs. In this section, we discuss the properties of each tab in detail.
The Main tab of the service contains the general configuration parameters, such as what protocol or protocols this service will accept and what partner or partners are allowed to access this service. The mandatory fields are:
The supported Front Side Protocol Handlers for the B2B Gateway Service are:
_ Active Partner Profiles: Partner definitions, such as AS security, business IDS, destinations, and contact information can be predefined in the Partner Profile section. When defining a B2B Gateway Service with message routing, you can simply select a preexisting internal or external trading partner relevant to the message flow or a new profile can be created within the B2B Gateway.
The archive mode is a required gateway configuration item. There are two modes of archiving: Archive and Purge or Purge only. the mandatory fields for the archive configuration when the archive mode is “Archive and Purge” are:
Archive and Purge mode
there are no mandatory fields for the archive configuration when the archive mode is “Purge. ” The three basic configuration parameters are:
Purge Only mode
Each B2B Gateway object has an Archive tab and can be independently configured to archive documents and metadata before purging or to purge the documents without archiving. As a best practice, we recommend that a remote file server (transferred through HTTPS or FTP) or a mounted iSCSI or NFS be used to store archived data. The relevant settings are (and can be seen in the example in Figure below):
B2B Archive and Purge example
XML Formats tab
The XML Formats tab is used to allow the user to configure the XPATH statements that are needed to find the Sender and Receiver information from incoming XML documents. Sender and Receiver IDs are needed to properly route XML documents through the B2B Gateway Service. The XML Formats tab has one parameter called XPath Routing Policies. The XPath Routing Policies contain the xpath statements used to extract the Sender ID and Receiver ID. The appliance has a built-in XPATH Tool that can easily build the statement used in this policy. These xpath routing policies can be shared by other B2B Gateway Services in the application domain.
The Advanced tab on the B2B Gateway contains global settings for the B2B Gateway:
External partner AS2 asynchronous MDN destination
B2B Transaction Viewer
The XB60 brings a new generation of transaction viewing capabilities to the DataPowerappliance concept. In the XB60, all data that flows through a B2B Gateway Service is displayed in an easy to read, at a glance viewer where users can see the status of their B2B transactions. Because we have to monitor the state in the B2B Appliance to support industry standard B2B messaging protocols, we needed the capability to easily monitor that state without having to navigate large log files. In the addition to being able to monitor B2B transactions, the B2B Transaction Viewer gives the user the ability to manually resend transactions and view “off-the-wire” files as well as viewing the decrypted payload and the MDN. Because the payloads by default are stored in the encrypted portion of the RAID volume, the only way to see them in the clear is with the appropriate permissions in the B2B Transaction Viewer or after they are archived off of the device.
The B2B Transaction Viewer can be configured to allow an external client access to only transaction (row) specific data, for example, to only transactions related to a particular partner ID. The transaction viewer can also limit the following: view access to the columnar metadata, view access to transaction message documents, and the ability to resendtransactions. These options will be outlined in “Manage transaction viewing with RBM”.
Enabling transaction viewing for external partners
The Web B2B Viewer Management Service can be set up and enabled to allow external partners access to view transactions. You will need to log in as admin in the default domain to configure this service.
To configure browser access to the viewer, use the following procedure:
The default is 600.
Manage transaction viewing with RBM
The XB60 Transaction Viewer allows controlled access to transaction data by authorized user accounts. This access is controlled by the XB60 administrator using the standard DataPower Role Based Management (RBM) functionality.
This section will outline RBM techniques for limiting authorized user account access to data through the implementation of user groups. These user groups define the rights that the user has to the DataPower B2B Viewer resource with respect to column visibility, partner visibility, and send/view actions.
Viewing transactions starts with creating user accounts for the B2B Transaction Viewer. The user account will allow the user to log in to the B2B Transaction Viewer browser. User accounts can be assigned to a predefined group upon creation.
User account list
Managing user group accounts
A user group represents a collection of users who perform similar duties and require the same level of access to the Data Power appliance. User groups are assigned rights to one or more DataPower resources. When adding these rights to the access profile of the specific user group, each right is known individually as an access policy. A collection of access policies is known as an access profile.
User group account
Related trading partner user accounts can be combined into one user group. Theseindividual user accounts are limited to the access profile of the user group account to which they are assigned. For instance, multiple partner IDs from one company can be combined in one group account for access to related transactions.
Limiting column visibility
Filtering of column data restricts the resultant dataset to specific metadata associated with each transaction. This type of filtering uses the b2b/column-visibility resource of the RBM policy. When defined, the user can view transactional data for the explicitly defined columns only. The policy can contain one or many columns that can be exposed for viewing. This granularity can be further refined by combining the partner visibility access policy. The policy string has the format that is shown in Example below, where each column added to the policy string will be viewable in the Transaction Viewer.
B2B Transaction Viewer policy string that defines column visibility resource
Tip:To allow all columns, set the access policy to:
This shows the mapping of B2B Transaction Viewer column labels to dataset fields.
Mapping of labels in B2B Transaction Viewer to dataset fields
Limiting partner visibility
Filtering of partner-sensitive data (rows) restricts the result dataset to specific transactions associated with previously configured user accounts. This type of filtering uses the b2b/partner-visibility resource of the RBM policy. When a partner-visibility policy string is defined for a user account, the user can view transactional data for the explicitly defined users only. Each policy string can contain only one user account entry. Therefore, to explicitly allow a user to view data for specific users, add a policy string for each account.
The policy string has the format.
B2B Transaction Viewer policy string that defines partner visibility resource
The administrator can add one or more partner visibility access policies to a user group. The RBM B2B logic will look for these policy strings and filter the resultant data sets returned to users.
Limiting B2B access control to actions
There is a requirement to allow the B2B administrator the ability to control access to certain B2B Viewer operations. These operations provide the ability to resend (retransmit) B2B transactions and to retrieve B2B documents associated with transactions. When the resend transaction access policy is enabled in a user group, it only applies to transactions for the trading partners that are listed in the B2B Partners Visibility RBM string.
The policy string to limit the ability to resend transactions has the format that is shown in Example below, where access to the function is unavailable unless explicitly listed in anaccess policy.
B2B Transaction Viewer policy string allowing resend transaction access
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.