Adapter for OFTP 9.0 | webMethods Adapter for OFTP Documentation | webMethods Adapter for OFTP Installation and User’s Documentation | Restrictions | Memory Efficient Approach
Memory Efficient Approach
The above approach is not memory efficient, hence the alternate approach of Adapter for OFTP is to use Trading Networks's large file handling feature and Integration Server's TSpace capability. With this approach, the large files received by OFTP Gateway are categorized into XML files and Non-XML files. Metadata of inbound file is stored in Trading Networks with oftpMessageIn as document type and the content is stored as part of separate transaction in Trading Networks. In Trading Networks the XML files are stored with partName as xmldata and Non-XML files are stored with partName as ffdata. Set the following properties to enable Trading Networks large file handling feature and provide the required TSpace size respectively:
This approach recommends you to have both Adapter for OFTP packages in the same Integration Server.