Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
addons:bizwizard:installation [2019-01-18 09:15] Ahmad Game removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Installation (Lime version 12.21 or lower) ====== | ||
- | ===== Requirements ===== | ||
- | The following is required for the Lime CRM Newsletter integration to work: | ||
- | * **Microsoft .NET Framework 4.0** (full edition) | ||
- | * **Lime CRM Web Service** | ||
- | During installation you will also need the following: | ||
- | * **Administrator privileges** on the machine where the integration is to be installed. | ||
- | * **Account details** (username and password) for the BizWizard-account, | ||
- | * **Site name** (e.g. //< | ||
- | * **Site GUID** Must be provided by the Marketing Tech team | ||
- | * **Connection details** for Lime CRM Web Service (shared account mode): | ||
- | * Set Session mode to **Shared** and provide a LIME username and password (eg BIAuser/ | ||
- | * Binding type (e.g. //basic http//) | ||
- | * Endpoint address (e.g. //< | ||
- | | ||
- | ===== Step-by-step guide ===== | ||
- | Follow these simple steps to get the Lime CRM Newsletter integration up and running: | ||
- | |||
- | ==== Lime CRM ==== | ||
- | - Make sure the tables, fields and properties in [[addons: | ||
- | - Start Lime CRM and adjust views and filters for the campaign table and the other newly created tables to your liking. | ||
- | |||
- | <WRAP round important> | ||
- | === Warning! === | ||
- | If any changes is made in the field configuration in Lime CRM through LISA you must restart the Lime CRM Web Service to update the structure | ||
- | </ | ||
- | |||
- | ==== BizWizard ==== | ||
- | |||
- | If you haven' | ||
- | |||
- | ==== Install and setup BIA ==== | ||
- | |||
- | The BIA setup is in standard configured to work with the default Lime CRM database (Core) but can be configured to work with any field setup. If field names and options differs from the standard it must be changed in various settings files. | ||
- | |||
- | ==== BIA Setting files ==== | ||
- | |||
- | **Default table names and field names** | ||
- | All default values will be generated when starting the integration the first time and will be found in | ||
- | LimeSettings.xml in the plugin folder. | ||
- | |||
- | **Default values in the Lime settings page in BizWizard** | ||
- | All default values will be generated when starting the integration the first time and will be found in | ||
- | LimeUserSettings.xml in the plugin folder. | ||
- | |||
- | **Default batch settings** | ||
- | All default values will be generated when starting the integration the first time and will be found in | ||
- | EventBatchSettings.xml in the plugin folder. | ||
- | |||
- | **Default fields for synched columns** | ||
- | All default values will be generated when starting the integration the first time and will be found in | ||
- | SynchedColumnSettings.xml in the plugin folder. | ||
- | |||
- | ==== Start installation ==== | ||
- | |||
- | - Copy the Netoptions to the Lime server (or other server that can talk to the Lime server). The standard configuration for all search paths are set for c:/ | ||
- | - Change all setting files in order to match the field and option key names in Lime CRM (only if you have different names than standard). | ||
- | - Open BiaSetting.xml in Netoptions/ | ||
- | - Open the file biaservicename.txt and set the name of the service (not mandatory, it is the service name that will appear under Services in windows e.g. LIME Bia Integrator) | ||
- | - Right click the .bat file and set the SERVICE_EXE=" | ||
- | - Setup the databasename (not the Display Name) and Web Service end-point address in jhe file BIA\Plugins\LimePro\Netoptions.BiaIntegrators.LundalogikLimePro.dll.config | ||
- | - Run the BAT file. | ||
- | |||
- | ===== Upgrading ===== | ||
- | Q: It is possible to upgrade from older version of Bizwizard integration? | ||
- | A: No, no really a upgrade. This is a total rewritten integration and must be seen as a new installation |