Remote user file

You can use the remote user file to identify required information to connect to a remote host.

A remote-user file can have multiple entries, identifying multiple remote Enterprise Server environments.

For each entry, these information fields are available:

  • host

    Remote host name.

  • [communication protocol [:port number] !]

    Optional field

    Communication protocol: rexec | baan

    Port number: related port number of chosen protocol as set on the remote host.

  • BSE

    BSE path of the remote environment.

  • [userid]

    Optional field.

    OS account to use for login at the remote host. If not set, the local account is used.

  • password

    The password that is related to the previously mentioned or local account, stored in encrypted form.

  • [OS authorization or remote user]

    yes | no

  • [Enterprise Server authorization of remote user]

    yes | no

The remote-user file information is stored in the Systems (ttaad0550m000) session.

If the rexec protocol is selected, the value added in front of the BSE-path is rexec!. If the BaanLogin protocol is selected, the value added will be baan!. For example: 

red baan!/usr3/Baan 3F'L|9)c)Z0Rw4|F>=LW+KtpMG_^T1]3

The default protocol here is also rexec. Therefore: 

blue /usr3/BAAN40 3F'L|9)c)Z0Rw4|F>=LW+KtpMG_^T1]3

is exactly the same as: 

blue rexec!/usr3/BAAN40 3F'L|9)c)Z0Rw4|F>=LW+KtpMG_^T1]3

To use a port number that differs from the default, you must add the port number between the protocol and the exclamation mark with a colon as the separator, for example: 

red baan:8000!/usr3/Baan3F'L|9)c)Z0Rw4|F>=LW+KtpMG_^T1]3

The additional fields protocol and port are not yet supported from the session. Therefore, you must add these files manually to the r<user> file, if required.

Note that the rexec protocol is unreliable. The Baan Login protocol is preferred.