Verastream Host Integrator Early Adopter Program
Some features in this product are provided as early adopter product features only. They are being made available to allow you to test and provide feedback on the new capabilities; however, they are not intended for production use and are not supported as such.
We will continue the development of additional features via service packs and future releases. Please contact Open Text Customer Care if you require further clarification.
In specific circumstances it may be possible to agree to the use of these Early Adopter Program (EAP) features for production – for more information please contact OpenText Sales Engineering and Product Management.
List of features
This release adds the ability to run Verasream Host Integrator in an opinionated Kubernetes environment.
- Airgap container images are packaged for offline installation in a private container registry.
- A Helm chart is provided for deploying Verastream Host Integrator as a Kubernetes application.
- Muliple Session Server replicas run alongside a single replica Management Server.
- REST & SOAP web services are mapped to a load-balanced Session Server service via an ingress.
- Models can be deployed via HTTPS from the Design Tool and the command-line.
- Java Event handlers deployed with models will execute as they do with a typical installation.
Limitations
- K3s with a Traefik ingress was used for developement and testing. Your results may vary on other environments.
- A Traefik ingress must be used when enabling the TCP ingress for use with connectors.
- .NET Event Handlers will not function in Kubernetes.
- Stateful sessions function only when running a single replica of the Session Server pod.
- Session Server pods must be manually restarted to load a deployed model.
- Design Tool cannot deploy deployment descriptors to a Kubernetes environment.
Early Adopter Program
Features that are part of the Early Adopter Program are noted within these callouts in the documentation. They are not in release status. We intend to provide the finalized feature in a future release. Please contact OpenText Customer Care if you require further clarification.