Managed File Transfer

Hello,

I'm encountering an issue with IBM Sterling Connect for UNIX versions 6.3.0.0 and 6.3.0.3 iFix000 while running on RHEL 8.1, 8.6, and 9.4. We're using the FileAgent component to monitor specific folders and trigger execution processes based on file detection. The agent works fine in detecting files that meet certain criteria (e.g., a file named test.tsv), but during functional testing using default and production parameters, the agent self-terminates without any error messages or exceptions, as shown in the screenshot attached.

Here are the details:

• We followed the IBM documentation precisely during the installation and configuration.
• We moved a file to the monitored folder, but upon detection, FileAgent stops abruptly without providing any feedback or logging errors.
• This issue happens consistently, with no visible crash logs or exceptions to trace the problem.

For now, we've rolled back to IBM Sterling Connect for UNIX 6.1, which works well in our production-simulated environment. We're waiting for a fix or update to the current version, but we would appreciate any guidance or suggestions for troubleshooting the current issue in 6.3.0.x.

Has anyone else encountered similar issues, and how can we further diagnose or resolve this self-termination issue in the FileAgent?

Thanks in advance!

Hi,

When using Integrated File Agent (IFA) installed with CD UNIX 6.3, ensure you have enabled it by setting cdfa.enable=y in your CD UNIX initparm.cfg file.
The CD UNIX node will start IFA automatically. Do not attempt to start IFA manually!

With CD UNIX 6.3, the node monitors the IFA state periodically and will start or stop IFA based on the current cdfa.enable setting. You can review this activity in the related cdfastart/cdfastop/cdfapoll logs in your <cd_dir>/fileagent/logs directory.

This is different from CD UNIX 6.1 and Standalone File Agent 1.4.0, where the user is responsible to starting and stopping File Agent.

------------------------------
Volker Friedrich

Original Message:
Sent: Thu October 24, 2024 08:46 AM
From: Zeif Ramadhan
Subject: Issue with IBM Sterling Connect for UNIX FileAgent Self-Terminating (Version 6.3.0.x)

Hello,

I'm encountering an issue with IBM Sterling Connect for UNIX versions 6.3.0.0 and 6.3.0.3 iFix000 while running on RHEL 8.1, 8.6, and 9.4. We're using the FileAgent component to monitor specific folders and trigger execution processes based on file detection. The agent works fine in detecting files that meet certain criteria (e.g., a file named test.tsv), but during functional testing using default and production parameters, the agent self-terminates without any error messages or exceptions, as shown in the screenshot attached.

Here are the details:

• We followed the IBM documentation precisely during the installation and configuration.
• We moved a file to the monitored folder, but upon detection, FileAgent stops abruptly without providing any feedback or logging errors.
• This issue happens consistently, with no visible crash logs or exceptions to trace the problem.

For now, we've rolled back to IBM Sterling Connect for UNIX 6.1, which works well in our production-simulated environment. We're waiting for a fix or update to the current version, but we would appreciate any guidance or suggestions for troubleshooting the current issue in 6.3.0.x.

Has anyone else encountered similar issues, and how can we further diagnose or resolve this self-termination issue in the FileAgent?

Thanks in advance!

------------------------------
Zeif Ramadhan
------------------------------

Additionally, here is an excerpt from my Default_Config.json configuration file, which I converted from our production FileAgent setup. I am not running the FileAgent manually; I have already set cdfa.enable=y, ensuring that the FileAgent starts automatically.

Moreover, I am not using a password since this points to a local connection, which doesn't require a password, as configured in cdjai.properties with the following line:

# Set to "true" to allow no-password local connections.allow.local.connection=true

Despite this configuration, I am encountering the following error: "Snap title: Error: Logon failed! Userid or password may be invalid."

I have ensured that the firewall is disabled and verified the connections with netstat -tulpn. Could someone help me troubleshoot this issue?

Thanks in advance!

------------------------------
Zeif Ramadhan

Original Message:
Sent: Tue October 29, 2024 09:53 AM
From: Volker Friedrich
Subject: Issue with IBM Sterling Connect for UNIX FileAgent Self-Terminating (Version 6.3.0.x)

Hi,

When using Integrated File Agent (IFA) installed with CD UNIX 6.3, ensure you have enabled it by setting cdfa.enable=y in your CD UNIX initparm.cfg file.
The CD UNIX node will start IFA automatically. Do not attempt to start IFA manually!

With CD UNIX 6.3, the node monitors the IFA state periodically and will start or stop IFA based on the current cdfa.enable setting. You can review this activity in the related cdfastart/cdfastop/cdfapoll logs in your <cd_dir>/fileagent/logs directory.

This is different from CD UNIX 6.1 and Standalone File Agent 1.4.0, where the user is responsible to starting and stopping File Agent.

------------------------------
Volker Friedrich

Original Message:
Sent: Thu October 24, 2024 08:46 AM
From: Zeif Ramadhan
Subject: Issue with IBM Sterling Connect for UNIX FileAgent Self-Terminating (Version 6.3.0.x)

Hello,

I'm encountering an issue with IBM Sterling Connect for UNIX versions 6.3.0.0 and 6.3.0.3 iFix000 while running on RHEL 8.1, 8.6, and 9.4. We're using the FileAgent component to monitor specific folders and trigger execution processes based on file detection. The agent works fine in detecting files that meet certain criteria (e.g., a file named test.tsv), but during functional testing using default and production parameters, the agent self-terminates without any error messages or exceptions, as shown in the screenshot attached.

Here are the details:

• We followed the IBM documentation precisely during the installation and configuration.
• We moved a file to the monitored folder, but upon detection, FileAgent stops abruptly without providing any feedback or logging errors.
• This issue happens consistently, with no visible crash logs or exceptions to trace the problem.

For now, we've rolled back to IBM Sterling Connect for UNIX 6.1, which works well in our production-simulated environment. We're waiting for a fix or update to the current version, but we would appreciate any guidance or suggestions for troubleshooting the current issue in 6.3.0.x.

Has anyone else encountered similar issues, and how can we further diagnose or resolve this self-termination issue in the FileAgent?

Thanks in advance!

------------------------------
Zeif Ramadhan
------------------------------

Hello,

I'm encountering an issue with IBM Sterling Connect for UNIX versions 6.3.0.0 and 6.3.0.3 iFix000 while running on RHEL 8.1, 8.6, and 9.4. We're using the FileAgent component to monitor specific folders and trigger execution processes based on file detection. The agent works fine in detecting files that meet certain criteria (e.g., a file named test.tsv), but during functional testing using default and production parameters, the agent self-terminates without any error messages or exceptions, as shown in the screenshot attached.

Here are the details:

• We followed the IBM documentation precisely during the installation and configuration.
• We moved a file to the monitored folder, but upon detection, FileAgent stops abruptly without providing any feedback or logging errors.
• This issue happens consistently, with no visible crash logs or exceptions to trace the problem.

For now, we've rolled back to IBM Sterling Connect for UNIX 6.1, which works well in our production-simulated environment. We're waiting for a fix or update to the current version, but we would appreciate any guidance or suggestions for troubleshooting the current issue in 6.3.0.x.

Has anyone else encountered similar issues, and how can we further diagnose or resolve this self-termination issue in the FileAgent?

Thanks in advance!

https://www.youtube.com/playlist?list=PLszsSZY88sohwIF3djnBmtBqWP8ajf5ks 

This is IBM Sterling Connect:Direct channel and it has the videos on how to configure CD components. 

Hello,

I'm encountering an issue with IBM Sterling Connect for UNIX versions 6.3.0.0 and 6.3.0.3 iFix000 while running on RHEL 8.1, 8.6, and 9.4. We're using the FileAgent component to monitor specific folders and trigger execution processes based on file detection. The agent works fine in detecting files that meet certain criteria (e.g., a file named test.tsv), but during functional testing using default and production parameters, the agent self-terminates without any error messages or exceptions, as shown in the screenshot attached.

Here are the details:

• We followed the IBM documentation precisely during the installation and configuration.
• We moved a file to the monitored folder, but upon detection, FileAgent stops abruptly without providing any feedback or logging errors.
• This issue happens consistently, with no visible crash logs or exceptions to trace the problem.

For now, we've rolled back to IBM Sterling Connect for UNIX 6.1, which works well in our production-simulated environment. We're waiting for a fix or update to the current version, but we would appreciate any guidance or suggestions for troubleshooting the current issue in 6.3.0.x.

Has anyone else encountered similar issues, and how can we further diagnose or resolve this self-termination issue in the FileAgent?

Thanks in advance!

Hello everyone,

Thank you for the previous guidance regarding the File Agent issues. Following that discussion, I noticed someone shared a helpful video tutorial that briefly mentioned IBM Sterling CD Web Service as well. I decided to set up IBM Sterling CD Web Service version 6.3.0.3 to integrate with IBM Sterling Connect version 6.3.0.3, but I am facing some challenges with the integration process. Here's what I've tried:

Scenario 1:

1. I installed both services using the default self-signed certificate settings. I then exported the trusted certificates for both CD Web Service and Connect, placing them in their respective truststores to enable login via TLS 1.2. I followed the guidelines in IBM's documentation on establishing secure connections:
   https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=cscws-establishing-secure-connection-between-connectdirect-connectdirect-web-service.
2. I verified that the CN in the certificate matches the username and configured application.properties with the correct settings.
3. Despite these steps, login attempts are unsuccessful, with a fail certificate status message at login.

Scenario 2:

1. I tried using CA-signed certificates instead, creating and installing CA-signed certificates for both Sterling CD and CDWS.
2. However, the result was the same, with login attempts still failing.

Scenario 3:

1. I installed IBM Sterling CD Web Service version 6.2 alongside IBM Sterling Connect version 6.3.0.3, disabling Secure+ for all nodes in Connect:Direct and turning off the LCU strong password encryption to disable all security features.
2. When attempting to log in from the web interface to Connect, I received a "node down" error. I confirmed that the node is active, disabled the firewall, and verified connectivity by successfully running sample.cd.

It feels like I might be missing an important step here. Could anyone provide insights or suggestions on what might be going wrong in this setup, especially in UNIX version? Your assistance in resolving this would be greatly appreciated!

Thank you in advance for your help :).

https://www.youtube.com/playlist?list=PLszsSZY88sohwIF3djnBmtBqWP8ajf5ks 

This is IBM Sterling Connect:Direct channel and it has the videos on how to configure CD components. 

Hello,

I'm encountering an issue with IBM Sterling Connect for UNIX versions 6.3.0.0 and 6.3.0.3 iFix000 while running on RHEL 8.1, 8.6, and 9.4. We're using the FileAgent component to monitor specific folders and trigger execution processes based on file detection. The agent works fine in detecting files that meet certain criteria (e.g., a file named test.tsv), but during functional testing using default and production parameters, the agent self-terminates without any error messages or exceptions, as shown in the screenshot attached.

Here are the details:

• We followed the IBM documentation precisely during the installation and configuration.
• We moved a file to the monitored folder, but upon detection, FileAgent stops abruptly without providing any feedback or logging errors.
• This issue happens consistently, with no visible crash logs or exceptions to trace the problem.

For now, we've rolled back to IBM Sterling Connect for UNIX 6.1, which works well in our production-simulated environment. We're waiting for a fix or update to the current version, but we would appreciate any guidance or suggestions for troubleshooting the current issue in 6.3.0.x.

Has anyone else encountered similar issues, and how can we further diagnose or resolve this self-termination issue in the FileAgent?

Thanks in advance!