Note: This section applies to the Cleo VLTrader and Cleo Harmony applications only.
When starting your HTTP server for the first time, no users are defined and therefore no access is granted to your server. To initiate creation of HTTP users as oppposed to AS2 or ebMS peer-to-peer partners. See HTTP Service. First, activate the preconfigured "Local HTTP Users" local host. See Activating a host from a template. To create a new HTTP server login, clone the default "myTradingPartner" or another mailbox. Local HTTP user mailboxes can have actions, but unlike remote host/mailbox actions that perform remote host operations, local HTTP user actions can only perform local host operations that manipulate files within the user's home directory.
Multiple Local HTTP Users local hosts may be created allowing users to be grouped together with the same host properties; however, usernames (for example, Local HTTP user mailbox names) will remain unique across all Local HTTP Users local hosts.
Configuring Local HTTP User directories
Configuring access for HTTP host users
Use the HTTP tab to configure access for HTTP host users.
- Acceptable inbound files patterns
- Specify patterns that files that must match to be permitted inbound. Patterns can include wildcards and regular expressions. See Using wildcards and regular expressions. If specifying multiple file patterns, separate them with semi-colons (;) or commas (,). Alternatively, enter them on separate lines.
- Users have read-only access
- Restricts HTTP users to read-only access of files and directory listings in their home directory. Users with read-only access may only retrieve files or directory listings from their home directory.
- Users can overwrite files
- Allows files uploaded to this host by HTTP users to overwrite existing files of the same name. When this option is disabled, existing files of the same filename are not overwritten. When this option is enabled, existing files of the same filename are overwritten.
Note: This check box is disabled when you select the Users have read-only access option.
- Use default file name
- Allows the incoming file to be given the name specified in its associated field. Use this option to override the file name specified by the sender. This feature is useful in situations where the received file name must be something other than its original file name. This field can also include any of the supported macros allowing for the incoming file to be named, for example, with a date-time stamp. See Using macro variables (Destination File context) for a discussion of all applicable macros.
Note: This check box and field are automatically disabled when you select the Users have read-only access option.
- Users must connect on a secure port
- Limits users to SSL connections only. When selected, users will able to successfully authenticate only when an HTTP/s connection is used.
- IP filter required
- When you select the IP filter required check box, all mailboxes under this host require whitelist IP addresses to be entered. If no whitelist IP addresses are entered for a mailbox, that mailbox is set to “not ready”. If a mailbox has whitelist IP addresses entered, login to the mailbox is allowed only from the IP addresses configured. If a mailbox does not have any whitelist IP addresses entered, the mailbox user can login from anywhere.
- Password Policy
- Defines the security requirements that will be enforced for all local users. By default, the Password Policy used by all mailbox users is globally defined using the Enforce Password Policy option on the tab. See Other system options.
- Associated web portal
- Designates the Portal ID of the web portal associated with this HTTP user host. Select None or a specific Portal ID from the drop-down list. For information on web portal setup, see Configuring VLPortal Web Browser service.
- Portal Applets
- If the Portal Applets check box is selected, manual file transfer uses applets to overcome limitations of certain browsers run by users. The Applet transfer limit sets the maximum number of simultaneous transfers an applet session can attempt to use to transfer a set of files and the Users can zip uploads option allows the user to compress the files being uploaded into a single zip file. If Use metadata is selected, then the metadata configured for the portal will be used to prompt the portal user for additional information. For information on web portal metadata setup, see Configuring manual file transfer metadata.
- Users can view transfers for all mailboxes associated at the Trading Partner level
- Select this check box to give users the option of including other mailboxes associated with the Trading Partner(s) that the users' mailbox is associated with in the File Transfer History table.
Configuring HTTP for Local HTTP Mailbox
- Username
- The mailbox alias. This value is used by your trading partner to log in to your HTTP server. Specify a value not already in use.
- Password
- The password for the mailbox. This value is used by your trading partner to log in to your HTTP server.
- User SSL Client Authentication
- Select this check box to enable public key-based SSL client authentication. Clear the check box to enable WWW authentication.
- Certificate
- If you select the User SSL Client Authentication check box, specify the certificate you want to use. You can click Browse to navigate to and select a certificate.
- User Home Directory
- Defaults to a username subdirectory under the default root directory defined on the General tab (see Configuring Local HTTP User directories). To override this path for this user only, clear the Use Default Root\Username check box and click the ... button to change the home directory; or select a custom macro variable from the drop-down list. See Using macro variables Using Macro Variables for a list of the applicable macros (Default Root Directory context).
- LDAP Usergroup
- Select the LDAP Usergroup check box to designate the mailbox as an LDAP user group mailbox and enable the Mailbox LDAP Tab (see Configuring LDAP for Local HTTP Mailbox. Many of the other fields on this tab are disabled as they are no longer applicable. An LDAP user group mailbox has the following features:
- The mailbox no longer corresponds to a single user, but rather a group of users configured in an external directory server.
- In addition to authenticating usernames and passwords through the external directory server, user home directory paths can also be provided by the directory service, if necessary, by selecting Use LDAP Home Directory. If this option is not selected, and Use Default Root\Username is selected, the VersaLex application dynamically appends the username to the root directory by way of a
%username%macro variable.
- Unlock
- This button is enabled when the user has too many failed log in attempts. Mouse over the Unlock button to display when the user will be unlocked automatically or you must unlock the user manually. Click Unlock and then click Apply to unlock the user.
- Subdirectories
- Click Subdirectories to display the Local User Subdirectories dialog box. This dialog box displays host-level settings (read-only) for the current folder configuration and allows you to specify additional folders at the mailbox level in the field. You can add multiple paths (one path per line) in the Others field. All paths must be relative and cannot include reserved macro variables (for example,
%mailbox%). - Pipe Incoming Payload
- Allows for this trading partner to send to your HTTP server and redirect, or pipe, the incoming payload out through a different protocol. If the transfer out to the pipe mailbox fails, the transfer into the local mailbox also fails.
- Associate to Primary Mailbox
- Indicates an alternate host\mailbox location for payload transfers with this trading partner. Even if the primary mailbox is specified, all transfers are still classified under the local HTTP user host\mailbox (and not the primary host\mailbox).
Configuring LDAP for Local HTTP Mailbox
Use the LDAP tab to specify values to for this mailbox. The LDAP tab is enabled when you select the LDAP Usergroup check box on the HTTP tab.
The values you specify on this tab supersede the values specified on the LDAP Settings or LDAP Server page.
- Override System Settings
- Select the Override System Settings check boxes to enable their related fields.
- Base DN
- The base organizational unit where the users are defined. Contact your directory administrator for the correct Base DN value. (The Base DN value entered here can be overridden in a local user host LDAP mailbox.)
- Search filter
- Optional. Used to limit the amount of information returned from the LDAP server when many users are defined. A more restrictive filter can be specified as a comma separated list. If necessary, contact your directory administrator to determine the appropriate attributes and values. You can override the value entered here in a local user host LDAP mailbox.
- Extend Search Filter
- Used to append rules to the default search system filter. This field is enabled regardless of the status of the Override System Options check boxes.
- List
- Used to display a list of users and their attributes matching the Base DN and Search Filter.
Configuring IP Filter for Local HTTP Mailbox
Local HTTP Mailbox Advanced Properties
See Setting advanced host properties for information aobut how to use and set properties supported in all protocols. Additional available properties specific to Local HTTP Users include:
- Client Type
- Indicates a specific HTTP client that requires special processing of the inbound message. The default value is no specified client type.
- 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.
- Email On Flag
- If a flagged event occurs, email the event. See Configuring email or execute based on results.
- 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 Repetitive Listener Failures
- When "Email On Fail" is enabled and the same failure occurs each time an inbound message is processed by the Listener 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. If the failure can be associated with a specific host, an email alert will be sent when the failure is resolved. Failure resolution email alerts will not be sent for general Listener failures since it is not possible to determine that these types of failures have been resolved.
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.
- Email On Successful Receive
- Send an email notification after successfully receiving a file. See Configuring email or execute based on results.
- Email On Successful Send
- Send an email notification after successfully sending a file. See Configuring email or execute based on results.
- 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.
- 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. - Execute On Repetitive Listener Failures
-
When Execute On Fail is enabled and the same failure occurs each time an inbound message is processed by the Listener 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 every system restart if the failure occurs again. If the failure can be associated with a specific host, the Execute On Fail command will be executed again when the failure is resolved. 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. Executions of the "Execute On Fail" command for resolution of general Listener failures will not be done since it is not possible to determine that these types of failures have been resolved.
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. - Execute On Successful Copy
- After successfully copying a file using LCOPY, run a system command. This command may be used for post-processing the file. See Configuring email or execute based on results.
- Execute On Successful Receive
- After successfully receiving a file, run a system command. This command may be used for post-processing the file. See Configuring email or execute based on results.
- Execute On Successful Send
- After successfully sending a file, run a system command. This command may be used for post-processing the file. See Configuring email or execute based on results.
- Fixed Record EOL Characters
- End-of-line characters to be inserted and/or deleted.
- Fixed Record Incoming Delete EOL
- If Fixed Record EOL Characters has been specified and Fixed Record Length is greater than 0, indicates to look for and delete EOL characters while receiving a file.
Note: When using FTP ASCII mode, standard EOL characters may already be changing if transferring between Windows and Unix platforms.
- Fixed Record Incoming Insert EOL
- If Fixed Record EOL Characters has been specified and Fixed Record Length is greater than 0, indicates to insert EOL characters while receiving a file.
Fixed Record Incoming Delete EOL and Fixed Record Incoming Insert EOL are mutually exclusive properties.
- Fixed Record Length
- The fixed record length after which end-of-line characters need to be inserted and/or deleted.
- 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.
- High Priority
- Indicates whether incoming and/or outgoing transfers through the mailbox should be treated as high priority. When both high priority and regular priority transfers are active, the high priority transfers get a larger portion of the available bandwidth. Go to to set the
High Priority Transfers Percentage Available Bandwidth(defaults to 75). See Other system options for more information. - LCOPY Archive
- If specified, contains the directory for archiving LCOPY source files.
- Log Individual LCOPY Results To Transfer Logging
- When this option is enabled, a
<send>and<receive>result is logged to the transfer log for each file copied.Note: This is a Cleo Harmony and Cleo VLTrader option. - Macro Date Format
- Specifies the date format to be used when the
%date%macro is used. - Macro Time Format
- Specifies the time format to be used when the
%time%macro is used. - Maximum Incoming Transfer Rate (kbytes/s)
- Sets the maximum incoming transfer rate in Kbytes (1024 bytes) per second for each mailbox or host. The default value of
0does not limit the transfer rate. The Maximum Incoming Transfer Rate system setting might also limit the transfer rates. The system Maximum Incoming Transfer Rate value is used unless this setting is more restrictive. For simultaneous transfers, the number of active transfers also affects individual transfer rates. See Advanced system options. - Maximum Outgoing Transfer Rate (kbytes/s)
- Sets the maximum outgoing transfer rate in Kbytes (1024 bytes) per second for each mailbox or host. The default value of
0does not limit the transfer rate. The system setting might also limit the transfer rates. The system Maximum Outgoing Transfer Rate value is used unless this setting is more restrictive. For simultaneous transfers, the number of active transfers will also affect individual transfer rates. See Advanced system options for more information about Maximum Outgoing Transfer Rate. - Outbox Sort
- Controls the order in which multiple files are transferred for a PUT command. If
System Defaultis specified, the value set on the tab takes precedence. ForAlphabeticalordering, the file extensions are not used to determine the sorted order unless they are needed to make the filenames unique. - PGP Compression Algorithm
- Compression method used when OpenPGP packaging (with compression) is requested through the Mailbox Packaging tab. See Configuring mailbox packaging. If
System Defaultis specified, the value set on the tab is in effect. - PGP Encryption Algorithm
- Encryption method used when OpenPGP packaging (with encryption) is requested through the Mailbox Packaging tab. See Configuring mailbox packaging. If
System Defaultis specified, the value set on the tab takes precedence. - PGP Hash Algorithm
- Signing method used when OpenPGP packaging (with signing) is requested through the Configuring mailbox packaging. If
System Defaultis specified, the value set on the tab takes precedence. - PGP Integrity Check
- When OpenPGP encrypting (see Configuring mailbox packaging), include an integrity check on encrypted data. Can be disabled for compatibility with certain OpenPGP implementation.
- PGP Signature Verification
- Indicates whether or not signed inbound PGP messages should verified when inbound OpenPGP packaging is requested through the Mailbox Packaging tab. See Configuring mailbox packaging. In general, this property should be enabled.
- PGP V3 Signature
- Unzip Use Path
- Indicates whether or not zip entry paths should be used for LCOPY -UNZIP operations. When enabled, the entry's path is added to the destination path, unless the entry contains an absolute path. In this case, the absolute path is used in place of the destination path.
- Wait For Execute On
- Indicates whether execution should wait for processing to complete within an Execute On Fail, Execute On Successful Copy,Execute On Successful Receive, or Execute On Successful Send command. Note that this option does not apply to native AS400 execution.
- XML Encryption Algorithm
- The method used to encrypt/decrypt files when XML Encryption packaging is requested through the Mailbox Packaging tab. See Configuring mailbox packaging . If
System Defaultis specified, the value set on the tab takes precedence. - Zip Comment
- Specifies the comment to be added to the zip archive file in LCOPY -ZIP operations.
- Zip Compression Level
- Controls the level of compression for LCOPY -ZIP operations. If
System Defaultis specified, the value set on the takes precedence - Zip Subdirectories Into Individual Zip Files
- Indicates whether or not subdirectories should be bundled for LCOPY –ZIP –REC operations. When enabled, each first-level subdirectory (and all of its descendents) will be bundled together into an individual zip file. The name of this zip file may optionally reflect the subdirectory name if an asterisk (
*) is placed in the destination path. Any files that are directly off the source root directory will not be copied.
Local HTTP Mailbox Packaging
See Configuring mailbox packaging for information about payload file packaging.
Local HTTP Mailbox Action Commands
The HTTP Server does not independently invoke send and receive actions, but rather acts on the actions of the connected client. Default collect and release actions are provided to allow the server to make sent and received files available for processing.
Collect Action
#Initialize inbound file
LDELETE recvfile.edit
#Merge all files received into recvfile.edit
LCOPY -DEL -APE %inbox%/* recvfile.ediRelease Action
#Release all not yet available files
LCOPY -DEL %outbox%/../* %outbox%See Composing an action and Local command reference for more information.
HTTP Server Command Reference
Note: This section applies to the Cleo Harmony and Cleo VLTrader applications only.
The HTTP Server allows users to log into the Cleo Harmony or Cleo VLTrader application and store and retrieve files using standard HTTP. A full description of the HTTP protocol can be found in the RFC 2616 specification.
The following HTTP methods and parameters are accepted and processed by the Cleo Harmony or Cleo VLTrader HTTP server (these methods and parameters are also captured in the preconfigured host, Generic Cleo HTTPs).
| Purpose | HTTP Method | Parameters | Comments |
|---|---|---|---|
| Login | POST | request=connect0 | Login can also occur via other requests, but if using request=send and 401 Unauthorized is bounced back by Cleo Harmony or Cleo VLTrader, file content will be sent more than once. |
| Send
Inbound |
POST | request=send | Uploading inbound payload |
| directory= | Optional parameter; defaults to inbox/ | ||
| filename= | Optional parameter; name of file being uploaded | ||
| Outbound
Directory Listing |
POST | request=list | Listing available outbound payload |
| directory= | Optional parameter; defaults to outbox/payload/ | ||
| Receive
Outbound |
POST | request=receive | Downloading outbound payload |
| directory= | Optional parameter; defaults to outbox/payload/ | ||
| filename= | Name of file being requested for download | ||
| Delete
Outbound |
POST | request=delete | Deleting outbound payload |
| directory= | Optional parameter; defaults to outbox/payload | ||
| filename= | Name of file being deleted |
The Cleo Harmony and Cleo VLTrader applications also support HTTP PUT, GET, and DELETE methods for sending payload, receiving directory listings and payload, and deleting payload respectively, but the POST methods are recommended. Following are captures of example HTTP requests and responses demonstrating the above methods. While the examples below only show parameters on the POST line, the Cleo Harmony and Cleo VLTrader applications do accept requests using the application/x-www-form-urlencoded andmultipart/form-data Content-types.
Client initial connect request without authorization
POST /server?request=connect HTTP/1.1
Host: test.cleo.com:5080
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3I (Windows XP)
Content-length: 0 Cleo Harmony or Cleo VLTrader application response (unauthorized; both basic and digest Authentication is enabled)
HTTP/1.1 401 Unauthorized
Server: Cleo VLTrader/3.5 (Windows 2000)
Date: Tue, 22 May 2007 17:04:13 GMT
WWW-Authenticate: Basic realm="Cleo VLTrader"
WWW-Authenticate: Digest realm="Cleo VLTrader",domain="/server",qop="auth",nonce="0qenmpn44",opaque="4b4c37373332"
Connection: close
Content-Type: text/html
Content-Length: 80
<html><head><title> Unauthorized</title></head><body> Unauthorized</body></html> Client connect request with digest authorization
POST /server?request=connect HTTP/1.1
Host: test.cleo.com:5080
Connection: TE
TE: trailers, deflate, gzip, compressUser-Agent: RPT-HTTPClient/0.3-3I (Windows XP)
Authorization: Digest realm="Cleo VLTrader",username="cleo",uri="/server%3Frequest=connect",nonce="0qenmpn44",response="b4f7542bdedce937de6aa93078fcdf17",opaque="4b4c37373332",cnonce="f5f20437b69ca661e4aedfedb54f5c32",qop="auth",nc="00000001"
Content-length: 0 Cleo Harmony or Cleo VLTrader application response (authentication successful)
HTTP/1.1 200 OK
Server: Cleo VLTrader/3.5 (Windows 2000)
Date: Tue, 22 May 2007 17:04:18 GMT
Content-Length: 0
Set-cookie: jSessionId=3513ld61kg8bt; path=/
Connection: keep-aliveClient send (upload) request
POST /server?request=send&directory=inbox%2F HTTP/1.1
Host: test.cleo.com:5080
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3I (Windows XP)
Cookie: jSessionId=3513ld61kg8bt
Cookie2: $Version="1"
Authorization: Digest realm="Cleo VLTrader",username="cleo",uri=...
Content-type: application/octet-stream; name="test.edi"
Content-length: 1533
...payload...Cleo Harmony or Cleo VLTrader application response (send successful)
HTTP/1.1 200 OK
Server: Cleo VLTrader/3.5 (Windows 2000)
Date: Tue, 22 May 2007 17:19:59 GMT
Content-Type: text/html
Content-Length: 84
Connection: keep-alive
<html><head><title>OK</title></head><body>File successfully uploaded.</body></html>Client list request
POST /server?request=list&directory=outbox%2Fpayload%2F HTTP/1.1
Host: test.cleo.com:5080
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3I (Windows XP)
Cookie: jSessionId=3513ld61kg8bt
Cookie2: $Version="1"
Authorization: Digest realm="Cleo VLTrader",username="cleo",uri=...
Content-length: 0Cleo Harmony or Cleo VLTrader application response (listing successful)
HTTP/1.1 200 OK
Server: Cleo VLTrader/3.5 (Windows 2000)
Date: Tue, 22 May 2007 17:04:18 GMT
Content-Type: text/html
Content-Length: 402
Connection: keep-alive
<head><title>'cleo' mailbox</title></head><body><pre><H2>Download</H2>Server directory: outbox/payload/<hr>
2007/05/03 08:43:17 1.497kB <A HREF="/server/outbox/payload/test.edi" >test.edi</A><br>
2007/05/22 08:32:46 4.491kB <A HREF="/server/outbox/payload/test2.edi" >test2.edi</A><br>
2007/05/22 08:33:28 28.444kB <A HREF="/server/outbox/payload/test3.edi" >test3.edi</A><br><hr></pre></body>Client receive (download) request
POST /server?request=receive&directory=outbox%2Fpayload&filename=test.edi HTTP/1.1
Host: test.cleo.com:5080
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3I (Windows XP)
Cookie: jSessionId=3513ld61kg8bt
Cookie2: $Version="1"
Authorization: Digest realm="Cleo VLTrader",username="cleo",uri=...
Content-length: 0Cleo Harmony or Cleo VLTrader application response (receive successful)
HTTP/1.1 200 OK
Server: Cleo VLTrader/3.5 (Windows 2000)
Date: Tue, 22 May 2007 17:25:57 GMT
Content-Description: test.edi
Content-Disposition: attachment; filename="test.edi"
Transfer-Encoding: chunked
Content-Type: application/edi-x12; name="test.edi"
Connection: keep-alive
...chunked payload...Client delete request
POST /server?request=delete&directory=outbox%2Fpayload&filename=test.edi HTTP/1.1
Host: test.cleo.com:5080
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3I (Windows XP)
Cookie: jSessionId=3513ld61kg8bt
Cookie2: $Version="1"
Authorization: Digest realm="Cleo VLTrader",username="cleo",uri=...
Content-length: 0Cleo Harmony or Cleo VLTrader application response (delete successful)
HTTP/1.1 200 OK
Server: Cleo VLTrader/3.5 (Windows 2000)
Date: Tue, 22 May 2007 17:25:58 GMT
Content-Length: 0
Connection: keep-aliveA web browser can also be used by a trading partner to manually trade with VerasLex's HTTP server. A trading partner would use the Cleo Harmony or Cleo VLTrader address and HTTP server resource path to start (for example, https://test.cleo.com:6080/server):
After logging in, a simple web page is displayed to allow uploading and downloading of files.
Note: For information about a more robust web portal interface, see Configuring VLPortal Web Browser service.
Comments
0 comments
Please sign in to leave a comment.