6-4 Configuring Server Environments for Oracle WebLogic Server
6.1.5.1 Persistent Store Migration
File-based stores and JDBC-accessible stores can also be migrated as part of a service-level migration for JMS-related services, such as stores, JMS servers, SAF
agents, and the path service, which rely on stores to maintain data. Service-level migration is controlled by a migratable target, which serves as a grouping of
JMS-related services, and which is hosted on only one physical server in a cluster. Such hosted services can be automatically migrated from the current unhealthy hosting
server to a healthy active server with the help of the Health Monitoring subsystem. JMS services hosted by a migratable target can also be manually migrated, either in
response to a server failure or as part of regularly scheduled server maintenance. When the migratable target is migrated, all pinned services hosted by that target are
also migrated. For more information on service-level migration, see Service Migration in Using Clusters for Oracle WebLogic Server.
Migratable JMS-related services cannot use the default file store, so you must configure a custom file store or JDBC store and target it to the same migratable target
as the JMS server, SAF agent, or path service associated with the store.
Migratable file stores must also either be configured on a shared disk that is available to the migratable targets in the cluster or you can use prepost-migration scripts to
migrate a file stores data to a backup server. See Custom Store Availability for JMS Services in Using Clusters for Oracle WebLogic Server.
6.1.5.2 High Availability Storage Solutions
If you have applications that need access to persistent stores that reside on remote machines after the migration of a JMS server or JTA transaction log, then you should
implement one of the following highly-available storage solutions:
■
File-based stores default or custom—Implement a hardware solution, such as a dual-ported SCSI disk or Storage Area Network SAN to make a file store
available from shareable disks or remote machines.
■
JDBC-accessible stores—Configure a JDBC store and use JDBC to access this store, which can be on yet another server. Applications can then take advantage of any
high-availability or failover solutions offered by your database vendor. In addition, JDBC stores support multi data sources, which provide failover between
nodes of a highly available database system, such as redundant databases or Oracle Real Application Clusters Oracle RAC. For more information about using
JDBC multi data sources, see Configuring JDBC Multi Data Sources in Configuring and Managing JDBC for Oracle WebLogic Server.
■
Any persistent store—Use high-availability clustering software such as VERITAS™ Cluster Server, which provides an integrated, out-of-the-box solution
Note: As a best practice, a path service should use its own custom
store and migratable target.
Note: If a file store is disconnected and re-connected again, its host
server instance must be rebooted to successfully continue sendingreceiving persistent JMS messages. For example, if for some
reason the file system containing a file store is unmounted and then remounted, attempts to send persistent JMS messages will generate
JMS exceptions until the host server is rebooted.
Using the WebLogic Persistent Store 6-5
for WebLogic Server-based applications. Another recommended high-availability software solution is IBM HACMP or the equivalent.
6.2 Using the Default Persistent Store
Kategori