How To Configure Port Number for Tuxedo WTC On-Demand Scaling (Doc ID 2831343.1)

Last updated on JANUARY 08, 2024

Applies to:

Goal

A Tuxedo application and has a WTC integration with Weblogic. Tuxedo services are invoked by WebLogic via WTC. At presently configured WebLogic domains as remote domains in Tuxedo.

There is a requirement to containerize WebLogic applications. Based on the load, Kubernetes can boot up / shutdown WebLogic domains.No issues if a WebLogic domain is shut down due to less load since our WTC connections are "on-demand"

Due to high load, if Kubernetes boots up an extra WebLogic domain, the IP address and port number of that RDOM(WebLogic domain) can be different than what has been configured in dom1configtux. To know how tuxedo can identify this on-demand scaling from Kubernetes for the WebLogic domain.

Below is a snapshot from dom1configtux. When Kubernetes boots up QTZ_Q03DSK_WLS_MS1(remote Weblogic domain), the IP address and port can be different from what the user configured. This ultimately may cause connection failures.

Need to know if there is a way to connect the RDOM without specifying a port number.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.