Develop > Controller layer > Integrate with back-end systems and external applications > Integration XML messages > Back-end integration messages
Update_NC_Customer message
The Update_NC_Customer message is an inbound message that contains customer information for a customer. A back-end application generates this message and sends it to the WebSphere Commerce inbound message queue, where the WebSphere Commerce system receives the message. WebSphere Commerce updates information for a registered customer by calling the UserRegistrationUpdate command. Since the message invokes the same WebSphere Commerce controller command, the message is identical to the Create_NC_Customer message.
The Update_NC_Customer message uses the XML message format and follows the Update_NC_Customer_10.dtd file.
The following table describes the format of the Update_NC_Customer message. For a description of the database column, follow the link to its associated table. All fields are optional unless otherwise noted. The tag value length in the XML message for database fields of type INT, BIGINT and DOUBLE should be CHAR (10), CHAR(19), and CHAR(16) respectively.
Level Field Name Comment Table Name Column Name 1 LoginInfo Mandatory N/A N/A 1.1 LoginID Mandatory USERREG LOGONID 1.2 Password USERREG LOGONPASSWORD 1.3 VerifyPassword USERREG LOGONPASSWORD 2 MerchantID N/A N/A 2.A1 type Attribute N/A N/A 3 MethodOfCommunication USERPROF PREFERREDCOMM 4 ChallengeQuestion USERREG CHALLENGEQUESTION 5 ChallengeAnswer USERREG CHALLENGEANSWER 6 ShopperField First occurrence USERS FIELD1 6 ShopperField Second occurrence USERS FIELD2 6 ShopperField Third occurrence USERS FIELD3 7 ContactPersonName N/A N/A 7.1 Title ADDRESS PERSONTITLE 7.2 FullName N/A N/A 7.3 LastName ADDRESS LASTNAME 7.4 FirstName ADDRESS FIRSTNAME 7.5 MiddleName ADDRESS MIDDLENAME 7.6 AlternateName ADDRESS NICKNAME 8 RepCompany ADDRESS ORGNAME 9 Address N/A N/A 9.1 AddressLine First occurrence ADDRESS ADDRESS1 9.1 AddressLine Second occurrence ADDRESS ADDRESS2 9.1 AddressLine Third occurrence ADDRESS ADDRESS3 9.2 City ADDRESS CITY 9.3 State ADDRESS STATE 9.4 Zip ADDRESS ZIPCODE 9.5 Country ADDRESS COUNTRY 10 ContactInfo N/A N/A 10.1 Telephone First occurrence ADDRESS PHONE1 10.1 Telephone Second occurrence ADDRESS PHONE2 10.2 First occurrence ADDRESS EMAIL1 10.2 Second occurrence ADDRESS EMAIL2 10.3 Fax ADDRESS FAX1 11 DayPhoneInfo N/A N/A 11.1 PhoneInfo N/A N/A 11.1.A1 type Attribute ADDRESS PHONE1TYPE 11.1.A2 isListed Attribute ADDRESS PUBLISHPHONE1 12 EveningPhoneInfo N/A N/A 12.1 PhoneInfo N/A N/A 12.1.A1 type Attribute ADDRESS PHONE2TYPE 12.1.A2 isListed Attribute ADDRESS PUBLISHPHONE2 13 BestTimeToCall ADDRESS BESTCALLINGTIME 14 IncludePackageInsert ADDRESS PACKAGESUPPRESSION 15 AddressOptField First occurrence ADDRESS FIELD1 15 AddressOptField Second occurrence ADDRESS FIELD2 15 AddressOptField Third occurrence ADDRESS FIELD3 16 Gender N/A N/A 16.A1 value Attribute USERDEMO GENDER 17 AgeGroup USERDEMO AGE 18 IncomeGroup USERDEMO INCOME 19 MaritalStatus USERDEMO MARITALSTATUS 20 NumberOfChildren USERDEMO CHILDREN 21 NumberInHouse USERDEMO HOUSEHOLD 22 WorkCompany USERDEMO COMPANYNAME 23 Interests USERDEMO HOBBIES 24 PreviousOrder USERDEMO ORDERBEFORE 25 Demographics First occurrence USERDEMO FIELD1 25 Demographics Second occurrence USERDEMO FIELD2 25 Demographics Third occurrence USERDEMO FIELD3 25 Demographics Fourth occurrence USERDEMO FIELD4 25 Demographics Fifth occurrence USERDEMO FIELD5 25 Demographics Sixth occurrence USERDEMO FIELD6 25 Demographics Seventh occurrence USERDEMO FIELD7 26 UserData N/A N/A 26.1 UserDataField N/A N/A
Related concepts