Custom Store Availability for JMS Services Default File Store Availability for JTA

8-12 Using Clusters for Oracle WebLogic Server

8.2.1 Custom Store Availability for JMS Services

Migratable JMS-related services cannot use the default persistent store, so you must configure a custom store and target it to the same migratable target as the JMS server or SAF agent. As a best practice, a path service should use its own custom store and migratable target. The custom File store or JDBC store must either be: ■ Accessible from all candidate server members in the migratable target. – If the application uses file-based persistence File store, the stores directory parameter must be configured so that it is accessible from all candidate server members in the migratable target. For highest reliability, use a shared storage solution that is itself highly available—for example, a storage area network SAN or a dual-ported SCSI disk. – If the application uses JDBC-based persistence JDBC store, then the JDBC connection information for that database instance, such as data source and connection pool, has to be available from all candidate servers. ■ Migrated to a backup server target by pre-migrationpost-migration scripts in the MW_HOMEuser_projectsdomainsmydomainbinservice_migration directory, where mydomain is a domain-specific directory, with the same name as the domain. In some cases, scripts may be needed to dismount the disk from the previous server and mount it on the backup server. These scripts are configured on the Node Manager, using the PreScript and PostScript methods in the MigratableTargetMBean in the Oracle WebLogic Server MBean Reference, or using the Administration Console. In other cases, a script may be needed to move not copy a custom file store directory to the backup server. The old configured file store directory should not be left for the next time the migratable target is hosted by the old server; therefore, the WebLogic administrator should delete or move the files to another directory.

8.2.2 Default File Store Availability for JTA

To migrate the JTA Transaction Recovery Service from a failed server in a cluster to another server backup server in the same cluster, the backup server must have access to the transaction log TLOG records from the failed server. Transaction log records are stored in the default persistent store for the server. If you plan to use service migration in the event of a failure, you must configure the default persistent store so that it stores records in a shared storage system that is accessible to any potential machine to which a failed migratable server might be migrated. For highest reliability, use a shared storage solution that is itself highly available—for example, a storage area network SAN or a dual-ported disk. In addition, only JTA and other non-migratable services can share the same default store. Optionally, you may also want to use prepost-migration scripts to perform any unmounting and mounting of shared storage, as needed. Basic directions for creating prepost-migration scripts are provided in a readme.txt file in the MW_ HOMEuser_projectsdomainsmydomainbinservice_migration Note: Basic directions for creating prepost-migration scripts are provided in the readme.txt file in this directory. Service Migration 8-13 directory, where mydomain is a domain-specific directory, with the same name as the domain.

8.2.3 Server State and Manual Service Migration