[Ramachandran R]

Dear David,

We use the following code snippet that will be used as inbound TPS to backup/archive in FTP and SFTP.  You may need to pass backup/archive directory of SFTP server. Kindly review the code snippt, and let me know if any clarifications needed.

# Extract the message ID from the incoming message arguments
keylget args MSGID mh

# Retrieve the raw message data using the message handle
set data [msgget $mh]

# Extract DRIVERCTL metadata from the message
set Filekeys [msgmetaget $mh DRIVERCTL]

# Get the file path from the DRIVERCTL metadata
keylget Filekeys FILENAME FilePath

# Get the backup directory path from the incoming arguments
keylget args ARGS.BKUPDIR bkupDir

# Extract the filename from the full file path (get the last element after ‘/’)
set Filename [lindex [split $FilePath /] end]

# Create a copy of the original message to modify and send back
set new_mh [msgcopy $mh]

# Prepare the output directory and file name for the outgoing message
keylset fileKeys OBDIR $bkupDir
keylset fileKeys OBFILE $Filename

# Wrap the fileKeys in a FILESET structure as required by Cloverleaf metadata format
keylset filesetKeys FILESET $fileKeys

# Set the updated DRIVERCTL metadata on the copied message
msgmetaset $new_mh DRIVERCTL $filesetKeys

# Continue processing the incoming message and send the modified message back
# as an acknowledgment that the file was fetched successfully
return “{CONTINUE $mh} {OVER $new_mh}”

[Ramachandran R]

Dear Jason,

I don’t remember from where I have downloaded the release notes, but it was from Concierge portal. Attached the same for your reference.

Thank you.

 

 

Attachments:

You must be logged in to view attached files.

[Ramachandran R]

We have implemented Microsoft Defender in our environment and, so far, have not encountered any issues. Below are the key details of our implementation for your reference:

Cloverleaf Version: 2022.09.03

Operating System: RHEL 9.5

Configuration: The entire Cloverleaf root directory has been excluded from Microsoft Defender’s scanning.

As a precautionary measure, request your IT Security team to first deploy Microsoft Defender in your development or testing environment in PASSIVE MODE. In this mode, Defender will only monitor and report potential threats without taking any automatic actions, allowing you to review and validate the findings before enabling active protection.

• This reply was modified 3 months, 2 weeks ago by Ramachandran R.

[Ramachandran R]

Yes, this is how we also managed to do.

[Ramachandran R]

Dear Keith,

Please check the below thread and see if it helps.

https://usspvlclovertch2.infor.com/forums/topic/intermittent-issues-with-basic-and-advanced-database-lookup-tables/

[Ramachandran R]

This solution is perfectly working fine. Thank you so much.

[Ramachandran R]

Thank you. This looks to be added in the newer version. I will try and update here if this resolves our issue.

[Ramachandran R]

After thorough testing with both SQL Server 2014 and SQL Server 2019 in Cloverleaf 20.1.3, it’s been confirmed that the issue lies not with the database, but with the patch itself.

Previously, we had a configuration where an Xlate pointed to the database-outbound thread within the same process. To resolve the issue, we had to separate the Xlate that utilizes the Advanced Database Lookup table into one process, and the database-outbound thread into another process.

In previous versions, such as 20.1.2, having both inbound and outbound processes within the same process, along with an Advanced Database Lookup table in Xlate, worked seamlessly for years. The sudden issue in 20.1.3 prompts the need for further investigation into its cause.

[Ramachandran R]

Dear Diana,

My bad, I didn’t see this response, it could have saved plenty of my time. Yes, this is what helped me.

[Ramachandran R]

I just made it work in our Cloverleaf 20.1.3.  Just for the documentation, provided below the steps,

Please download and try with the cpython from https://github.com/indygreg/python-build-standalone/releases/download/20230826/cpython-3.8.17+20230826-x86_64-unknown-linux-gnu-install_only.tar.gz

Unzip the package (assuming the path is $PYTHON_PATH) and add $PYTHON_PATH/bin to $PATH, add $PYTHON_PATH/lib to $LD_LIBRARY_PATH

Validate which Python is being used by hci user, it needs to be the path you had just set up.

You may need to install all the Python packages again and try from Cloverleaf

[Ramachandran R]

I just made it work in our Cloverleaf 20.1.3.  Just for the documentations, provided below the steps,

Please download and try with the cpython from https://github.com/indygreg/python-build-standalone/releases/download/20230826/cpython-3.8.17+20230826-x86_64-unknown-linux-gnu-install_only.tar.gz

Unzip the package (assuming the path is $PYTHON_PATH) and add $PYTHON_PATH/bin to $PATH, add $PYTHON_PATH/lib to $LD_LIBRARY_PATH

Validate which python is being used by hci user, it needs to be the path you had just set up.

You may need to install all the python packages again and try from Cloverleaf

[Ramachandran R]

Dear David,
Were you able to get this working, as we are having the same issue in both Cloverleaf 20.1.2 and 20.1.3. The Set up our Cloverleaf, platform, and Python version are the same as yours.

Thank you.

[Ramachandran R]

We also recently migrated from Cloverleaf 6.2.3 to 6.2.6, and having the same issue as mentioned in the original ticket. As a workaround we switch the thread autostart mode off, and then stop specific threads for any testing or validations.

[Author]

Replies