WTX (name before 2017) belonged to the WebSphere family; therefore, the product was called WebSphere HCL Integration Platform (HIP). In WebSphere Message Broker (WMB) V8, the HCL Integration Platform (HIP) lab has integrated the 2 products such that you can invoke an HCL Integration Platform (HIP) map from a IIB Message Flow. So why should customer consider using it while IIB has its own mapper; as a matter of fact, several of them including the Compute node.
Before we discuss those values, let’s talk about how the 2 products are integrated in terms of being able to use HCL Integration Platform (HIP) in an IIB environment and coexisting with other mappers.
Now let’s talk about the values HCL Integration Platform (HIP)ITX bring to the table.
In addition to these mapping features, HCL Integration Platform (HIP) Industry Packs provide IIB with a much needed gap in the area of Industry Standards. These packs are licensed product unlike those provided by Dublin which are service based products (except for HL7). Customers obtain the latest version as part of software maintenance.
X12, EDIFACT, HIPAA and SWIFT include validation beyond data type and data structure. For example, HIPAA supports HIPAA validation 1 to 7; SWIFT supports SWIFT User Handbook validation; X12 and EDIFACT support EDI validation. In addition, they also support Acknowledgement commonly known as 997, 999 and CONTRL.
HCL Integration Platform (HIP) Design Studio integration with IIB Toolkit
Toolkit can operate with Integration Developer perspective or HCL Integration Platform (HIP) perspective
WTX Map as a node in Message Flow
Different Deployment Options
Multiple Inputs and Outputs
Changing Map settings in a Message Flow
Integration with Message Domain such as Blob and XMLNSC
Integration with Dynamic Named Terminal
World Wide tech sales
HCL Integration Platform (HIP) is a trademark of IBM Corporation in at least one jurisdiction and is used under license.