Virtual member manager provides limited transaction support when called by the WebSphere security or by an application.
If virtual member manager is called by WebSphere security , virtual member manager always uses a local transaction for its operations with an underlying repository.
If virtual member manager is called by an application through its Java SDO-based API or through its stateless session EJB after the caller global transaction has started, virtual member manager participates in the caller global transaction. Virtual member manager does not provide a method to prevent its participation caller global transaction in this situation. If the caller has not started a global transaction, virtual member manager starts its own global transaction.
This behavior is enabled because the transaction attribute is set to TX-Supports in the virtual member manager stateless session EJB. When the virtual member manager stateless session EJB is not used, virtual member manager uses the WebSphere Application Server transaction manager.
If virtual member manager is configured with a mixture of transactional and non-transactional repositories and if a transaction needs to be rolled back, only the transactional repositories are rolled back. Error messages are logged and administrator might need to manually clean up the non-transactional repositories. For example, virtual member manager is configured with an LDAP server and the property-extension repository (which is a database), and you are creating a person entry on the LDAP repository with some additional properties in the extension database. If the person entry is created successfully on the LDAP repository, but the creation of the additional properties in the database failed, the extension database is rolled back, but the person entry created on LDAP is not removed automatically. An error message is logged. The administrator must examine the log and remove the person entry from the LDAP repository.