web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Java Session Service (JSS) Properties For more information about the configuration.xml, go to the Deployment Op-Center (BDOC) Developer's Guide. The JSS supports two kinds of backend storage: JDataStore or a JDBC datasource. For more information, go to Chapter 6, “Java Session Service (JSS) configuration.” Table 31.4 Property JSS properties Console Property Name Description Default jss.workingDir= Working directory The directory where the backend database (JDataStore) file is located. Note: This property is applicable only if the jss.pstore property is configured to use a JDataStore file as backend storage. jss.factoryName= Factory name Name given to the JSS factory created by this service. The service gets registered with this name in the Smart Agent (osagent). If not specified and the JSS runs in the Partition, then the Partition's working directory /var/ domains/ / configurations/ /mos/ is used. If not specified and the JSS runs as part of a standalone EJB container, then the current directory where the container started is used. If not specified and the JSS runs in the Partition, the default value is: :file: / var/ domains/ / configurations/ / mos/ / . If not specified and the JSS runs in a standalone EJB container, the default value is EJB/ JSS[]. Chapter 31: EJB, JSS, and JTS Properties 347
Java Session Service (JSS) Properties Table 31.4 Property jss.softCommit=true| false jss.maxIdle= jss.debug=true|false jss.pstore= JSS properties (continued) Console Property Name Description Default Soft commit Max idle Persistent store If true, the JSS uses the JDataStore backend database with the Soft Commit mode enabled. Setting this property improves the performance of the Session Service, but can cause recently committed transactions to be rolled back after a system crash. Note: This property is applicable only if the jss.pstore property is configured to use a JDataStore file as backend storage. For more details, see the JDataStore documentation at:http:// info.borland.com/ techpubs/jdatastore. The time interval in seconds between runs of JSS garbage collection job. The JSS garbage collection job is responsible for removing the state of expired sessions from the backend database. If set to 0, the garbage collection job never starts. Print debug information. If set to true, the JSS prints out debug traces. Specifies the JDatastore file to use for backend storage. If the file does not exist, JSS creates the file with the .jds extension, for example jss_factory.jds. For any compatible database supporting JDBC, specifies the JNDI name with the serial: prefix, for example serial://datasources/ OracleDB to use for backend storage. In this case, JSS uses a datasource that is deployed in the Naming Service under the JNDI name specified. true 1800 (=30min) false If the JSS runs in the Partition, the JDataStore file named is used, such as jss_factory.jds. If the JSS runs in a standalone ejb container, the _js s.jds is used. 348 BES Developer’s Guide
- Page 309 and 310: Using the iastool command-line tool
- Page 311 and 312: Using the iastool command-line tool
- Page 313 and 314: Using the iastool command-line tool
- Page 315 and 316: Using the iastool command-line tool
- Page 317 and 318: Using the iastool command-line tool
- Page 319 and 320: Using the iastool command-line tool
- Page 321 and 322: Using the iastool command-line tool
- Page 323 and 324: Using the iastool command-line tool
- Page 325 and 326: Using the iastool command-line tool
- Page 327 and 328: Using the iastool command-line tool
- Page 329 and 330: Using the iastool command-line tool
- Page 331 and 332: Using the iastool command-line tool
- Page 333 and 334: Executing iastool command-line tool
- Page 335 and 336: 324 BES Developer’s Guide
- Page 337 and 338: element ■ ■ ■ element The
- Page 339 and 340: element The Partition statistics ag
- Page 341 and 342: element element The services eleme
- Page 343 and 344: element element The archive elemen
- Page 345 and 346: EJB Container-level Properties Tabl
- Page 347 and 348: EJB Container-level Properties Tabl
- Page 349 and 350: EJB Customization Properties: Deplo
- Page 351 and 352: Complete Index of EJB Properties Co
- Page 353 and 354: Complete Index of EJB Properties Ta
- Page 355 and 356: Complete Index of EJB Properties Ta
- Page 357 and 358: Complete Index of EJB Properties Ta
- Page 359: Java Session Service (JSS) Properti
- Page 363 and 364: Partition Transaction Service (Tran
- Page 365 and 366: Borland-specific web DTD 33, 36 bra
- Page 367 and 368: ejb.mdb.maxMessagesPerServerSession
- Page 369 and 370: J J2EE VisiClient 97 VisiClient env
- Page 371 and 372: optimistic concurrency 130 SelectFo
- Page 373 and 374: Sonic clustered service 228 SonicMQ
- Page 375: X XML DTD 99 VisiClient 98 grammar
Java Session Service (JSS) Properties<br />
Table 31.4<br />
Property<br />
jss.softCommit=true|<br />
false<br />
jss.maxIdle=<br />
jss.debug=true|false<br />
jss.pstore=<br />
JSS properties (continued)<br />
Console Property<br />
Name Description Default<br />
Soft commit<br />
Max idle<br />
Persistent store<br />
If true, the JSS uses the<br />
JDataStore backend<br />
database with the Soft<br />
Commit mode enabled.<br />
Setting this property<br />
improves the performance<br />
of the Session Service,<br />
but can cause recently<br />
committed transactions to<br />
be rolled back after a<br />
system crash.<br />
Note:<br />
This property is applicable<br />
only if the jss.pstore<br />
property is configured to<br />
use a JDataStore file as<br />
backend storage. For<br />
more details, see the<br />
JDataStore<br />
documentation at:http://<br />
info.borland.com/<br />
techpubs/jdatastore.<br />
The time interval in<br />
seconds between runs of<br />
JSS garbage collection<br />
job. The JSS garbage<br />
collection job is<br />
responsible for removing<br />
the state of expired<br />
sessions from the<br />
backend database. If set<br />
to 0, the garbage<br />
collection job never starts.<br />
Print debug information. If<br />
set to true, the JSS prints<br />
out debug traces.<br />
Specifies the JDatastore<br />
file to use for backend<br />
storage. If the file does not<br />
exist, JSS creates the file<br />
with the .jds extension,<br />
for example<br />
jss_factory.jds.<br />
For any compatible<br />
database supporting<br />
JDBC, specifies the JNDI<br />
name with the serial:<br />
prefix, for example<br />
serial://datasources/<br />
OracleDB to use for<br />
backend storage. In this<br />
case, JSS uses a<br />
datasource that is<br />
deployed in the Naming<br />
Service under the JNDI<br />
name specified.<br />
true<br />
1800 (=30min)<br />
false<br />
If the JSS runs in<br />
the Partition, the<br />
JDataStore file<br />
named is used,<br />
such as<br />
jss_factory.jds.<br />
If the JSS runs in a<br />
standalone ejb<br />
container, the<br />
_js<br />
s.jds is used.<br />
348 BES Developer’s Guide