X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

Build, test and deploy apps on Oracle Cloud. Start Now
  • March 4, 2020

Expose T3 protocol for managed servers in SOA Domain on Kubernetes

Ravi Pinto
Director, Product Management, Oracle Integration & Digital Assistant

T3 ports for Managed Servers in Oracle SOA deployed in WebLogic Kubernetes operator Environment are not available by default.

This document provides steps to create T3 channel and the corresponding Kubernetes Service to expose the T3 protocol for Managed Servers in SOA Domain.

Exposing SOA Managed Server T3 Ports

With the following steps you will be creating T3 port at 30014 on all Managed Servers for soa_cluster with below details:

  • Name: T3Channel_MS

  • Listen Port: 30014

  • External Listen Address: <Master IP Address>

  • External Listen Port: 30014

Note: In case you are using different NodePort to expose T3 for Managed Server externally, then use same value for "External Listen Port

Step 1 : Create T3 Channels for Managed Servers

WebLogic Server supports several ways to configure T3 channel. Below steps describe the methods to create T3 channel using WebLogic Server Administration Console or using WLST Scripts.

Method 1 : Using WebLogic Server Administration Console

  1. Login to WebLogic Server Administration Console and obtain the configuration lock by clicking on Lock & Edit

  2. In the left pane of the Console, expand Environment and select Servers.

  3. On the Servers page, click on the soa_server1 and go to Protocols page