bea.jolt.ServiceException Invalid Session

 bea.jolt.ServiceException Invalid Session

Reason:

If the following message appears on the login page :

CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS,

BECAUSE OF: bea.jolt.ServiceException: Invalid Session

Check your configuration.properties file which lives in the WEB-INF\psoftdocs\<site> folder.

For example on PeopleTools 8.51 with Weblogic the path might be:
PS_HOME\webserv\<site>\applications\peoplesoft\PORTAL.WAR\WEB-INF\psoftdocs\<site>\

The problem might be the hostname/port specified for psserver or psservername E.g.:

Psserver=servername: port

Solution:

Check that you have the correct server name and port here. Also make sure you use a host name and not an IP address. If this is incorrect. Stop the web server, fix the values and then start it back up again. This might have changed after you applied a PeopleTools patch - so make sure you backup configuration.properties before you apply a patch. Also check that the PTWEBSERVER user account is not locked.

Field is Required: HRS_JOB_OPENING - HRS_JOB_OPENING_ID (124,64)

Integration gateway: general connection Failed (158,10836)

Reason:

We send a XML Message to Vertex using HTTPTargetConnector in an app engine program in batch mode.
Occasionally we see that the Return response is the following: Integration Gateway: General Connection Failed (158, 10836).
On seeing some other resolution the following could be the cause of this message.
This error is thrown when there is no valid response.
Possible errors include:

1.      Bad gateway URL.

2.      Sync Service Timeout set and Service actually timed out.

3.      Java exception thrown - Check Application Server for possible Java exception.
Since URL is correct and there is no Java exception, the reason is Sync Service Timeout set and Service actually timed out.

·         In HTTPTargetConnector Properties there is a Header Property called Timeout for which the default value is 50 seconds.

Solution:
Specify the time in milliseconds for the connector to wait for the message to transmit. If the timeout period expires without a successful transmission, the transaction fails.
The default value is 50000 (50 seconds).
Setting the property value to 120000 (120 seconds or 2 minutes), resolved the issue. Make sure that you modify the Node Connector as well as routing connector properties if one is defined.



Navigation: PeopleTools –> Integration Broker –> Integration Setup –> Nodes –> Connectors.
Property ID: HEADER.
Property Name: Timeout.
Value: 120000.
Go to Routings Tab and Select the Outbound Routing and Select Connector Properties. If you have a Property defined for e.g. PRIMARYURL then you will need to add it here as well, otherwise if it is blank then it is not needed to be added here.

Cannot establish HTTP connection (158,2842)

REASON: secureFileKeystorePasswd is blocking the connection.

SOLUTION:

 1. Go to integrationgateway.properties AVAILABLE in webserv directory.

 2. And search for secureFileKeystorePasswd.

 3. Encrypt the password using PSCipher.bat or PSCipher.sh which is under your webserv/PeopleSoft/bin directory.

  Type following command

    Pscipher.bat password

Otherwise

1. Go to People Tools->Integration Broker ->Nodes.

2. Go to connector tab.

3. You can find a Password encryption utility there. Encrypt "password" there copy the encrypted password and paste it in integrationgateway.properties as a value for secureFileKeystorePasswd.