BEA White Paper BEA AquaLogic Service Bus behind the Firewall in Service-Oriented Architecture

17

weblogic.xml source code :

<?xml version= 1.0 encoding= UTF-8 ?>

<!DOCTYPE weblogic-web-app PUBLIC -//BEA Systems, Inc.//DTD Web Application 8.1//EN

http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd >

<weblogic-web-app>

<security-role-assignment>

<role-name>Admin

<externally-defined/>

</security-role-assignment>

</weblogic-web-app>

Create a WAR file ExternalServiceClientCert.war using the JAR tool, using the following command:

jar c[v0M]f jarfile [-C dir] inputfiles [-Joption]

For example:

<your directory>jar cvf ExternalServiceClientCert.war *

After starting BEA WebLogic Server, choose the Deployments option from the main menu and deploy the

ExternalServiceClientCert.war.

5.2. Proxy service

Configure the proxy and business services using BEA AquaLogic Service Bus Console. The proxy service defi-

nition relies on configuration of a proxy service provider. You must associate PKI credentials (SSL client key-

pair) with the proxy service provider using the Credentials section of the Security Configuration module.

After you registered a business service definition, which uses the HTTPS transport protocol with client certifi-

cate authentication, configure a proxy service to route a message to the business service.

5.3. Client

For testing this scenario, the Grinder open-source development test framework was used. It is available for

download at the following URL: http://sourceforge.net/projects/grinder/

1. Download the grinder-3.0-beta27.zip or later release.

2. To run the Grinder client you need three files: grinder.properties, https-ClientCert.py, and an input XML file.