This command is used in business indirect scenarios. It registers a new organization and creates a new user whose parent is the newly created organization. The new reseller organization and reseller administrator are placed in pending approval state. After the Site Administrator has approved the organization and user, then the user can log onto the associated organization.
The ResellerRegistrationAdd command is a wrapper command for the OrgEntityAdd and UserRegistrationAdd commands. Specifically, this command first calls the OrgEntityAdd command and then 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 do 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.
After the reseller is registered, the reseller cannot log on until the Site Administrator provides approval. Information for new users are stored in the ADDRESS, BUSPROF, MBRREL, MEMBER, ORGENTITY, USERDEMO, USERPROF, USERREG, and USERS database tables.
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 reseller ABC:
https://myhostname/webapp/wcs/stores/servlet/ResellerRegistrationAdd? storeId=10001&URL=ResellerRegistrationApprovalView&org_orgEntityName=ABC &usr_logonId=myUserLogonId&usr_logonPassword=myUser1Password &usr_logonPasswordVerify=myUser1Password
Behavior
- Since this command first 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="ResellerRegistration".
Exception conditions
- Since this command first 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.