These settings configure EAServer to save in a remote database a copy of the the session bean’s serialized data after every method invocation. When running in a cluster, the instance data can be restored on any server in which the component is installed, permitting load balancing and failover of the component. Configure the settings in Table 28-2, using the Persistence Tab in the Component Properties dialog box:
Field |
Value |
|---|---|
Persistence |
Automatic Persistent State. |
State |
The name of the component’s Java class. |
Primary Key |
None (leave blank). |
State Methods |
Enter |
Storage components |
The name of the storage component. See “Storage components” for more information. |
Connection cache |
If you are using database storage, enter the name of a JDBC connection cache that connects to the database. The cache must have by-name access enabled. |
Table |
If you are using database storage, enter the name of a database table where the serialized data is to be stored. 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”. |
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
