This is the ninth article in our series profiling the benefits, use cases, and sometimes challenges of the platforms we support. In this installment, we explain why many OpenText users don’t see their EDI solutions as outdated. Or even as software.
Over time, and particularly the past five years, we’ve seen OpenText shift its EDI/B2B focus to its cloud-based Business Network. OpenText presents its solutions in logical tiers, aligned to the user’s job function. This is novel and potentially helpful.
Manufacturers, distributors, logistics providers, and healthcare supply chains use TrustedLink and Data Integrator (formerly called BizManager). They also use other OpenText tools for key tasks.
These organizations see their EDI systems as essential business infrastructure, not just software. We know this because we help many of them enhance the lifecycle and increase the effectiveness of the OpenText tools they use.
Not surprisingly, the primary focus of this article is why enterprises, from manufacturers to pharmaceutical distributors, continue to run multi-billion-dollar industries on OpenText on-prem solutions.
As a reminder, we provide links to each of the previous blogs in the series at the end of this article. Check out the list to access insights on any platform you may want to learn more about.
What Kind of Companies Still Run TrustedLink and/or Biz Manager?
Organizations that still rely on OpenText’s on-premise EDI/B2B tools share a common denominator:
They operate in industries where a stable EDI/B2B integration environment matters more than chasing a platform trend.
For example, automotive manufacturers and suppliers often maintain mature EDI ecosystems. These environments feature highly customized maps and strict retailer or OEM compliance requirements.
Migrating such environments to the cloud is neither cheap, fast, nor easy.
Moves like these, especially those that involve an iPaaS, managed services, or outsourced solution, require meticulous planning. The C-Suite doesn’t readily embrace any project with the potential to disrupt production schedules, revenue cycles, or shipping dates.
This is especially true for healthcare distributors and pharmaceutical supply chains. These players must plan for potential disruption risks and the added layers of HIPAA and item serialization sensitivities.
What Do Established OpenText Environments Look Like?
Organizations that established OpenText on-prem environments think of them as essential operational infrastructure. Such setups are often efficient and nimble.
A small integration team might manage hundreds of active trading partners. They also handle thousands of daily EDI transactions. In some organizations, one or two long-time integrators still manage mappings and workflows.
Also likely is that those map nuances and point connections have evolved over ten or fifteen years. That’s not necessarily a bad thing. Smart organizations often rely on creative customizations to address their unique requirements.
But sooner or later, market demands and initiatives like a new ERP make EDI modernization inevitable. We see it frequently in our client work.
In the meantime, these environments can connect some on-premises OpenText tools with APIs, managed file transfer solutions, and hybrid integration architectures. This lets them move towards modernization gradually while preserving stability.
Does OpenText Still Support TrustedLink and BizManager?
OpenText now emphasizes Trading Grid, Business Network, and cloud-based B2B Integration services in its public-facing product strategy. But several TrustedLink-related products and other legacy product references still appear within OpenText lifecycle and support resources.
Organizations may still encounter references to TrustedLink Enterprise (TLE), TrustedLink Windows (TLW), and TrustedLink for IBM i (TLI). On the other hand, BizManager users will discover, if they haven’t already, that OpenText has re-branded and re-tooled the solution.
OpenText also provides lifecycle and product rebranding resources that help customers identify current product names, support status, and migration paths. Providing the resources does not necessarily mean OpenText considers these products as strategic growth platforms.
At the same time, we like how the company—which has grown partly through acquiring much-embraced niche platforms—shows respect for the many organizations that still operate and maintain these environments.
What Does the Path from OpenText On-Prem Solutions to the Cloud Look Like?
OpenText’s long-term strategy aims to guide customers to cloud-based Business Network and managed services. For some organizations, this shift is practical for operations and staffing. However, it doesn’t work for all.
Many companies find themselves in transition. TrustedLink or BizManager often continues to support core EDI workflows. At the same time, newer cloud services, whether from OpenText or others, take care of partner onboarding, analytics, and ERP/EDI modernization.
These organizations choose hybrid architectures that preserve existing investments while modernizing surrounding systems gradually. Some current users want to weigh modernization paths outside the OpenText ecosystem entirely.
Companies that want to move beyond their OpenText tools can benefit from outside expertise. Objective counsel from a credible partner can help them focus on the right solution to support their operations.
Also, we’ve seen organizations with domestic and multinational trading partners benefit from contracting with an outside advocate when moving from on-prem to managed services. Having an advocate in the mix helps as the go-between the organization and its integration partners.
A specialist performing in this role ensures timely performance along contract terms and SLA compliance, and they can resolve and even help prevent productivity and communication issues.
How Can Remedi Support Legacy and Transitioning OpenText Environments?
Remedi can support OpenText customers by:
- Providing staff augmentation during ERP, EDI, and infrastructure modernization initiatives
- Assessing, stabilizing, maintaining, and extending mission-critical OpenText environments
- Supporting hybrid integration environments that combine on-premises and cloud-based systems
- Delivering flexible long-term support models that complement internal teams
Ready to learn more about our OpenText expertise or discuss your environment? Contact Remedi here.
Other Articles in the Series:
Are all B2B Integration Platforms Alike? Yes and No.
The Platforms We Support: Microsoft BizTalk Server and Azure Logic Apps
The Platforms We Support: Boomi
The Platforms We Support: True Commerce and SPS Commerce
The Platforms We Support: IBM B2B / Hybrid Integration & Data Exchange Solutions
The Platforms We Support: Cleo Integration Cloud
The Platforms We Support: The SEEBURGER Business Integration Suite
The Platforms We Support: 1 EDI Source from Epicor
FAQs
1. Does OpenText still support TrustedLink products?
Several TrustedLink-related products still appear in OpenText support and lifecycle resources, although OpenText now emphasizes cloud-based Business Network offerings.
2. What is BizManager called today?
BizManager now appears under the OpenText Data Integrator portfolio and branding.
3. Are TrustedLink environments still business-critical?
Yes. Many manufacturers, distributors, logistics providers, and healthcare organizations still rely on TrustedLink environments to process daily business transactions.
4. Can OpenText legacy environments connect with cloud systems?
Some organizations operate hybrid environments where established OpenText systems interact with cloud ERP platforms, APIs, and managed services.
5. How can organizations support aging OpenText environments with limited internal staff?
Many organizations use consulting partners or staff augmentation services such as Remedi to maintain operational continuity while planning modernization efforts.
