SMTP Server Setup

Create a new SMTP Server with the following settings:

• Server – smtp.office365.com
• Port – 587
• User – Your Office365 Login (this can be different to your email)
• Password – The password for the user above.
• TLS – Checked

Press the Test button to ensure the connection can be successfully made.

Email Group Setup

Create an Email Group with the following settings:

• Mail Server – Select the Office365 Server created in the step above.
• From – Enter a valid email address which the user specified in the SMTP Server has the rights to send on behalf of. It is probable the sender email will be the same as this user.
• To, CC, Bcc – These will be recipients of the email. Dependent on your email policies these may only be addresses within your organisation.

Press the Test button to ensure a test email can be successfully sent. Again this will be dependent on your policies, if an error is displayed, somewhere within the error will point you to the issue.

Backup

Backup the IMan database.

Take a copy of the IMan shared data directory. This directory contains several folders: Cache, Config, Debug, & JobConf. The ‘JobConf.’ folder is critical and contains the Xml configuration files.

Note the username in which IMan is running under, by clicking the Permissions button at the bottom of the screen.

License Key

If you are moving from one major version to another i.e. from v3.x to v4.x, please contact Realisable to obtain your new license key.

Obtain New Connectors

If you are use any of the non-bundled connectors (Magento, Salesforce, Shopify, etc) please contact Realisable to obtain new connectors.

Updating Existing IMan Instance

Uninstall existing version.

Install new version. When prompted, ensure the ‘IIS Application Pool’ is the IMan Application Pool. Also, double check that the IMan shared data directory is the same directory as in step two of the ‘Backup’ section above.

After installing you will need to update both the database and each integration job, due to all the enhancements & changes. To do this, follow the steps detailed below.

Updating the Database

Open the IMan Admin Console.

Press the ‘Test’ button in the database settings. The ‘DB Created’ status should display ‘Requires Update’.

Press the ‘Update’ button.

When the update is complete, press ‘Save’ and select ‘Yes’ to restart the services and IMan Application Pool. This will allow the update to come into effect

Updating the License

Press the ‘License Info’ button on the Admin Console.

Enter your company contact details and correct serial number.

Press ‘Activate’ and follow the prompts.

Updating Integration Jobs

Due to possible schema changes within the job configurations it is necessary to update each integration job to the latest schema version.

Login to IMan, and load an integration job from the drop down.

A prompt will indicate if the schema has been updated.

Close the prompt and repeat the above steps for each integration.

This FAQ describes the procedure for migrating IMan from one server [source] to another [target].

The FAQ assumes competency with SQL server as well as knowledge of the IMan install procedure and pre-requisites. The target server is assumed to have all the pre-requisites installed.

A lot of this document borrows from the Copy and Upgrade FAQs.

Installing IMan onto New Server

Install IMan onto the new server, taking note of the IMan shared data folder (typically C:\IMan).

Backing Up Jobs & IMan Database

If you’re moving the IMan database to another server, open SQL Server Management Studio and take a backup of the IMan database. Restore the database onto the new server.

Take a copy of the IMan job configuration folder. In this case C:\IMan\JobConf

Restore the IMan job configuration files to the IMan shared data folder (C:\IMan\JobConf) on the new IMan server.

Note the username in which IMan is running under, by clicking the Permissions button at the bottom of the screen.

Configuring New IMan Instance

Open the IMan Console, set the Database settings according to where the IMan database is located. Test and update the database if required.

If IMan was set to run under non Default Permissions (step 4 above), press the Permissions button, setting the permissions accordingly. This may involve creating up a local user, dependent on the user setup.

Press Save to commit the settings.

Checking All Existing Dependencies

This section describes how the various settings should be checked, after the database & job migration has been completed. Essentially, you need to ensure all the various dependencies (Database connections, File Locations, Email & FTP Servers) can all be connected with.

If you have installed a new version of IMan, open each job in the designer, to ensure the configuration version is current.

Database Connections – Depending on whether all database connections have been setup in Setup, Database Connections or specified individually within the integration configurations themselves will dictate how you test. If setup with the Database Connections screen, simply edit each connection and press the Test button. If the database has been specified within the configuration, you will need to open the integration configuration, open either the Database Reader or Writer and check connectivity by hitting Refresh.

SMTP, POP3 & FTP Servers – Go to the respective configurations within the Setup tab of IMan, edit each record and press the Test button.

File Locations – Any Reader, Writer or Task which has a file path should be checked to ensure the path exists on the new server.

CSV, Xml, Fixed With Text or Excel Readers/Writers

File Task

Un-install Old Server

Before un-installing the server, launch the IMan Admin console and click the License Info button.

Make a note of the Serial Number and other details.

Uninstall the software, and when prompted to unregister the license, select Yes.

Licence New Server

Open Admin Console on the new IMan server, press License Info, enter the details per the step above, press Activate and follow the steps as you would normally to license IMan.

FTP/SSH Setup

To authenticate with an SSH server using keys you must create a private/public key using either RSA or DSA type keys in OpenSSH format.

The server you are connecting with will hold the public key and you enter the unencrypted private key into IMan.

RSA Private Key Sample

			-----BEGIN RSA PRIVATE KEY-----
			MIIEpQIBAAKCAQEAvTjHMg1+nAogY3o8V8zXKwf+VuTMtIZggCiUQ9NU884PeHnb
			tezsx5KRuAtNqhWtgEsNg0/aHv6o/7E4HJE9PCqVpUXnTV1mZE14BvmusCnuz1HL
			nV3CtSW3BOh98sHixwu0I4y2RZy0sfaTBn1zDXvCv2mrVL5D1QnOZ8B/Vi5fceQd
			eaLe6Uzj6vTi5MBWjzvVog/xDr0tEo4FPRmu6SUkmTzhwEiETScm5qOm9VnTr2O9
			sCibFPmqrODGAzpj/OWIH2RMMT1B9Nl6P6JvHWZc92rqrUVZHBkSoakNWkytLN5j
			WyxwIdCFxQvCnAKic7uOodMSiqDUPJHHlPIghwIDAQABAoIBAAK9V4JPz9beH3dk
			cqzyfW33VTH6nFX/cr0ISE7c9F+45D4vCTfsfYHvix/mCXbTsJapIagWc9FqZdF2
			+Xd4ayB7riguwz+x1o9YR4cRywwoLBFP9tzvjMnvkaepAQHTG+HHFUTNskfDVngC
			wOtlvGHXZPIbU+QLvoGtMFZSOHBrs1cOfoUO1BToN1cGfgp/DuJY6WWVoNs93C8J
			wgnH2DdosRcMDYOQsASH60hEE2JJuF7Ox+BwlcsV5AUDwIeAChQI0Aend7NL9cee
			U8o3UXAVjABowGI9EQJYUmysir5mFs/BETlPambyvEWWNCtJsT2qrCi2Xme5BRzD
			p5MMJ+ECgYEAzfbbQagHiP48yGiZS2j7i1UcV/0pgeamtjaxJf1njyMrkyxMFOFW
			PfLOVLcRnx4HcqYYv9Opo8mbYlxjUUFxhMBYdyNICx8OjM7eijSjGisvAh0S20Vo
			LvhQ0zzv1/QUdnj4jO4FWNgHYUF+mre8nX8k/s8AcudBR7n5w+MhP7cCgYEA6zCw
			DGB8ipBQMryEWVNc0eYFFXojxlFRKjp4BRc43F0s0gyRLWGCUHTN0Z1DPKQRilo6
			D8nGANN8BYVFDEcuFk8SCks5Xk76YfL+9uAETKv7y//AE8dyrCRk8/7kyOdMhHtq
			1bHsAutfxeiYrdRWyK0ZApAKdSEy+BvdVRv9hbECgYEAzcNdvlUg2gKsNMcSxpym
			GMe5nknj6svEJ2uyRLLJf91yDgEGLSIFp7Pn4AhYiW9Vn3tCZHoQEvo5yuVjr2zC
			/Q2wE63iroGjZpbRCp+VhnI371OeYAMSF0KqdK5/Km7E9qraHOk53E1N6iKlWepP
			e8Tm781btG9F72NjnAhQUjcCgYEA1XB2FIVsAQQ/BAx5v+cbkZHCg185ID2j/0LY
			sSYGAFa+2lF1X03iycl3EAg8gMgU8w43KyTegNls8EWmCCKA/NX9dUIXajMan9G6
			+akLvdlGxjfvxQN4WikdRSHJ11mx43lt10mE+pFJdX5FMVxG9g/BZsX595qNewUu
			tJKWXcECgYEAqHYYHyZI9dah6JVpm5UQ6kJbDPZad7uus/lmJfTgY+ZCH1sEVySL
			UYk4TyswyUqzLfazhhQ9yZsDBmdm6jRJLYtQBo9fybpOzeyK20aFIGQTSaVFbAGG
			YIsv2DOWk9HHr0TSG7yu/1hiMf3ol0ofpTEQpXyM8qjVuqCeqsMeJ9I=
			-----END RSA PRIVATE KEY-----
			

RSA Private Key Sample

			-----BEGIN DSA PRIVATE KEY-----
			MIIDPgIBAAKCAQEAqj/5FQjdsvxasIvxdEKbIe0SuHfJxlLSdCqvKsknpn26UBSd
			W5wXqiUSmLrU7mLIRAVxdQ7umcp3N8w/dIiVkiJvm+tUQqlPYrd6n2JK+eQ0lGtP
			emsn6fQzHhUmG0jCFgot3nNodspb5euUxVrU0BCq2PpKRuGKt6cyq5oEAvlg1K6p
			vpze8tZ+etZGToN2uBQ/3ysGjgiDs3Zgh/k3o+8UteuBdjd8awEHcIzFml8w3+XW
			EjuOslWrda8KiPCRZEQIbNfiZrcTzAefNRzJhKJL6EkuCU+3oZo8DL6Xc+0Obkk6
			46kYV5oDYbPBDmNIQBCr6odNHnWnBBnSs3TbLQIVANkiO001oz4lzhsO/tDx9rpO
			yH/5AoIBAA8UN/pP7CYBI1KJ5KvBM7SSd5S5ItjA2ALboHF5uAWBKpaJvaHyHi/v
			/eCd1BahglmdTsWoP2W5p4HmHjr6fLseuPGyLTHkGFgKd/zC5eTBid8ShNPJIByK
			m7XVGvLFhDqhiNKIIsOqYKYkNXmQjms5VInwT4GfE2orVr5MPSg3k3DtX220CIrE
			BaPXK4JRdrq2Jezxh7Pp76w+ZEfaQhgf9uEPWtBe0zmKsQ2gjdjRphm+tl4gFR0r
			4JuJeOTs9UZ4rZlMojK2Ew64rHhaAROHHjOJiQdvBEBYxXNru71sqt7xQbYtqHBR
			+oBgRFbPPouNMIUexC4DKxyNeuN2zIcCggEAXh/Akb90+cojwtyjzXTxA9h4CzfT
			E1G0cWziwToFYPVt/xWZM1/kDEAWRWtTDidZWRxWXxP+8J7PrMwA4Pwoq2SPW1u9
			qQh1mGpPaPDluPiRbMKL2uV9oLfVEY7naVrqH05EPgtbiNjDin7EQljo3IoKzpEK
			B1lFHT/Vd4CMTdl7o+QhZ5ftMGv9sbmf2eZ6y9fQpebO7o4w7/LgQ5SaIWYaCiTZ
			WNTS4vLeNBuJBVJL/pL3tMQrQFqHAg4o94q6M5Y6NvnsSoyZ3gs5bnuyH/wk2oXd
			lNhRVx1DMYBSdeWRlgjLYUBEKDABs+1N/9nBIZDEUQYvVA71Fawp4cqizgIVAKI4
			pSbllzsgU0NB+IQTQU7C/TKv
			-----END DSA PRIVATE KEY-----
			

Identify the job ID

Copy the configuration file

Located in jobconf (usually C:\IMan) to another folder:

(Optional) If you are copying on the same installation

The “jobid” attribute within the configuration file must be unique. In this case for example, change:

FROM:

TO (it is also recommended that you alter the “name” attribute to make the copy, once imported, easier to identify):

Stopping IMan

• Start the administration console and stop all the IMan services.
  
• Stop the IMan IIS App Pool.
  

Steps for Connectors

What Are Connectors?

Connectors provide the integration with a specific application such as Sage, Magento, Salesforce, Concur, etc.

Connectors files have file names which are in the form .Connectors*...dll e.g.

• Realisable.Connectors45.Sage300.dll
• Realisable.Connectors45.Sage200.2017.dll
• RealSW.Connectors45.Amazon.dll
• ECInternet.Connectors.Magento.dll

• Navigate to the addins folder for the IMan shared data. This is typically c:\IMan\addins
• Copy the existing file to an external directory as a backup. Do NOT rename files, move them out of the directory.
• Ensure that any files being copied are unblocked.
  

Steps for Core Files

What Are Core Files

Core files are files which are not ‘connector’ files. These are common files are used by different aspects of IMan from UI to processing.

Core files have file names which are NOT in the form of connector files, basically everything else.

Please note the different directions for v4.1 vs v4.0 and earlier.

Version 4.1

• Navigate to your IMan install folder C:\Program Files (x86)\Realisable Software\IMan\Web\bin
  
• Copy the existing file to an external directory as a backup.
• Copy the new file to the bin folder replacing the original file. Do NOT rename files, move them out of the C:\Program Files (x86)\Realisable Software\IMan\Web\bin folder or sub folders.
• Ensure that any files being copied are unblocked.
  

Version 4.0 and earlier

• Navigate to your IMan install IIS folder e.g. C:\inetpub\wwwroot\IMan\bin
  
• Copy the existing file to an external directory as a backup.
• Copy the new file to the bin folder replacing the original file. Do NOT rename files, move them out of the \inetpub\wwwroot\IMan folder or sub folders.
• Ensure that any files being copied are unblocked.