The /atg/userprofiling/ProfileServices component (class atg.userprofiling.ProfileServices) manages many of the Web service functions related to user profiling. Note that some of these functions mimic the behavior of standard Oracle Commerce Platform profile form handlers; this behavior is designed to help you reproduce any profile form handler custom code as extensions of out-of-the-box Web services.
The following list shows the properties of the ProfileServices component.
transactionManagerType:
javax.transaction.TransactionManagerThe service that manages any transactions used to execute repository methods on this instance.
Default:
/atg/dynamo/transaction/TransactionManager(set in DPS module)mappingManagerType:
atg.repository.xml.ItemDescriptorMappingManagerThe component that manages mapping files based on repository item descriptor name combinations. Any methods that return repository items consult this service to retrieve the mapping files to use when transforming these items into XML. Note that this behavior assumes the
useDefaultMappingFilesproperty is set to true.Default:
/atg/repository/xml/ItemDescriptorMappingManager(set in DPS module)xmlGetServiceType:
atg.repository.xml.GetServiceThe service that turns repository items into XML.
Default:
/atg/repository/xml/GetService(set in DPS module)xmlAddServiceType:
atg.repository.xml.AddServiceThe service that adds repository items in XML format to a repository.
Default:
/atg/repository/xml/AddService(set in DPS module)xmlUpdateServiceType:
atg.repository.xml.UpdateServiceThe service that takes repository items in XML format and updates them in their corresponding repositories.
Default:
/atg/repository/xml/UpdateService(set in DPS module)profileToolsType:
atg.userprofiling.ProfileToolsThe profile tools service that provides access to common profiling functions, as well as access to other profile components such as the
PropertyManagerandProfileRepository.Default:
/atg/userprofiling/ProfileTools(set in DPS module)updateEventListenersType:
atg.userprofiling.ProfileUpdateListener[]An array of
ProfileUpdateListenersthat are notified when a profile is updated. Note that thegenerateUpdateEventsproperty must be set to true for this behavior to occur.Default:
/atg/userprofiling/ProfileUpdateTrigger(set in DPS module)generateLoginEventsType: boolean
If true, the
LoginUserWeb service fires login events after a user has been successfully logged in.Default: true (set in DPS module)
generateUpdateEventsType: boolean
If true, the
UpdateUserWeb service fires update events after a user profile has been successfully updated.Default: true (set in DPS module)
generateRegisterEventsType: boolean
If true, the
CreateUserWeb service fires register events after a user profile has been successfully created.Default: true (set in DPS module)
generateLogoutEventsType: boolean
If true, the
logoutUserservice fires logout events after a user has been successfully logged out.Default: true (set in DPS module)
expireSessionOnLogoutType: boolean
Behaves the same way as the
expiresSessionOnLogoutproperty in theProfileFormHandlerclass. See the description of thehandleLogoutmethod in Profile Form Handlers.Default: true (set in DPS module)
usingLDAPProfileType: boolean
Behaves the same way as the
usingLDAPProfileproperty in theProfileFormHandlerclass. It indicates whether the profile in use is stored in an LDAP directory.Default: false (set in DPS module)
useDefaultMappingsType: boolean
If true, methods that return
Repo2Xmlitems map properties according to the default mappings configured in theItemDescriptorMappingManager(unless the Web service calls a variation of a method that takes a mapping file location as an argument).Default: true (set in DPS module)
logoutProfileTypeType: String
Behaves the same way as the
logoutProfileTypeproperty in theProfileFormHandlerclass. It specifies the item descriptor type of the profile defaulted to when the current user logs out.Default:
user(set in DPS module)createProfileTypeType: String
Behaves the same way as the
createProfileTypeproperty in theProfileFormHandlerclass. It specifies the item descriptor type of the profile created when a new profile is added to the repository.Default:
user(set in DPS module)loginProfileTypeType: String
Behaves the same way as the
loginProfileTypeproperty in theProfileFormHandlerclass. It specifies the item descriptor type of the profile accessed when a user logs in.Default:
user(set in DPS module)propertiesToCopyOnLoginType: String[]
Behaves the same way as the
propertiesToCopyOnLoginproperty in theProfileFormHandlerclass. It specifies the property values to copy from the anonymous profile to the persistent profile when a user logs in.Default: null (set in DPS module)
propertiesToAddOnLoginType: String[]
Behaves the same way as the
propertiesToAddOnLoginproperty in theProfileFormHandlerclass. It specifies the properties to add from the anonymous profile to the persistent profile when a user logs in.Default:
scenarioInstances,slotInstances(set in DSS module)maxAuthenticationWaitType: long
Indicates how long a password encryption conversation is allowed to last, which is the length of time between calls to
getPasswordHashKeyandloginUser. If the length of time between these two calls exceeds themaxAuthenticationWaitproperty value, the login is invalid. Note that this behavior assumes the login attempt is encrypted (in other words, thatpIsPasswordEncryptedis true for theloginUsercall).Default: 30000 (30 seconds) (set in DPS module)
badPasswordDelayType: long
Behaves the same way as the
badPasswordDelayproperty in theProfileFormHandlerclass. It specifies the number of milliseconds to wait before proceeding after a user submits a password that fails authentication.Default: 1000 (1 second) (set in DPS module)
profilePathType: String
The component path of the
Profilecomponent.Default:
/atg/userprofiling/Profile(set in DPS module)requestLocalePathType: String
The component path of the
RequestLocalecomponent.Default:
/atg/dynamo/servlet/RequestLocale(set in DPS module)allowEncryptedPasswordsType: boolean
If true, allows login attempts that use passwords encrypted on the client. Even if this property is true, the
canClientEncryptPasswords()method still needs to return true to verify that the application itself can handle passwords encrypted in this way.Default: true (set in DPS module)

