Use generic AS3 Hosts to specify an AS3 installation based on a specific AS3/FTP server product.
This includes the product's specific server choreography, or the commands needed to successfully log in to the remote server and send and receive files. The product choreography for each generic AS3 host was established during AS3 interoperability testing with the server products, and a generic host for all interoperability-certified AS3 products is included in the VersaLex installation. Since these hosts were created for a test environment, you might need to adjust some settings and commands to establish successful file transfers in a production environment. If it is available, use a pre-configured host specific to your trading partner's remote server. This makes for a faster and easier set up of your installation.
The AS3 standard provides the ability to securely transport EDI (and other data, including binary and XML) to a remote host over FTP, guaranteeing that the message has not been changed in-transit and has been received and can be read only by the intended trading partner. A Message Disposition Notification (MDN) receipt further guarantees that the intended trading partner has received the message.
AS3 uses the FTP protocol as its transport mechanism to send and receive files over the Internet. VersaLex uses the PUT/GET action commands to transport the secure data to/from the remote host.
Connector Access & Licensing
Connectors require separate licenses and are governed by commercial terms. Although all connectors are accessible in-product by default, usage beyond the Customer’s contract is subject to audit and adjustment.
For compliance or subscription inquiries, please contact Cleo Sales.
AS3 Configuration
A host describes the remote server of your trading partner to which messages will be sent. The host's parameters specify its location and how it is reached. Your remote trading partner should have provided information to you in the form of a URL, which you will use to configure the host parameters.
This section describes how to configure a generic AS3 pre-configured host.
AS3 Host
The following sections describe how to configure any of the generic AS3 hosts. A host describes the remote server of your trading partner to which messages will be sent. The host's parameters specify its location and how it is reached.
AS3 Host: General Tab
The host General tab for an AS3 Host contains the fields described in detail below. The default values of these fields vary per generic or pre-configured host. For pre-configured hosts, the fields on the General tab typically remain unchanged unless you need to either connect through a forward proxy or change the Default Directories.
| Field | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Server Address | Either a fully qualified name (recommended) or an IP address. This is the address of your trading partner's server that will receive your messages. |
||||||||||
| Port | The port on the server where your trading partner will receive your messages. Default value: 80 for HTTP and 443 for HTTPs (SSL) |
||||||||||
| Connection Type |
The kind of connection you want to use for this host.
Default value: System Default |
||||||||||
| Forward Proxy | The address of the forward proxy you want to use for this host. Select the System Default check box to use the default proxy. See Configuring for a proxy for information about specifying a default proxy. |
||||||||||
| Default Directories |
Modify the default directories, if necessary. You can use macro variables from the drop-down lists. See Using Macro Variables for a list of the applicable macros (Default Host Directory context) and example usage. For Cleo VLTrader and Cleo Harmony, see URI File System interface overview for information about you can use a Cleo-provided or custom URI for the Inbox and Outbox. See Specifying default host directories for information about setting up system-level directories and custom directory macro variables.
Note: If the host is has an external association, the default directories might be managed outside of VersaLex and not shown here.
|
AS3 Host: AS3 Tab
Use the AS3 tab to specify values for AS3-specific parameters.
| Setting | Description |
|---|---|
| Overwrite duplicate file names | Disabled for AS3. |
| Use default file name | Disabled for AS3. |
| Add Content-Type Directory to Inbox |
Allows you to sort incoming messages based on content-type to a subdirectory under the Inbox specified on the General tab. Specify each of the Content-Types you want to direct to specific subdirectories by entering a name in the Directory field. You can specify directories for Content-Types of: EDIFACT, X12, XML, Binary, Plain Text, EDI Consent and Other (a default for messages with all other Content-Types you might receive). You can specify the same subdirectory for multiple Content-Types. You can also leave Directory entries blank, which causes any received messages of that Content-Type to be stored in the Inbox specified on the General tab. For IBM i / iSeries (AS/400) usage, see AS/400 Setup and installation or AS/400 PC network access setup for information on configuring the Content-Type Inbox settings to access the Native File System (NFS).
Note: If you use this feature, incoming messages are placed in the specified folder based on the content type specified in the HTTP header of the message. VersaLex does not check the actual content of the message to determine its content type.
|
AS3 Host: FTP Tab
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Security Modes |
If the AS3/FTP server requires use of the Secure Socket Layer (SSL), select a security mode.
Default value: SSL Explicit |
||||||
| Default Data Type | The data type used when transferring files to and from the FTP server. The only valid Data Type for AS3 commands is Binary. | ||||||
| Data Channel Mode |
The default behavior for opening data port connections between the AS3 client and AS3/FTP server.
|
AS3 Host: Advanced Tab
The host's Advanced tab contains several property settings fields. These settings typically do not affect the ability to connect to a host. However, you might want to change some of these settings when configuring a runtime environment.
See Setting advanced host properties for information about how to use and set the properties supported in all protocols. Properties available for AS3 include:
| Field | Description |
|---|---|
| Abort In Process Transfers | Indicates that the FTP server supports the ABORT command when a data transfer is interrupted. Possible values: On or Off Default value: Off
|
| Add Mailbox Alias Directory to Inbox | Appends a subdirectory at the end of the host's configured inbox directory. This allows files received through different mailboxes to be kept separate. Possible values: On or Off Default value: Off
|
| Add Mailbox Alias Directory to Outbox | Appends a subdirectory at the end of the host's configured outbox directory. This allows files to be sent through different mailboxes to be kept separate. Possible values: On or Off Default value: Off
|
| Add Mailbox Alias Directory to Receivedbox | Appends a subdirectory at the end of the host's configured receivedbox directory. This allows files that have been sent through different mailboxes to be kept separate. Possible values: On or Off Default value: Off
|
| Add Mailbox Alias Directory to Sentbox | Appends a subdirectory at the end of the host's configured sentbox directory. This allows files that have been sent through different mailboxes to be kept separate. Possible values: On or Off Default value: Off
|
| Allow Actions To Run Concurrently |
Normally, actions and host actions within the same host are allowed to run concurrently. You can use this property to not allow actions and host actions to run concurrently.
Note: This is a Cleo Harmony and Cleo VLTrader option.
|
| Allow Duplicate Incoming Message IDs | Ignores messages with duplicate message IDs and allows reprocessing of the message. Possible values: On or Off Default value: Off
|
| Avoid List Command When Space In Path | When using the retrieving nested subdirectories (GET –REC option) and any of the nested subdirectories have spaces, indicates that the FTP server does not properly handle spaces in the LIST command path and that CDs should be used to avoid the issue. Possible values: On or Off Default value: Off
|
| Base64 Encode Content |
Base64 is the encoding format used by Multi-purpose Internet Mail Extension (MIME) for transmitting non-text material over text-only communications channels. Base64 is based on a 64-character subset of US-ASCII, enabling 6 bits to be represented per printable character. Possible values: On or Off Default value: Off
|
| Canonicalize Inbound Signed Content | When this option is selected, a canonicalizer is used to ensure that ‘\r’ and ‘\n’ characters always occur together as ‘\r\n’. This option may be used when the inbound signature hash verification fails and the trading partner is using OpenSSL to sign its messages. Possible values: On or Off Default value: Off
|
| Command Retries |
If an error or exception occurs during a command, the number of times the command should be retried.
Note: Command Retries does not apply to exceptions related to TCP/IP or ISDN dial-up connections. This is because dial-up connections are managed by the framework so that they can be shared across actions.
|
| Compression- Signing Order | When both signing and compression are enabled, indicates which is applied first. Possible values: Sign then compress or Compress then sign Default value: Sign then compress
|
| Connection Keep Alive Timeout (seconds) |
Allows the connection to the server to remain open while the message is being processed by sending NOOP commands every n seconds. This setting may be lowered if the connection to the server is being closed before the message can be fully processed.
Default value: |
| Connection Timeout |
The amount of time allowed for each read operation.
Default value: |
| Data Socket Accept Timeout | The amount of time allowed for each read operation on the data port. Possible values: 0 - 600 seconds, where 0 indicates no timeout. Default value: 150 seconds |
| Delete Zero Length Files | Indicates whether files received that are zero-length (<= 5 bytes) should be deleted rather than processed. Possible values: On or Off Default value: Off
|
| Disable Address Resolution | Indicates to connect directly to an IP address if the IP address is known and a DNS lookup is not desired. Possible values: On or Off Default value: Off
|
| Do Not Send Zero Length Files | Indicates whether zero length files to be sent to the server should be ignored rather than processed. If the -DEL option is being used, any zero length file ignored will also be deleted. Possible values: On or Off Default value: Off
|
| Email On Check Conditions Met |
Send an email notification after running a CHECK command where the overall conditions of the check are met. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
|
| Email On Check Conditions Not Met |
Send an email notification after running a CHECK command where the overall conditions of the check are not met. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
|
| Email On Fail | If an error occurs during a command, email the error condition. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;), or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Flag | If a flagged event occurs, email the event. See Configuring email or execute based on results. Email addresses separated by commas (,), semicolons (;) or colons (:). The first address should be an internal email address. Possible values: Email addresses separated by commas (,), semicolons (;), or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Repetitive Action Failures |
When "Email On Fail" is enabled and the same failure occurs each time an action is run for a specific host, leaving this option unchecked suppresses emailing of the same alert multiple times. If the same email alert continues to be suppressed after 24 hours, the suppressed email alert will be sent every 24 hours and after every system restart if the failure occurs again. When the failure is resolved an email alert will be sent.
Note: This feature only suppresses multiple emails if the same failure occurs multiple times in a row. Suppression is not maintained across synchronized hosts.
|
| Email On Successful Copy | Send an email notification after copying a file using LCOPY. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Successful Receive | Send an email notification after successfully receiving a file. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Successful Send | Send an email notification after successfully sending a file. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Execute On Check Conditions Met |
After executing a CHECK command where the overall conditions are met, run a system command. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
Note: Note that if multiple files contribute to the conditions being met, and one of the file macros is in the command (e.g., %file%), the system command will be executed repeatedly - once for each file.
|
| Execute On Check Conditions Not Met |
After executing a CHECK command where the overall conditions are not met, run a system command. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
|
| Execute On Fail | If an error occurs during a command, run a system command. See Configuring email or execute based on results. Possible values: System command to be executed. Default value: The value specified for this property on the panel (if set). |
| Execute On Repetitive Action Failures |
When Execute On Fail is enabled and the same failure occurs each time an action is run for a specific host, leaving this option unchecked suppresses multiple executions of the Execute On Fail command. If suppression of execution of the command for this failure continues after 24 hours, the suppressed Execute On Fail command will be executed every 24 hours and after a system restart if the failure occurs again. When the failure is resolved, the Execute On Fail command will be executed again. Users must account for this by including the %status% macro variable for the Execute On Fail command (see Using macro variables) and then checking for a success or failure.
Note: This feature only suppresses multiple executions of the Execute On Fail command if the same failure occurs multiple times in a row. Suppression is not maintained across synchronized hosts.
|
| Email On Fail | If an error occurs during a command, email the error condition. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;), or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Flag | If a flagged event occurs, email the event. See Configuring email or execute based on results. Email addresses separated by commas (,), semicolons (;) or colons (:). The first address should be an internal email address. Possible values: Email addresses separated by commas (,), semicolons (;), or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Repetitive Action Failures |
When "Email On Fail" is enabled and the same failure occurs each time an action is run for a specific host, leaving this option unchecked suppresses emailing of the same alert multiple times. If the same email alert continues to be suppressed after 24 hours, the suppressed email alert will be sent every 24 hours and after every system restart if the failure occurs again. When the failure is resolved an email alert will be sent.
Note: This feature only suppresses multiple emails if the same failure occurs multiple times in a row. Suppression is not maintained across synchronized hosts.
|
| Email On Successful Copy | Send an email notification after copying a file using LCOPY. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Successful Receive | Send an email notification after successfully receiving a file. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Successful Send | Send an email notification after successfully sending a file. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Execute On Check Conditions Met |
After executing a CHECK command where the overall conditions are met, run a system command. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
Note: Note that if multiple files contribute to the conditions being met, and one of the file macros is in the command (e.g., %file%), the system command will be executed repeatedly - once for each file.
|
| Execute On Check Conditions Not Met |
After executing a CHECK command where the overall conditions are not met, run a system command. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
|
| Execute On Fail | If an error occurs during a command, run a system command. See Configuring email or execute based on results. Possible values: System command to be executed. Default value: The value specified for this property on the panel (if set). |
| Execute On Repetitive Action Failures |
When Execute On Fail is enabled and the same failure occurs each time an action is run for a specific host, leaving this option unchecked suppresses multiple executions of the Execute On Fail command. If suppression of execution of the command for this failure continues after 24 hours, the suppressed Execute On Fail command will be executed every 24 hours and after a system restart if the failure occurs again. When the failure is resolved, the Execute On Fail command will be executed again. Users must account for this by including the %status% macro variable for the Execute On Fail command (see Using macro variables) and then checking for a success or failure.
Note: This feature only suppresses multiple executions of the Execute On Fail command if the same failure occurs multiple times in a row. Suppression is not maintained across synchronized hosts.
|
| Email On Fail | If an error occurs during a command, email the error condition. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;), or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Flag | If a flagged event occurs, email the event. See Configuring email or execute based on results. Email addresses separated by commas (,), semicolons (;) or colons (:). The first address should be an internal email address. Possible values: Email addresses separated by commas (,), semicolons (;), or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Repetitive Action Failures |
When "Email On Fail" is enabled and the same failure occurs each time an action is run for a specific host, leaving this option unchecked suppresses emailing of the same alert multiple times. If the same email alert continues to be suppressed after 24 hours, the suppressed email alert will be sent every 24 hours and after every system restart if the failure occurs again. When the failure is resolved an email alert will be sent.
Note: This feature only suppresses multiple emails if the same failure occurs multiple times in a row. Suppression is not maintained across synchronized hosts.
|
| Email On Successful Copy | Send an email notification after copying a file using LCOPY. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Successful Receive | Send an email notification after successfully receiving a file. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Email On Successful Send | Send an email notification after successfully sending a file. See Configuring email or execute based on results. Possible values: Email addresses separated by commas (,), semicolons (;) or colons ( : ). The first address should be an internal email address. Default value:The value specified for this property on the panel (if set). |
| Execute On Check Conditions Met |
After executing a CHECK command where the overall conditions are met, run a system command. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
Note: Note that if multiple files contribute to the conditions being met, and one of the file macros is in the command (e.g., %file%), the system command will be executed repeatedly - once for each file.
|
| Execute On Check Conditions Not Met |
After executing a CHECK command where the overall conditions are not met, run a system command. See Configuring email or execute based on results.
Note: This is a Cleo Harmony and Cleo VLTrader option.
|
| Execute On Fail | If an error occurs during a command, run a system command. See Configuring email or execute based on results. Possible values: System command to be executed. Default value: The value specified for this property on the panel (if set). |
| Execute On Repetitive Action Failures |
When Execute On Fail is enabled and the same failure occurs each time an action is run for a specific host, leaving this option unchecked suppresses multiple executions of the Execute On Fail command. If suppression of execution of the command for this failure continues after 24 hours, the suppressed Execute On Fail command will be executed every 24 hours and after a system restart if the failure occurs again. When the failure is resolved, the Execute On Fail command will be executed again. Users must account for this by including the %status% macro variable for the Execute On Fail command (see Using macro variables) and then checking for a success or failure.
Note: This feature only suppresses multiple executions of the Execute On Fail command if the same failure occurs multiple times in a row. Suppression is not maintained across synchronized hosts.
|
| Fixed Record Outgoing Insert EOL |
If Fixed Record EOL Characters has been specified and Fixed Record Length is greater than 0, indicates to insert EOL characters while sending a file.
Note: When using FTP ASCII mode, standard EOL characters may already be changing if transferring between Windows and Unix platforms.
|
| Get Number of Files Limit |
Limits the number of files retrieved from a server directory listing by one GET command.
Default value: |
| High Priority |
Indicates whether incoming and/or outgoing transfers through the host should be treated as high priority. When both high priority and regular priority transfers are active, high priority transfers receive a larger portion of available bandwidth.
Note: This is a Cleo Harmony and Cleo VLTrader option.
Warning: Setting High Priority will not improve transfer rates if the trading partner’s bandwidth is the bottleneck.
|
| Ignore Exception After Quit | Indicates whether I/O errors that occur after issuing a QUIT command should be ignored. Possible values: On or OffDefault value: Off
|
| Ignore Retrieve Error Code |
Specifies FTP response codes (after a RETR) that should not be treated as errors.
Caution: Misuse may mask real errors.
Example: |
| Include Failure In Subject Of Email |
Includes the exception message in failure notification emails.
Note: Messages longer than 256 characters are truncated.
|
| Include Filename In Store Unique Command | Indicates whether the FTP server expects a filename when using PUT -UNI. Possible values: On or OffDefault value: Off
|
| Interim Retrieve | Marks successfully retrieved files as Interim Success instead of Success. Possible values: On or OffDefault value: Off
|
| Issue Command After Opening Data Connection | Delays issuing transfer commands until after the data connection is established. Possible values: On or OffDefault value: Off
|
| Keepalive Noop Command (seconds) | Interval for issuing NOOP commands while a data transfer is active. Possible values: 0 – nDefault value: 0
|
| LCOPY Archive | Directory used to archive source files copied using LCOPY. Possible values: Any local or shared directory. Macros supported. |
| Log Individual LCOPY Results To Transfer Logging |
Logs individual send/receive results for each file copied.
Note: Cleo Harmony and Cleo VLTrader only.
|
| Macro Date Format | Date format used by the %date% macro. |
| Macro Time Format | Time format used by the %time% macro. |
| Maximum Incoming Transfer Rate (kbytes/s) | Limits incoming transfer rates per host or mailbox. Possible values: 0 – n
|
| Maximum Outgoing Transfer Rate (kbytes/s) | Limits outgoing transfer rates per host or mailbox. Possible values: 0 – n
|
| Next File On Fail | Determines whether wildcard GET continues after a failure. |
| Only Retrieve First Available File | Limits wildcard GET operations to the first available file. |
| Only Retrieve Last Available File | Limits wildcard GET operations to the last available file. |
| Outbox Sort | Controls file transfer order for PUT operations. |
| Outgoing Insert EOL Between Interchanges | When Fixed Record Outgoing Insert EOL is enabled, also inserts EOL characters between EDI interchanges. Possible values: On or OffDefault value: Off
|
| Partner Email Address |
Email address of the trading partner. When set, it is used to send profile information and certificates.
Note: Cleo LexiCom only. For Cleo Harmony and Cleo VLTrader, this is managed through Trading Partner Management.
|
| Password Automatic Update (days) | Number of days after which a new FTP password is generated and applied, when Password Update Format is set. Possible values: 0–n daysDefault value: 0 days |
| Password Update Format | Format of the PASS command when changing a password. Server-defined. Use %old% and %new% placeholders (for example, %old%/%new%). |
| PGP Compression Algorithm | Compression algorithm used when OpenPGP packaging with compression is enabled. Possible values: System Default, ZIP, ZLIBDefault value: System Default
|
| PGP Encryption Algorithm | Encryption algorithm used for OpenPGP packaging with encryption. Possible values include: System Default, TripleDES, Blowfish, CAST5, DES, AES‑128/192/256, Twofish Default value: System Default
|
| PGP Hash Algorithm | Signing hash algorithm used when OpenPGP signing is enabled. Possible values include: System Default, MD2, MD5, RIPE‑MD‑160, SHA‑1, SHA‑256/384/512 Default value: System Default
|
| PGP Integrity Check | Includes an integrity check when encrypting OpenPGP messages. Possible values: On or OffDefault value: On
|
| PGP Signature Verification | Verifies signatures on inbound signed PGP messages. Possible values: On or OffDefault value: On
|
| PGP V3 Signature | |
| Post Get Command | Commands executed only after a successful GET. Use a SET command in the action before GET, not the Advanced tab. |
| Post Put Command | Commands executed only after a successful PUT. Can be set to QUIT to force reconnects. |
| Pre Get Command | Commands executed before a GET. Keeps logs scoped to GET operations. |
| Pre Put Command | Commands executed before a PUT. Prevents unnecessary connections when no files exist. |
| Pre Put Change Directory | Forces a CWD before issuing a PUT. Possible values: On or OffDefault value: Off
|
| Pre Put Command For First File Only | Executes Pre Put commands only once instead of per file. Possible values: On or OffDefault value: On
|
| Resume Failed Transfers | Attempts to resume failed transfers when retries are enabled. Requires FEAT, SIZE, and REST STREAM support. Possible values: On or OffDefault value: Off
|
| Retain Temporary Inbound Message Files |
Retains inbound temp files in the temp\ folder for diagnostics.
Note: Files are retained for seven days.
|
| Retrieve Directory Sort | Controls file download order and forces use of LIST. Possible values: Alphabetical, Date/Time Modified, Size |
| Retrieve Last Failed File First | Attempts the most recently failed file first on subsequent downloads. |
| Retry Delay | Amount of time (in seconds) before a retry attempt is made. Possible values: Any value greater than zero Default value: 60 seconds |
| Reuse SSL Session | Reuses the command port SSL session for data port connections when possible. Possible values: On or OffDefault value: Off
|
| Reuse SSL Sessions Across Actions | Allows SSL sessions from previous actions to be reused for connections to the same destination. Possible values: On or OffDefault value: On
|
| RSA-OAEP Key Algorithm Parameter | Specifies the mask and hash generation functions used when the RSAES-OAEP algorithm is used. Possible values: MGF1-SHA1, MGF1-SHA256, MGF1-SHA512Default value: MGF1-SHA1
|
| SSL Allow Legacy Renegotiation | Allows legacy SSL renegotiation. If disabled, RFC 5746 secure renegotiation is required. Possible values: On or OffDefault value: On
|
| SSL Cipher | Specifies the cipher used for SSL key exchange, encryption, and hashing. If unset, the server selects the cipher. Possible values: Any cipher from the supported list |
| SSL Maximum Protocol Version | Specifies the maximum SSL/TLS protocol version allowed. If blank, the most recent supported version is used. Possible values: SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2 |
| SSL Minimum Encryption Key Size | Specifies the minimum allowed encryption key size. Possible values: 0 – n bitsDefault value: 0
|
| SSL Minimum Protocol Version | Specifies the minimum SSL/TLS protocol version allowed. Possible values: SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2 Default value: SSL 3.0
|
| SSL Use Record Splitting | Enables 1/n‑1 record splitting in CBC mode as a mitigation for BEAST attacks. Possible values: On or OffDefault value: On
|
| Store Raw Sent Message | Stores a copy of the outbound message in the HTTP/sent directory. Possible values: On or OffDefault value: Off
|
| Terminate On Fail |
Stops the action when a command fails.
Note: Behavior differs for CHECK vs non‑CHECK commands.
|
| Unzip Use Path | Uses zip entry paths when extracting files via LCOPY -UNZIP. Possible values: On or OffDefault value: On
|
| Use Content Type For File Extension | Determines file extensions for inbound messages using Content‑Type instead of .file. Possible values: On or Off
|
| Use EPRT and EPSV | Uses EPRT/EPSV commands for IPv6‑style addressing. Possible values: On or OffDefault value: Off
|
| Use External IP Address in PORT request | Uses the external IP address in active‑mode PORT requests. Possible values: On or OffDefault value: Off
|
| Use Folded Headers For Outbound Messages | Enables line wrapping for outbound HTTP headers longer than 76 characters. Possible values: On or OffDefault value: Off
|
| Use NLST | Uses NLST rather than LIST for wildcard GET operations. Possible values: On or OffDefault value: On
|
| Use SMIME Over FTP Headers | Enables compatibility with pre‑AS3 servers by translating AS3 headers to standard SMTP headers. Possible values: On or OffDefault value: Off
|
| Wait For Execute On | Waits for Execute‑On commands to complete before continuing. Possible values: On or OffDefault value: On
|
| XML Encryption Algorithm | Specifies the encryption algorithm used for XML Encryption packaging. Possible values: System Default, TripleDES, AES‑128/192/256 Default value: System Default |
| Zip Comment | Comment added to zip archives created using LCOPY -ZIP. |
| Zip Compression Level | Controls compression level for zip operations. Possible values: 0 (none) – 9 (best) Default value: System Default |
| Zip Subdirectories Into Individual Zip Files | Bundles each first‑level subdirectory into its own zip file during recursive zip operations. Possible values: On or OffDefault value: On
|
AS3 Mailbox
Mailbox parameters allow you access to the remote host and define the security of files being sent.
You can use the AS3 mailbox wizard to configure your system for the most common setup. See Using the wizard to create a host or mailbox.
AS3 Mailbox: AS3 Tab
Select encryption and signing for sending messages and optional security for receiving messages. If an MDN receipt is required, you can also select the format and delivery method of that receipt.
| Setting | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Request |
Specify the S/MIME format for messages sent to the remote host.
|
||||||||||
| Receipt | Enables the MDN Receipt section. See MDN Receipt. | ||||||||||
| Encryption Algorithm | When Encrypted is selected, allows you to choose the encryption algorithm used to send messages to the remote host. The trading partner must support the selected algorithm. Default encryption method: TripleDES. See Cryptographic Services. |
||||||||||
| Key Algorithm |
When Encrypted is selected, specifies the algorithm used to encrypt the content encryption key with the trading partner’s public key.
|
||||||||||
| Signature Algorithm |
When Signed is selected, specifies how the signature hash is encrypted using your signing certificate.
|
||||||||||
| Hash/MIC Algorithm |
When Signed is selected in the Request section, this algorithm is used with the signature algorithm to secure the signature.
Note: If RSASSA‑PSS is used with SHA‑512, the signing certificate must support SHA256withRSA or stronger.
|
||||||||||
| Compress Content | When Compress is selected, the message is compressed using ZLIB to improve transfer efficiency and security, typically for large files. | ||||||||||
| Inbound Message Security | Indicates how inbound messages must be received. Select any combination of Force Encryption, Force Signature, and Force MDN Signature to enforce message security requirements. If no options are selected, inbound message security is not checked. |
||||||||||
| MDN Receipt |
Attributes of the Message Disposition Notification (MDN) receipt.
|
AS3 Mailbox: Certificates Tab
Associate a trading partner's signing and encryption certificates with this AS3 mailbox and override the signing and encryption certificates defined in the Local Listener, if necessary.
You must acquire your trading partner's signing and encryption certificates and provide yours to your trading partner. See Acquiring your trading partner's signing and encryption certificates and Creating and providing your signing/encryption certificates.
| Section | Description | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Trading Partner's Certificates |
|
||||||||||||||
| My Certificates |
|
Overriding AS3 Local Listener Certificates
By default, the certificates you configured on the Certificates tab of the Local Listener panel will be the certificates used to sign messages sent to your trading partner and decrypt messages received from your trading partner. See Configuring certificates for Local Listener.
Use Override Local Listener Certificates to select alternate certificates for signing and decrypting messages with this particular trading partner. If you do override the default the certificates, don't forget to export and exchange these alternate certificates with your trading partner.
AS3 Mailbox: FTP Tab
| Section | Description | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Login |
|
|||||||||||
| Headers |
|
AS3 Mailbox: Security Tab
If a Security Mode is specified in the host's FTP tab, a remote host can issue client certificates. If so, import the client certificate using Certificate management and then specify or browse for the imported certificate's alias and password.
AS3 Action
An action's parameters define a repeatable transaction for your mailbox designated for the host system.
AS3 Action: Action Tab
Use the Action tab to configure commands within the action. See Composing an action. See also FTP Command Reference for further information.
Verifying Your AS3 Names
When configuring a client to exchange messages with a Cleo VLTrader or Cleo Harmony AS3 server, you can use the following SITE command to verify the client has correctly defined the AS3-To and AS3-From names. The command syntax is:
SITE VERIFY AS3-To: ‘your-AS3-To-name’, AS3-From: ‘your-AS3-From-name’If your AS3 names are properly configured, the server returns a positive response. Otherwise, a failure response is returned.
When using a VersaLex client, you can use the %as3.to% and %as3.from% macros in place of your-AS3-To-name and your-AS3-From-name, and so on.
SITE VERIFY AS3-To: %as3.to%, AS3-From: %as3.from%
AS3-Specific Directories
The following additional directories are created either during the AS3 installation or as needed by the application:
| Directory | Purpose |
|---|---|
| lostandfound\ | Default inbox where incoming data is deposited when the application cannot determine where to put it. |
| AS3\ |
Location where raw (unprocessed) incoming and outgoing messages are stored. Incoming messages are located in the AS3\received directory and outgoing messages are located in the AS3\sent directory. These files can be helpful in diagnosing problems. Old files should be deleted or archived by the user, if necessary. The AS3\unsent directory contains raw header, data and message setup information files. These files are used if a message needs to be retransmitted, and are deleted automatically by the application once the message transfer has either completed successfully or has failed due to timeouts, exceptions, or the number of retries has been exhausted. The AS3\mdn directory contains subdirectories for received (and optionally sent) MDNs. This directory can be changed on the AS3 Service Panel. MDNs can be automatically archived by the application or manually archived by the user from the MDNs tab on the listener panel. Archived MDNs are stored inAS3\mdn\received\archive\mdn.zip or AS3\mdn\sent\archive\mdn.zip. The AS3\data directory contains an AS3msgs.txt file used by the application to determine the receipt of duplicate messages. Entries in this file are retained for the time interval configured on the AS3 Service panel . |
| temp\ | Temporary location where incoming messages can be stored while being processed by the application. By default, they are deleted automatically once the message has been completely processed; however, these files can be kept for problem diagnosis by using the Retain Temporary Inbound Message Files host-level Advanced property. These temporary files will automatically be deleted after 7 days. |
Comments
0 comments
Please sign in to leave a comment.