Overview#

The program validates the proper installation, configuration, and revision of the PeopleSoft PeopleTools client software on the computer hosting the DirXML Driver for PeopleSoft.

The CITester program performs all of the validation procedures in the same manner as the driver. Therefore, successful operation of CITester ensures proper client functionality for the driver.

The CITester completes the following checks during four phases:

  • Phase I: Ensures that a PeopleSoft client session can be created.
  • Phase II: Ensures that connection and authentication parameters to the PeopleSoft Application Server are correct.
  • Phase III: Verifies that the Transaction CI required fields and keys are present.
  • Phase IV: Verifies that the Schema CI required fields and keys are present.

There might be variations of the error message data depending on the PeopleTools release. The CITester program runs all platforms supporting Java 1.3.1 or later and uses the Java PeopleSoft Component Interface (PSJOA.jar) package for PeopleTools 8.4x.

When not using the default Schema CI, it will be necessary to build the APIs for the desired CI. See Chapter 4, "Customizing the Driver by Changing Data Schema Component Interface", of the PeopleSoft Driver Implementation Guide for information on building custom CI API JAR files.

Important Considerations#

When running this test you must either:
  • Set the CLASSPATH environment variable to include the path of the CITester.class, psjoa.jar and dirxmlcomps.jar files.
    • If a custom CI API JAR files is required, include it in CLASSPATH.
  • Set the –classpath option on the java command line to include the CITester.class, psjoa.jar and dixmlcomps.jar and any required custom CI API JAR files.
  • It is also important to note that the java for JRE/JDK version 1.3.1 or later must be installed and accessible via the PATH environment variable or be explicitly called out from the java command line.

How Do I Run the Test? #

On Windows#

From a command shell, execute the CITester.class test file. A sample CITester.bat file is provided as a reference that indicates the correct syntax and class files required to execute the test and the driver. To accept the test’s default values, press Enter. In Phase II, you are required to enter a value for the Application Server Name.

The test writes output to the screen and to CITesterOutput.txt. The output file is written to the location where CITester.class resides.

Linux#

From a command shell, execute the CITester.class test by executing a line similar to:
/opt/novell/eDirectory/lib64/nds-modules/jre/bin/java -classpath /home/<where ever the CITester.class is>:/opt/novell/eDirectory/lib/dirxml/classes/psjoa.jar:/opt/novell/eDirectory/lib/dirxml/classes/dirxmlcomps.jar CITester

Running#

You will be prompted for:
  • Enter the Application Server Name or IP address. Forward slashes are required when entering the Application Server Name (for example, //255.255.255.255).
  • Enter the Application Server Port Number.
  • Enter the PeopleSoft UserID.
  • Enter the PeopleSoft UserID Password.

Phase I: Creating a PeopleSoft Client Session#

If the test program establishes a session with the PeopleSoft client, you will see the following message:
** PeopleSoft client session established successfully.

Phase I Errors#

You might encounter the following errors during the test. Suggestions for resolving errors are provided below.
Error MessageSolution
Exception in thread "main" java.lang.NoClassDefFoundError: psft/pt8/util/PSProperties.|You must add a path to the 8.4x psjoa.jar file to the environment CLASSPATH variable or set the path to the psjoa.jar file in the java command line.
This error will also occur if an invalid version of the JVM (JRE/JDK) is being used. Refer to the Important Considerations at the beginning of this document for more information.

Phase II: Authenticating to the PeopleSoft Client#

If the test program verifies the connection and authentication parameters, you will see the following message indicating success:
** The Connection and Authentication Parameters are verified to be correct.

Phase II Errors#

You might encounter the following errors during the test. Suggestions for resolving errors are provided below.
Error MessageSolution
ERROR: Failed Connection to the PeopleSoft Application Server.Please make sure you entered your authentication information correctly.
PeopleSoft Error/Warning Messages Pending.
Number of Messages: 1
Message 1: Connect Failed: No additional information available (90, 01)
The target Application Server generates error and warning messages. This error indicates that you entered the wrong Application Server Name or Application Server Port Number.

Ensure that the Server Name or address you entered contains a leading double slash (//) and that the address and name data is correct. Also, verify that you entered the Jolt port configured on the Application Server.
ERROR: Failed Connection to the PeopleSoft Application Server. Please make sure you entered your authentication information correctly.
PeopleSoft Error/Warning Messages Pending.
Number of Messages: 1
Message 1: DOWNbea.jolt.ServiceException: Invalid Session
This message indicates an invalid Application Server Name or Port Number. In some instances, if an invalid port number is specified the CITester program will hang and will require a manual interrupt.
PeopleSoft Error/Warning Messages Pending
Number of Messages: 2
Message 1: PeopleTools release (8.<num>) from web server is not the same as Application Server PeopleTools release (8.<num>) Access denied.
This message indicates that the PeopleTools version of the specified psjoa.jar does not match the version of the target PeopleSoft Application Server. PeopleTools requires a version match of the client and server.
PeopleSoft Error/Warning Messages Pending.
Number of Messages: 3
Message 1: <UserID>@<Client computer> is an Invalid User ID, or you typed the wrong password. User ID and Password are required and case-sensitive. Make sure you’re typing in the correct case.
Message 2: Failed to execute GetCertificate request
Message 3: Invalid certificate for user <User ID>
The target Application Server generates the Error/Warning messages. Either the User ID or User ID Password are incorrect or have been entered using improper case.

Phase III: Validating the Transaction Component Interface#

The driver uses a Component Interface to access application modification transaction records from the Application Server.

The field definitions of this interface must be identical to the DIRXML_TRANS01 Component Interface delivered with the driver. This test phase validates the field definitions of the named Transaction Component Interface.

Enter the Transaction Component Interface name or press Enter to validate DIRXML_TRANS01. If the test program retrieves and validates that all required fields and elements are present, you will see the following message:

** Retrieval of Transaction Component Interface "DIRXML_TRANS01" succeeded.

- Property 'DIRXML_DRIVER' is present and validated as key field.
- Property 'DIRXML_INST' is present and validated as key field.
- Property 'DIRXML_SCHEMA' is present.
- Property 'DIRXML_PROCESSED' is present.
- Property 'DIRXML_EVENT' is present.
- Property 'DIRXML_STATUS' is present.
- Property 'DIRXML_ASSOC_ID' is present.
- Property 'DIRXML_DESCR' is present.
- Property 'DIRXML_VALUE' is present.
- Property 'DIRXML_FIELDNAME' is present.
- Property 'DIRXML_FIELDKEY' is present.
- Property 'DIRXML_DTTM' is present and validated as key field.
- Property 'DIRXML_CURRDTTM' is present.

** Transaction Component Interface element validation succeeded.

Phase III Errors#

You might encounter the following errors during the test. Suggestions for resolving errors are provided below.
Error MessageSolution
PeopleSoft Error/Warning Messages Pending.
Number of Messages: 4
Message 1: Cannot find Component Interface {<Transaction CI Name>} (91,2)
Message 2: Initialization Failed (90,7)
Message 3: Not Authorized (90,6)
Message 4: Failed to execute PSSession request
ERROR: Retrieval of Component Interface <Transaction CI Name> failed.
The target Application Server generates error and Warning messages. This error indicates that the Transaction CI Name specified does not exist or cannot be found by the Application Server. Ensure that you specified the correct name.
-Property '<property field name>' is not required.This is only an advisory message. It indicates that an additional field or fields that are not required by the driver have been defined in the specified Component Interface.
ERROR: Transaction Component Interface element validation failed. Required Fields are not all present.The Transaction Component Interface specified does not contain all of the fields required by the driver. Verify that you entered the proper Transaction Component Interface name and validate that all fields contained in the default DIRXML_TRANS01 Component Interface are present.
ERROR: Property '<Key field name>' is not defined as key field.A field in the Transaction Component Interface is present, but is not properly configured as a key field. The Transaction Component Interface DIRXML_DRIVER and DIRXML_INST fields must be specified as key fields.

Phase IV: Retrieving the Schema Component Interface#

The Schema CI defines the application data that is to be synchronized via the driver. The specified Schema CI must contain a key field that is specified via the Data Record ID field name.

To test the Schema CI, type the Schema Component Interface name or press Enter to retrieve DIRXML_SCHEMA01. Enter the Data Record ID field name. If the test program retrieves and validates that all required fields and elements are present, you will see the following message:

** Retrieval of Schema Component Interface "DIRXML_SCHEMA01" succeeded.

- Property 'ASSOC_ID' is present and validated as Data Record ID Field.
- Property 'STATUS' is present.
- Property 'FULL_NAME' is present.
- Property 'FIRST_NAME' is present.
- Property 'MIDDLE_NAME is present.
- Property 'LAST_NAME' is present.
- Property 'BIRTH_DATE' is present.
- Property 'DEPT_ID' is present.
- Property 'DEPT_LONG_DESCR' is present.
- Property 'DEPT_DN' is present.
- Property 'TITLE_ID' is present.
- Property 'TITLE_SHORT_DESCR' is present.
- Property 'TITLE_LONG_DESCR' is present.
- Property 'MANAGER_ID' is present.
- Property 'MAIL_DROP' is present.
- Property 'ADDRESS1' is present.
- Property 'CITY' is present.
- Property 'STATE' is present.
- Property 'POSTAL' is present.
- Property 'MANAGER' is present.
- Property 'COMMON_NAME' is present.
- Property 'DISTINGUISHED_NAME' is present.
- Property 'DESCRIPTION' is present.
- Property 'EMAIL_ID' is present.
- Property 'PHONE_BUSN' is present.
- Property 'PHONE_CELL' is present.
- Property 'PHONE_HOME' is present.
- Property 'PHONE_PAGR' is present.

** Schema Component Interface element validation succeeded.

** All expected platform support is verified correct.
If you are testing a customized Schema CI, you will obviously see different field names. If there is more than one field designated as a Key field in the Schema CI, you will also see Property information messages such as:
- Property "KEY_2" is present and validated as a key field.
This message is provided to indicate the presence of additional "Get" Key fields in the Schema CI. The Driver will NOT use any "Get" keys for access other than the key field configured as the "Data Record ID Field".

Phase IV Errors#

You might encounter the following errors during the test. Suggestions for resolving errors are provided below.
Error MessageSolution
PeopleSoft Error/Warning Messages Pending.
Number of Messages: 4
Message 1: Cannot find Component Interface {<Schema CI Name>} (91,2)
Message 2: Initialization Failed (90,7)
Message 3: Not Authorized (90,6)
Message 4: Failed to execute PSSession request
ERROR: Retrieval of Component Interface <Schema CI Name> failed.
The target Application Server generates error and Warning messages. This error indicates that the Schema CI Name specified does not exist or cannot be found by the Application Server. Ensure that you specified the correct name.
ERROR: Specified Schema Component Interface Data Record ID Field '<Data Record ID Field Name>' not found.The field name specified as the key field of the Schema Component Interface is not in the Component Interface definition. Verify that you entered the proper field name.
ERROR: Property '<Data Record ID Field Name>' is not defined as key field.The field name specified as the key field of the Schema Component Interface is present but is not properly defined as the key field. Validate the Component Interface definition or verify that the proper field name was specified.

Summary#

At the completion of the test, the program provides a summary containing the results of the test. The validated parameters are shown below in the summary.
Component Interface Test Summary
--------------------------------
Full Component Interface Functionality has been verified.
The following parameters may be used for PeopleSoft 5.0 Driver Configuration

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-4) was last changed on 28-Apr-2016 05:04 by jim