BuyerRegistrationAdd command

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:

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.
 
Diagram of the command structure: the command starts with the fully qualified name of your WebSphere Commerce Server and the configuration path, followed by the command name, BuyerRegistrationAdd  and the ? character. End the command with a list of parameters in the form of name value pairs. Separate each name value pair with the & character. For a detailed description of the parameters and their values, refer to the list entitled Parameter values.

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

Exception conditions