App Connect

Hi,

We are migrating our existing IIB V10 applications to ACE on CP4I on cloud. We have 25% of applications using FTP based nodes (FTPInput, FTPOutput, FTPGet) .. When we run Transformation Advisor Tool against these applications we are getting recommendations as below:

IIB05

Consider a different protocol rather than relying on local file integration.

True

True

The message flow contains an instance of a FileInput message flow node that relies on local file interaction and is not configured to use FTP. Although IBM App Connect Enterprise v11 continues to support reading local files with the FileInput node, for users who embrace a container-based architecture, this choice has architectural drawbacks. Consider changing your configuration to use FTP, or a more suitable messaging-based transport.

1. What exactly the architectural drawbacks of using FTP nodes as it is in ACE on CP4I?
2. Since changing more than 25% of applications to modify the protocol is a huge work for a migration project and it has impact in other timelines also. So is there a we can mount the file storage for ACE image and use the applications as it is to process the files in CP4I environment?

The file size processed by (input and output) IIB flows range from few MBs to 10 GB (some of batch process). For current IIB V10 on prem setup the file storage is mounted to IIB server as NAS mount. How these kind of applications can be migrated to ACE on CP4I?


Thanks,

------------------------------
Santhosh Ramanathan
------------------------------

I think there is no drawback using FTP nodes, the drawback is in working with local files.
This applies if your solution is running on 2 or more containers. If one container experiences a life cycle the local file my vanish without getting processed.
You will have to work with file systems that are independent from the container.
I would expect you could work with IBM Cloud File Storage as NAS provider.

------------------------------
Matthias Jungbauer
------------------------------

Original Message:
Sent: Fri January 22, 2021 07:29 AM
From: Santhosh Ramanathan
Subject: Migration of IIB Flows with FTP nodes to App Connect on cloud (CP4I)

Hi,

We are migrating our existing IIB V10 applications to ACE on CP4I on cloud. We have 25% of applications using FTP based nodes (FTPInput, FTPOutput, FTPGet) .. When we run Transformation Advisor Tool against these applications we are getting recommendations as below:

IIB05

Consider a different protocol rather than relying on local file integration.

True

True

The message flow contains an instance of a FileInput message flow node that relies on local file interaction and is not configured to use FTP. Although IBM App Connect Enterprise v11 continues to support reading local files with the FileInput node, for users who embrace a container-based architecture, this choice has architectural drawbacks. Consider changing your configuration to use FTP, or a more suitable messaging-based transport.

1. What exactly the architectural drawbacks of using FTP nodes as it is in ACE on CP4I?
2. Since changing more than 25% of applications to modify the protocol is a huge work for a migration project and it has impact in other timelines also. So is there a we can mount the file storage for ACE image and use the applications as it is to process the files in CP4I environment?

The file size processed by (input and output) IIB flows range from few MBs to 10 GB (some of batch process). For current IIB V10 on prem setup the file storage is mounted to IIB server as NAS mount. How these kind of applications can be migrated to ACE on CP4I?


Thanks,

------------------------------
Santhosh Ramanathan
------------------------------

Thanks Mathias for the response.

My understanding based on your reply is, then we can use the applications as it is in cp4i by attaching Cloud File storage as NAS Provider and make the file Nodes listen to local host path (just like on prem) and it process the files without any issues (considering I am using only one replication/instance of the application).

Please correct my understanding if it is wrong...

------------------------------
Thanks,
Santhosh Ramanathan
------------------------------

Original Message:
Sent: Mon January 25, 2021 05:57 AM
From: Matthias Jungbauer
Subject: Migration of IIB Flows with FTP nodes to App Connect on cloud (CP4I)

I think there is no drawback using FTP nodes, the drawback is in working with local files.
This applies if your solution is running on 2 or more containers. If one container experiences a life cycle the local file my vanish without getting processed.
You will have to work with file systems that are independent from the container.
I would expect you could work with IBM Cloud File Storage as NAS provider.

------------------------------
Matthias Jungbauer

Original Message:
Sent: Fri January 22, 2021 07:29 AM
From: Santhosh Ramanathan
Subject: Migration of IIB Flows with FTP nodes to App Connect on cloud (CP4I)

Hi,

We are migrating our existing IIB V10 applications to ACE on CP4I on cloud. We have 25% of applications using FTP based nodes (FTPInput, FTPOutput, FTPGet) .. When we run Transformation Advisor Tool against these applications we are getting recommendations as below:

IIB05

Consider a different protocol rather than relying on local file integration.

True

True

The message flow contains an instance of a FileInput message flow node that relies on local file interaction and is not configured to use FTP. Although IBM App Connect Enterprise v11 continues to support reading local files with the FileInput node, for users who embrace a container-based architecture, this choice has architectural drawbacks. Consider changing your configuration to use FTP, or a more suitable messaging-based transport.

1. What exactly the architectural drawbacks of using FTP nodes as it is in ACE on CP4I?
2. Since changing more than 25% of applications to modify the protocol is a huge work for a migration project and it has impact in other timelines also. So is there a we can mount the file storage for ACE image and use the applications as it is to process the files in CP4I environment?

The file size processed by (input and output) IIB flows range from few MBs to 10 GB (some of batch process). For current IIB V10 on prem setup the file storage is mounted to IIB server as NAS mount. How these kind of applications can be migrated to ACE on CP4I?


Thanks,

------------------------------
Santhosh Ramanathan
------------------------------