My session in RSA 2008 conference at San Francisco

I co-presented a session with Marc Chanliau on "Java and Web Services Security in Action" under the SOA track in RSA 2008 conference held at Moscone Center in San Francisco. Inspite of the session being at 8am on Wed morning, we got a full room of audience. Thanks to everyone who attended.

The presentation can be downloaded from here.

Replay of Thomas Kurian's keynote at RSA conference 2008 in San Francisco

Thomas Kurian delivered keynote at RSA conference 2008 in San Francisco. He highlighted that customers are looking for holistic approach towards security especially in the 3 areas - Data Protection, Identity and Access Management, and Controls Enforcement. He was later joined by John Stewart, Chief Security Officer, Cisco Systems, who addressed how Cisco is using Oracle solutions to secure major portions of it's business.

See replay of the keynote here.

How To - 10.1.3 OWSM: Configure gateway to talk to failover enabled web services

It's a common use case to provide fail over for your web services. If OWSM Gateway is protecting such webservices then one of the following methods can be used for such configuration.

Method 1: Gateway -> Load Balancer (LBR) -> Web Services
This is the most commonly used approach of using a hardware load balancer between gateway and the web services. When performing service registration in the gateway, enter the load balancer endpoint.

Method 2: Gateway -> Oracle HTTP Server (OHS) -> Oracle Web Services
Here OHS acts as a software load balancer.

Method 3: Gateway -> Web Services
Gateway also has a built in mechanism to perform failover on the webservices by passing in bunch of failover urls. You can configure it at the time of service registration (page 2) or later on by editing service details, and clicking "Modify Protocol Parameters".
There are 3 relevant properties that need to be set.

• FailoverURLs - List of comma separated web service urls. Gateway communicates with the web service endpoint in the order listed.
• Attempts - Number of failed attempts before which Gateway tries to contact next url from the FailoverURLs list. The default value is 5, but you change it to 1 if you want to failover to next web service after first failed attempt.
• RetryInterval - Gateway waits for this interval (ms) before retrying the same url based on the number of attempts set.