sharing of Jalosession between web apps

[Former Member]

Hello there, I have two question about JaloSession:

-Is JaloSession can be share between several web apps and requires custom configuration? -Is Cronjob create own session when run or is it use existing JaloSession?

[Former Member · Accepted solution]

Hi ,

Please find the reply over your queries -

Is Cronjob create own session when run or is it use existing JaloSession ?

In Hybris, cron job must run within a certain user context. CronJob type has an attribute named sessionUser that holds a single user. This user is used for the session, in which the cron job is going to run. By default, the user account set for the sessionUser attribute is the one used for the creation of the cron job. That is, if the admin user creates a cron job, it then uses the admin user for the session by default. If a cron job is created using the anonymous account, the sessionUser attribute is set to anonymous. A cron job has the same access rights as the user whose account is used for the session. This is both for security and safety reasons.

Is JaloSession can be share between several web apps and requires custom configuration?

The JaloSession class implements the Serializable interface so that JaloSession objects could be transferred across application server nodes within a SAP Commerce cluster only.

As JaloSessions are bound to the tenant at instantiation, you cannot use one single JaloSession across a multi-tenant system (that is, using one single JaloSession to manage multiple tenants is not possible).

JaloSession is bound to an HttpSession and has the same life time. It means if an http session is closed or expired, the hybris session will also be destroyed.

For more details on this you can refer below link explaining HttpSession failover mechanism -

https://help.sap.com/viewer/d0224eca81e249cb821f2cdf45a82ace/1811/en-US/8c745d01866910149f9cdd3e8303...

[Former Member · Accepted solution]

Thank you so much . It is very good explanation.