For single-server deployments, these settings configure EAServer to passivate instances when the instance has been idle for the period specified by the Instance Timeout property. EAServer serializes the instance, saves the data in a remote database, and removes the instance from memory. When using this option, you can tune the timeout setting to balance your application’s memory use against the average response time.
The following component properties that must be set in addition to the default EJB stateful session bean component settings:
com.sybase.jaguar.component.timeout – Enter the instance time out period, in seconds.
com.sybase.jaguar.component.ps – Set
to serialize.
com.sybase.jaguar.component.state.gs – Set
to default.
com.sybase.jaguar.component.transient – Set
to false
com.sybase.jaguar.component.storage – Set to:
CtsComponents/JdbcStorage(cache=c_name,table=t_name,transient)
Where c_name is the name of a JDBC connection cache that connects to the target database and t_name is the name of the table used. If you use Adaptive Server Enterprise or Adaptive Server Anywhere, EAServer creates the table if it does not exist. When you are using another data server, you or your database administrator (DBA) must create the table manually. The table must have the schema described in “Table schema for binary storage”.
In EAServer Manager, use the Advanced tab in the Component Properties dialog box to configure these properties. You can also use jagtool or jagant to configure components that use this option, or add an EAServer configuration file to your EJB-JAR file that configures the component properties. See the following references in the EAServer System Administration Guide for more information:
“Using EAServer configuration files in J2EE archives” in Chapter 9, “Importing and Exporting Application Components”
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
