SRT: Knowledge Base


Developers Guide

Introduction

This manual is an expansion of the general manual. General points will not be mentioned or explicated here, but technical possibilities will be covered.

Preliminary

The Magento and the Shopware Interface help themselves with the SOAP functionality. Therefore there are further access data needed, especially for the Shops.

  • SOAP WSDL Key [ normally dynamic determined]
  • API Group (all rights given ->Admin)
  • API Username
  • API Password

1. Configuration

1.1 Configuration possibilities of the Automatic Mode

The following parameter can be applied for the automated data alignment. A combination is possible (Example: debugger.exe katexport artikelexport…)

ParameterModuleDescription
katexportArtikelexportCategory alignment
artikelexportArtikelexportItem export
artikelimport_imagesArtikelexportEntire alignment incl. image export
artikelexport_geaendertArtikelexportChanged article
artikel_geaendert_imagesArtikelexportChanged article with images
preis_bestandPreis- und BestandArticle inventory / Article price
preisPreis- und BestandOnly price alignment
bestandPreis- und BestandOnly quantity inventory
sonderpreiseAktionspreisBargain/Special offer price
kundenexportKundenexportCustomer alignment
kundenexport_geaendertKundenexportChanged customers
bestellimportBestellimportImport of the ordering
zubehoer_artikelC/U/Z ModulAccessory article
up_sellingC/U/Z ModulUp-Selling
cross_sellingC/U/Z ModulCross-Selling
staffelpreiseStaffelpreiseQuantitative rebate
kundenimportKundenimportImport of customers
docs_exportDokumentenverwaltungTransfer of the relative documents/technical PDFs
detailsWill be conducted at the end. Export is dependent on the configuration

1.2 Transformation of a SageDB to MySQL/MSSQL

The migration of SageDB to a MySQL or MSSQL is only necessary in case of buying an ordering-import. In standard the SageDB can be readout, but it is write-protected.

The interface needs a write authorization on the Database for the ordering-import module. You will get the necessary authority through the migration of SageDB.

  1. Install a MySQL/MSSQL-environment (advisable with administration surface)
  2. Start Sage and establish a new “Server” (Menü->Datei->Serververwaltung)
  3. Jump to mandatory administration and select the desired mandatory with a right click.
  4. Select the option “migrieren” and follow the installation instruction.

Tip: In an installation of a network all PC-names or IP’s (not allowed to be dhcp) must be added to Apache MySQL.

INSERT INTO user (Host, User, Password, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv, Create_view_priv, Show_view_priv, Create_routine_priv, Alter_routine_priv, Create_user_priv, Event_priv, Trigger_priv, ssl_type, ssl_cipher, x509_issuer, x509_subject, max_questions, max_updates, max_connections, max_user_connections) VALUES (‘WORKGROUP’, ‘root’, ”, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ”, ”, ”, ”, 0, 0, 0, 0);

1.3 Connection of different Database Forms

Database callDatabaseConnection String
ODBCODBCProvider=SQLOLEDB;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername; Password=myPassword;
MSSQL 2000, MSSQL2000Microsoft MS SQL <-2005Server=myServerName\theInstanceName;Database=myDataBase;Trusted_Connection=True;
MSSQL 2005, MSSQL2005Microsoft MS SQL <-2008Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
MSSQL 2008, MSSQL2008Microsoft MS SQL >-2008Data Source=myServerAddress;Initial Catalog=myDataBase;User Id= myUsername;Password=myPassword;
SQL Server Compact EditionSQL Server Compact EditionData Source=MyData.sdf;Persist Security Info=False;
SQLBaseSQLBaseDataSource=myServerAddress;UserId=myUsername;Password=myPassword;
Mimer SQLMimer SQLDatabase=myDataBase;Protocol=local;User Id=myUsername;Password=myPassword;
Postgre SQLPostgre SQLServer= myServerAddress;Port=5432;Database=myDataBase;User Id=myUsername;Password=myPassword;
SQL AzureSQL AzureServer=tcp:[serverName].database.windows.net;Database=myDataBase;User ID=[LoginForDb]@[serverName];Password= myPassword;Trusted_Connection=False;Encrypt=True;
MySQLMySQLServer=myServerAddress;Port=1234;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Access MS Access (mdb, accdb)Driver={Microsoft Access Driver (*.mdb, *.accdb)}; Dbq=C:\mydatabase.accdb; Uid=Admin;Pwd=;
OracleOracleData Source=username/password@myserver/myservice: dedicated/instancename;
InformixInformixDatabase=myDataBase;Host=192.168.10.10;Server=db_engine_tcp;Service=1492; Protocol=onsoctcp;UID=myUsername; Password=myPassword;
InterbaseInterbaseDriver={Easysoft IB6 ODBC};Server=localhost;Database=localhost:C:\mydatabase.gdb; Uid=myUsername;Pwd=myPassword;
PervasivePervasiveServer Name=myServerAddress;Database Name=myDataBase;User ID= myUsername; Password=myPassword;
Sybase Advantage DatabaseSybaseProvider=Advantage OLE DB Provider;User ID=adssys;Data Source=MyDataDictionaryPath;Advantage Server Type=ADS_REMOTE_SERVER;
Sybase Adaptive Server EnterpriseSybaseDriver={Adaptive Server Enterprise};server=myServerAddress;port=myPortnumber; db=myDataBase;uid=myUsername;pwd=myPassword;
IBM UniData, IBM, IBM UniVerseIBMDATA SOURCE=myDataSource;LOCATION=myLocation;USER ID=myUsername;PASSWORD=myPassword;
IBM DB2IBM DB2DataSource=myServerAddress;UserID=myUsername;Password=myPassword; DataCompression=True;
ProgressProgressDataSourceName=myDSN;HostName=myServerAddress;Database=myDataBase;LogonID=myUsername; Password=myPassword;PortNumber=2055;
ParadoxParadox;Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\myDb;Extended Properties=Paradox 5.x;
IngresIngresProvider=MSDASQL;DRIVER=Ingres;SRVR=xxxxx;DB=xxxxx;Persist Security Info= False;Uid=myUsername;Pwd=myPassword; SELECTLOOPS=N;Extended Properties= “SERVER=xxxxx; DATABASE=xxxxx; SERVERTYPE= INGRES”;
LightbaseLightbaseUser=myUsername;Password=myPassword;UDB=USERBASE;Server=myServerAddress;
FirebirdFirebirdUser=SYSDBA;Password=masterkey;Database=SampleDatabase.fdb;DataSource=localhost; Port=3050;Dialect=3; Charset=NONE;Role=;Connection lifetime=15;Pooling=true; MinPoolSize=0;MaxPoolSize=50;Packet Size=8192;ServerType=0;
TeradataTeradataData Source=myServerAddress;User ID=myUsername;Password=myPassword;
DBMakerDBMakerProvider=DMOLE43;User ID=myUserName;Password=myPassword;Data Source=myDatabaseName;
VistaDBVistaDBData Source=D:\folder\myVistaDatabaseFile.vdb3;Open Mode=ExclusiveReadWrite;
Netezza DBMSNetezza DBMSDriver={NetezzaSQL};servername=myServerAddress;port=myPortNumber;database=myDataBase; username=myUsername; password=myPassword;
FileMakerFileMakerDriver=FileMaker Pro;AllAsText=0;ApplicationUsingThreads=1;FetchChunkSize=100;FileOpenCache=0; IntlSort=0;MaxTextlength=255;ServerAddress=127.0.0.1; TranslationOption=0;UseRemoteConnection=1;
SharePointSharePointProvider=Microsoft.ACE.OLEDB.12.0;WSS;IMEX=2;RetrieveIds=Yes; DATABASE=http://pp1webofficelivecom.officelive.com/Documents/;LIST={5999B8A0-0C2F-4D4D-9C5A-D7B146E49698};

2. Configuration of XML Structures / Modules

In this section, the establishment and the structure of XML will be explained. For the protection of the modules’ flexibility, every module was outsourced in a XML before.

You can find the configurationdata for the export under

“{Installation path/_Struktur/xml/module/}” and for the import “{Installation path/_Struktur/xml/import/}”.

2.1 Export of the Informations in the Shop

The XML module-data include different SQL-statements. In a change in the parameter sequence you have to pay attention to the online interface which also must be adapted.

If there are only the entries which must be changed, a reconfiguration of the online-interface is not necessary.

Parameter/FeldnameBezeichnungDatentyp
NummerCategoriesalphanumerisch
BezeichnungCategory namealphanumerisch
0ParentZahl
‘langtext’Long-textalphanumerisch
‘1’StatusZahl
Nummer.jpgCategory image descriptionalphanumerisch
KategorienSortierungSorting keysZahl
MetaKeywordsMeta keywordsalphanumerisch
MetaTitleMeta titelalphanumerisch
MetaDescMeta descriptionalphanumerisch
suchbegriffSearch termalphanumerisch
katSeoSeo Keywordsalphanumerisch
spracheLanguageIDZahl
FF1FF1alphanumerisch
FF2FF2alphanumerisch

2.1.1 Example on Category Export

<MODUL_KATEGORIEN>

select g.Nummer AS KatID, g.Bezeichnung AS KatName, ‘0’ as Parent, ‘Langtext’ as Langtext, ‘1@’+g.Nummer as Aktiv_Sortierung, (g.Nummer+’.jpg’) AS Kategorie_Bild, g.Nummer AS Kategorie_Sortierung, ‘KeyWords’ AS Kategorie_MetaKeywords, ‘MetaDesc’ AS Kategorie_MetaDesc, ‘MetaTitle’ AS Kategorie_MetaTitle, ‘Suchbegriff’ AS Kategorie_Suchbegriffe, ” AS Kategorie_SEO, ‘2’ AS Kategorie_Sprache_Store, ” AS KategorieFF1, ” AS KategorieFF2 FROM gruppen as g where (g.ID = ‘AG’) AND (g.PARENT is NULL) ORDER BY g.Nummer

</MODUL_KATEGORIEN>

2.1.2 Example on Article Export

<ARTIKEL_MIT_FILTER>

select ” as Artikel_Typ, ” AS Artikel_Kategorie_ID, ” AS Hersteller_ID, ” AS Artikel_Artikelnr, ” AS Artikel_Menge, ” AS Artikel_Preis,” AS Artikel_Preis1, ” AS Artikel_Preis2, ” AS Artikel_Preis3,” AS Artikel_Preis4, ” AS Artikel_Gewicht, ” AS Artikel_Status , ” AS Artikel_Steuersatz, Artikelnummer AS Artikel_Bilddatei, ” AS Artikel_VPE, ” AS Artikel_Lieferstatus, ” AS Artikel_Startseite, ” AS SkipImages, ” AS Artikel_Bezeichnung, ” AS Artikel_Text, ” AS Artikel_Kurztext, ” AS Artikel_TextLanguage, ” AS Artikel_MetaTitle, ” AS Artikel_MetaDescription, ” AS Artikel_MetaKeywords, ” AS SuperAttribut, ” AS Aktiv, ” as AttributSet, ” AS Artikel_Variante_Von, ” AS Merkmal, ” AS Auspraegung FROM TABELLE  Artikelnummer like ‘$AktionMitFilter’ AND getdate()>’$srtTimeStamp’

</ARTIKEL_MIT_FILTER>

Parameter/FeldnameBezeichnungDatentyp
Artikel_TypArticletype for Magento

–          Configurable

–          Simple

–          Bundle

–          Grouped

 

Other: 0

alphanumerisch
Artikel_Kategorie_IDCategory assignmentalphanumerisch
Hersteller_IDProduceralphanumerisch
Artikel_ArtikelnrArticle number

 

Additional option: EAN

Article number + „@“ + EAN

alphanumerisch
Artikel_MengeStockZahl
Artikel_PreisPrice (List price, unit price)Zahl
Artikel_Preis1Price for group 1Zahl
Artikel_Preis2Price for group 2Zahl
Artikel_Preis3Price for group 3Zahl
Artikel_Preis4Price for group 4Zahl
Artikel_GewichtArticle weightZahl
Artikel_StatusArticle status

 

Magento: 1-4

Other: 1

Zahl
Artikel_BilddateiArticlenumber (Quantity: unbounded)alphanumerisch
Artikel_VPEPackaging unit (ml, l, Stk)alphanumerisch
Artikel_LieferstatusDeliver statusalphanumerisch
Artikel_StartseiteDisplay on the homepageBoolean
SkipImagesLeap image editing for certain articleBoolean
Artikel_BezeichnungArticle description (Shop: Name)alphanumerisch
Artikel_TextArticle long-text (Shop: Long Descriptionalphanumerisch
Artikel_KurztextArticle short-text (Shop: Short Descriptionalphanumerisch
Artikel_TextLanguageLanguageidZahl
Artikel_MetaTitleMetainformation titlealphanumerisch
Artikel_MetaDescriptionMetainformation descriptionalphanumerisch
Artikel_MetaKeywordsMetainformation search termsalphanumerisch
SuperAttributSuperAttribute (Magento type: Configurable) is a filter-possibility in the Shop

 

alphanumerisch
AktivStatus aktive/inaktiveBoolean
AttributSetMagento: the relative attribute-set which bundles the attributesalphanumerisch
Artikel_Variante_VonParent/Main/Configurable Article number: Server for the assignment of the subordinate article „Variante“Zahl
MerkmalArticle attribute

 

If multiple, then must be divided with an „@“

e.g.: color@size

alphanumerisch
AuspraegungArticle specification

If multiple, then must be divided with an „@“

e.g.: blau@12

alphanumerisch
$AktionMitFilterSpecial feature: filter functionalphanumerisch
$srtTimeStampSpecial feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

2.1.3 Example on Special Offer Prices

<MODUL_ACTIONSPREISE>

select ” AS Artikel_Artikelnr, ” AS Artikel_Anzahl, ” AS Aktionspreis, ” VonDatum, ” BisDatum, ” FreiFeld1, ” FreiFeld2 FROM Tabelle where  Artikelnummer like ‘$AktionMitFilter’

</MODUL_ACTIONSPREISE>

Parameter/FeldnameBezeichnungDatentyp
Artikel_ArtikelnrArticle numberalphanumerisch
AktionspreisSpecial offer priceZahl
VonDatumSpecial offer valid fromDatum
BisDatumSpecial offer valid toDatum
FreiFeld1FreiFeld1alphanumerisch
FreiFeld2FreiFeld2alphanumerisch
$AktionMitFilterSpecial feature: Filter functionalphanumerisch

 

2.1.4 Example on Cross-Selling

<MODUL_CROSS_SELLING>

select ‘cross_sell’ AS Xsell_Type, ” AS Artikel_Artikelnr, ” AS Xsell_Artikel_Artikelnr, ” AS FreiFeld1, ” AS FreiFeld2, ” AS FreiFeld3, ” AS FreiFeld4 FROM TABELLE WHERE  Artikelnummer like ‘$AktionMitFilter’ AND getdate()>’$srtTimeStamp’

</MODUL_CROSS_SELLING>

Parameter/FeldnameBezeichnungDatentyp
Xsell_TypeType: ‘cross_sell’alphanumerisch
Artikel_ArtikelnrArticle numberalphanumerisch
Xsell_Artikel_ArtikelnrReference article numberalphanumerisch
FreiFeld1FreiFeld1alphanumerisch
FreiFeld2FreiFeld2alphanumerisch
FreiFeld3FreiFeld3alphanumerisch
FreiFeld4FreiFeld4alphanumerisch
$AktionMitFilterSpecial feature: Filter functionalphanumerisch
$srtTimeStampSpecial feature: In diese Variable wird der akt. Wert eingetragen, sobald der Export durchgelaufen wird. Die Datei mit den aktuellen werden befindet sich in der timestamp.xmlDatum

2.1.5 Example on Up-Selling

<MODUL_ARTIKEL_UP_SELLING>

select ‘up_sell’ AS Xsell_Type, ” AS Artikel_Artikelnr, ” AS Xsell_Artikel_Artikelnr, ” AS FreiFeld1, ” AS FreiFeld2, ” AS FreiFeld3, ” AS FreiFeld4 FROM TABELLE WHERE  Artikelnummer like ‘$AktionMitFilter’ AND getdate()>’$srtTimeStamp’

</MODUL_ARTIKEL_UP_SELLING>

Parameter/FeldnameBezeichnungDatentyp
Xsell_TypeTyp: ‘up_sell’alphanumerisch
Artikel_ArtikelnrArtikelnummeralphanumerisch
Xsell_Artikel_ArtikelnrReferenz Artikelnummeralphanumerisch
FreiFeld1FreiFeld1alphanumerisch
FreiFeld2FreiFeld2alphanumerisch
FreiFeld3FreiFeld3alphanumerisch
FreiFeld4FreiFeld4alphanumerisch
$AktionMitFilterSpecial feature: Filterfunktionalphanumerisch
$srtTimeStampSpecial feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

2.1.6 Example on Accessory Article

<MODUL_ARTIKEL_UP_SELLING>

select ‘up_sell’ AS Xsell_Type, ” AS Artikel_Artikelnr, ” AS Xsell_Artikel_Artikelnr, ” AS FreiFeld1, ” AS FreiFeld2, ” AS FreiFeld3, ” AS FreiFeld4 FROM TABELLE WHERE  Artikelnummer like ‘$AktionMitFilter’ AND getdate()>’$srtTimeStamp’

</MODUL_ARTIKEL_UP_SELLING>

Parameter/FeldnameBezeichnungDatentyp
Xsell_TypeType: related’alphanumerisch
Artikel_ArtikelnrArticle numberalphanumerisch
Xsell_Artikel_ArtikelnrReference article numberalphanumerisch
FreiFeld1FreiFeld1alphanumerisch
FreiFeld2FreiFeld2alphanumerisch
FreiFeld3FreiFeld3alphanumerisch
FreiFeld4FreiFeld4alphanumerisch
$AktionMitFilterSpecial feature: Filter functionalphanumerisch
$srtTimeStampSpecial feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

2.1.7 Example on Customer Export

<MODUL_KUNDEN>

select ” AS customers_id_ustidnr, ” AS customers_gender, ” AS customers_firstname, ” AS customers_lastname, ” AS customers_dob, ” AS customers_email_address, ” AS customers_telephone, ” AS customers_fax, ” END AS customers_group, ” AS customers_company, ” AS customers_street_address, ” AS customers_postcode, ” AS customers_city, ” AS customers_countries_iso_code, ” AS customers_password, ” Freifeld1, ” Freifeld2, ” Freifeld3, ” Freifeld4, ” Freifeld5 FROM tabelle WHERE Nummer like ‘$AktionMitFilter’

</MODUL_KUNDEN>

Parameter/FeldnameBezeichnungDatentyp
customers_id_ustidnrCustomer numberalphanumerisch
customers_genderGenderalphanumerisch
customers_firstnameNamealphanumerisch
customers_lastnameSurnamealphanumerisch
customers_dobBirthalphanumerisch
customers_email_addressE-Mailalphanumerisch
customers_telephonePhonealphanumerisch
customers_faxFax numberalphanumerisch
customers_groupCustomer groupZahl
customers_companyFirmalphanumerisch
customers_street_addressStreetalphanumerisch
customers_postcodePostcodeZahl
customers_cityCityalphanumerisch
customers_countries_iso_codeCountry code (ISO Standard)alphanumerisch
customers_passwordCustomer passwordalphanumerisch
Freifeld1Freifeld1alphanumerisch
Freifeld2Freifeld2alphanumerisch
Freifeld3Freifeld3alphanumerisch
Freifeld4Freifeld4alphanumerisch
$AktionMitFilterSpecial feature: Filter functionalphanumerisch
$srtTimeStampSpecial feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

 

2.1.8 Example timestamp.xml

The explanation of the verification date is marked with the attribute „FORMAT_TIMESTAMP“. The description of the format begins in row 19.

2.2 Details / Individual Expansion

In the export module, XML-Tags are defined with “DETAILS”, which can be used for subsequent transactions. These tags need the same quantity of parameters and are free configurable.

3. Import

3.1 Ordering-Import

The Ordering-Import is subdivided in 2 processes. First of all the orderings will be imported online in the “\_Struktur\xml\import\orders\opentrans_xml.xml” and afterwards they will be specified for the relative ERP through “opentrans_xslt.xsl”.

The last step is the importing of the data over the image of XML “xml_into_DB.xml”.

Process order
opentrans_xml.xml -> opentrans_xslt.xsl -> opentrans_xslt_xml.xml -> xml_into_DB.xml

Tip Ordering-Import (Data format)

The ERP New Classic Line, MOS-Tangram, AFS-Software and Lexware XML can archive a data in standard in file INSTALLATION PATH/_STRUKTUR/Bestellung. The establishment of the created data is as the following: DATUM.XML, DATUM.TXT or DATUM.CSV.

3.2 Characteristics of the Ordering-Imports

3.2.1 Characteristic (Sage) New Classic Line

The orderings will be provided for the import as XML File. To import the generated XML, the following steps must be obeyed.

  1. Open the ERP
  2. Select the menu item job-processing -> Webshop
  3. Select Webaufträge aus Datei übernehmen
  4. Push the button F2
  5. Data will be imported

3.2.2 Characteristics of the ERP Sage

In the product-line Sage PC-Kaufmann / Sage GS-Auftrag / Sage GS-Office / Sage GS-Quantum / Sage Office Line the same tables will be used as in the Sage GS Shop import. If the functionalities are deactivated, the following commands must be discharged on the Database.

  1. In the table “sg_sys_objektdaten” it is about the entry with
    DatenObjectIndex = “bghia_etpsn”. It proofs if this mandatory was newly applied and therefore may not be used with GS-Shop. Please remove the date
  2. The three terms for the GS-Shop activations are: There must be a minimum of one GS-Shop article, customer and procedure.

Alternative:

  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ” WHERE DatenObjektIndex = ‘bghia_etpsn’;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‘1’ WHERE DatenObjektIndex = ‘GsShop_sg_auf_artikel@onlineartikel’;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‘1’ WHERE DatenObjektIndex = ‘GsShop_sg_adressen@onlinekunde’;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‘1’ WHERE DatenObjektIndex = ‘GsShop_sg_auf_fschrift@ausshop’;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‘1’ WHERE DatenObjektIndex = ‘GsShop_GssMigratedProductCount’;
  • UPDATE sg_auf_artikel SET onlineartikel = 1 WHERE SG_AUF_ARTIKEL_PK = (SELECT SG_AUF_ARTIKEL_FK FROM sg_auf_fpos ORDER BY SG_AUF_FSCHRIFT_1_FK DESC LIMIT 1);
  • UPDATE sg_adressen SET onlinekunde = 1 WHERE SG_Adressen_PK=(SELECT SG_Adressen_FK FROM sg_kunden LIMIT 1);
  • UPDATE sg_auf_fschrift SET ausshop = 1 WHERE SG_AUF_FSCHRIFT_PK = (SELECT SG_AUF_FSCHRIFT_1_FK FROM sg_auf_fpos ORDER BY SG_AUF_FSCHRIFT_1_FK DESC LIMIT 1);

3.2.1 Characteristic Lexware

The Ordering-Import through the Lexware XML structure occurs over the e-Business module. Normally you can reach the settings on the Homepage in the menu Extras over the options in the section Configurations – Sale – eBusiness.

3.3 Mapping of opentrans-XML

The opentrans_xslt.xsl is appropriate for the simplified configuration. Hereby it is possible to set fast and new pay- and ordering-conditions.

Example:
<xsl:when test=”ORDER_HEADER/ORDER_INFO/DELIVERY_METHOD = ‘prepayment’”>
<SHIPPING_METHOD>10</SHIPPING_METHOD>
</xsl:when>

The XML-Tag <DELIVERY_METHOD> will be read out of the “opentrans_xml.xml” and reconverted. Thereby “prepayment” change to VersandID 10.

4. Automatic Mode / Service

4.1 Installation

To install the interface as a service please start:

“Start -> All Programs -> Microsoft Visual Studio 2008 -> Visual Studio Tools -> Open Visual Studio Command Prompt” [Image Command Prompt]

entwickler_Auomatik_1

Image: Command Prompt

Afterwards jump to the SRT “Dienst.exe” in the open Visual Studio Commando Shell. The “Dienst.exe” reside in the installation register.

entwickler_Auomatik_2

Step 2:

When arrived in the correct register, please export the command Installutil Dienst.exe.

 

Step 3:

Start the service under System Control/Service/srtDienst

 

4.2 Un-installation

For the un-installation you must enter the following command in the Visual Studio Commando Shell. Installutil /u Dienst.exe

Related Articles