Upgrading to I/NET Rev 2.13 steps to follow if changing to Server/Remote Client configuration
I/NET site with release prior to 2.13
Help with upgrade to 2.13
Rev 2.13 Introduces a Server/Client option for I/NET Seven. The following steps should be taken if the upgrade is to change from a Filemaster with Equalized Clients to the new Server/Remote Client Configuration. Otherwise the normal upgrade procedure should be used. Note there are new DCU binary files as well as new DPU48k and SCU1284 binary files in this release. The DCU files introduce the Reliable messaging capability and the DPU48k and SCU1284 binaries introduce the door code control option.
- Open I/NET Config on each Equalized Client Host and drop the equalization.
- Open Host Masking on each Equalized Client and Clear all masks on all Links.
- Open I/NET Config on the Filemaster and make sure all Clients have been dropped.
- Open Host Masking on the Filemaster and make sure masks have been set to receive messages and trends from all hosts and NPRs on the network.
- Open Network Configuration on the Filemaster and make the Filemaster the Restore Host for all Links.
- Stop I/NET on all hosts. Start DbCreate on the Filemaster and make a backup.
- Install I/NET Seven Rev 2.13 on all hosts.
- Configure one host (Filemaster most likely) to be the Standalone Host which will act as the Server. Configure the remaining hosts to be Remote Clients pointing to the Standalone host.
- If ID Works was installed on an Equalized Client pc, use Administrative Tools on that pc to configure the System DNS Seven ODBC to connect to the SQL Server on the I/NET Seven Server pc.
- If there were Seven Trend definitions only on an Equalized Client, they must be created on the Server after the upgrade since Trends are no longer saved on the Remote Clients.
- Make sure the message and trend archiving is configured as desired on the Server since archives are no longer saved on the Remote Clients.
- If there were any Network Functions specified only on an Equalized Client they must be created on the Server since the Remote Clients no longer perform Network Functions.