IBM B2B Integrator Reviews

There are several use cases because IBM B2B Integrator is an integrator that allows our customers to process files. I have use cases depending on the industry. For example, in logistics and retail, it's been used above all for EDI file transfer to connect our customers with their third party in order to interchange purchase orders, file advisements, and so on. In IBM B2B Integrator, it's normalized to standard EDI messages.

In banks, IBM B2B Integrator has had a new mapper added in the platform for the last six or seven years, which is IBM Transformation Extender. For example, in the financial environment, it supports SWIFT messages. It's used with the B2B communication layer. It's possible to interchange files with several different communication protocols, with security, and so on. With the translator, it's possible to adapt the format incoming from the third party, the external third party, to SWIFT messages. Financial customers typically work with mainframes, and in mainframes, they use flat files. The new standards that are on XML must be normalized to this flat file, and we accomplish this with IBM B2B Integrator.

The main feature of IBM B2B Integrator is that it's the most complete integrator on the market. You can integrate every type of protocol, every type of custom layer, and every type of security level. You can integrate or interchange with external third parties using different layers of security. It's the most secure product in the market.

The platform is comprehensive but tends to be the most expensive on the market. It can do whatever is needed with every type of file, but it has been expensive for small-medium customers. It's focused primarily on medium enterprise and large enterprise customers. The new versions are very REST-API-oriented, making it very easy to integrate with external applications to expose processes. The hybrid version is quite powerful because the use of containers is very dynamic.

The support for various communication protocols and data formats in IBM B2B Integrator is the power of the platform. It can expose every type of protocol. The platform out-of-the-box supports more than 40 protocols. Additionally, customization is possible. For example, one of the proprietary protocols in the market is XCOM. While XCOM is not supported out-of-the-box, we can create a custom layer to support it using external scripts or Java classes and integrate this other protocol in IBM B2B Integrator.

Based on my experience and my clients' feedback, there are a few points IBM can improve for IBM B2B Integrator. One of these is the graphical user interface. For several years, IBM has been promising to renew this interface, which has an ancient, old aesthetic, though it contains many functionalities. Creating a new interface would incur a very high internal cost with no new profitability for IBM. This is one of the points where customers say it feels like working in the 1990s with this interface.

Another significant issue is that the platform is not multi-tenant. It's not possible to have different tenants in the cloud. This creates problems when trying to create SaaS offers based on IBM B2B Integrator, as there is the possibility that some workflow for a customer can be visible to another one. Since it's not multi-tenant, it's running on the same tenant of the platform. This is the main issue that the platform has.

I have been working with IBM B2B Integrator for approximately 18 years.

Out-of-the-box, IBM B2B Integrator is not a product that allows you to have good reporting and analytics. While it has some analytics engine embedded, this is a platform that works with files, so it's not oriented to get statistics, reports, optimization, and so on. It needs to be integrated with other products of the IBM Sterling suite that work with the platform to get these analytics. From this perspective, when a customer asks for analytics on the file transfer or reports, I suggest other products, such as IBM Control Center or similar products that are more oriented to the performance of the end-to-end file transfer.

The initial setup for IBM B2B Integrator is not very easy. It's not a simple process because it implies a specific configuration for the operating system and for the server. It needs an external database that has to be handled by an external team. While it's not a very easy implementation or basic installation, including the patching, once it's installed, it's a very stable platform. It doesn't usually suffer from performance problems.

For scalability, IBM B2B Integrator deserves top marks. If it's properly configured and installed with the right infrastructure, it's the best product for scalability. We have customers who started working on a cluster of two nodes, and with increasing business and volume, the same customers are now working on 16 nodes with no issues with development.

The technical support from IBM varies depending on the country. In Spain, Portugal, Mexico, and the USA, and until last year, Italy, the support quality differs. The support in Spain and Italy is quite good, deserving an eight or nine out of ten.

However, in Mexico, the support is not as good, especially at the first level. The first level support often doesn't comply with the SLA. They answer very late, and their responses are often limited to requesting logs. In Europe, the support is typically excellent and fast. In Mexico and Latin America, the support quality would rate at a four or five out of ten, while in Europe it would rate at an eight or nine.

The initial setup for IBM B2B Integrator is not straightforward. It's not a simple process as it requires specific configuration for the operating system and server. It needs an external database that must be handled by an external team. The implementation, basic installation, and patching process are all complex tasks.

Regarding pricing, IBM B2B Integrator rates in the middle range. This integrator has embedded all the functionality needed to handle files and messages. It tends to be very expensive because the IBM license model is oriented toward paying for the power of the machine where you install the platform. Customers have to purchase the whole platform, as it's not possible to purchase only specific components such as communication, file transfer, or transmission separately. The cost depends on the power of the machine, making it relatively expensive.

IBM B2B Integrator compares mainly with Axway, which has a platform that is practically the twin of IBM Sterling, with a different point of view and focus.

For pure file transfer with no translation of the file, GoAnywhere from Fortra is one of the stronger competitors in the market, as it's a very cost-effective and useful platform. There are other challengers, but the main competitors are Axway and Fortra GoAnywhere. MuleSoft can also be considered a competitor, but only for some of the IBM B2B Integrator features. A customer using MuleSoft can replace it with IBM B2B Integrator, and conversely, IBM B2B Integrator can be partially replaced by MuleSoft.

The automation capabilities of IBM B2B Integrator effectively streamline business processes. Starting this year, Sterling B2B Integrator is under the layer of the automation area in IBM. This is the automation integration because you can set up and customize several business processes to handle files as needed. After that, you can set up internal schedules or integrate with external schedulers to have extreme automation, both on the normal workflow and error handling. The platform provides ways to restart processes automatically and in some cases self-adjust errors, depending on the developers. It's a platform that guarantees extensive process automation capabilities.

IBM B2B Integrator's compliance management features are very comprehensive. IBM prioritizes compliance as it's one of the main ways to attract new customers. The platform is very open to implementing and being compliant with third-party normatives, European or US normatives. It's a very good product for compliance management.

Based on my experience, I rate IBM B2B Integrator an 8 out of 10.

IBM B2B Integrator is majorly used in banks for managed file transfer, integrating with their external and internal applications for large files, especially huge files which need to be transferred, translated, and sent to backend systems.

The data transformation tool in IBM B2B Integrator is useful because many banks face challenges with legacy applications that don't understand current data structures or formats, making it very difficult for them to obtain the current or live status for their customers. It helps in data transformation and ensures they get the status immediately.

In the current scenario, the most valuable features of IBM B2B Integrator are that most applications today are subscription models and on the cloud, while IBM B2B Integrator still offers on-premises and perpetual licenses, which is a value addition customers are seeing more.

It can integrate with multiple other applications such as IBM API Connect, App Connect, or DataPower Gateway to make it more rigid in API calls for external entities and monetize that.

The reporting and monitoring features of IBM B2B Integrator are comparatively easier than other applications because it is modularized, making it much faster to port, and it supports all compliances related to financial industries.

The security features of IBM B2B Integrator are secure enough as it updates and supports all compliances, whether it is HIPAA, financial institution standards, or retail and logistics industry standards.

For high volume transactions, IBM B2B Integrator works effectively and can scale. You can have multiple threads running, making it highly scalable and fitting for high volume transactions.

From the automation perspective, IBM B2B Integrator has its own powerful workflow, but compared to other applications such as MuleSoft or Boomi, they have many cloud connectors and multiple connectors for integrating with Salesforce or other CRM or ERP applications, whereas here you may have to develop them, which is not native.

There is room for improvement in IBM B2B Integrator, particularly in the automation parts, and from a UI perspective. They are making some changes to make it more intuitive. The current UI is not aesthetically pleasing, but features-wise, it is rich enough to provide all the valuable information required.

I have been working with IBM B2B Integrator for almost 20 years.

IBM B2B Integrator can be recommended for both enterprise and small to medium enterprises because it is modularized. The licensing is based on what components or features you are trying to use, and Fortune 500 companies are using Sterling IBM B2B Integrator.

The stability of IBM B2B Integrator rates as 10 out of 10.

The scalability of IBM B2B Integrator rates as 10 out of 10.

The technical support from IBM is good compared to other enterprises. They are reachable and provide immediate answers, but since multiple support vendors are involved, getting support altogether might be a challenge. Otherwise, it is very good.

Positive

Regarding competitors of IBM B2B Integrator such as Boomi, one key feature that makes IBM better is that it offers many adapters or connectors for enterprise applications that are not available in IBM B2B Integrator. People often think it is competitively priced, but that is not true. Having been in this industry for 20 years and understanding how IBM's license model works, it is much cheaper compared to others, but when people hear 'IBM,' they often think the pricing is high.

The setup process for IBM B2B Integrator is simple.

For high volume transactions, IBM B2B Integrator works effectively and can scale. You can have multiple threads running, making it highly scalable and fitting for high volume transactions. I rate IBM B2B Integrator a 9 out of 10.

IBM B2B Integrator is primarily used when I want to send a file from one partner to another and I need to make changes like renaming the file, do some processing or automation, or other modifications. We use B2B Integrator to create maps or business processes that can rename files, pull files from one remote server, or send files to another remote server. If a partner sends a file in one format (like XML) but needs it in another format (like CSV), we can use mapping to change the file format.

There are also different tabs where we can check the status of file transfers and business processes, and we can monitor adapters and services in the link. Rules can be used to control where files are placed, like in specific mailboxes or folders.

B2B Integrator integrates with Sterling File Gateway, so the two applications can work together.

For me, business process creation is the most valuable. If the consumer wants any changes in file name or file core, or they want to automate file processing, we can use business processes. I really enjoy creating business processes.

There are some notifications on the home screen that we need to clear manually. Sometimes there's a doc status point notification or other notifications that we see in the admin console. It would be helpful if these notifications could be cleared automatically or if there was a pop-up notification that we could easily dismiss.

So, I'd like the ability to clear the different notifications that appear in the app.

Also, we often need to change property files for accounts, and I don't always have access to them. For core mapping, we need to install JDK, and there's no documentation on how to install the map editor and the necessary libraries for specific versions. It would be helpful if the IBM map editor was installed in something like a SIRLINK file data and SIRLINK Integrator tool, which would make it easier to understand the mapping.

I have been using it for about three and a half years. In my last project, I used 6.0.3, and now I use 6.1.2.

I have experience in B2B Integrator, Sterling File Gateway, and IBM Control Center.

We often encounter issues when the activity account gets high. It doesn't perform well and throws errors. Installing file core mostly impacts sending files, and we see most failures in Sterling File Gateway. There's also a trading concept with node one and node two clusters. We get most of the errors in Sterling File Gateway.

In my company, everyone who uses the Sterling File Gateway also uses B2B Integrator. So, about there are five to six end users. 

We need to raise IBM ticket if we need help, and most of the time, they respond quickly. They often connect with us directly, ask about the issues, and try to resolve them. They usually provide solutions.

We have different environments. First, we create a safe environment. 

If it works properly in the page environment, then we deploy it in production. It's not that difficult. If you understand the concept of how to create it in the page environment, it won't take much time to create it in production.

To understand B2B Integrator for the first time, you should go through the IBM documentation. There aren't many videos available on YouTube. You can search on Google or other websites, but the IBM documentation is very helpful. However, you also need the tool itself. 

When you're learning how to create trading partners, for example, you need practical knowledge as well. It's helpful if someone shows you how to create a trading partner, and then you can try it yourself. It's easy to understand, but you need hands-on practice.

Overall, there are only two things that are difficult to understand: mapping and business process creation. There are around 15 business processes. Suppose you create one trading partner, and another trading partner creates the setup using the routing channel. If you drop a file from one partner to the other, and you want to receive it in the consumer mailbox or consumer site, there's a business process that's invoked in the middle. It can be difficult to understand that business process and the mapping involved. Other than that, it's not that difficult to understand.

Compared to other tools, I would rate it an eight out of ten.

It's about moving data from one point to another, whether internally or externally. We use it primarily to transfer files and objects for B2B integrations with products supporting EDI. IBM developed it years ago but hasn't kept pace with modern cloud support compared to newer products on the market.

It supports many of our use cases but falls short in some areas as technology evolves, especially with data transfer between edge locations and the cloud or on-premise systems. The solution doesn’t fully address the need for high-speed data movement required by modern use cases like AI, which demands large volumes of data. Additionally, IBM's solution is primarily integrated with their cloud offering, which limits flexibility. Another limitation is the lack of a managed service offering that allows us to use it as a SaaS solution where they manage the infrastructure.

Moreover, while most MFT and file gateway solutions offer similar file movement and integration features, IBM Sterling lacks a key feature: a web UI for end-users to upload files.

I have been using IBM B2B Integrator for over ten years.

There are some networking challenges with IBM B2B Integrator because the setup requires multiple components to be deployed rather than being a single application that supports everything. Setting up a robust or high-availability environment is difficult due to the need for various configurations across these components. Additionally, implementing automated failover capabilities is particularly complex, with significant networking-related challenges that make the process far from straightforward.

It uses VMs, allowing us to enable horizontal scaling. We've sized our clusters to handle the expected data load, and with horizontal scaling enabled, we can manage any peaks in data from the source. It is scalable and doesn't present any issues.

From a technical support perspective, IBM is quite supportive, and we have a good relationship with them. The tool is becoming outdated and lacks some of the features and support we need for our evolving requirements.

Positive

It runs on IBM-based VMs in the cloud. However, setting it up is complex because it's not a managed service. Our dedicated team is responsible for deploying, maintaining, and patching the system, which adds significant overhead to the maintenance side. This makes supporting this solution more resource-intensive compared to managed offerings.

A dedicated team of about ten to twenty people supports this platform.

IBM does provide value for the cost according to the volume and criticality of the data. Since it's not a managed service, additional overhead costs exist for maintaining the product.

It is not cheap.

Overall, I rate the solution a seven out of ten because it lacks modern advancements.

I have used the tool in different projects for our clients. It is a middleware tool that works between two members. It is used for integration purposes.

The product makes it easy to work with REST API. We are onboarding partners. We create mailboxes and set up everything in SFC. When we create a generic process for mail filters, it takes a huge amount of code and time. When we use REST API, the data is in JSON format. Five to six lines of code is enough to onboard a partner. The solution is fast and easy to use. A beginner will take time to understand the product. With proper guidance and training, we can understand it easily.

One of our customers asked us to generate a PDF copy of the invoice, so I installed third-party JARs and SSL blocks. The product does not have any default options for PDF generation. We had to implement a new feature.

I have been using the solution for six and a half years.

I have seen a few stability issues. There are some data restrictions when I test 1000 files in the bucket. We can pass only 64,000 characters in Map Editor. There is a limitation in the field length of the data while encrypting or decrypting it.

I rate the tool’s stability a seven out of ten.

In the initial stage, I used only business processes to build code. As I used the product more and more, I learned that we could monitor, perform support activities, and install and upgrade servers. We can learn how to manage the clients to get business. We must get into a call with customers and get their requirements. We must pass all the test cases, both positive and negative. We need to manage our team as well.

We use various protocols for data security, like SFTP, FTP, and HTTP. We follow the security levels based on the customer’s requirements. We encrypt the file, and the customers decrypt it using the public and private keys we provide. Customers who need high security opt for HTTP certificates and AS2. I have also worked on AWS and Azure to pass files to the buckets.

I also work on single sign-on authentication. External users can access our dashboard with a few details. For example, if our customers need to see whether a file is transferred from our end, they can easily log in to the details and monitor it. They can also perform health checks. I will recommend the tool to others.

People who want to use the tool must not do anything blindly. They must analyze, learn the concept, and understand the purpose of the tool. There are other products in the market, like MuleSoft, that have the same functionality. We must understand why we are using IBM B2B Integrator. We must gather some information. I take some introductory classes for the new joiners in my organization.

Overall, I rate the solution an eight out of ten.

IBM B2B Integrator is a great tool, robust, reliable, low-maintenance, and ideal solution.

The product is an ideal tool for extracting templates and supporting all B2B EDI standards.

API integration could be improved. The legacy system could be on the cloud.

I have been using IBM B2B Integrator for ten years.

The product is very stable. I rate its stability a nine out of ten.

The product is very reliable because five or more GB files process well in the cloud. It takes time, but it doesn't hang. It starts lagging if you have a low disk space in the cloud and load more than five MB of files.

We have around 800 users using this solution.

The technical support services need improvement in terms of response time.

Neutral

I've worked with Dell Boomi. It is good for those who have less technical knowledge. IBM, Boomi, and MuleSoft have API advantages.

The initial setup process is easy if you know the product well.

We did the deployment by ourselves.

The product costs more than 40K.

I recommend IBM B2B Integrator only if they have an alternate API-based B2B solution. It is a very robust product but unsuitable for API integration.

Overall, I rate it a seven out of ten.

IBM B2B Integrator is primarily used for EDI transmissions, audits, and VDA transactions.

We have application developers, EDI mapping experts, system administrators, and architects using this solution.

The solution is deployed on-premises.

The most valuable features are the flexibility and the range of EDI standards that IBM Sterling can handle. It's easy to design a process and streamline the VDA transaction. There are different possibilities for connectivity. IBM handles almost all communication protocols and comes with an adapter. It's easy to set up. The range of connectivity and data handling is really good compared to other products.

The one thing that is lacking is easy visibility. It's hard to provide business users with a view into the statuses of their transactions.

The EDI translation mapping could be more simplified with more templates.

I have used this solution for several years.

It has a good range of tuning possibilities. If the capacity is designed correctly, it's very stable.

The scalability is high, but the ease of scalability depends on what you're using. IBM Sterling has the container option, which you can use to auto scale, but it depends on what kind of implementation you have done.

Technical support is fairly good. I would rate them as eight out of ten.

I would rate the setup as seven out of ten. Deployment takes a maximum of six hours if you consider the step-by-step procedures.

Building the servers will take additional resources, but installation itself is a one-person job. It also depends on what kind of capacity you are implementing.

The pricing is based on how many cores are used and the type of cores. They have something called PVU, process value units, which are based on the chip set and the number of chip sets being used for capacity. There are different pricing models, including an enterprise edition.

For a company that's a typical size, the cost is not significant.

I would rate this solution as seven out of ten, due to the lack of visibility and mapping.

Our company uses the solution for 50% of our sales orders and our integrations with 100 trading partners. Company wide, we have 100 users. 

The best feature is that many companies use the solution so there is a lot of peer support. You can talk to people from different companies who understand and can help you troubleshoot. 

The initial setup is complex. 

I have been using the solution for three years. 

The solution is pretty stable. 

We have not yet scaled, but I'm pretty sure the solution is easy to scale. 

We previously used a combination Axway Interchange and OpenText TLE. We had to switch because TLE was not being updated and people were moving away from the product. 

We did not want to go with OpenText's product because it did not offer on-premises, in-house maintenance. 

We chose the solution because it matched our requirements. 

The initial setup is complex and deployment took a few days. 

Ongoing maintenance can be handled by two or three technicians. 

We used a third-party reseller for implementation. 

The return on investment is that the solution is much less expensive than our previous solution. We save money so it is cheaper for B2B annually to use the solution. 

The solution is priced at $20,000 to $30,000 per year with no extra costs. Our previous solution was a lot more expensive. 

It is important to talk with your consultant before implementing the solution. 

I rate the solution an eight out of ten. 

I work for a bank, and we've used IBM B2B for internal and external transfers at all levels. In the past 10 years, we've used it in every way imaginable. It transfers files from point A to point B.

B2B Integrator has made us more secure. People who used to transfer confidential data through emails can now set up file transfers within 48 hours through an automated system using this product without any security risks.

IBM B2B is user-friendly. The most valuable features are the most basic, like the logs and the security features. It can monitor and communicate issues directly to us before they become more significant problems. It's a great product.

Patching or upgrading the product is a bit of a nightmare. It would be nice if they removed the installation manager port. We find it complicates upgrading and patching a great deal. The installation manager is supposed to make things easier, but it actually makes it a lot worse.

I've been using IBM B2B since 2011.

B2B Integrator's stability is rock-solid. It never goes down. It's one of the bank's most prized uptime software products.

Scalability is a bit tricky because we're limited on file sizes. We're exploring ways to integrate into PCI DSS, a security requirement for the credit cards system. So it might be a little challenging to scale above what we have now. I'd say it's a moderate level of difficulty. We can do some things, but some aspects are more complex because of security. We plan to increase our usage to cover anything that goes in and out of the bank. Eventually, everything will pass through the product, so it's the only gateway to transfer anything in and out of the bank.

IBM support was horrible.

The previous product was an in-house solution built on a Windows NT. We needed something with more security features and maturity.

Setting up B2B Integrator was complex. Right off the bat, we set it up on a HADR.  It's high availability and active on two different sites. Getting all the rules set and the firewalls open was challenging. It was complicated to get it to work in the mesh design. Total deployment time took about two years. It took that long to get everything fully working. We had a project team that included the integrators from Sterling and a group of three people from the bank. In addition to that, we had another five people handling network security, configuring the firewall, and setting up the database. So there were eight in total on our end. 

We had help from a consulting firm called ComResource. I believe that's what they were called at the time. It was Sterling Commerce's consultant firm. They were really hands-on and helped deliver the product the way we needed it, with custom features. 

I can't give a precise figure, but we get our money's worth.

We pay an annual fee based on the number of VPUs. It's fairly reasonable. We're in the middle of analyzing other products, and they're all pretty much in the same range. When we have problems and the support is inadequate, we pay outside consultants. We've had this issue twice, so sometimes there are additional costs when we need consultants to fix problems support can't handle, and we need help fast.

Before selecting IBM B2B Integrator, the bank looked at Axway and another IBM product called MQ Transfers. These were the three that our integrator Sterling Commerce suggested at the time. Now we're looking into BMC B2B MFT. We've got the training and the license, but we haven't started using it. One of the advantages of BMC is that upgrades take only 15 minutes.  We installed it, but we found BMC lacks the maturity of the current product, so we won't be deploying it at the bank any time soon. 

I would rate IBM B2B Integrator a nine out of 10. It's a great product. It's highly stable, and the redundancy is amazing. B2B Integrator also has a high availability option to work in a cluster environment. You rarely have issues operating it because of the HA. The only problem is support. When something goes wrong, you sometimes have to find the answers yourself on the internet. But overall, after working with it for 10 years, I can say it's been great to work with and learn to use

My clients utilize IBM B2B Integrator for various purposes, such as financial services, including Swift and transformation, healthcare, and large file transfers via firewall gateway. Additionally, we employ API integrations and perform XM reconfiguration for certain use cases.

This solution can be deployed in the cloud, on-premise, hybrid, multi-cluster, and hybrid environments.

IBM B2B Integrator has helped companies with, time consumption, resources, transferring files, changing the files, and mapping, conversion, and content validation.

The most valuable feature of IBM B2B Integrator is its security and flexibility.

IBM B2B Integrator could improve the business process itself, there is no resignation of duties and in terms of the console should be changed in a way that is more user-friendly.

I have been using IBM B2B Integrator for more than 12 years.

IBM B2B Integrator is a reliable solution.

The solution is scalable.

I have used the support a long time ago. My experience was poor because they ask a lot of questions which is a waste of time. If we use the support it will take a few days. However, if we escalate the support, the response can be quicker.

I have not used a similar solution to IBM B2B Integrator before.

The initial setup of IBM B2B Integrator is simple. However, for some customers it is difficult.

To implement the solution, we follow a series of steps. Initially, we conduct a gap analysis to identify any discrepancies. Then, we gather requirements from various sources and comprehend the customer's business needs, including their reasons for seeking a solution and how it will be utilized. Based on this information, we propose the most practical scenarios. Finally, we proceed with building the necessary processes and templates.

The duration required for implementing a solution varies depending on several factors, including the specific use case and the capabilities of the engineer responsible for the implementation. If the engineer is skilled and efficient, the implementation process is likely to be quicker.

We do the implementation of the solution. We use a changing number of people to do the intention based on the requirements and complexity. For example, if we are implementing the solution in a bank, corporate will be sending a payroll file and they should be validating file content. There are two parts involved and therefore two engineers are involved.

We have seen an ROI by using IBM B2B Integrator.

The price of IBM B2B Integrator is too high. However, IBM may be willing to give a discount if there are negotiations. If they see that there is a good opportunity for them they can provide a discount.

Maintaining the solution is not a challenging task, provided that the person responsible for it possesses a thorough understanding of the operating system, such as Windows, Linux, AIX, database, and application. Therefore, the level of difficulty or ease in maintaining the solution depends on the capabilities and expertise of the maintainer or support personnel. 

There are instances where an individual may work with a solution for ten years without acquiring much knowledge beyond basic login and logout procedures. In contrast, someone else may work for only a year and acquire a comprehensive understanding of all the intelligent features within the solution. Therefore, the level of expertise is not necessarily dependent on the duration of work experience, but rather on the individual's ability and willingness to learn.

My clients use this solution because it is from IBM and of its strong partnership compliance standards, such as AS2. Additionally, IBM works with other vendors to ensure that the solution's functionality and compliance are kept up-to-date. This is a value-added service that other solution vendors do not offer.

My advice to others is they should undergo some training before using the solution.

I rate IBM B2B Integrator a nine out of ten.