Troubleshooting
API errors
The external API is not always explicit about its problems, but there are a few common errors with simple solutions.
Failed to load API dll
PeopleSoft runs under the Oracle Tuxedo application server. There will be binaries from 4 different vendors mixed in this integration:
agent\aaftpsft* and util\psftping* from Bravura Security
Tuxedo API dlls from Oracle
PS API dlls
ODBC system client from Microsoft
After version 8.49, PeopleSoft changed from 32-bit client binaries to 64bit ones. In some PeopleSoft instances where an in-place upgrade was completed, both bitsizes of libraries (.dll) with the same name exist, in different directories; winx86 for 32bit and winx64 for 64 bit. The agent can report an error like "failed to load API dll" if the wrong bitsize is found in the System PATH before the correct bitsize library.
If there are several paths containing different versions of the PeopleSoft API, the one with the bitsize matching agtpsft*.exe must be the first one listed.
WARNING: LLE Configuration discovered! Note that LLE has been deprecated. You should upgrade to SSL to secure network links
After a PeopleSoft upgrade, the Tuxedo module in the PeopleSoft client produces this error. In this situation, util\psftping854.exe succeeds, but the agent still fails because the warning breaks the KVG input. Refer to the PeopleSoft documentation to configure the integration to use SSL.
Connect Failed: No additional information available (90,-1)
Later versions of Microsoft Windows 2003 lack the Microsoft Java Virtual Machine. The PeopleSoft External API requires this JVM (as of June 2004, v8.19.09 and earlier) and does not know how to use Sun’s JVM.
Microsoft is no longer allowed to distribute the JVM due to an injunction by Sun, and PeopleSoft has not yet acknowledged this problem. Search the Internet for Microsoft JVM Setup (msjavx86.exe) . In most search engines this should yield a download server.
PeopleSoft also provides their own jvm.dll. The PATH settings must correctly point to this file. If there are several paths containing different jvm.dlls, the PeopleSoft jvm.dll must be the first one listed.
Java exception thrown: java.lang.NoClassDefFoundError: bea/jolt/JoltSessionAttributes
The Peoplesoft External API has not installed a jar file which it requires. To fix this:
Search your PeopleTools share for bea.jar and copy it into the directory where you installed the External API. The default directory is:
C:\Pt810\bin\client\winx86_extapi
Edit your system Environment Variables to add the fully qualified path for the bea.jar file. For example:
CLASSPATH=C:\Pt810\bin\client\winx86_extapi\bea.jar
If IIS is installed, reboot the server to apply the new classpath.
Log onto the Manage the system (PSA) module and click Maintenance > Environment variables.
Ensure that the CLASSPATH is defined on the Server diagnostics page with the fully qualified path to bea.jar as specified above.
Testing
You can use the psftping program, in the <Program Files path>\Bravura Security\Bravura Security Fabric\<instance>\ util\ directory, to test connectivity with the API.
Run the program with no arguments on the command line. psftping prompts you for the PeopleSoft server’s address line in the format of //hostname:port, then prompts you for the administrator ID and password. It then tries to connect to the server. If it succeeds, it prints "Connected to server successfully.", otherwise, it prints "Failed to connect to Application Server <address>".
Check PSFT DB
Sometimes, the PSFT DB may have a listing thread locked for the DBUser configured in the ODBC connection (process running, but not using any resources, like CPU or disk I/O, only RAM and the RAM value not changing).
When that is the case, kill the listing process so the new connections from the ODBC connector can come though.