Documentation Comments

Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.

Reality V15.0 ()

Setting-up Remote Logon (Networking) (m6050+remotelogon.htm)

To	Reality
Version
Topic
Submitted by
Company
Location
Email address
Comment

Setting-up Remote Logon

The remote logon facility allows the user of a terminal logged onto a Reality database to log on to an account on another Reality database.

To configure a remote logon connection:

On the local host, set up a destination (either UNIX or Windows) entry for the remote host using the DDA protocol and, for the remote database, a Q-type (UNIX) or Remote Database (Windows) entry that references this destination entry.
- On UNIX, use the ROUTE-FILE Maintenance Utility (netadmin option 2).
- On Windows, use the netadmin Network Administration Utility.
Note: If the remote database is on the local host, these entries will already exist.
For each local user that will be allowed access to the remote database, create a network user-id for the remote database, specifying the name of the Q-type or Remote Database entry created in step 1 as the system name and a remote user-id and password to use:
- On UNIX, use the USERS-FILE Maintenance Utility (netadmin option 4).
- On Windows, add the network user-id to the user's profile (SSM Option 2 - Define User Profiles, option 17).
Notes:
- If the remote database is on a UNIX host, the remote user-id must be a host user-id that is the same as a Reality user-id on the remote database; the UNIX password must be used when connecting. If the remote database is on a Windows host, the remote user-id and password must be those on the remote database. See Differences between UNIX and Windows.
- If connecting to a remote database on a UNIX host, if you prefer you can use User Equivalence instead of network user-ids.
On the local database, use CREATE-ACCOUNT to create a remote account that references the required account on the remote database. Set the remote system name to the name of the Q-type or Remote Database entry you created in step 1.
Each local user that will be allowed access to the remote account must have a security profile that permits remote logon (SSM Option 3 - Define Security Profiles, options 13 and 14).

Once a remote account has been defined it can be accessed using the LOGTO command or by making it the default account for a local user-id (set SSM - Define User Profiles option 7).