Oracle Waveset 8.1.1 Deployment Guide

Migrating from Access Enforcer Version 5.1 or 5.2

Upgrading from an SAP Access Enforcer resource to an external resource that connects to SAP Access Control 5.3 requires multiple tasks. Read the following procedure carefully.

Waveset provides a sample workflow, InstallDir/sample/wfexternalmigration.xml, for the purpose of migrating users from SAP Access Enforcer to SAP Access Control 5.3. It must be customized according to your environment and configuration.

The workflow requires the following account attributes:

You may add attributes as needed.

This workflow currently displays the result of each user update. The current way around this is to modify the taskLaunch.jsp so that instead of displaying the results, the page is redirected back to the taskList.jsp page.

  1. Determine the attributes that need to be migrated and update the workflow defined in the InstallDir/sample/wfexternalmigration.xml file.

  2. Import the updated workflow.

  3. Create an external resource for the SAP Access Control 5.3 integration. Ensure that the External Resource user store is configured properly. Refer to Understanding and Managing External Resources in Oracle Waveset 8.1.1 Business Administrator’s Guide for more information.


    Note –

    The SAP Access Control adapter, which uses Metro for Web Service communication, can not be instantiated in some application servers together with the Access Enforcer resource adapter, which uses Apache Axis for Web Service Communication.


  4. Run the Sample SAP Access Enforcer To Access Control Migration server task. The system should not be in use by anyone else during this process..

  5. Remove Apache Axis from application server.

  6. Download and install Glassfish Metro 1.5 from the following location: https://metro.dev.java.net/1.5/

  7. Remove the Access Enforcer resource from Waveset.

  8. Create the SAP Access Control resource.

  9. Modify the external resource to use SAP Access Control web services.