Sterling performance and troubleshooting
Fix the Sterling problems that keep coming back
Halted business processes, growing queues, slow translation, adapters that stop and a database that keeps growing. ECOM's Sterling specialists find the root cause of production problems in B2B Integrator and File Gateway, fix them and help you keep them from returning.
At a glance
- Production incident troubleshooting
- Root cause analysis
- Throughput and queue tuning
- Business process optimization
- Database, archive and purge
- Adapter and communication stability
The challenge
Recurring production problems drain the team
In many Sterling environments the same problems return every week. Business processes halt or wait, queues back up at peak times, translation slows as volumes grow, adapters stop without obvious reasons and the database grows until purge cannot keep up. Teams restart services and reprocess documents to keep partners happy, but without root cause analysis the problems keep coming back and capacity runs out.
- Business processes halting, waiting or failing intermittently
- Queue backlogs and slow processing at peak volumes
- Adapters and communication sessions that stop or hang
- Database growth, slow purge and full file systems
- Restarts and reprocessing instead of permanent fixes
Scope
What ECOM's Sterling specialists do
-
Production incident troubleshooting
Diagnose halted or failed business processes, translation errors, adapter failures and failed transfers, and restore processing safely.
-
Root cause analysis
Analyze logs, business process history, system settings and timing to find why a problem happens, not only how to clear it.
-
Throughput and queue tuning
Review queue configuration, thread usage and business process design for bottlenecks, and tune for your volumes.
-
Business process optimization
Simplify inefficient business processes, reduce unnecessary persistence and improve error handling and retries.
-
Database, archive and purge
Review database growth, indexes, archive and purge schedules and storage, and bring housekeeping back under control.
-
Adapter and communication stability
Stabilize adapters, perimeter servers and partner sessions, including timeouts, certificates and connection settings.
-
IBM support case preparation
Gather diagnostics and reproduce issues so IBM support cases move faster, with your authorization.
Approach
How an engagement runs
- 01
Triage
Understand symptoms, timing, business impact and recent changes, and stabilize production if needed.
- 02
Diagnose
Collect logs, settings and performance data, reproduce the issue where possible and identify the root cause.
- 03
Fix and verify
Apply configuration, design or housekeeping changes through your change control, and verify the effect under real volumes.
- 04
Prevent
Add monitoring, alerting and runbooks so the problem is caught early or does not recur.
Technical considerations
Where Sterling performance problems usually come from
Problems rarely have a single cause. These are the areas ECOM examines.
-
Business process design
Large documents, excessive persistence, synchronous waits and loops in business processes can consume resources quickly.
-
Queues and threads
Queue and thread settings that do not match workload patterns cause backlogs at peak times or idle capacity at others.
-
Database and housekeeping
Archive and purge settings that fall behind lead to large tables, slow queries and storage pressure.
-
Memory and JVM settings
Heap and other JVM settings must match the volumes and document sizes the environment processes.
-
Infrastructure
Storage latency, network paths, database server capacity and virtualization settings all affect throughput.
-
Partner and adapter behavior
Slow partner endpoints, retries and connection limits can tie up adapters and delay other traffic.
Why it matters
What you gain
Fewer repeat incidents
Root causes are fixed instead of cleared, so the same problems stop returning.
Processing that keeps up
Tuned queues, business processes and housekeeping help the platform handle peak volumes.
Time back for your team
Less firefighting and reprocessing frees your team for partner and business work.
Fit
When teams call us
Peak season slowdowns
Volumes rise during peak periods and processing falls behind when partners need documents most.
Recurring halted processes
The same business processes halt or wait regularly and the team restarts them by hand.
After an upgrade or migration
Performance or stability changed after an upgrade, infrastructure move or new partner volume.
Product background
IBM guidance on Sterling performance
IBM's B2B Integrator documentation includes guidance on performance planning and tuning, which ECOM uses as the baseline for reviews.
IBM source, checked October 20, 2026:
IBM publishes lifecycle and compatibility information that changes over time. Always confirm current details with IBM for your versions and entitlements. IBM and related product names are trademarks of IBM.
- IBM documents planning for performance and tuning Sterling B2B Integrator
- IBM documents configuring performance tuning parameters and how thread pools work
- IBM documents scheduling archiving and purging
- IBM publishes known issues and return codes for each release
Why ECOM
Sterling expertise, plus everything around it
Most Sterling problems are not only platform problems. They involve maps, partners, infrastructure and people. ECOM brings these together:
-
IBM Sterling technical expertise
Specialists who install, upgrade, administer and develop on B2B Integrator, File Gateway and Connect:Direct.
-
EDI mapping and partner integration
Maps, business processes and trading partner onboarding, not only platform administration.
-
Managed infrastructure and operations
Hosting, monitoring and day-to-day operations when you want ECOM to run the environment.
-
PRISM integration and visibility
Add ECOM PRISM for visibility, partner connectivity or a future platform path alongside Sterling.
-
EDI Team as a Service
Sterling and EDI specialists who extend your team on an ongoing basis.
-
Automotive integration
Deep automotive integration experience: schedules, ship notices and plant routing on Sterling or PRISM.
Ways to work with ECOM
A defined project
An upgrade, migration, implementation or fix with an agreed scope, plan and hand-over to your team.
Ongoing administration
ECOM specialists share administration and development work with your team through EDI Team as a Service.
Managed service
ECOM operates the environment within an agreed scope and service levels defined in the service agreement.
Each engagement is scoped individually. Not every engagement includes every service listed on this site.
Frequently asked questions
Can ECOM help with a production problem right now?
Contact ECOM with a description of the problem and its impact. Availability and how urgent work is engaged are agreed with you; customers with a managed service follow their agreed escalation path.
Do you need access to our environment?
Usually yes, through secure access you approve. Some analysis can start from logs and configuration exports if access takes time to arrange.
Will tuning require downtime?
Some changes take effect only after a restart and are scheduled in a maintenance window. ECOM plans changes through your change control.
How is this different from a health check?
A health check is a broad, planned review of the environment. Troubleshooting focuses on a specific production problem and its root cause, often under time pressure.
Get help with a Sterling production problem
Describe the problem, when it happens and its impact. A Sterling specialist will get back to you about next steps.