Configure Odette FTP Adapter

If you use the Odette FTP Adapter and are using the Partner Profile XML file version 2.00 used in Sterling Gentran Integration Suite 4.3, you must modify it to match the new Partner Profile version 3.00.

If you use the Odette FTP Adapter and are using the Partner Profile XML file version 2.00 used in Sterling Gentran Integration Suite 4.3, you must modify it to match the new Partner Profile version 3.00. To modify the XML file, refer to the following table:
Section Name of Structure or Field Action Comment
Partner Profiles <GeneralParameters>

<PartnerProfileVersion>3.00

</PartnerProfileVersion>

</GeneralParameters>

Use correct version label of the Partner Profile. New Version label: 3.00
Physical Partner Description Add field and description content Mandatory in OFTP Partner database
Physical Partner SubMailbox Add field, if used. Optional
Physical Partner <AuthenticationCertificate

type =”…”>

<Subject>string</Subject>

<Issuer>string</Issuer>

<Serial> Bignumber_string

</Subject>

</AuthenticationCertificate>

Add Structure, if used. OFTP 2.0: Mandatory for security only. Structure may be repeated.
Physical Partner <AuthenticationCertificate

type =”Private Key”>

<Subject>string</Subject>

<Issuer>string</Issuer>

<Serial>Bignumber_string

</Subject>

</AuthenticationCertificate>

Add Stucture, if used. OFTP 2.0: Mandatory for security only.
Physical Partner/ CAPI DWindowSize Delete field  
Physical Partner/ IP IPFilter   Uses IPv4 or IPv6 addresses.
Physical Partner IP SSL Add field, if used. OFTP 2.0: Mandatory for security only.
Physical Partner IP CipherStrength Add field, if used. OFTP 2.0: Mandatory for security only.
Physical Partner IP <SSLCertificate

type =”…”>

<Subject>string</Subject>

<Issuer>string</Issuer>

<Serial> Bignumber_string

</Subject>

</SSLCertificate>

Add structure, if used. OFTP 2.0: Mandatory for security, only. Structure may be repeated.
Physical Partner Contract Description Add field and description content. Mandatory in OFTP Partner database.
Physical Partner Contract MultipleLoginSessions   Now used.
Physical Partner Contract DuplicateFilePeriod Rename

DuplicateFileProcessingTestings

To DuplicateFilePeriod

 
Physical Partner Contract SessionLogLevel Add fields. Optional
Physical Partner Contract GroupNameList Add fields, if used. Optional
Physical Partner Contract Secure Authentication Add fields. OFTP 2.0: Mandatory
Physical Partner Contract <TimeScheduleTable>

...

<TimeScheduleTable>

Delete structure and create schedules in the Scheduler. Initiator Business Process and Business Process user fields are still used.
Physical Partner Contract OdetteFTPAPILevel Rename OdetteAPILevel to OdetteFTPAPILevel  
Logical Partner Description Add field and description content. Mandatory in OFTP Partner database.
Logical Partner <FileServiceCertificate

type =”…”> <Subject>string</Subject>

<Issuer>string</Issuer>

<Serial>string</Subject>

</FileServiceCertificate>

Add structure, if used. OFTP 2.0: Mandatory for security, only. Structure may be repeated.
Logical Partner Contract Description Add field and description content. Mandatory in OFTP Partner database.
Logical Partner Contract FileTransmissionRetries Rename FileTransmitRetries to FileTransmissionRetries  
Logical Partner Contract SignedEERPRequest Add field, if used.  
Logical Partner Contract EERP/NERPSignatureCheck Add field, if used.  
Logical Partner Contract File Signing Add field, if used.  
Logical Partner Contract File Encryption Add field, if used.  
Logical Partner Contract CipherSuite Add field, if used.  
Logical Partner Contract File Compression Add field, if used.  
Logical Partner Contract CharEncoding Add field, if used.  
Logical Partner Contract Receive VitualFilenamePattern Add field, if used.  
Logical Partner Contract EERPTimeout Rename WaitForEERP to EERPTimeout  
Logical Partner Contract FileScheduleTimeout Add field, if used.  
Logical Partner Contract InboundBusinessProcess Add field, if used. Optional
Logical Partner Contract InboundBusinessProcessUser Add field, if used. Optional, if no Inbound business process is specified.

After changing the Partner Profile for version 3.00, import the Partner Profile into the new Odette FTP Partner Profile database. For additional information, see Odette FTP Partner Profile.