2.109 .exec

.exec defines that the application should start a process specified by the path on the host (defined by the host name or IP address). It contains the program name, path, host name, and other information.

Definition

  • Data type

    string

  • Access

    get, set

  • changed event

    yes

  • C

    Identifier: AT_exec

    Data type: DT_string

  • COBOL

    Identifier: AT-exec

    Data type: DT-string

  • Classification

    object-specific attribute

  • Objects

    application

For the TCP/IP protocol, the attribute value has the syntax

"<host>[%<username>[%<password>]]:<path>"

where either the name of the host or its IP address can be specified.

To start the application side using SSH instead of RSH, the command specification can be prefixed with the scheme "ssh://" (example .exec "ssh://myserver:list";).

By default, the RSH protocol is used if no security scheme is specified with the .transport attribute. Otherwise, the SSH protocol is used. To deviate from this default, the appropriate scheme has to be specified with the .exec attribute. The SSH protocol is selected by "ssh://" and the RSH protocol by "rsh://".

The "ssh://" scheme also supports the OpenSSH command. First it is searched whether the libssh DLL is available. If it is not available, it checks whether an ssh command can be called. Additionally there is the scheme "sshlib://" to use only libssh and "sshcmd://" to use only OpenSSH. The disadvantage of the command is that no password can be used. OpenSSH must be configured to allow a connection without a password (see the man pages of ssh).

Example

Without SSH

With SSH

 
application Appl1 {
  .exec"host%account%passwd:list";
}
 
application Appl1 {
  .exec "ssl://host%account%passwd:list";
}

Without SSH

With SSH and SSL

 
application Appl2 {

  .exec "host%account%passwd:list";
}
 
application Appl2 {
  .transport "ssl";
  .exec "host%account%passwd:list";
}

Remarks

  • The attributes .transport, .connect, and .exec can only be changed if .active is set at false.
  • The attributes .connect and .exec depend on the transport mechanism used, i.e. future versions of the transport layer may have different types of connection establishment.
  • To use a colon before the syntactically required colon (in the name or password), this needs to be doubled. In the command part of the .exec attribute (after the mandatory colon) colons are taken over directly.
  • The additional command options required for SSL need to be specified with the command. Only the security scheme ssl, if used, is automatically included in the command as additional command line option -IDMtransport ssl.
  • The command line automatically gets the option -IDMtellport. If instead of an IDM server application a script or something similar is specified as command, then from the output of the IDM server application at least the line beginning with -IDMport has to be forwarded completely (including leading and trailing line breaks \n).

  • As of IDM version A.05.02.i, the Distributed Dialog Manager (DDM) supports the IPv6 protocol on all architectures that natively support IPv6.

See also

Object application

Manual “Distributed Dialog Manager (DDM)”