On Windows modify the file c:\ProgramData\Serena\Bridge\conf\startup.properties On UNIX /Linux modify the file: $DM_ROOT/ bridge_data/conf/startup.properties Change the line:
Steps 1) and 2) should be performed before any project configuration or data files are created on both the Unix and the PC side. It is always worth making backup copies of the files within the PVCSPROJ (i.e. the project root directory) as any mistake made is setting up the above NFSMAP file could result in the shared project files being re-written into Unix format.
We know that this environment should work and we have customers and us setting up this environment. However this is not a tested or certified environment, and you will have to make sure that you have enough resources in your UNIX box to cope with it, also no documentation about this is provided.
By default a Unix Server installation creates: /opt/pcms/oracle which is found on your machines root directory. A Unix client installation has no oracle database reference.
and makedb Refer to the document "Support: 62117: Wrapper for UNIX command-line executables to use the nfsmap file." to use these commands in a heterogeneous environment.
Check with the unix administrator to see what the default umask is set to for the group. This default must be writable for the group. This group must also be the user's primary group.
By default the Agent installers for UNIX do not update the auto update configuration file dfs/upgrade_config.dat. To enable auto update on an agent node add these lines to the configuration file: mode=agent server=<host>:<port> where: <host> is the hostname of the Dimensions CM server system. <port> is the port number on which the Dimensions CM server is listening (default: 671).
Setting the DMDB variable to DMDB=<BaseDB>@<SID > should stop Dimensions prompting for a password. This has to be in a Dimensions server installation only and it doesn't work for Dimensions client installation. Also you can modify the dimensions.rc
