Configuring Oracle Web Services Manager for High Availability (HA)

Purpose

This OBE tutorial describes and shows how to implement a high availability solution for Oracle Web Services Manager (Oracle WSM) gateway, policy manager, and control components. The gateway, policy manager, and control components are configured for Active-Active configuration. The monitor can be configured for only Active-Passive configuration because of the nature of metrics aggregation it performs.

Note: In this tutorial, the gateway is running on the same application server instance as the policy manager, control, and monitor components. In real world scenario, gateway is installed on a different application server instance.

Time to Complete

Approximately 1 hour

Topics

This OBE tutorial covers the following topics:

 Prerequisites
 Verifying Oracle WSM Components
 Creating and Registering an Oracle WSM Gateway
 Registering the TimeService Web Service to the Gateway
 Testing the TimeService Web Service
 Verifying the Status of the Gateway and Monitor
 Testing Oracle WSM High Availability with Gateway
 Testing Oracle WSM High Availability with Policy Manager
 Summary
 Related Information

Viewing Screenshots

 Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: Because this action loads all screenshots simultaneously, response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.

 

Prerequisites

Before starting this tutorial, you must complete the Setting up the Oracle Web Services Manager High-Availability (HA) Topology tutorial. The current tutorial is based on the setup environment you created in Setting up the Oracle Web Services Manager High-Availability (HA) Topology tutorial.

Back to Topic List

 

Verifying Oracle WSM Components

Verify that Oracle WSM components—gateway, control, monitor, and policy manager—are working fine in both the application server environments.

1.

Open any Internet browser and log in to the Oracle Application Server Control by entering the following URL in the address bar:

http://<hostname>.<domain>:80/em

Note: In this tutorial, the <hostname>.<domain> is edixr4p1.us.oracle.com .

 

2.

Log in with the user ID oc4jadmin and password welcome1 .

 

3.

Before verifying the execution of Oracle WSM components, make sure that the status of the following Oracle WSM components is up in the first application server instance. On the Cluster Topology page, expand the home node of the first application server instance ( soa1 ) to view the status of the components.

ccore

policymanager

coreman

gateway

 

4.

Expand the home node of the second application server instance ( soa2). Select the check box associated with Coreman and click the Stop button. Click the Yes button on the Confirmation page.

You may come across an error that the topology members could not be stopped. Ignore it and just refresh the Cluster Topology page. Expand the home node of the second application server instance ( soa2 ). You should find that the status of the Coreman application is down.

Note : Coreman is stopped on the second application server instance because Oracle WSM Monitor can run only as a single process in a clustered environment. You cannot have multiple instances of Coreman running in a cluster.

 

5.

Verify the status of the following Oracle WSM components. Make sure that the status is up in the second application server instance.

ccore

policymanager

gateway

 

Back to Topic List

 

Creating and Registering an Oracle WSM Gateway

Create and register an Oracle WSM gateway by using the Web Services Manager Control. To perform this task, execute the following steps:

1.

Open any Internet browser and log in to the Web Services Manager Control by entering the following URL in the address bar:

http://edixr4p1.us.oracle.com/ccore

 

2.

Enter admin in the User Name field and oracle in the Password field. Click Login.

 

3.

On the Web Services Manager Control: Enforcement Points page, click the Add New Component button.

 

4.

On the Add New Component page, enter the following details and click the Register button:

Basic Parameters

Value

Component Name

MyGateway

Component Type

Gateway

Container Type Oracle Web Services Manager
Component URL http://edixr4p1.us.oracle.com/gateway

 

5.

Verify that the component has been successfully added. Click OK.

Not e: You need to create the gateway as the first component, because by default the gateway.component.id property in the gateway-config-installer.properties file is set to C0003001. If the component ID is different, you need to edit the gateway-config-installer.properties file, located in the ORACLE_HOME\j2ee\home\applications\gateway\gateway\WEB-INF directory, and replace the value of the gateway.component.id field with the component ID of the gateway you want to install (for example, gateway.component.id=C0003006). Save the configuration file and restart the application server to start the gateway.

You can also deploy the gateway to a different application server by using the wsmadmin tool. Refer to Oracle Web Services Manager Deployment Guide 10g (10.1.3.1.0) for more details.

 

Back to Topic List

 

Registering the TimeService Web service to the Gateway

In this section, you register the TimeService Web service to the gateway that you have just created. The TimeService is a test service, which is used to verify if the high availibility of the Oracle WSM components are working correctly. To perform this task, execute the following steps:

1.

Log in to the Web Services Manager Control. Expand Policy Management in the navigation menu and click the Register Services option.

 

2.

Click the Services link of MyGateway gateway.

 

3.

On the Gateways/List of Services page, click the Add New Service button.

 

4.

On the Add New Service page, enter the following service details and click the Next button.

Property Name

Value

Service Name

TimeService

Service Version

1.0

Service Description Display the time
WSDL URL http://edixr4p1.us.oracle.com/ccore/TimeService.wsdl
Service Protocol Accept the default, HTTP(S).
Service Groups Accept the defaults

 

5.

On the Configure Messenger Step for New Service page, verify that the URL matches the URL you provided on the previous page. Accept the default values for the remaining fields, and click Finish.

 

6.

On the Services page, click the OK button.

 

7.

On the Gateways/List of Services page, click the commit link.

 

8.

On the Gateways page, click the OK button.

 

Back to Topic List

 

Testing the TimeService Web Service

Test the TimeService Web service that is registered with the gateway. To perform this task, execute the following steps:

1.

Expand Policy Management in the navigation menu and click the Register Services option.

 

2.

Click the Services link of the MyGateway gateway.

 

3.

On the Gateways/List of Services page, click the View Details icon of the TimeService service.

 

4.

On the Gateways/View Details page, copy the URL in the Service WSDL URL field. Click OK.

 

5.

Expand Tools in the navigation menu and click the Test Page option.

 

6.

On the Test Web Service page, paste the URL you copied into the Enter wsdl url text box and click the Submit Query button.

 

7.

On the Test Page/Test Web Service page, click the Invoke button.

 

8.

On the Test Result page, click the Formatted XML link to view the result.

 

Back to Topic List

 

Verifying the Status of the Gateway and Monitor

Verify that the gateway and the monitor are executing without any problem. To perform this task, execute the following steps:

1.

To verify the status of the gateway, click and expand the Overall Statistics menu located under the Operational Management menu. Click the Message Logs option under the Overall Statistics menu. You should see a request and a response message listed in the table for the gateway component just added.

 

2.

To verify the status of the monitor, click and expand the Overall Statistics menu located under the Operational Management menu. Click the Execution Details option under the Overall Statistics menu. Hover the cursor over the green dot. If you see an execution statistic balloon, then monitoring is working successfully.

Note: If you cannot view the execution details, restart soa1 and soa2 by using the opmnctl command. Run the test again for the registered TimeService Web service and execute the above step to view the details.

Back to Topic List

 

Testing Oracle WSM High Availability with Gateway

To test the high availability of the gateway component in Oracle WSM, stop the gateway on the first application server instance. Execute the steps to test the Web service. If the test is successful, then the high availability for the gateway is working.

1.

Log in to the Oracle Application Server Control of the first application server instance.

 

2.

Expand the home node of the second application server instance ( soa2). Select the check box associated with gateway and click the Stop button. Click the Yes button on the Confirmation page.

You may come across an error that the topology members could not be stopped. Ignore it and just refresh the Cluster Topology page. Expand the home node of the second application server instance ( soa2 ). You should find that the status of the gateway application is down.

 

3.

Execute the steps specified in the Testing the TimeService Web Service and Verifying the Status of the Gateway and Monitor sections of the tutorial. If the test is successful, then the gateway failover is working.

 

Back to Topic List

 

Testing Oracle WSM High Availability with Policy Manager

Test Oracle WSM high availability with modifying the policy of the registered TimeService Web service in the first application server instance. Then, stop the policy manager component in the first application server instance and execute the following steps to test the Web service. The message logs should reflect the modified policy. Therefore, you must perform the following task to test Oracle WSM high availability for the policy manager component.

  1. Modify the request pipeline of the policy associated with the TimeService Web service registered earlier such that you now have two log steps in the request pipeline. The new policy will be picked up by the gateway within ten seconds, which is the default policy-polling interval.
  2. Stop the policy manager on the first application server instance.
  3. Run the test again for the TimeService Web service. Look for the message logs in the Web Services Manager Control. If you see two request messages logged instead of one, then the high availability for the policy manager is working.

1.

Log in to the Web Services Manager Control. Expand Policy Management in the navigation menu and click the Manage Policies option.

 

2.

Click the Policies link of the MyGateway component.

 

3.

Click the Edit icon of the TimeService(1.0) policy.

 

4.

In the Pipeline: Request section, click the Add Step Below link in the Log policy step.

 

5.

In the New Step dialog box, select Log from the Select Step Template drop-down list. Click OK.

 

6.

Scroll down and click the Next button.

 

7.

Accept the default policy name and click the Save button.

 

8.

Click the Commit link to commit the changes to the policy.

 

9.

Log in to the Oracle Application Server Control of the first application server instance.

 

10.

Expand the home node of the second application server instance ( soa2). Select the check box associated with policymanager and click the Stop button. Click the Yes button on the Confirmation page.

You may come across an error that the topology members could not be stopped. Ignore it and just refresh the Cluster Topology page. Expand the home node of the second application server instance ( soa2 ). You should find that the status of the gateway application is down.

 

11.

Execute the steps specified in the Testing the TimeService Web Service and Verifying the Status of the Gateway and Monitor sections of the tutorial. If you see two request messages logged instead of one, then the high availability for the policy manager is working.

 

Back to Topic List

 

Summary

In this lesson, you learned how to:

 Verifying Oracle WSM Components
 Creating and Registering an Oracle WSM Gateway
 Registering the TimeService Web Service to the Gateway
 Testing the TimeService Web Service
 Verifying the Status of the Gateway and Monitor
 Testing Oracle WSM High Availability with Gateway
 Testing Oracle WSM High Availability with Policy Manager

 

Related Information

 To ask a question about this OBE tutorial, post a query on the OBE Discussion Forum.

Back to Topic List

 Place the cursor over this icon to hide all screenshots.

 

 

 

Left Curve
Popular Downloads
Right Curve
Untitled Document