Create standard message
ERP expectations
ERP expects the a request and response with the following XML:
Request UPDATECUSTOMER
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33 | <WC_USER_MANAGEMENT>
<PROCESS_TYPE>UPDATECUSTOMER</PROCESS_TYPE>
<GUID>1</GUID>
<WEB_SITE>HOME</WEB_SITE>
<NUMBER>1000006</NUMBER>
<BLOCKED />
<CURRENCY />
<WEB_NEWSLETTER>1</WEB_NEWSLETTER>
<JOB_TITLE />
<E_MAIL></E_MAIL>
<NAME>Toni Kreucher</NAME>
<NAME_2 />
<ADDRESS />
<ADDITIONAL_ADDRESS_INFO />
<CITY>Hamburg</CITY>
<COUNTRY_CODE />
<COUNTY />
<RESPONSIBILITY_CENTER />
<COMPANY_NUMBER></COMPANY_NUMBER>
<FAX_NUMBER></FAX_NUMBER>
<POST_CODE />
<PHONE_NUMBER></PHONE_NUMBER>
<HOME_PAGE />
<E_MAIL />
<LANGUAGE_CODE>DEU</LANGUAGE_CODE>
<SALUTATION />
<SALESPERSON_CODE />
<CUSTOMER_POSTING_GROUP />
<GEN_BUS_POSTING_GROUP />
<VAT_BUS_POSTING_GROUP />
<CONTACT_PERSON />
<CREDIT_LIMIT_LCY />
</WC_USER_MANAGEMENT>
|
Response UPDATECUSTOMER
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19 | <WC_USER_MANAGEMENT>
<PROCESS_TYPE>HOME</PROCESS_TYPE>
<GUID>1</GUID>
<WEB_SITE>UPDATECUSTOMER</WEB_SITE>
<NUMBER>1000006</NUMBER>
<NAME>Toni Kreucher</NAME>
<CITY>Hamburg</CITY>
<LANGUAGE_CODE>DEU</LANGUAGE_CODE>
<CUSTOMER_POSTING_GROUP>INLAND</CUSTOMER_POSTING_GROUP>
<GEN_BUS_POSTING_GROUP>INLAND</GEN_BUS_POSTING_GROUP>
<VAT_BUS_POSTING_GROUP>INLAND</VAT_BUS_POSTING_GROUP>
<WEB_NEWSLETTER>1</WEB_NEWSLETTER>
<COUNT_OF_SHIP_TO_ADRESSES>0</COUNT_OF_SHIP_TO_ADRESSES>
<CUST_PRICE_GROUP>
<CODE>DVGW</CODE>
<END_DATE>17530101</END_DATE>
<ASSOCIATION_NO></ASSOCIATION_NO>
</CUST_PRICE_GROUP>
</WC_USER_MANAGEMENT>
|
Tip
You have to know the webservice operation that is used for this message.
If you see that all XML elements are written with capital letters, usually it means that the webservice operation is SV_RAW_MESSAGE.
Define request and response document
The request and response documents are used as a frame for the generating PHP classes that are used in shop.
The generator uses them to create the classes automatically.
Message name
Create two .xml files, one for request, one for response,
in /silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml.
Naming conventions
The files must be named:
| request.[messageName].xml
response.[messageName].xml
|
For example:
| vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml/request.updateCustomer.xml
vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml/response.updateCustomer.xml
|
Request XML
Root Tag
Create a root tag in your request document:
| <?xml version="1.0" encoding="UTF-8"?>
<RequestUpdateCustomer>
</RequestUpdateCustomer>
|
Tip
The root tag must be unique in the target directory (in this example, vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle).
Content
Now you have to fill it with some content.
You can use standard .xml documents to become a part of our message.
These documents are located in /vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml as well:
| Contact.xml
DeliveryParty.xml
LineItem.xml
Party.xml
//You can also create your own structure and define an own document, it can be used in every message
MyCustomXml.xml
|
Content structure
If you take a look inside these documents and compare the structure with the UPDATECUSTOMER that is expected by ERP
you can find out that there are many commonalities with Party.xml.
UPDATECUSTOMER
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33 | <WC_USER_MANAGEMENT>
<PROCESS_TYPE>UPDATECUSTOMER</PROCESS_TYPE>
<GUID>1</GUID>
<WEB_SITE>HOME</WEB_SITE>
<NUMBER>1000006</NUMBER>
<BLOCKED />
<CURRENCY />
<WEB_NEWSLETTER>1</WEB_NEWSLETTER>
<JOB_TITLE />
<E_MAIL></E_MAIL>
<NAME>Toni Kreucher</NAME>
<NAME_2 />
<ADDRESS />
<ADDITIONAL_ADDRESS_INFO />
<CITY>Hamburg</CITY>
<COUNTRY_CODE />
<COUNTY />
<RESPONSIBILITY_CENTER />
<COMPANY_NUMBER></COMPANY_NUMBER>
<FAX_NUMBER></FAX_NUMBER>
<POST_CODE />
<PHONE_NUMBER></PHONE_NUMBER>
<HOME_PAGE />
<E_MAIL />
<LANGUAGE_CODE>DEU</LANGUAGE_CODE>
<SALUTATION />
<SALESPERSON_CODE />
<CUSTOMER_POSTING_GROUP />
<GEN_BUS_POSTING_GROUP />
<VAT_BUS_POSTING_GROUP />
<CONTACT_PERSON />
<CREDIT_LIMIT_LCY />
</WC_USER_MANAGEMENT>
|
Party.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36 | <Party ses_unbounded="PartyIdentification PartyName" ses_type="ses:Contact" ses_tree="SesExtension">
<PartyIdentification>
<ID>10000</ID>
</PartyIdentification>
<PartyName>
<Name>Möbel-Meller KG</Name>
</PartyName>
<PostalAddress ses_unbounded="AddressLine" ses_tree="SesExtension">
<StreetName>Tischlerstr. 4-10</StreetName>
<AdditionalStreetName />
<BuildingNumber>4-10</BuildingNumber>
<CityName>Berlin</CityName>
<PostalZone>12555</PostalZone>
<CountrySubentity>Berlin</CountrySubentity>
<CountrySubentityCode>BER</CountrySubentityCode>
<AddressLine>
<Line>Gartenhaus</Line>
</AddressLine>
<Country>
<IdentificationCode>DE</IdentificationCode>
<Name>Deutschland</Name>
</Country>
<Department>Development</Department>
<SesExtension />
</PostalAddress>
<Contact>
</Contact>
<Person ses_tree="SesExtension">
<FirstName>Frank</FirstName>
<FamilyName>Dege</FamilyName>
<Title>Herr</Title>
<MiddleName />
<SesExtension />
</Person>
<SesExtension />
</Party>
|
For this reason Party.xml is good enough to be used as a part of the message:
| <?xml version="1.0" encoding="UTF-8"?>
<RequestUpdateCustomer ses_type="ses:Party">
<Party />
</RequestUpdateCustomer>
|
ses_type
Pay attention if you want to use an external XML document inside your message.
In this case ses_type is required and the second part after the colon must be the referred file name (excluding .xml).
The prefix ses: causes the message generator to look up the external XML file within SilversolutionsEshopBundle.
It also generates the PHP objects within SilversolutionsEshopBundle.
With any other prefix (which should be cust:) the file is looked up in the specified source directory and generated to the specified target directory.
Response XML
Root Tag
Create a root tag in your response document:
| <?xml version="1.0" encoding="UTF-8"?>
<ResponseUpdateCustomer ses_type="ses:Party">
</ResponseUpdateCustomer>
|
Content
Fill your response document with content:
| <?xml version="1.0" encoding="UTF-8"?>
<ResponseUpdateCustomer ses_type="ses:Party">
<Party />
</ResponseUpdateCustomer>
|
Generator
Now you can use the generator to generate the classes automatically:
| //Usage
php bin/console silversolutions:generatemessages --message [message name] --sourceDir [path to the request and response .xml dir] --targetDir [path to the target bundle]
//Example
php bin/console silversolutions:generatemessages --message updateCustomer --sourceDir vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml --targetDir vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle
//Re-generation of messages
//If you are re-creating the messages (e.g. the request .xml has been adapted) you have to use to optional --force parameter
php bin/console silversolutions:generatemessages --message updateCustomer --sourceDir vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml --targetDir vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle --force
|
Mapping
Mapping is done during runtime.
Performing the mapping is often enough if only the mapping is overridden in the project,
instead of overriding the .xml and re-generating of the messages.
Symlinks
There should be a symlink to the mapping in app/Resources:
xsl - project symlink for the specific project - always has a higher priority
xslbase - standard symlink for eZ Commerce as a default
| cd app/Resources
ls -l
xsl -> ../../src/MyProject/MyProjectBundle/Resources/xsl
xslbase -> ../../vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/xslbase
|
Mapping is done inside the vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/xslbase folder.
Naming conventions
The mapping document does not have to same the same name as message name,
but th structure must look like this:
| request.[mappingName].xsl
response.[mappingName].xsl
|
| //Example
vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/xslbase/request.updatecustomer.xsl
vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/xslbase/response.updatecustomer.xsl
//But you could also add:
vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/xslbase/request.myMapping.xsl
vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/xslbase/response.myMapping.xsl
|
Request XSL
As you can see above, the structure of UPDATECUSTOMER expected by ERP and the Party.xml is not exactly the same. For this reason you have to add mapping - how the information of UPDATECUSTOMER will be mapped into the Party object.
First, copy the structure of UPDATECUSTOMER and add it as a content into the request .xsl document.
Note
In the line <xsl:template match="/RequestUpdateCustomer/Party"> you have to add the element of the .xml document which you are going to map on. In this case take a look at the request .xml (vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/specifications/xml/request.updateCustomer.xml).
It is the root tag RequestUpdateCustomer and the Party tag.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35 | <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/RequestUpdateCustomer/Party">
<WC_USER_MANAGEMENT>
<PROCESS_TYPE>UPDATECUSTOMER</PROCESS_TYPE>
<WEB_SITE>HOME</WEB_SITE>
<NUMBER></NUMBER>
<BLOCKED />
<CURRENCY />
<WEB_NEWSLETTER />
<JOB_TITLE />
<NAME></NAME>
<NAME_2 />
<ADDRESS></ADDRESS>
<ADDITIONAL_ADDRESS_INFO></ADDITIONAL_ADDRESS_INFO>
<CITY></CITY>
<COUNTRY_CODE></COUNTRY_CODE>
<COUNTY></COUNTY>
<RESPONSIBILITY_CENTER />
<COMPANY_NUMBER />
<FAX_NUMBER></FAX_NUMBER>
<POST_CODE></POST_CODE>
<PHONE_NUMBER></PHONE_NUMBER>
<HOME_PAGE />
<E_MAIL></E_MAIL>
<LANGUAGE_CODE></LANGUAGE_CODE>
<SALUTATION></SALUTATION>
<SALESPERSON_CODE />
<CUSTOMER_POSTING_GROUP></CUSTOMER_POSTING_GROUP>
<GEN_BUS_POSTING_GROUP></GEN_BUS_POSTING_GROUP>
<VAT_BUS_POSTING_GROUP></VAT_BUS_POSTING_GROUP>
<CONTACT_PERSON></CONTACT_PERSON>
<CREDIT_LIMIT_LCY />
</WC_USER_MANAGEMENT>
</xsl:template>
</xsl:stylesheet>
|
Then add mapping information how the attributes of UPDATECUSTOMER are supposed to be mapped into Party attributes.
Note
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37 | <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/RequestUpdateCustomer/Party">
<WC_USER_MANAGEMENT>
<PROCESS_TYPE>UPDATECUSTOMER</PROCESS_TYPE>
<WEB_SITE>HOME</WEB_SITE>
<NUMBER>
<xsl:value-of select="PartyIdentification/ID"/>
</NUMBER>
<BLOCKED />
<CURRENCY />
<WEB_NEWSLETTER />
<JOB_TITLE />
<NAME><xsl:value-of select="PartyName/Name"/></NAME>
<NAME_2 />
<ADDRESS><xsl:value-of select="PostalAddress/StreetName"/></ADDRESS>
<ADDITIONAL_ADDRESS_INFO><xsl:value-of select="PostalAddress/AdditionalStreetName"/></ADDITIONAL_ADDRESS_INFO>
<CITY><xsl:value-of select="PostalAddress/CityName"/></CITY>
<COUNTRY_CODE><xsl:value-of select="Country/IdentificationCode"/></COUNTRY_CODE>
<COUNTY><xsl:value-of select="PostalAddress/CountrySubentity"/></COUNTY>
<RESPONSIBILITY_CENTER />
<COMPANY_NUMBER />
<FAX_NUMBER><xsl:value-of select="Contact/Telefax"/></FAX_NUMBER>
<POST_CODE><xsl:value-of select="PostalAddress/PostalZone"/></POST_CODE>
<PHONE_NUMBER><xsl:value-of select="Contact/Telephone"/></PHONE_NUMBER>
<HOME_PAGE />
<E_MAIL><xsl:value-of select="Contact/ElectronicMail"/></E_MAIL>
<LANGUAGE_CODE><xsl:value-of select="Contact/SesExtension/LanguageCode"/></LANGUAGE_CODE>
<SALUTATION><xsl:value-of select="Person/Title"/></SALUTATION>
<SALESPERSON_CODE />
<CUSTOMER_POSTING_GROUP><xsl:value-of select="SesExtension/CustomerPostingGroup"/></CUSTOMER_POSTING_GROUP>
<GEN_BUS_POSTING_GROUP><xsl:value-of select="SesExtension/GenBusPostingGroup"/></GEN_BUS_POSTING_GROUP>
<VAT_BUS_POSTING_GROUP><xsl:value-of select="SesExtension/VatBusPostingGroup"/></VAT_BUS_POSTING_GROUP>
<CONTACT_PERSON><xsl:value-of select="Contact/Name"/></CONTACT_PERSON>
<CREDIT_LIMIT_LCY />
</WC_USER_MANAGEMENT>
</xsl:template>
</xsl:stylesheet>
|
Response XSL
You have to add a backward mapping from Party attributes into UPDATECUSTOMER attributes. For this reason copy the content of the Party.xml and use it as content for your response .xsl.
Then add mapping information on how the attributes of Party are suppose to be mapped into UPDATECUSTOMER attributes.
Note
Some standard .xml document such as Party.xml can contain other standard documents such as Contact.xml.
In this case you also have to copy the content of the sub-documents.
Note
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48 | <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/*">
<ResponseUpdateCustomer>
<Party>
<PartyIdentification>
<ID>
<xsl:value-of select="NUMBER"/>
</ID>
</PartyIdentification>
<PartyName>
<Name><xsl:value-of select="NAME"/></Name>
</PartyName>
<PostalAddress ses_unbounded="AddressLine" ses_tree="SesExtension">
<StreetName><xsl:value-of select="ADDRESS"/></StreetName>
<AdditionalStreetName><xsl:value-of select="ADDITIONAL_ADDRESS_INFO"/></AdditionalStreetName>
<BuildingNumber />
<CityName><xsl:value-of select="CITY"/></CityName>
<PostalZone><xsl:value-of select="POST_CODE"/></PostalZone>
<CountrySubentity><xsl:value-of select="COUNTY"/></CountrySubentity>
<AddressLine>
<Line />
</AddressLine>
<Country>
<IdentificationCode><xsl:value-of select="COUNTRY_CODE"/></IdentificationCode>
</Country>
<SesExtension />
</PostalAddress>
<Contact>
<Name><xsl:value-of select="CONTACT_PERSON"/></Name>
<Telephone><xsl:value-of select="PHONE_NUMBER"/></Telephone>
<Telefax><xsl:value-of select="FAX_NUMBER"/></Telefax>
<ElectronicMail><xsl:value-of select="E_MAIL"/></ElectronicMail>
<SesExtension>
<LanguageCode><xsl:value-of select="LANGUAGE_CODE"/></LanguageCode>
</SesExtension>
</Contact>
<Person ses_tree="SesExtension">
<Title><xsl:value-of select="SALUTATION"/></Title>
</Person>
<SesExtension>
<CustomerPostingGroup><xsl:value-of select="CUSTOMER_POSTING_GROUP"/></CustomerPostingGroup>
<GenBusPostingGroup><xsl:value-of select="GEN_BUS_POSTING_GROUP"/></GenBusPostingGroup>
<VatBusPostingGroup><xsl:value-of select="VAT_BUS_POSTING_GROUP"/></VatBusPostingGroup>
</SesExtension>
</Party>
</ResponseUpdateCustomer>
</xsl:template>
</xsl:stylesheet>
|
Message configuration
You also have to configure the message. The generator has created some frames already.
By default the messages are configured in the messages.yml.
You need to add imports and parameters:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18 | //Import the auto-generated listener here
imports:
- { resource: "@SilversolutionsEshopBundle/Resources/config/updatecustomerfactorylistener.service.yml" }
//Add message configuration
parameters:
silver_erp.config.messages:
...
//take a look in the auto-generated vendor/silversolutions/silver.e-shop/src/Silversolutions/Bundle/EshopBundle/Resources/config/updatecustomermessage.message.yml
updatecustomer:
//path to the auto-generated message
message_class: "Silversolutions\\Bundle\\EshopBundle\\Entities\\Messages\\UpdateCustomerMessage"
//path to the auto-generated response class
response_document_class: "\\Silversolutions\\Bundle\\EshopBundle\\Entities\\Messages\\Document\\ResponseUpdateCustomer"
//name of the webservice operation
webservice_operation: "SV_RAW_MESSAGE"
//mapping name
mapping_identifier: "updatecustomer"
|