If your installation uses a different prefix, or none at all, update the the table names in these instructions to match your installation. Most IEM installations use email_ as a prefix to their table names. Alternatively, you can perform the steps listed in the MySQL or PostgreSQL section below if you’d prefer not to grant this level of access.
If you’re using MySQL, the root level user is typically named root, and if you’re running PostgreSQL, the root level user is typically named postgres. If your IEM installation’s database is running on a different physical server than your GreenArrow Engine installation, root level access to your operating system and database will be needed so that your database can be configured to allow remote connections.
This will be needed to send a test campaign following the patch installation. Login information for an IEM user who is able to edit their SMTP server settings.An SSH account with permission edit your IEM installation’s files, upload new files, and create new cron jobs.In order for GreenArrow to install GreenArrow Engine’s IEM integration patch, we’ll need the following information: This is followed by installation instructions, in case you’d like to install the patch yourself, or are curious about what’s done during the patch installation process. It starts with a list of what GreenArrow will need to install this patch for you.
#Interspire email marketer 6.1.3 how to#
This document describes how to install and configure GreenArrow Engine’s IEM Patch.