![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
1.
2. Check the SSHFTP check box.
3. Click Enable.
1.
4. In the Edit Protocol Binding dialog, click the Transports tab.
5. Select the SSHFTP check box in the Allowed Inbound Transports area.
6. Click Edit Settings next to the selected transport.
Table 38 Inbound SSH Settings
• host_name is the name of the machine (server) where the SSHFTP server is running
• port is the port on the machine to which the SSHFTP server is listening to
• path_name is the relative path that starts from the base directory of the SSHFTP server
• Password User account’s password must be configured.
• Keyboard Interactive It is a generic authentication method that can be used to implement different types of authentication mechanisms.
• Public Key BusinessConnect Server SSH private key must be configured.
• Public Key and Password BusinessConnect Server SSH private key and user account’s password must be configured.Note: ClientAuthenticationIdentity (for SSHFTP) under Business Agreement must have the TIBCO BusinessConnect Server SSH private key if either Public Key or Public Key and Password is selected.
•
• See SSH Server Public Key Retriever for more details.
•
•
•
•
•
• File Mask Choose to control file renaming. Enter a mask in the File Mask field.
• Script Choose to process files. Specify a script in the Scripts field.
• Select the Delete File check box, which causes each file to be deleted after it is retrieved, if this is allowed by the FTP server.See Supported File Mask Options for more information.See TIBCO BusinessConnect EDI Protocol User’s Guide for information on pre-defined and user-defined options for input file masks for EDI. Specify an SSHFTP script. See Appendix B, Scripts for information on how to write scripts, and File Specification Dialog for information on how to upload a script.See the JavaDoc on the TIBCO BusinessConnect SSH API in TIBCO BusinessConnect API Reference.
•
• Note: The FESI EcmaScript engine originally supported by TIBCO BusinessConnect is out of support by the vendor. It is good practice to use the Nashorn script engine as a substitute because the Nashorn script engine is roughly compatible with the FESI EcmaScript engine. If PGP unpackaging is required, the PGP keys used for the unpackaging are configured in the Inbound Document Exchange portion of the Document Security tab in a Business Agreement. PGP policy only takes effect if the Require PGP Processing check box is selected. The following options are available in the list:
• None No specific policies are mandated for the incoming message; the message can be signed and/or encrypted, with or without compression. However the message has to be PGP packaged in certain way, otherwise it will be rejected.
• Must Sign The incoming message must be and only be signed, with or without compression;
• Must Encrypt The incoming message must and only be encrypted with or without compression;
• Must Sign and Encrypt The message must be both signed and encrypted, with or without compression.
• Pass-Through In this mode, the software does not package the data in any way. The software takes the original notify message that the private process sent and forwards it over the Internet to the trading partner.
8. Click Save three times.Figure 46 No Key ConfiguredFigure 47 Configured Key is DifferentFigure 48 Configured and Retrieved Keys MatchFigure 49 Server Is Not AvailableThe credential will be normally named with a pattern <partner-name>-<hostname>-<port>-<algorithm>-<index>, such as partner-sshserver.com-10022-rsa-2 or partner-sshserver-dsa.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |