Hi Hariom,
Migration of these protocols can be done on wM 9.5, and then you can transport the new settings to the newer versions.
As long as you do not require an active FTP Port on your IS it is advisable to migrate to SFTP instead of migrating to FTPS.
When you are currently using a FTP-Port in your IS-Port-Config it might be worth to be checked if this can be replaced by a WS-Notification and then get the offered file via SFTP from remote SFTP server instead of placing the file in the working directory of your local IS-FTP-Port.
See IS Built-In-Services Reference for the pub.client.ftp:* and pub.client.sftp:* folders for further informations.
See IS Administrators Guide for informations about how to set up server certificate and chain which can be used in HTTPS-Ports as well as outgoing HTTPS-Calls to Partner systems.
Remember to switch your HTTPS-Ports to “useJSSE=Yes” and set the Extended Settings in IS accordingly to disable unsecure SSLv3, TLS v1.0 and TLS V1.1 protocols. More details can be found in several threads here in the community.
When migrating from wM 9.5 to wM 10.5, you will need an intermediate Hop (either wM 9.12, wM 10.1 or wM 10.3).
Migrating from wM 9.8 to wM 10.5 should be possible as a direct migration.
See Supported Upgrade Pathes documentation in Empower´s or TechCommunity´s Documentation section.
Regards,
Holger
#Integration-Server-and-ESB#webMethods#webmethods-Protocol-and-Transport