This command creates a registration record for a Buyer, which includes an organization and a user. After the Buyer is registered, the Buyer can only log onto the system after approval. By default approval is turned on. Information for new users are stored in the MEMBER, USERS, USERREG, MBRREL, USERPROF, BUSPROF, USERDEMO, and ADDRESS database tables.
A B2B direct or value chain user can be created by specifying the profileType to have a value of 'B' and may need to be approved.
The BuyerRegistrationAdd command is a wrapper command for the ResellerRegistrationAdd command. The main difference between this command and ResellerRegistrationAdd, is that this command reads a different section of the MemberRegistrationAttributes.xml file. In turn, the ResellerRegistrationAdd command is a wrapper for the OrgEntityAdd and UserRegistrationAdd commands. Thus, the BuyerRegistrationAdd command first calls the ResellerRegistrationAdd command, which in turn calls the OrgEntityAdd command and the UserRegistrationAdd command. Except for a few parameters, this command accepts all the parameters of the UserRegistrationAdd command with "usr_" prepended to each parameter. Likewise, except for a few cases, this command accepts all the parameters of the OrgEntityAdd command with "org_" prepended to each parameter. The following are the exceptions:
- You cannot pass the parentMember parameter to the OrgEntityAdd command, that is do not prepend "usr_" to the parentMember parameter to make it usr_parentMember. Instead, the parentMember information is read from the <RegistrationParents> element of the MemberRegistrationAttributes.xml file.
- For the OrgEntityAdd command, the administratorFirstName, administratorLastName, and administratorMiddleName values are retrieved from usr_firstName, usr_lastName, and usr_middleName. Thus you cannot pass in org_administratorFirstName, org_administratorLastName, and org_administratorMiddleName.
- For the OrgEntityAdd command, you cannot pass in the orgEntityType value as this is set to O.
- For the UserRegistrationAdd command, you cannot pass in the parentMember value since this is determined when the new organization is created.
Use this command with SSL (Secure Sockets Layer) to ensure that the user's information is encrypted. To do so type the command with the HTTPS secure protocol.
Command structure
- http://host_name/path/
- The fully qualified name of your WebSphere Commerce Server and the configuration path.
Parameter values
Since this command first calls the OrgEntityAdd command, refer to the Parameter values section for OrgEntityAdd command. Next, refer to the Parameter values section of the UserRegistrationAdd command. Also note the information mentioned above about "usr_" and "org_" prepended to each parameter and the exceptions for the parameters.
Example
The following example creates a registration record for the Buyer ABC:
https://myhostname/webapp/wcs/stores/servlet/BuyerRegistrationAdd? storeId=10001&URL=OrgRegistrationAddPendingForApprovalView &org_orgEntityName=ABC&usr_logonId=myUserLogonId&usr_logonPassword=myUser1Password &usr_logonPasswordVerify=myUser1Password
Behavior
- Since this command calls the OrgEntityAdd command, refer to the Behavior section for OrgEntityAdd command. OrgEntityAdd reads the appropriate section within the MemberRegistrationAttributes.xml file for this command.
- Next, refer to the Behavior section of the UserRegistrationAdd command. Note that this command reads the <UserRoles> element of the MemberRegistrationAttributes.xml file, and applies the roles that have a qualifier of registrationQualifier="BuyerRegistration".
Exception conditions
- Since this command calls the OrgEntityAdd command, refer to the Behavior section for OrgEntityAdd command.
- Next, refer to the Behavior section of the UserRegistrationAdd command.
- Note the information mentioned above about "usr_" and "org_" prepended to each parameter and the exceptions for the parameters.