The configuration steps described below are applicable to both multiuser configuration examples illustrated earlier in this section:
1. Set the Startup Parameters.
2. Configure the Developer Repository. 3. Configure the Developer Server. 4. Configure the client workstations.
Setting the Startup Parameters
1. Decide how you will use the LINC.INI file. That is, one LINC.INI file to be shared by all users or a separate LINC.INI file for each user. Consider the following scenerios: • Allow a single LINC.INI file for all users to ensure a uniform development
environment including colors and fonts used in the Developer application windows. The single LINC.INI file can specify the path to the Repository (REPOSPATH parameter) and all developers point the command-line of their Developer shortcuts to this LINC.INI file.
• Allow individual LINC.INI files and point to the Repository either from each LINC.INI file or from the command-line of the Developer shortcuts.
2. Decide where to locate the LINC.INI file and how to point to it.
Default locations in which Developer looks for the LINC.INI file are the working directory (in the shortcut properties) and the application directory. You can override both of these with a location defined by the /I command-line argument in the application properties.
Copy the file from the shared application directory into either:
• The working directory specified in the shortcut properties for Developer and Developer Test
• The directory specified by the command-line argument in the shortcut properties for Developer and Developer Test
You can then either delete the copy of the LINC.INI file from the shared application directory or leave it as a master copy.
3. Decide whether you will point to the repository using LINC.INI or using the shortcuts:
• LINC.INI
Set the Repospath parameter to point to the Repository directory on the Developer Server, and set the MultiUser parameter in the LINC.INI file to Y.
• Shortcuts
Edit all the shortcut properties to include the /R parameter to point to the Repository directory on the file server. For examples, see Developer Shortcut Properties later in this section.
4. Define the working directory in the properties of each of the shortcuts.
It is recommended that, for multiuser mode, you leave the working directory separate from both the Developer application directory and the Repository directory, to give each user the ability to customize settings.
The workstation must have read-write access to the working directory.
The location of individual Developer Test Databases in a multiuser environment has implications for the naming of the working directory. For details, see “Facts about the Working Directory” on page 5–3.
Configuring the Developer Repository
1. Check Repository installation.
Check that the Repository has been installed correctly on the file server. Your Repository directory (by default \Enterprise Application Developer\Rep) should contain repository data files. Repository data files have a .DAT extension. 2. Establish access rights to directories and files.
Ensure that the Developer Server has full read-write access to the drive and directory where the Repository is located.
If the Developer application (executable files) also resides on this or another server, check to ensure that all executable files are flagged as read-only.
If you have decided to use a single LINC.INI file for all users, ensure that all the client workstations have read-write access to the LINC.INI file.
3. Check the JADE.INI file settings.
This file, which is located in the Repository directory, should have its parameters set to optimize performance. On installation, default settings are assumed by the system.
Configuring the Developer Server
Note: The Developer Server does not require a hardware security key.
To configure the Developer Server:
1. Check Developer Server software installation.
Ensure that Developer Server software has been installed on the Developer Server workstation and that Server workstation can be accessed by all the client
workstations via TCP/IP.
Check that shortcuts were created for the Developer Server, Monitor, and Repository Utilities during the installation process.
2. Establish access rights to directories and files.
If the Repository is on a LAN file server, ensure that the Developer Server has login and read-write access to the LAN file server where the Repository is located. If the Repository is on the Developer Server, ensure that read-write access rights are available to the drive and directory where the Repository is located.
The Repository files must be flagged as read-write. This is to ensure that intermediate files can be created during initialization and deleted at closedown.
3. Check JADE.INI file for NodeName and other parameter settings.
The JADE.INI file is located by the Developer Server, Developer Monitor, and Repository Utility programs in the following order:
• Directory specified by the path parameter • Working directory / Start In directory • Windows directory
A path parameter must be given for the Developer Server and Developer Monitor programs to start. If a path parameter is not given for the Repository Utility program, and a JADE.INI file is not found, a new JADE.INI file will be created and placed in the Windows directory.
To ensure that your Developer Server is correctly configured, you should check and, if necessary, correct the following JADE.INI settings:
• The [JadeServer] section of the JADE.INI file contains a NodeName parameter. This node name is displayed in the title bar of the server window and does not have to be the same as the Windows machine name.
• The [JadeClient] section of the JADE.INI file contains a ServerNode parameter. The monitor program uses this server name to determine with which Developer Server it should communicate.
• The [JadeClient] section of the LINC.INI file contains a ServerNode parameter. This server name is the name of the Windows machine on which the Developer Server is running.
• The parameter settings in the JADE.INI file should be set to optimize performance. On installation, default settings are assumed by the system.
Running Developer Server as a Windows Service
The Developer Server controls multiuser interaction with a Developer Repository. You can configure your Developer Server to run as a Windows Service. When the Server is configured as a Service, the Developer Server program becomes simply an interface for configuring the Service, and can be opened and closed without affecting users currently connected to the Repository.
Note: Services can also be configured via the Control Panel.
To configure the Developer Server to run as a Windows Service: 1. Start the Developer Server from the shortcut.
2. Select the Service option from the Options menu in the Developer Server window. This displays the Service Configuration dialog box.
3. Check the Run Server as Service check box to register your Developer Server as a Service.
4. Click the OK button.
A Service named after the NodeName parameter in the [JadeServer] section of your JADE.INI initialization file is registered in the Windows registry in automatic startup mode. The RunAsService parameter in the [JadeServer] section of your JADE.INI initialization file is set to true. At this stage the Developer Server is only registered in the Windows registry as a Service. The Developer Server window must be closed to start the Service.
5. Select the Exit command from the File menu to close the Developer Server window. Next time you start the Developer Server (or reboot the machine), it will be run as an interface to configure the Service.
Alternatively, once the Service is registered, you can configure it by double-clicking on the Services icon in the Control Panel and selecting the appropriate Developer Server. To run multiple Developer Servers as Services on the same machine, each Developer Server must have a unique TCP/IP port number, as well as a unique NodeName parameter in the [JadeServer] section of the JADE.INI initialization file.
Any Developer Servers running as Windows Services must first be stopped and unregistered before you can uninstall them. To stop and unregister the Developer Server Service:
1. Start the Developer Server from the shortcut.
2. Select Stop Service from the File menu. This stops the Developer Server Service, and disconnects any users that may be connected to the Developer Server.
3. Select Service from the Options menu. This displays the Service Configuration dialog box.
4. Uncheck the Run Server as Service check box to unregister your Developer Server as a Service.
5. Click OK.
The entry for the Developer Server in the Windows Services is removed and the associated keys are removed from the Windows registry. The Developer Server application can now be uninstalled safely.
If the Developer Server is uninstalled without first unregistering the Service, the Windows registry keys need to be removed manually. Failure to remove them may cause problems with the Windows Services feature. To remove the Developer Server registry keys:
1. Start Registry Editor (REGEDT32.EXE). 2. Delete the following key folders:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NodeName Where NodeName is the name of your Developer Server running as a Service, as defined by the NodeName parameter in the [JadeServer] section of the JADE.INI initialization file.
3. Exit the registry.
4. Shutdown and restart Windows.
Caution
You should only use the Registry Editor if you are an experienced system administrator. Incorrect use of the Registry Editor can cause serious problems.
For more information about Windows Services, see your Windows documentation.
Configuring Developer Client Workstations
To configure Developer client workstations:
1. Implement and configure your network software. 2. Establish access rights to directories and files.
In a multiuser environment, the Developer Server requires read-write access rights to the drive and directory in which the Developer Repository is located. Client
workstations do not require access to the Repository or Repository machine. Client workstations must have read-write access rights to their nominated working directories.
3. Set the environmental variable TEMP for Developer Test forms creation. For example:
TEMP=C:\TEMP
For details on setting the TEMP environmental variable, see “Setting the TEMP Environmental Variable” on page 5–2.
4. Check the settings of the following parameters in the LINC.INI file: • Multiuser in [repository] section
For multiuser mode, this parameter should be set to Y. • Repospath in [repository] section
Set the Repospath parameter to point to the Repository directory on the Developer Server.
The Developer Server reads this parameter in the [JadeClient] section of the client LINC.INI file, and interprets the driver mappings for the Developer Server machine and not the workstation machine.
• ServerNodeSpecifications in [JadeClient] section
ServerNodeSpecifications defines the connection path to a remote Developer Server, using the ServerNode and TcpServerPort parameters. Enter these parameters in the following format:
ServerNodeSpecifications=TcpIp,<ServerNode>,<TcpServerPort>
Note that no white space is allowed between the ServerNodeSpecifications parameters.
The TcpIp parameter specifies that the TCP/IP transport protocol is used. The ServerNode parameter specifies the machine name or IP address of the Developer Server to which the LINC.INI file refers.
The TcpServerPort parameter specifies the port number that, together with the ServerNode parameter, identifies a Developer Server. The default value for this parameter is 6005. However, if you are running multiple Developer Servers on the same machine, you must ensure that this parameter corresponds to the appropriate value in the [JadeServer] of the Jade.ini file associated with the required Developer Server.
• TransientDbPath in [JadeClient] section
This parameter is set by the Developer installation. Ensure that the specified directory exists. The parameter value is only used if client applications do not have read/write access to the Repository directory.