Building Novell Nsure® Identity Manager Drivers
With Composer

Helen Morahan

R&D exteNd™ Composer

hmorahan@novell.com

Novell, Inc.

Kevin Boogert

IDM Engineer

kmboogert@novell.com

Novell, Inc.

Leveraging Identity Manager
with exteNd

What is Identity Manager?

What is exteNd?

Differences

Similarities

Where to use exteNd

Where to use Identity Manager

Where to use Composer

Can we share?

Using exteNd to create IDM2 Drivers

Using Driver shims for legacy integration

What is Identity Manager 2?

A bi-directional data sharing and synchronization service.

Acts as the data “hub” for the enterprise providing a meta directory for access by enterprise applications.

Provides self-service features that enable users to maintain their own passwords and profile information.

Performs policy-based provisioning between disparate applications.

Available IDM2 Drivers

Active Directory

Avaya PBX

Delimited Text

eDirectory™

Exchange 5.5

GroupWise®

JDBC

DB2

Informix

MSSQL

MySQL

Oracle

PostgreSQL

CA Ingres

Sybase

LDAP

Lotus Notes

NIS / NIS+

NT Domains

PeopleSoft –

Release 3.6 for PeopleTools 7.5x

Release 4.0 for PeopleTools 8.1x and 8.4x

RACF

SAP HR

SAP User Management

SIF

Service Drivers

Entitlements

Loopback Driver

Manual Task - Workflow

Sample IDM2 Overview

Sample Driver Shim Representation

Sample policy

What is exteNd 5.2?

Novell exteNd 5.2 is a comprehensive suite for the rapid development and deployment of service-oriented Web applications. With Novell exteNd 5.2 corporate application, developers can powerfully combine identity, integration and portal services to securely deliver relevant business information, at the appropriate time, to the right people.

Extensive Enterprise Connectivity

3270

5250

Microsoft .NET

MS SQL Server

CORBA

Web/HTML

Flat File

SAP R/3

IMS

IDMS

ANSI X.12/EDIFACT

PeopleSoft

XML

Oracle ERP

Data General

CICS

Informix

Java

Email

Siebel

ODBC/JDBC

Oracle

MQ Series

DB2

JMS

Sybase

JD Edwards

TIBCO

HP/3000

Tandem

3270

5250

Telnet

Data

General

HP/

3000

Tandem

HTML

CICS

RPC

SAP

EDI

XML

Java

SDK

JDBC

JMS,

MQ

Series

What is exteNd Composer 5.2?

Software that can single-handedly help you develop and deploy a complete integration solution for your organization. A key component of the Novell exteNd family of solutions, exteNd Composer Enterprise Edition offers:

A richly appointed visual environment for developing and testing Web services

A 100-percent standards-based runtime environment

Sample Action Model

Sample Connector Component

Differences

Identity Manager

Bidirectional data sharing service

Meta Directory

Provides application specific logic controlled by user defined policy

exteNd Composer

Tool for building applications

Produces web services

Exposes target system APIs. Logic and policy implemented in Action Models

Similarities

Connector Model

Wide variety of target systems

Data represented using XML

Communicates with disparate systems

Scripting Language

Hub & Spoke

Where to use Identity manager

Bi-directional synchronization of common data.

Data provisioned via Identity Manager to connected systems specified by policy.

Provide a central Identity Vault where applications, such as those authored in Composer, may access aggregated data and account information.

Enables a white pages application to pull data from one central location.

Role based policies can be used to control access to enterprise systems and resources.

Synchronized data can be evaluated against policies to provide account generation/revocation and access control.

Where to use Novell exteNd Composer

Creating Integrated Solutions

Interface to different systems, perform business functions across applications. Incorporate external web services as part of an integrated solution

Creating Web Services

Writing applications that run on Application Servers using Web Services

Creating Long Running Processes

Using Process Manager to create processes that reflect business functions that may need wait times, and human intervention

What is an Identity Manager Shim?

The shim handles communication between Identity Manager and the target systems.

A driver shim can:

Initialize data to set up connections.

Get Events from the target system.

Execute actions on the target system.

Query the target system

Perform schema discovery

Shut down – Clean up used objects, close connections

How to use exteNd to create IDM2 Drivers

Using the Identity manager Composer driver shim, Composer Action Models can be written to implement application specific logic.

The Composer Action Model can connect to the target systems and perform creates, deletes, modifies and queries as specified by Identity Manager.

A Composer Action Model is built for each type of system, based on the requirements of that system.

Implement policies using Identity Manager 2.0 policy builder. Just like any other IDM driver.

Sample Applications

EPM Driver for Provisioning

Sample Application from NDK

What the IDM Driver for Composer does

Extends the Identity Manager subscriber and publisher channels to Composer.

Receives XML documents from Composer and passes them to the IDM DirXML® Engine. The engine then applies policies as specified by the user.

Receives XML documents from the IDM DirXML Engine and passes them to composer.

Maintains the publisher-side cache for guaranteed delivery.

What the Composer Action Model does

Provides support for all IDM command and event documents as specified in the NDS.dtd.

Provides the association ID for synchronized objects.

Provides status level and status type returns for each command or event received on the subscriber channel.

Responds to the schema discovery command from the IDM driver.

Detects changes on target system and publishes them as XDS documents to the IDM driver.

Responds to shutdown requests from the IDM driver.

Getting Composer Sample Driver to run.

Download and install the Feb-2005 IDM NDK from novell.com.

From the sample/ComposerIntegration context:

Copy the contents of the driver/depends folder to the RemoteLoader/lib or nds/lib folder.

Copy driver/release/ComposerDriverShim.jar to RemoteLoader or nds folder.

Copy actionModel/ComposerSkeletonDriver.jar to Remoteloader or nds folder.

Add the driver to Dirxml driver set and configure it using the ComposerSkeletonDriverConfig.xml file found in the actionModel folder.

IDM 2 NDK

Sample Skeleton Configuration

Using Sample ComposerSkeletonDriver project to begin development

From the sample/ComposerIntegration/actionModel context:

Unzip the ComposerSkeletonDriver.zip file

Open .../ComposerSkeletonDriver project file using Composer.

Implement Execute, GetEvents, GetSchema, Initialize, InitializePublisher, InitializeSubscriber, and Shutdown web services components using action model.

Archive the project.

Copy driver to the nds or remoteloader folder.

Composer Detail

The Future

Action Model as a Policy Builder

Calling Composer Services from Stylesheet Policies

Built in Provisioning in Identity Manager

With GUI Approval Flow Creating

New Drivers to Legacy Systems

User created Composer Drivers for IDM

Drag & Drop functionality in Identity Manager

Visual Representation of Complete Systems

And much more.........

Demo

Q&A

Connectors available in Composer Designer are in yellow circles.

Other systems connected via XML, JMS, JDBC or Java.

Levering Identity Manager with exteNd

2003-12-08T12:43:39