Klish Group is a consulting firm specializing in Web and Digital Content Management strategy, design and implementation
Learn about the 100 plus installations and upgrades we have done.
Work with the customer to inventory and size the required infrastructure.
Perform the installation.
Perform post installation tasks, configure users, apply updates.
Collaboratively work with the customer to validate platform functionality.
We performed a standard installation of TeamSite on RedHat Enterprise Linux in the Travel & Hospitality customer's on premise data center.
We partnered with the customer's infrastructure team to come to an agreement on the operating system and database versions that were certified to work with TeamSite.
Platform components:
TeamSite Integrations:
This customer's development resources had deep experience with .NET, so we successfully performed the first customer installation of a TeamSite platform with LiveSite .NET.
We worked closely with the TeamSite engineering team to make adjustments to the platform to allow for seamless page authoring for web sites rendered using the LiveSite Display Services .NET platform.
This platform evolved to also have the same TeamSite server deploying content out to both LiveSite Java and .NET Runtimes, demonstrating the flexibility provided by both the OpenDeploy and TeamSite products.
Platform components:
TeamSite Integrations:
This installation was deployed in Azure and consisted of TeamSite being deployed on Virtual Machines, while the LiveSite Runtime components were deployed in Kubernetes using the OpenText Cloud images
This was the pilot project for the customer's migration from on premise data center to Azure, so we overcame challenges with provisioning and connectivity to deliver a flexible platform.
As the first platform deployed in Azure, we worked with the customer to define Infrastructure as Code (IaC) practices using Terraform to automate the creation of the required resources.
Platform components:
TeamSite Integrations:
Inventory all of the existing content and customizations within the existing platform.
Work with the customer to determine layout, count and size of necessary resources.
Depending on the changes included with the version, determine if an in place upgrade or new install is recommended.
Address changes introduced in the upgraded version that impact customer extensions.
If a new installation, transfer the existing content and customizations.
Confirm existing authoring processes and web site visitor experience remains the same.
The customer wanted to migrate their existing on premise TeamSite and IDOL Windows Server based platforms to Azure.
The upgrade project consisted of the following initial and target versions of software and infrastructure components:
Component | Existing Version | Target Version | Notes |
---|---|---|---|
IDOL | 11.2 | 24.3 | Web, ODBC Connectors |
SQL Server | 2014 | 2022 | |
TeamSite | 16.3 | 23.4.1 | Includes LiveSite .NET |
TeamSite Search | IDOL 8 | Solr 8.11.2 | TeamSite version 16.3 last version based on IDOL |
Windows Server | 2016 | 2022 |
This customer wanted to upgrade and migrate all of their TeamSite, LiveSite and IDOL platforms from on premise to AWS as part of this project.
OpenText only provides Docker containers for Kubernetes TeamSite deployment, so our team created the following Linux containers for deployment in AWS ECS as the customer did not want to manage the additional complexity of AKS:
Similarly, MicroFocus (now owned by OpenText) does not provide containers for all of the required IDOL services, so our team created the following Linux containers:
The upgrade project consisted of the following initial and target versions of software and infrastructure components:
Component | Existing Version | Target Version | Notes |
---|---|---|---|
IDOL | 12 | 24.4 | Web Connector |
Database | SQL Server 2017 | AWS Aurora PostgreSQL Serverless | |
TeamSite | 20.4.0.5 | 23.4.1.0 | Includes LiveSite .NET |
Windows Server | 2016 | 2022 |