Troubleshooting tips for Connect:Direct protocol communication in IBM Sterling B2B Integrator

Issue: Sterling Connect:Direct Server Begin Session Service error out with handshake failure.

Cause: The issue can occur if

- Certificates are not exchanged properly.

- Proper protocol is not mentioned in the setup

- Certificates are exchanged properly, but there is an issue with certificate itself.

Sterling Connect:Direct Server Adapter configuration.

Remote node configuration.

BPML and all the parameters to Sterling Connect:Direct Begin Session Service

Status report and instance data from Sterling Connect:Direct Begin Session Service.

Remote Connect:Direct system should be examined for Certificates, Protocol setup.

- Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

- This issue will be benefited by obtaining SSL debug trace.

- Examine certificates and certificates exchanged with Trading Partner.

Issue: Remote Connect:Direct is not able to authenticate with IBM Sterling Connect:Direct Server Adapter.

Cause: This issue may occur due to below causes

- User account is not configured properly

- User account is configured properly, but it is LDAP authentication and there is an issue with LDAP Server

- User account is setup properly, but Remote Connect:Direct system is using wrong credentials.

- Mailbox does not have proper permission

Sterling Connect:Direct Server Adapter configuration.

Configuration of user account

Configuration of mailbox and permission

Configuration on Remote Connect:Direct System in regards to what credentials they are using.

Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

Authentication.log Logging level ON

mailbox.log Logging level ON

Issue: Sterling Connect:Direct Server Adapter is not enabled

Cause: This issue occur if adapter is not configured properly or if there is a port conflict.

Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

servicesctl.log Logging level ON

Issue: Sterling Connect:Direct Server CopyTo Service corrupt file contents

Cause: This happens in scenario where file go though multiple platforms like, file on Windows system is transferred in mailbox and then later forwarded via Sterling File Gateway with custom protocol using Sterling Connect:Direct Server CopyTo Service to Trading Partner's Connect:Direct system on Red Hat Linux.

Sterling Connect:Direct Server Adapter configuration.

Sterling Connect:Direct CopyTo Service configuration.

BPML.

Status report, instance data and document from Sterling Connect:Direct Server CopyTo Service.

All the systems need to be examined as the file has transferred to different systems before delivering to Trading Partner. This will identify where the file is corrupted.

- Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

wf.log Logging level ON

- File Contents and File size to be examined on all systems.

Issue: Sterling Connect:Direct Server CopyTo Service does not create a file on Remote Connect:Direct system on mainframe with proper DCB attributes.

Cause: DCB attributes are not correct. DCB attributes are mentioned by the Remote system. This can not be guessed. Please work with administrator of remote Connect:Direct system to obtain proper DCB attributes and then mention correct attributes in Sterling Connect:Direct Server CopyTo Service.

Sterling Connect:Direct Server Adapter configuration.

Sterling Connect:Direct CopyTo Service configuration.

BPML.

Get proper DCB attributes from Remote Connect:Direct system.

Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

wf.log Logging level ON

Sterling Connect:Direct Server Adapter configuration.

Sterling Connect Server BP Response Service configuration.

BPML.

Status Report and Instance data from Sterling Connect Server BP Response Service .

- Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

wf.log Logging level ON

- Communication issue may need additional data like network traces, netstat output.

Sterling B2B Integrator Connect:Direct communication is slow.

Cause:

- Slow network

- Slow systems

- Configuration not tuned properly

Identify what Adapter/Service/Business process is slow and look at appropriate configuration.

Some tuning parameters are set in the Service/Adapter configuration.

- Sterling B2B Integrator logs:

cdinterop.log Logging level ON
cdinterop_cdjava Logging level ON
perimeter.log Logging level ALL

system.log Logging level ON

noapp.log Logging level ON

wf.log Logging level ON

- Sterling B2B Integrator Properties files:

Some tuning parameters are set at the property level.

- Network traces

- Netstat output

- System utilization statistics (CPU, memory)

- Thread dumps.