Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does BridgeWorks differ from other HP integration tools?

April 26, 2017bridgeworks differ HP Integration tools

0

Posted

How does BridgeWorks differ from other HP integration tools?

1 Answer

0

Posted

Several HP integration tools are tailored to applications using some particular OpenVMS technology, such as DECforms Web Connector (for forms-based applications). If a specialized integration tool is available for your existing application, this may be the right choice for you. In contrast, BridgeWorks is designed to provide flexible interoperability between most standard-component platforms and most OpenVMS applications. Such applications must use the OpenVMS Calling Standard and have callable routines, ACMS tasks, or DCL procedures that can be logically mapped to a new front end (typically, Java clients, web clients, or other Windows clients).