PeopleSoft Integration Broker and SNI: A New Option in PeopleTools 8.62

By Marije Politiek • 27 januari 2026

For years, PeopleSoft Integration Broker (IB) has had a known limitation when making outbound HTTPS calls to servers requiring SNI (Server Name Indication). By default, IB resolves hostnames to IP addresses before establishing the TLS handshake. While functional in many cases, this approach prevents Java from sending the hostname in the TLS handshake, causing connections to fail on SNI-required endpoints, especially common in modern cloud environments.

This has historically required a workaround using the integrationGateway.properties file, where you had to list all service operation aliases requiring SNI: ig.UseDomainName.ExternalOperationNames=MYSOP1.v1,MYSOP2.v1
With this setting, IB would preserve the hostname for those specific outbound calls, enabling SNI support.


The New Approach in PeopleTools 8.62
PeopleTools 8.62 introduces a simpler and more robust way to handle SNI.
 

New Global Option: ig.UseDomainName
# By default, hostnames in URLs are converted to IP addresses in Integration Gateway.
# Setting this property to TRUE instructs Integration Gateway to use domain names for all HTTP/HTTPS connections
# unless overridden by an individual HTTP Target Connector property (Use-DomainName=N).
ig.UseDomainName=TRUE

 

Benefits of this new option:


·      No longer necessary to maintain a long list of service operation aliases in ig.UseDomainName.ExternalOperationNames.

·      Automatically preserves the hostname for all outbound HTTPS calls, enabling SNI wherever required.

·      Simplifies configuration and reduces maintenance, especially in environments with multiple service operations.


Legacy Option Still Available


For selective use, the old property is still supported:
ig.UseDomainName.ExternalOperationNames=MYSOP1.v1, MYSOP2.v1

·      This allows you to enable domain-name usage for specific integrations only.

·      Values are comma-separated; no spaces.

 

Steps to Enable the Feature


  1. Open your integrationGateway.properties file.
  2. Add or update the new property: ig.UseDomainName=TRUE
  3. 3. (Optional) If needed, list any service operation aliases in the legacy property: ig.UseDomainName.ExternalOperationNames=
  4. Restart the Integration Gateway web server to apply changes.
Blog PeopleSoft Integration Broker

We like to do things a little differently

Our strength lies in people who truly understand Oracle and are always curious about what's really going on. Discover how we work and who we are.

Stay up to date

Don't miss the most important MCX news, developments in cloud, Oracle and security, and our perspective on technology and collaboration? Sign up for our newsletter.

Newletter ENG

Most recent posts

MCX Jmeter

JMeter & PeopleSoft: pioneering performance testing

door Marije Politiek • 15 januari 2026
Performance testing is crucial for delivering reliable IT services. But what if there is hardly any documentation on how to properly test your specific systems? MCX took on exactly that challenge by combining JMeter and PeopleSoft - a journey that started with frustration but ended in innovation. ‘It was a struggle, but that's exactly what makes the end result so satisfying.’ says Anu Khurana, Subject Matter Expert at MCX. Read Anu's full blog post below:
Bert MCX

Bert is aligned with MCX's values

door Marije Politiek • 2 december 2025
Bert shares how MCX’s honest culture, teamwork and broad technical roles create a workplace where reliability, loyalty and personal growth truly matter.
Tim at MCX

Tim talks about the confidence he gets at MCX

door Marije Politiek • 2 december 2025
Tim explains how trust, freedom and honest collaboration at MCX help him grow while working on complex IT challenges and improving the internal landscape.