When you run the server-side connection diagnosis tool from the Development Hub server, the following tests are run:
- Eclipse test machine
- The test attempts to ping the client machine specified by
eclipse-client.
- When the
-v flag is also set, the ping results are displayed. If no client machine is specified, the test is skipped.
- If the test fails, the server cannot ping the client machine, which suggests some sort of network configuration issue (such as a failed DNS lookup, or a firewall or routing issue). Contact your network administrator to troubleshoot further.
- Development Hub daemon status
- The test checks that the Development Hub daemon is running. The daemon is required if you are using either the
Micro Focus Development Hub using RSE or the
Micro Focus Development Hub using SAMBA, NFS etc connection type. If you are using another type of connection, the test is skipped.
- If the test fails, see
To launch a server on the remote host using a daemon process for details on restarting the daemon.
- Development Hub daemon connect
- The test checks that it can connect to the daemon.
- If the test fails, it could suggest a firewall problem, in which case, temporarily turn off the firewall and rerun the test. We also advise stopping and restarting the daemon; see
Configuring the Remote System Explorer Support for details.
- JVM version
- The test checks that the version of Java is from one of the supported vendors, and a supported version.
- If the test fails, you should check the version of Java against the list of supported versions listed in
Additional Software Requirements for Micro Focus Visual COBOL Development Hub.
- Required tools
- The test checks that all the required tools are present on the Development Hub. When the
-v flag is also set, a list of the required tools is displayed.
-
If the test fails, re-install the tools highlighted as missing.
Note: If the test indicates that
sed or
ed is missing, we advise that you also reinstall the Development Hub after the required tools have been re-installed.
- SE Linux
- The test checks if the SE Linux security module is enabled. This module is not supported with the Development Hub.
- If the test fails, you must disable the SE Linux module.
- License daemons
- The test checks that the license daemons are running during compilation and run time.
- If the test fails, you must start the license daemons by logging in with super user privileges and running:
/var/microfocuslicensing/bin/startmfcesd.sh
- Password crypt
-
The test checks if the password supplied is valid for the user ID.
Note: The test uses the
etc/passwd function as its authentication model.
-
If the test fails, check the user credentials using the substitute user (su) command.
- Compile & run
- The test checks that it can compile and run a program.
- If the test fails, rerun the test with the
-v flag set to provide more information, then troubleshoot as you would for a standard compilation or run-time problem.
- X Display
- The test checks that an X Server installation is running on the client machine.
- If the test fails, it indicates that either the specified X Server is not running or not configured to allow remote connections. Either start the X Server on the client machine, or if it is already running, configure it to allow remote connections. Refer to your X Server installation documentation for details on allowing remote connections.
- Shell.pm
-
The test checks if a Perl module called Shell.pm can be located.
- If the test fails, it means that Shell.pm is not found using @INC. To solve this, you could define the PERLLIB or PERL5LIB environment variable to specify the path to the missing module, and then restart the daemon.
- su to user
- The test checks that it can execute the
su command for the specified user name.
- If the test fails, contact your network administrator to troubleshoot further.
