Socket Server Errors

Keystore was tampered with, or password was incorrect

The keystore file that establishes the trusted connection between Apache and the Socket Server could have been created incorrectly. This was an issue found prior to 10.4.2. To correct this:

Stop the socketserver.

Remove the webrf.jks file from the following location (installpath may vary) <installpath>\infor\sce\scprd\wm\socketserver\jwebsocket\conf

Run the following command from the Command Window (This will create a new

webrf.jks file). 
	 
		keytool -genkeypair -dname
			 cn=<servername>.<domain>.com,o=Infor10SCE,c=US
			 -keystore
			 <installpath>\infor\sce\scprd\wm\socketserver\jwebsocket\conf\webrf.jks
			 -keyalg RSA -alias webrf -storepass infor1234 -validity 1825 -keysize 1024
			 -keypass infor1234

Where the infor1234 password is arbitrarily chosen and only needs to match what is in the jWebSocket.xml file:

<installpath>\infor\sce\scprd\wm\socketserver\jwebsocket\conf\jWebSocket.xml

<!-- jWebSocket engine configuration --> (only this section needs the proper keystore location and password)

<keystore>C:\infor\sce\scprd\wm\socketserver/jwebsocket/conf/webrf.jks</keystore>

<password>infor1234</password>