Using the Delegate Features

Learn how to use an Apache Axis client solution to provide message formatting and transportation of a web service description stored in Policy Manager.

Using Admin Console Managing Containers

Policy Manager 7.x Delegate for Apache Axis

Supported Platforms: 7.x, 8.0

Table of Contents

  1. Introduction
  2. Prerequisites
  3. Configure Collocated Option
  4. Configure Remote Options

Introduction

The Axis Delegate and Apache Axis client solution provides message formatting and transportation based on a web service description stored in the Policy Manager product. The solution is implemented by a set of Axis message handlers that work in conjunction with an OSGi container. This container typecan support multiple features. When used as part of the Delegate solution, the Delegate feature must be installed. Remote delegates are also supported.

Delegate Features

The solution uses the following Platform features:

  • Delegate - Includes the policy implementation point for third-party web service frameworks, and provides support for WS-Policy and dynamic endpoint resolution. It can only be deployed with a web service framework like Apache Axis. For remote delegates, this feature can be used if the OSGi container is a J2EE container. For containers that do not have native delegate support, use the Delegate Access Point feature.
  • Access Point - Provides a remote interface to delegates for policy implementation and message delivery. Any delegate that does not provide its own policy implementation and message delivery mechanism can route messages through the Access Point. This feature is installed on a container that does not have native delegate support.

Back to top

Deployment Options

The architecture of the Delegate supports two different deployment options:

  • Collocated Option - Using this option, the OSGi container is deployed in the same Java Runtime Engine (JRE) as the Axis engine.
  • Remote Option - Using this option the OSGi container is deployed in a separate JRE from the Axis Engine.

Back to top

Prerequisites

  • Apache Axis - You must be experienced Apache Axis user. The delegate configuration process requires that you install Apache Axis, the Axis SOAP Client, and install and deploy a web service.
  • Documentation - Before configuring a delegate, review the Policy Manager Delegate for Apache Axis Technical Note to become familiar with the delegate architecture, delegate handler, configuration handler parameters, and delegate identity credentials.

Back to top

Configure Collocated Option

Step 1: Install and Configure Tomcat Container and Features

  1. Configure Tomcat Container (GUI / Silent). See Step 2 of Using Tomcat Agent Feature topic.
  2. Install Tomcat Agent Feature. See Step 3 of Using Tomcat Agent Feature topic.
  3. Configure Tomcat Agent Feature. See Step 4 of Using Tomcat Agent Feature topic.

Step 2: Install Delegate Feature

  1. Launch the Administration Console (http://<hostname:<port>/admin/).
  2. On the Installed Features screen, select Feature from the Filter menu.
  3. Select the Delegate feature and click Install Feature.
  4. After the installation is complete, click Configure. On the WS-MetaDataExchange Options screen specify the URL of the Policy Manager Metadata Exchange Service.
  5. Restart the container.

Step 3: Install Axis Service & Client

  1. Install Axis service and Axis client in Tomcat (i.e., copy to /webapps).
  2. Restart Tomcat.

Step 4: Register Tomcat Container

  1. Register Tomcat container in the Policy Manager Management Console. See Step 5 of Using Tomcat Agent Feature topic.

Step 5: Create and Manage Physical Service Policy Manager

  1. Launch the Policy Manager Management Console.
  2. Using Create Physical Service, register the physical service (e.g., http://<hostname>:8080/axis/services/echo?wsdl).
  3. On the Select Service Management Option screen, select a service management option (i.e., Manage within Container, or Manage through a Virtual Service).
  4. On the Select Container screen, select the Tomcat container you registered in Step 4.
  5. Complete configuration.

Step 6: Test

  1. Create SOAP UI project with physical service URL.
  2. Bring up the client page at http://<hostname>:8080/example-axis-client/echo.jsp
  3. Enter any value and submit.

Back to top

Configure Remote Options

Prerequisites

Before configuring the remote options, the following must be installed and configured.

  • A Policy Manager container instance with Policy Manager features installed (i.e., Policy Manager Console and Policy Manager Services.

Configure Remote Delegate Option for Standalone Container (ND)

With this option the Delegate Access Point feature is required to perform the message processing.

  1. Create Standalone Container.
  2. Install Delegate Access Point feature.
  3. Install Network Director feature.
  4. Install Axis service and Axis client in Tomcat or any . i.e., copy to <TOMCAT HOME>/webapps. Restart TOMCAT.
  5. Edit client-config.wsdd file in <TOMCAT_HOME>/webapps/example-axis-client/WEB-INF/classes
  6. Change “type” attribute of the “handler” entry to “java:com.soa.delegate.axis.RemoteAxisPivotHandler”.
  7. Add parameter element for the proxy.address with address of container installed with Delegate Access Point feature as follows: <parameter name="proxy.address" value="http://<host>:<port>/soapdelegate"/>
  8. Restart Tomcat.
  9. Deploy Delegate handlers as illustrated in the Policy Manager 7.x Delegate for Apache Axis Technical Note

Back to top

Configure Remote Delegate Option for J2EE Container

With this option you can install the Delegate feature and it can act as an access point and collocated delegate.

  1. Create Standalone Container.
  2. Install Delegate feature in J2EE container
  3. Install Axis service and Axis client in Tomcat or any . i.e., copy to <TOMCAT HOME>/webapps.  Restart TOMCAT.
  4. Edit client-config.wsdd file in <TOMCAT_HOME>/webapps/example-axis-client/WEB-INF/classes.
  5. Change “type” attribute of the “handler” entry to “java:com.soa.delegate.axis.RemoteAxisPivotHandler”.
  6. Add parameter element for the proxy.address with address of container installed with Delegate Access Point feature as follows: <parameter name="proxy.address" value="http://<host>:<port>/soapdelegate"/>
  7.  Restart Tomcat.
  8. Deploy Delegate handlers as illustrated in the Policy Manager 7.x Delegate for Apache Axis Technical Note

Back to top

Agent Container

Delegate support is provided for a variety of different agents (i.e., tc Server, WebSphere, JBoss, etc.). Contact Customer Support for more information.

Back to top