This is an old revision of the document!
Configuration
Configuration files
The configuration files found in different folders:
netoptions/bia folder:
biaservicename.txt: Name of the service created, not mandatory to change
RegisterService.bat: The installation .bat file, you must set the path correct:
- SERVICE_EXE=“C:\Netoptions\BIA\Netoptions.BizWizard.v3.Bia.WinService.exe”
netoptions/bia/settings:
BiaSettings.xml: The file where you edit transaction intervalls and bia integrator settings. You must add/change
- BIAIntegrator id, choose any number you like
- ddlPath: dllPath=“C:\Netoptions\BIA\Plugins\LimePro\Netoptions.BiaIntegrators.LundalogikLimePro.dll”
- url=
"http://www.bwz.se/lundalogik" - siteGuid=“
363659d0-a012-11dd-ad8b-0800200c9a66”
netoptions/bia/settings:
LimeSettings.xml All connected tables and fields in LIME Pro. If the names differ it must be changed here
<?xml version="1.0" encoding="utf-8"?> <LimeSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <CampaignSettings> <TableName>marketing</TableName> <NameField>name</NameField> <TypeField>type</TypeField> <CampaignStatusField>marketingstatus</CampaignStatusField> </CampaignSettings> <ParticipantSettings> <TableName>participant</TableName> </ParticipantSettings> <PersonSettings> <TableName>person</TableName> <EmailField>email</EmailField> <FirstNameField>firstname</FirstNameField> <LastNameField>lastname</LastNameField> <TotalOptOutField>totaloptout</TotalOptOutField> <InvalidEmailField>emailbounce</InvalidEmailField> <CompanyField>company</CompanyField> </PersonSettings> <MailingSettings> <TableName>mailing</TableName> <StatusKeySent>sent</StatusKeySent> <StatusKeyOpened>open</StatusKeyOpened> <StatusKeyBounce>bounce</StatusKeyBounce> <StatusKeyClicked>clicked</StatusKeyClicked> <StatisticLinkField>statisticlink</StatisticLinkField> <MailOutLinkField>sendoutlink</MailOutLinkField> <SubjectField>subject</SubjectField> <CampaignField>marketing</CampaignField> <MailingidField>mailingid</MailingidField> </MailingSettings> <RecipientSettings> <TableName>recipient</TableName> <MailingField>mailing</MailingField> <PersonField>subscriber</PersonField> <StatusField>sendoutsstatus</StatusField> </RecipientSettings> <CompanySettings> <TableName>company</TableName> <NameField>name</NameField> <BuyingStatusField>buyingstatus</BuyingStatusField> <CoWorkerField>responsible</CoWorkerField> </CompanySettings> <CoworkerSettings> <TableName>responsible</TableName> <EmailField>email</EmailField> </CoworkerSettings> </LimeSettings>
<Wrap Info> If any changes are made to the campaign fields in LIME Pro and the limesetting.xml file it must also be changed in the LimeUserSettings.xml
<CampaignSettings>
<TableName>campaign</TableName> <NameField>name</NameField> <TypeField>type</TypeField> <CampaignStatusField>campaignstatus</CampaignStatusField> </CampaignSettings>
LimeUserSettings.xml
SynchedColumnSettings.xml
Sample configuration
The following is an example of a typical Apsis Integration configuration file:
The lundalogik.dataaccess
section specifies how the application connects to LIME Pro Web Service for adding and updating LIME Pro data. The name
attribute of the database
element must match the database
attribute of the lime
element in the lundalogik.apsis
section. Apsis account details are specified in the apsis
element. The apsis userName is the Apsis-API account, specified for the customer (customer must order this in advance).