Sample Scenario

A typical (simple) use case for configuring PasswordSync with a JMS server is to enable users to change their passwords on Windows, have Waveset pick up the new password, and then update the user accounts with the new passwords on an Oracle Directory Server.

The following environment was configured for this scenario:

• Windows Server 2003 Enterprise Edition– Active Directory

• Sun Java System Identity Manager 6.0 2005Q4M3

• MySQL running on SUSE Linux 10.0

• Tomcat 5.0.28 running on SUSE Linux 10.0

• Sun Java System Message Queue 3.6 SP3 2005Q4 running on SUSE Linux 10.0

• Sun Java System Directory Server 5.2 SP4 running on SUSE Linux 10.0

• Java 1.5 (Java 5.0)

The following files were copied to the Tomcat common/lib directory to enable JMS and JNDI:

• jms.jar (from Message Queue)

• fscontext.jar (from Message Queue)

• imq.jar (from Message Queue)

• jndi.jar (from Java JDK)