Just as the proj file points to the locations of all PDS projects, the schemas file points to the locations of all databases. It is important that all users access the same schemas file (typically stored on a server) so that all can share the same data. As with the proj file, a directory should be created on the server for storing this file. In this example, it is named c:\ris. As with the proj file, the security can be set on this directory to domain users---change and domain administrators---full control.
The location of the schemas file is set using RIS Schema Manager. This utility is in the RIS XX.XX (where XX represents the version number) program group. Having multiple versions of the RIS client software loaded can lead to problems---make sure that you have only one RIS XX.XX program group. You should have a RIS program group on all nodes where PDS is loaded. If you load a RIS data server to a node where PDS is loaded, this may result in a newer RIS client being loaded. In this case, you should remove the older version (using the Configure RIS Version utility) and try to use the newer version of the RIS client software.
RIS communicates with remote nodes using a communication protocol such as TCP/IP, XNS, or DNP. TCP/IP is used as an example throughout this document. RIS has no interaction with file sharing protocols such as LAN manager. Installing or changing the settings of LAN manager has no effect on the ability of RIS to communicate with a remote database or to access a schemas file.
When using Windows, you have two options for getting to a schemas file on a server:
Use TCPIP as the protocol and specify a valid login on the server.
Specify a Local schemas file, but for the schema file location enter a UNC path that specifies the location on the server.
To use TCPIP as the protocol, you have to install and configure FTP Server on the server node (this procedure is not required for the clients). For Windows, you need to install Microsoft Peer Web Server. For Windows Server, you need to install Microsoft Internet Information Server.
Click Start > Settings > Control Panel. Double-click on Network, and then select the Services tab. Click Add.
Select Microsoft Peer Web Server on a Windows Workstation system or Microsoft Internet Information Server on a Windows Server system. Click OK.
Enter the location of the Windows distribution media and press ENTER.
Click OK on the Welcome form to display a checklist of components which can be loaded. The only required option is FTP Service. Selecting FTP Service will automatically select Internet Service Manager as well. Click OK to install the required files into the default directory.
The next form shows the default FTP Publishing Directory. This is the directory a user will be put into if they establish an FTP session and the user they log in as does not have a home directory specified. This can be changed to c:\temp. Click OK to install the FTP Service.
You may get the message "The guest account is enabled - do you want to disable guest access to the FTP service?" Clicking Yes is a prudent choice. The installation is complete and you can exit out of Control Panel.
Click Start > Programs > Microsoft Peer Web Services > Internet Service Manager (on a Windows) or Start > Programs > Microsoft Internet Server > Internet Service Manager (on a Windows Server node). You should see an entry for your node and that the service is running.
Double-click on the node name to activate the FTP Service Properties form. Disable Allow Anonymous Connections (an optional choice - if taken, accept the form warning about passwords being passed over the network) then select the Directories tab.
You should see an "Alias" for the home directory (c:\temp in this example). In this example it is assumed that the schemas file is located somewhere on the C drive. Click Add. For the directory, browse to the C drive and click OK. It should enter C: into the Directory box. Make sure that the "Virtual Directory" button is selected, enter C: for the Alias.
The colon (:) after the drive letter in the alias name is critical! It must be included as part of the alias name or RIS will find the schemas file but not display the schemas. At the bottom of the form also make sure that Read and Write have been selected.
Click OK on the Directory Properties form. In the FTP Service Properties form you should see the entry for your drive. Make sure that the colon (:) is included as part of the alias name. Click OK on the FTP Service Properties form to apply the change. Exit from the Internet Service Manager form.
Test the FTP service by going to another client open a DOS window and type ftp <server name> to open a connection to the server. Type a valid login on the server, type dir to list files in the c:\temp directory. Type get filename where filename is some file in the c:\temp directory. This simply tests the FTP connection.
The username you specify in the Locate Schema File form must also be able to log in at the FTP prompt as described above.
You can now do a Locate Schema File from a client node and specify TCPIP as the protocol.
In this example, a file named schemas in the c:\ris directory on the server CADSRV has been specified. The username/password is a login in the PDS domain that has the right to log on locally on the server. In this example, the generic user pds has been used. All client nodes should use the same operating system username when locating the schemas file.
When you click Apply, the system writes the location of the schemas file on the server into the parms file. The schemas file is not created until a schema is created. As with the proj_file directory, the directory where the schemas file is located should be backed up regularly.
The Locate Schema File operation should be performed on all client nodes so that they all refer to the same schemas file on the server. There is an exception to this rule, however. In certain cases, where many projects are being managed, some system administrators prefer to maintain multiple schemas files, each listing a number of related projects.
Using UNC path
You can use a UNC path to locate the schema file. Share the directory where the schemas file is located and on the client node go into the Locate Schema File form. Click Local as the protocol and for the schema file location type:
As an example \\pdssmp1\c:\ris\schemas. FTP Server is not required for this to work.
Some systems have not worked with the colon after the drive letter. In this case, use the following syntax:
Note however that locating the schemas file in this manner to a Windows Server node uses Windows licenses (as seen in Control Panel > Licensing under "Windows Server"). Windows Server is delivered with five user licenses. When user number six tries to access the schemas file using the UNC path method, they will get an error. Increasing the number of licenses will fix this problem, but you also cannot violate the terms of your license agreement (you must purchase additional Client License Packs to legally allow you to have the extra connections). On Windows Workstation nodes you are limited to 10 connections per share.