G Appendix: Troubleshooting Problems

This appendix contains information that may be useful if you encounter errors running Point-of-Service for the first time after an install.

The configuration steps enable Point-of-Service to communicate with Back Office and Central Office in order to receive parameter updates and to send EJournal and POSLogs up to Central Office. If you have problems, you may want to ensure the steps were successfully completed by the installer.

jndi.properties File Name

In the Central Office/Back Office Server Information window, you enter the host name for the Central Office server. In the
<POS_install_directory>/pos/config directory, there is a jndi.properties file for Central Office. When this file is created during installation, the name of the file includes the host name you entered for the Central Office server.

For example, if you enter centraloffice for the host name, the name of the created file is centraloffice.jndi.properties.

Secure RMI and Secure JDBC

Understanding SSL/TLS connection problems can be difficult, especially when it is not clear what messages are actually being sent and received. The SunJSSE has a built-in debug facility that is activated by the system property javax.net.debug.

To enable SSL debugging for the Point-of-Service server, add -Djavax.net.debug=all to the StoreServerConduit.bat file and restart the server:
```
set COMMAND "java %JAVA_OPTIONS% -Djavax.net.debug=all com.extendyourstore.foundation.config.TierLoader %CONDUIT_CONFIG%"
```
To enable SSL debugging for the Point-of-Service client, add -Djavax.net.debug=all to the ClientConduit.bat file and start the client:
```
set JAVA_OPTIONS=%JAVA_MEM_OPTIONS% %JAVA_OPTIONS%  -Djavax.net.debug=all
```

For information on understanding the debug output, see the following web site:

http://docs.oracle.com/javase/1.5.0/docs/guide/security/jsse/ReadDebug.html

In the log files for the server and client, look for HandshakeExceptions. The following examples list the most common exceptions:

Certificates not yet active—This occurs when the date on the store server is ahead of the date on the client. Because of this dated discrepancy, the certificate exported from the server has not become active yet.
Location for the Key Store or trust store is incorrect—For information about the files that are changed when enabling secure RMI, see the Oracle Retail POS Suite Security Guide.
KeyEncryptionService (RSA) is not located in the correct place—Due to this configuration error, the passwords in the XML files and posfoundation.properties file cannot be generated. An empty posfoundation.properties is created in OracleRetailStore\Server\pos\config and OracleRetailStore\Client\pos\config.

After fixing the KeyEncryptionService configuration issue, you either have to reinstall Point-of-Service or get a copy of the original posfoundation.properties file located in the <INSTALL_DIR>\product\ config and update the file. To update the file, follow the steps in the Oracle Retail POS Suite Security Guide to manually update the posfoundation.properties file.
Type of the store server Key Store is different than the type of the client trust store—To check the type, use the following keytool commands:
```
keytool -list -keystore <your_key_store_name_and_location>
keytool -list -truststore <your_truststore_name_and_location>
```
The above commands list the Key Store and trust store type and provider along with all the certificates that are stored in these files, as shown in the following example:
```
Keystore type: jks
 
Keystore provider: Oracle
 
Your keystore contains 1 entry
Oracle, Jul 9, 2009, keyEntry,
Certificate fingerprint (MD5): EF:33:FE:13:0D:EC:8C:64:1B:C1:89:4C:86:62:6C:53
```
Make sure that the Key Store type matches in both files.