Configuring a Default Persistent Store for Transaction Recovery Deploying Applications

5-178 Oracle Fusion Middleware High Availability Guide Managed Server. A simple HTTP monitor that pings the HTTPHTTPS port and expects a pre-determined response in turn should suffice. If only a specific SOA component is being used such as B2B, then a monitor that does a deeper level check all the way to the managed server can be considered to validate the health of the component in use. Please check with your load balancer vendor on setting up the HTTP monitors with your load balancer. If you do not set the front end HTTP host and port, you get the following message when trying to retrieve a document definition XSD from Oracle B2B: An error occured while loading the document definitions. java.lang.IllegalArgumentException: Cluster address must be set when clustering is enabled.

5.14.18 Configuring a Default Persistent Store for Transaction Recovery

Each server has a transaction log, which stores information about committed transactions coordinated by the server that may not have been completed. WebLogic Server uses the transaction log when recovering from system crashes or network failures. To take advantage of the migration capability of the Transaction Recovery Service for servers in a cluster, you must store the transaction log in a location that is available to a server and its backup servers the nodes the WebLogic Server can failover to, preferably on a dual-ported SCSI disk, or a Storage Area Network SAN. To configure the default persistent store:

1. In the Domain Structure tree, expand Environment and select Servers.

2. Select the server you want to modify.

3. Select the Configuration, Services tab.

4. Under Default Store, in the Directory field, enter the path to the folder where you

want the default persistent store to store its data files. To enable migration of the Transaction Recovery Service, you must specify a location on a persistent storage solution that is available to other servers in the cluster. Therefore, the directory that you enter must be accessible by both WLS_ SOA1 and WLS_SOA2 for the SOA_Cluster and WLS_OSB1 and WLS_OSB2 for the OSB_Cluster. This directory must exist before the server is restarted.

5.14.19 Deploying Applications

You can deploy SOA composite applications from Oracle Enterprise Manager Fusion Middleware Control Console with the Deploy SOA Composite wizard. Use the Deploy SOA Composite wizard to deploy any of the following: ■ A new SOA composite application for the first time ■ A new revision for example, 2.0 alongside an older revision for example, 1.0 without impacting the latter. The revision deployed last becomes the new default revision of that composite unless you specify otherwise at a later step during deployment. ■ A bundle ZIP file containing multiple SOA composite application revisions for example, revisions 2.0, 3.0, and 4.0 of a SOA composite application that already has a different revision that is currently deployed for example, 1.0. This option enables you to deploy revisions 1.0, 2.0, 3.0, and 4.0 at the same time. The bundle can also contain revisions of different composites. There is no restriction that all revisions must be of the same composite application. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-179 Deployment extracts and activates the composite application in SOA Service Infrastructure. Once an application is deployed, you can perform administration tasks, such as creating instances, configuring properties, monitoring performance, managing instance life cycles, and managing policies and faults. To deploy applications: 1. Access the Deploy SOA Composite wizard through one of the following options: The Select Archive page appears.

2. In the Archive or Exploded Directory section, specify the archive of the SOA

composite application to deploy. The archive contains the project files of the composite to be deployed for example, HelloWorld_rev1.0.jar for a single archive or OrderBooking_rev1.0.zip for multiple archives.

3. In the Configuration Plan section, optionally specify the configuration plan to

include with the archive. The configuration plan enables you to define the URL and property values to use in different environments. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment.

4. Click Next.

The Select Target page appears. Note: If you want to redeploy an existing revision of an application, do not use this wizard. Instead, use the Redeploy SOA Composite wizard. From SOA Infrastructure Menu... From the SOA Folder in the Navigator... From the SOA Infrastructure Home Page... From the SOA Composite Menu... 1. Select SOA Deployment Deploy . 1. Right-click soa-infra. 2. Select SOA Deployment Deploy . 1. Click the Deployed Composites tab. 2. Above the Composite table, click Deploy. 1. Select SOA Deployment Deploy Another Composite. 5-180 Oracle Fusion Middleware High Availability Guide 5. Select the WebLogic Server or cluster to which to deploy the SOA composite application archive. You can deploy to multiple servers and clusters.

6. Click Next.

The Confirmation page appears. 7. Review your selections. 8. Select whether or not to deploy the SOA composite application as the default revision. The default revision is instantiated when a new request comes in.

9. Click Deploy.

Processing messages are displayed.

10. When deployment has completed, click Close.

5.14.20 Configuring Server Migration for the WLS_SOA Servers