Reference > Shop flow URLs > Member subsystem URLs > Buyers
BuyerRegistrationAdd URL
This URL creates a registration record for a Buyer, which includes an organization and a user.
This URL 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 B2B indirect user can be created by specifying the profileType to have a value of 'B' and may need to be approved.
The BuyerRegistrationAdd URL is a wrapper URL for the ResellerRegistrationAdd URL. The main difference between this URL and ResellerRegistrationAdd, is that this URL reads a different section of the MemberRegistrationAttributes.xml file. In turn, the ResellerRegistrationAdd URL is a wrapper for the OrgEntityAdd and UserRegistrationAdd URLs. Thus, the BuyerRegistrationAdd URL first calls the ResellerRegistrationAdd URL, which in turn calls the OrgEntityAdd URL and the UserRegistrationAdd URL. Except for a few parameters, this URL accepts all the parameters of the UserRegistrationAdd URL with "usr_" added as a prefix to each parameter. Likewise, except for a few cases, this URL accepts all the parameters of the OrgEntityAdd URL with "org_" added as a prefix to each parameter. The following are the exceptions:
- You cannot pass the parentMember parameter to the OrgEntityAdd
URL, that is do not add a prefix to "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 URL, 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 URL, you cannot pass in the orgEntityType
value as this is set to O.
- For the UserRegistrationAdd URL, you cannot pass in the parentMember value since this is determined when the new organization is created.
Use this URL with SSL (Secure Sockets Layer) to ensure that the user's information is encrypted.
To do so type the URL with the HTTPS secure protocol.
URL structure
- http:// host_name/path/
- The fully qualified name of the WebSphere Commerce Server and the configuration path.
name-value pair with the &
character. For a detailed description of the parameters and their values, see the list entitled Parameter values." />
Parameter values
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 URL calls the OrgEntityAdd URL, refer to the Behavior
section for OrgEntityAdd URL. OrgEntityAdd reads the appropriate section
within the MemberRegistrationAttributes.xml file for this URL.
- Next, refer to the Behavior section of the UserRegistrationAdd URL. Note that this URL reads the <UserRoles> element of the MemberRegistrationAttributes.xml file, and applies the roles that have a qualifier of registrationQualifier="BuyerRegistration".
Exception conditions
- Since this URL calls the OrgEntityAdd URL, refer to the Behavior
section for OrgEntityAdd URL.
- Next, refer to the Behavior section of the UserRegistrationAdd
URL.
- Note the information mentioned above about "usr_" and "org_" added as a prefix to each parameter and the exceptions for the parameters.
Related concepts
Related reference
BuyerUserRegistrationUpdate URL
Sample: Member subsystem properties files