Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jan 31, 2024

Connect to SMB shares from Sterling B2B Integrator hosted on Unix / Linux

For Sterling Integrator hosted on Unix/Linux OS, there is no direct capability to exchange files with Windows Network Shared folders.


The recommended solution from IBM for this is to use a samba client on the Unix/Linux machine and mount the windows network shared folder as a persistent filesystem, thus making it available to read/write files from using the Sterling Integrator built in Filesystem Adapter.

This model tends to be less sustainable when we have a high number of network shares that are needed to be accessed, and there is frequent change / additional network shares - as this would require frequent modifications to the underlying host OS configuration (e.g. continually adding new mount points for additional network shares).

We are looking for a way to connect directly from a Sterling Integrator Business Processes to the remote Windows network shared folders to push or pull files, using SMB3 protocol (in order to ensure the encryption of the traffic).

We are looking into the possibility of creating either a custom java service or using some external jar library to call some library functions to perform this. There are open source libraries that offer some varying support for SMB3 (JCIFS and SMBJ libraries) and there is a commercial library (JNQ from Visuality Systems) which claims to be SMB3 compatible.


It would be ideal if IBM could create a new type of Client adapter & related services to directly connect to network shares using SMB and put/get files.


What is your industry? Banking
How will this idea be used?

When a file is received in Sterling Integrator that needs to be delivered to a Windows based network share, there is no direct capability for this, so currently we need to use an intermediary SFTP server (hosted on a Windows server) which has virtual directories mapped to remote network shares, so the delivery can be made from Sterling using an SFTP client.

However, we would prefer not to have an intermediary and be capable of performing direct transfers from the Sterling Integrator (hosted on Unix/Linux) to windows network shares (using SMB3 protocol which supports encryption).


Persistent mounting of the network share to the Unix/Linux server on which Sterling Integrator is running (using samba client) is possible, but as described above, not sustainable for frequently changing network share endpoints, it would be better to have the configuration stored in the application layer, rather than the underlying server OS configuration.