Administration Guide › CA Role & Compliance Manager Integration › How to Configure Integration with CA RCM › How to Configure a Connection in CA Identity Manager › How to Create TEWS Jars

How to Create TEWS Jars

CA RCM uses the Task Execution Web Service (TEWS) to reset the role owners for new provisioning roles that it creates in CA Identity Manager.

The CA RCM Client Tools includes TEWS jars that will work for most deployments. However, if you customized the following Identity Manager tasks, you need to create Java proxy source code (.java files) based on the WSDL for those tasks:

• Reset Provisioning Role Owner
• Create Identity Policy Set
• Modify Identity Policy Set

The following procedure outlines the high-level steps involved in generating the TEWS jars:

1. Prepare the Environment for web services.
2. Build Apache Axis Java proxy classes.
3. Create a Java jar file for the compiled proxy classes.

Prepare an Identity Manager Environment for Web Services

To prepare an Environment for web services

1. In the Management Console, enable web services execution and WSDL generation for the Environment.
2. In the User Console, enable web services for the following tasks:
   • Reset Provisioning Role Owner
   • Create Identity Policy Set
   • Modify Identity Policy Set

Note: For more information about web service configuration and client application development, see the Task Execution Web Service chapter in the Programming Guide for Java.

Build Apache Axis Java Proxy Classes

The Apache Axis framework includes a utility WSDL2JAVA that generates Java proxy source code (.java files) based on WSDL. Once the Java files are generated, they need to be compiled into Java classes.

When invoking WSDL2JAVA, pass the name of the Identity Manager WSDL URL for the Identity Manager Environment. In the following example, MyCorp is the name of the environment.

wsdl2java  --timeout -1  –-output genoutput  http://localhost:8080/idm/TEWS6/MyCorp?wsdl

Once the proxy Java files are generated, compile the .java files into .class files. Be sure to include the complete set of Axis jar files on the compiler class path.

Note: CA Identity Manager includes web service samples for AXIS that contain a sample build script that that you can use as an example of how to generate and compile the Java proxy classes. See samples\WebService\AXIS\build.xml in the Administrative Tools. The Administrative Tools are placed in the following default locations:

• Windows: C:\Program Files\CA\Identity Manager\IAM Suite\Identity Manager\tools
• UNIX: /opt/CA/IdentityManager/IAM_Suite/Identity_Manager/tools

Create a Java Jar File for the Complied Proxy Classes

The CA RCM Connector for CA Identity Manager requires use of the Axis Java Proxy classes when invoking Identity Manager tasks with web services. To provide these proxy classes, compile the classes into a Java jar file and copy that jar to the CA RCM server.

The following example shows a command that you can use to create the Java jar file:

jar –c  RCMTews.jar build

After you create the jar file, copy it to following folder on the system where the CA RCM Client Tools are installed:

RCM_install\Client Tools\Software\Converters\CA\lib

Analyzing CA Identity Manager Data in CA RCM

After you establish a connection between CA Identity Manager and CA RCM, you can import information about provisioning roles into CA RCM. Role engineers can then analyze that data using various tools in CA RCM. Once the role engineers have determined the provisioning role structure, they can apply changes, based on that structure, to CA Identity Manager.

You poll (import) and update (export) endpoints managed by CA Identity Manager by defining connector jobs in the CA RCM Portal. You can then run the job, or define a schedule that automatically runs the job at specified intervals. You can define several jobs based on the connector that apply different options, such as data enrichment or scheduling.