The OnePoint Diagnostics portal allows you to connect to remote servers. The remote servers must also have the same version of OnePoint Diagnostics installed and running.
Let's assume OnePoint Diagnostics is installed on three servers, with server names and port numbers as follows:
| Server Name | Port Number |
| serverx | 9030 |
| servery | 9030 |
| serverz | 9030 |
You can logon to the OnePoint Diagnostics portal environment of each server by entering the correct addresses in the browsers' address bar. Alternatively, you may choose to logon to one portal only, e.g. the serverx portal, and through the Remote Servers facility connect to the other two OnePoint Diagnostics environments. The latter option is explained here. It has the advantage that you don't need to switch portals to collect information about different servers.
Setting up a remote server is required if you wish to run a SSA ERP LN Diagnostic Scan of a Baan software environment running in client/server mode (see the help page on mandatory connections).
The procedure to setup one or more remote server connections is:
The difference between the options "Add Existing Server" and "Add New Server" is explained next.
Via "Existing Server" a wizard is started through which other OnePoint Diagnostics servers are detected automatically.
Other OnePoint Diagnostics environments can be detected when a TCP/IP broadcast command is accepted by those servers (which is typically true for servers on the same network segment). Another (remote) OnePoint Diagnostics server will see and accept the broadcast command when that (remote) OnePoint Diagnostics server is listening to the same port number as the local OnePoint Diagnostics server and the (remote) OnePoint Diagnostics server is configured to support incoming connection requests from the issuing (local) OnePoint Diagnostics server. You can use IP-address maintenance (as user admin) to check the settings of the (remote) OnePoint Diagnostics server.
When other (remote) OnePoint Diagnostics servers are detected via the "Existing Server" method, the "Add Remote Servers Wizard" is started with a welcome message. After reading the introductory text, click "Next". Pressing the "Next" button activates the following screen:
Select one or more checkboxes and click Next. Passwords must be entered for each server:
By selecting the "Validate" button all remote servers are accessed with the (single) user name and the password as supplied for each server. When access is granted by the remote server, it will be added to your tree.
Note: If the wizard fails to detect an environment which fulfills the criteria (with respect to port number / user name / IP-address configuration) mentioned above, try to map the server by means of the "New Server" option mentioned next.
When no other (remote) OnePoint Diagnostics servers can be detected via the "Existing Server" method, use the "New Server" method which starts the following window:
Specify the name of the OnePoint Diagnostics server that is to be included in your tree. Specify the port number on which the local OnePoint Diagnostics server is running. At least that is common practice. Another port number easily could work but is not advised. Finally fill in the password as valid on the specified remote OnePoint Diagnostics server (for this OnePoint Diagnostics user account). When the "OK" button is selected, access to the remote server will be checked and when granted, the specified remote server is added to your tree.
Access to a remote OnePoint Diagnostics server is only granted when the active OnePoint Diagnostics user is defined on the remote OnePoint Diagnostics server. In order to achieve this, the OnePoint Diagnostics user account should have been created before on the (remote) OnePoint Diagnostics server. This is to be done by a local user of that remote OnePoint Diagnostics server. Either the OnePoint Diagnostics admin user needs to establish this or alternatively another local user with the rights to create other users. The password as entered on the remote OnePoint Diagnostics server is to be used during the procedure to connect to a remote server as outlined above.