Technical Guide Reference Guide Frequently Asked Questions Tutorials
Show menu

Progress OpenEdge sender

Progress OpenEdge sender

The Progress OpenEdge sender can be used to call an OpenEdge procedure. The called procedure has no output parameter, but does have one or more LONGCHAR input parameters. If you use more than one input parameter, separate them with a ,

If a procedure has to be called with an input parameter and an output parameter, the Progress OpenEdge Gateway Service must be used.

The input parameters are filled with the String content of the MessagePart-In on the ConnectMessage. If you use more than 1 parameter, use ALL at the messagePart-in to make use of multipart messages (one per parameter).

In the table below, you will find an explanation of these properties. All attributes with a ‘*’ are mandatory.

Attribute

Description

Name*

By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional.

Enabled

Set this value to true, if you want this producer to be enabled.
Appserver Type

 

Set the type of your AppServer here. The following types are allowed:

  • DC, for AppserverDC
  • DCS, for secure AppserverDCS
  • Pacific, for PASOE Server
  • Pasific Secure, for secure PASOE Server

When selecting this type, the correct URL will be entered in the field AppServer URL.

AppServer URL*

URL to connect to the Progress AppServer / Pacific AppServer.

Username*

AppServer username.

Password*

AppServer password.

AppServer Info

AppServer info.

AppServer Procedure*

Name and path of Progress procedure.

AppServer Session

Choose AppServer session type.

AppServer Input Parameter*

Name of INPUT parameter of called procedure. If you need more than one parameter, use a , to separate the parameters.

MessagePart In

Name of the MessagePart in a ConnectMessage where the content of the file is being stored. If you have more than 1 input parameter use ALL.

Description

Description of the specific producer. This is for documentation purposes.

Overriden OpenEdge properties

With the use of a header enricher, it is possible to override certain properties of the OpenEdge Gateway.

  • openedge_procedure_name
  • openedge_appserver_url
  • openedge_appserver_username
  • openedge_appserver_password
  • openedge_appserver_info
  • openedge_appserver_session