A multiuser configuration of Developer means that a group of developers have shared access to a Developer Repository.
To run Developer in multiuser mode, you must have the Developer Server running on a dedicated workstation.
The Developer Repository may be located either on the Developer Server or the LAN file server. Both scenarios are illustrated in this section.
Locating the Developer Test Database
You create a Developer Test Database when you first run a Developer Test session. You must create a separate database for each Business Segment.
By default each Business Segment Database is located in a subdirectory under the working directory, named after the system, for example:
C:\Program Files\Enterprise Application Developer\WORK\TEST1 C:\Program Files\Enterprise Application Developer\WORK\TEST2
The location of the Database can also be specified in the Test Options dialog box accessed in Developer from the Business Segment Options dialog box.
The implications of the Developer Test Database location in multiuser mode depend on the particular configuration. There are three possible configuration scenarios:
1. Each developer in a group has a separate, local Developer Test Database. All developers in the group have access to the same Developer Repository.
2. All developers in a group have access to the same Developer Test Database. Each developer in the group has a separate, local Developer Repository.
3. All developers in a group have access to the same Developer Test Database. All developers have access to the same Developer Repository.
In all three cases, entries in the LINCDB.INI file and the current Repository settings must match before Developer Test can locate and access the Database.
Entries in the LINCDB.INI file identify where the Developer Test Database files were created last. These file locations are compared to the current settings in the Repository. In a normal Developer Test session, any discrepancy will result either in Developer Test closing or, if you have the necessary privileges, Developer Test will ask whether or not a logical reorganization should be continued.
Depending on how the Repository is opened, the LINCDB.INI file will be located in either the Repository directory or the Developer Test Database directory. When the Repository is opened in single user mode, the LINCDB.INI file is written to the Repository directory. When the Repository is opened in multiuser mode the LINCDB.INI file is written to the Developer Test Database directory.
In the three configuration scenarios cited above, scenarios 1 and 3 are examples of a Repository being opened in multiuser mode, so in both of these cases the LINCDB.INI file will be located in the Developer Test Database directory. Case 2 is an example of a Repository being opened in single user mode, so the LINCDB.INI file will be located in the Developer Repository.
In cases where each developer in a group has:
• A local Developer Test Database (configuration scenario 1) OR
• A local Developer Repository (configuration scenario 2) AND
• Developer is installed on a network drive THEN
• The working directory of LINCRUN.EXE and LINCDEV.EXE should be set to an existing local path for each developer.
If each developer requires a separate LINC.INI file, you should copy the LINC.INI file from the Developer application directory to the local path.
If a group of developers are sharing the LINC.INI file, you should set the -i option for LINCRUN.EXE and LINCDEV.EXE to the directory where the LINC.INI file is located.
Relocating the Developer Test Database
If you need to move your Developer Test Database from one location to another, you must remember to update the LINCDB.INI file so that it reflects the new location of the Developer Test Database.
For example, if you need to move your Developer Test Database from C:\SAMPLE to F:\SHARED\SAMPLE, you must follow the steps set out below to accomplish the database move successfully:
1. Move all the Developer Test Database files from C:\SAMPLE to the new location at F:\SHARED\SAMPLE.
2. Update the database paths in the Repository with the new location. 3. Update the LINCDB.INI file with the new location.
If you attempt to run Developer Test without updating the LINCDB.INI file first, you will incur the following problem:
1. Developer Test will compare the C:\SAMPLE settings in the LINCDB.INI file against the F:\SHARED\SAMPLE Repository settings and will find a discrepancy.
2. Depending on your user privileges, Developer Test will either close or tell you that a reorganization is necessary because it did not find the files in the place it last created them as shown by the LINCDB.INI file.
3. If you reorganize without updating the LINCDB.INI first, the reorganization utility would find no data in C:\SAMPLE. It would, therefore, create zero length files in F:\SHARED\SAMPLE by overwriting the files you moved to that location.
Developer Test hubbing to Business Integrator
Steps required for setting up Developer Test hubbing to Business Integrator. Configuration: Developer and Business Integrator located on the same machine. 1. Install Developer GCA and then Developer IC 3140.
2. Install Business Integrator IC 3080 and then Business Integrator IC 3140 (please do not install the version BI GCA)
3. Use computer management and stop DEVTEST hub socket service. Set the Service to manual start.
4. Make sure that _EXT_COMP hubsocket service is started. Please note that only one hubsocket socket is allowed to start on one machine as they all configured to run on port 6001. Hence this sample configuration will use _EXT_COMP hubsocket as the running service.
6. Edit Developer ntlinc,cfg (LINCIIDIR, LINCII_ENV) to match Business Integrator ntlinc.cfg located in <business_integrator_install_directory>\Config\
For example:
LINCIIDIR=C:\PROGRA~1\UNISYS\ENTERP~1.3 LINCII_ENV=_EXT_COMP
HUB_PORT=6001
This will allow Developer Test to use _EXT_COMP hub socket instead of DEVTEST hub socket.
7. Load your model into Developer.
8. Open Developer Test, click on File > Manage External Systems.
9. Add an external system - For more details, see Developer documentation or Developer online help.
For Example:
External name: HUBSOURCE Environment name: _EXT_COMP Business Segment: HUBSOURCE Enable: True
Default: True
10. You can create new database for the system 11. Open session.