4.4 Running and Evaluating the Test

4.4.1 Running the Test

To run the JCO Test utility on a Win32 platform:

  1. In Windows Explorer, double-click UserJCO3Test.bat. or In a command prompt, run the UserJCO3Test.bat script.

To run the JCO Test utility on a UNIX platform:

  1. In your preferred shell, run the userjco3test script file.

NOTE:When you run the test program, an error message sometimes appears before any test output is displayed. This indicates an improper installation of the JCO client components. The error messages are documented for each platform in Understanding Test Error Messages.

4.4.2 Evaluating the Test

If the JCO client is installed properly, the following output is displayed:

**The SAP JCO client installation has been verified to be correct.

Version of the JCO-library: version information
Input SAP Server Connection Information

You then receive a series of prompts for connection and authentication information. All data must be provided unless a default value, identified by [] delimiters, is provided. Failure to fill in a response value to each prompt ends the test. Enter the following when prompted:

  • Application server name or IP address

  • System ID

  • Connection type <APPServer - 1/ MSGServer - 2>

  • System number [00]

  • Client number

  • User

  • User password

  • Language code [EN]

  • SNC <Disabled - 1/Enabled - 2>

The values you provide are the same values that could be used to authenticate via the SAPGUI client. Based on the validity of the input, the test either displays error messages with solution suggestions or runs to completion. At the end of the test, a status message displays. If the test indicates full functionality as required by the driver, the status message displays valid values that can be used as the configuration parameters for the driver.

If the test indicates that the functionality required by the driver is not available, the following status message is displayed:

**There are <number> required BAPI functions NOT supported on this platform.

JCO Test Summary
JCO/BAPI functionality issues have been detected that will prevent proper driver functionality.

4.4.3 Post-Test Procedures

After the JCO Test utility has successfully passed all tests, you can create the driver. See Section 5.0, Creating a New Driver Object for more information. Make sure that the sapjco3.jar file is copied to the location where the sapumshim.jar file has been installed.

On UNIX systems, ensure that the environment variables used for the successful completion of the User JCO Test are also in the environment of the driver. If these conditions are met, there should be no driver errors that are related to the JCO.