Liaison Messenger Installation Guide

Liaison Messenger

®

 

 

 

INSTALLATION GUIDE 

 

 

This document is also available on the CD in a PDF format and  can also be printed on 8‐1/2 x 11 paper for easier reading. 

 

 

 

Please see the Help menu on Liaison Messenger Server for the Configuration and User manuals. 

 

 

 

 1991‐2009 Liaison Software Corporation 

2021 E. 4 th

 Street • Suite 218 

Santa Ana, CA 92705 

Phone 714.543.9877 • Fax 714.543.9879 

 

 

 

ALL RIGHTS RESERVED. THIS WORK AND THE COMPUTER PROGRAMS TO WHICH IT RELATES ARE THE PROPERTY OF, AND 

EMBODY  TRADE  SECRETS  AND  CONFIDENTIAL  INFORMATION  PROPRIETARY  TO,  LIAISON  SOFTWARE  CORPORATION.  

MANUAL COPYRIGHT 



 2008 LIAISON SOFTWARE CORPORATION. ALL RIGHTS RESERVED. 

MESSENGER®  AND  LIAISON  MESSENGER®  ARE  REGISTERED  TRADEMARKS  OF  LIAISON  SOFTWARE  CORPORATION  IN  THE 

UNITES  STATES  AND  CANADA.  LIAISON  SOFTWARE  CORPORATION  IS  A  TRADEMARK.  THE  NAMES  OF  COMPANIES, 

PRODUCTS,  PEOPLE,  AND/OR  DATA  USED  IN  WINDOW  ILLUSTRATIONS  AND  SAMPLE  OUTPUT  ARE  FICTITIOUS  AND  ARE  

IN  NO  WAY  INTENDED  TO  REPRESENT  ANY  REAL  INDIVIDUAL,  COMPANY,  PRODUCT,  OR  EVENT,  UNLESS  OTHERWISE 

NOTED.

OFFICIAL LICENSE AGREEMENT

Liaison Software Corporation

 

The Software or Firmware, referred to as “Program”, is licensed not sold. 

Liaison Software Corporation, or the applicable Liaison Software Country  organization, grants you a license for the Program only in the country for  which it was acquired. You obtain no rights other than those granted you 

  under this license. 

The term “Program” means the original and all whole or partial copies of it,  including modified copies or portions merged into other programs. Liaison 

Software Corporation retains title to the Program. Liaison Software 

Corporation owns, or has licensed from the owner, copyrights in the 

 

 

Program. 

You are responsible for the selection of the Program and for the installation  of, use of, and results obtained from the Program. 

1. License 

Under this license, you may: 1) Use the Program on only one machine at any  one time for the Single‐user version of the program and on only one server at  any one time for the multi‐user version of the Program. When data and  programs are on different servers, a multi‐server or WAN (Wide Area 

Network) license is required. 2) Copy the Program for backup. 3) Transfer  possession of the Program to another party. 

 

If you transfer the Program, you must transfer a copy of this license, all other  documentation, and at least one complete, unaltered copy of the Program to  the other party. You must, at the same time, either transfer all of your other  copies of the Program to the other party or destroy them. Your license is then  terminated. The other party agrees to these terms and conditions by its first  use of the Program. 

 

You may not: 1) Use, copy, modify, merge, or transfer copies of the program  except as provided in this license. 2) Reverse assemble or reverse compile  the Program. 3) Sublicense, rent, lease, or assign the Program. 

 

2. Limited Warranty 

The Programs are not warranted and are licensed on an “AS IS” basis by 

Liaison Software Corporation. All Programs have a 30 day limited warranty 

  on their media, which commences from the date of purchase. 

THESE WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES (OR 

CONDITIONS), EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A 

 

PARTICULAR PURPOSE. 

SOME JURISIDICTIONS DO NOT ALLOW THE EXCLUSIONS OF IMPLIED 

 

WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. 

3. Limitations Of Remedies 

Liaison Software Corporation entire liability and your exclusive remedy shall  be: 1) The replacement of any diskette not meeting the “Limited Warranty”  and which is returned to Liaison Software Corporation along with your  original purchase receipt. 

 

 

If Liaison Software Corporation is unable to deliver a replacement diskette,  which is free from defects in materials or workmanship, you may terminate  this Agreement by returning the programs, documentation, hardware and  any other materials provided, within 90 days of purchase, and your money  will be refunded. 

 

 

IN NO EVENT WILL LIAISON SOFTWARE CORPORATION BE LIABLE TO YOU 

FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR 

OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 

USE OR INABILITY TO USE LIAISON SOFTWARE CORPORATION PROGRAMS 

OR HARDWARE EVEN IF LIAISON SOFTWARE CORPORATION HAS BEEN 

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR FOR ANY CLAIM BY 

 

ANY OTHER PARTY. 

SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF 

LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE 

 

ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. 

4. General Provisions 

You may terminate your license at any time. Liaison Software Corporation  may terminate your license if you fail to comply with the terms and  conditions of this license.  In either event, you must destroy all your copies of  the Program. You may not sublicense, assign or transfer this license,  programs, or the program documentation except as expressly provided for in  this Agreement. Any attempt otherwise to sublicense, assign or transfer any  of the rights, duties, or obligations hereunder is null and void.  You are  responsible for payment of any taxes, resulting from this license. Neither  party may bring an action, regardless of form, more than two years after the  cause of action arose. If you acquired the Program in the United States, the  laws of the state of California govern this license. If you acquired the 

Program in Canada, the laws of the Province of Ontario govern this license. 

Otherwise, this license is governed by the laws of the country in which you  acquired the Program. 

 

5. Intellectual Property Rights  a) RESELLER recognizes LIAISON's and/or the relevant manufacturer(s)  right, title and interest in and to the rights to patents, design, utility models,  software architecture and coding methodology, trademarks, trade names,  know‐how, trade secrets, copyright, photography rights and other industrial  and intellectual property rights, hereafter collectively referred to as 

"Intellectual Property Rights", relating to the Products. b) Specifically, all  right, title and interest in and to the Intellectual Property Rights relating to  the Products shall at all times remain the property of LIAISON and/or the  manufacturer(s) and RESELLER shall not use any Intellectual Property 

Rights in any manner except as permitted in this Agreement or by prior  written authorization of LIAISON and/or the manufacturer(s). c) RESELLER  shall not remove or alter any Intellectual Property Rights notice associated  with the Products without the express written permission of LIAISON and/or  the manufacturer(s). d) RESELLER agrees that it will not de‐compile, reverse  engineer, or otherwise in any manner attempt to derive or have derived the  source code for the Products, except to the extent allowed under applicable 

  law. e) RESELLER agrees that it will not use the provided Not For Resale  products to develop a product, which may compete with Liaison Software 

Corporation or the products of Liaison Software Corporation. f) RESELLER  agrees not to lend, borrow, resell, or reassign the provided products to any 

3 rd

 Party who may develop, produce or resell a competing product or who  may compete with Liaison Software Corporation. 

Should you have any questions about this 

Agreement, you may contact Liaison Software 

Corporation by writing to 2021 E. 4 th

 Street, 

Suite 218, Santa Ana, CA 92705.

ii

 

Liaison Messenger

®

 Support  and Maintenance Agreement 

 Upon payment of the annual maintenance and support services fee, 

Liaison Software Corporation© doing business as Liaison, (“Liaison”)  will provide the following maintenance and support services to the  registered user (“you”) for Liaison Messenger® software (the 

“Software”) during the Term: 

 

MAINTENANCE AND SUPPORT BENEFITS.  All (a) updates for the  installed and registered Software (including related documentation)  commercially released by Liaison during the Term (updates consist of  new releases of a particular software version which provide functional  enhancements and error corrections which are indicated by a change  in the numeric identifier in the digits to the right of the decimal such as  from version .0 to version .0a). In addition, Liaison shall provide a  discount on all version and product upgrades to the Software that are  commercially released by Liaison during the Term (version upgrades  consist of new releases with a higher version number such as from 2.x 

  to 3.x.  

TELEPHONE AND FACSIMILE SUPPORT. Liaison shall provide  unlimited telephone and facsimile support. The hours of support of  operation are 7:00a.m. to 4:00 p.m. Pacific Standard Time, during  normal business hours (Monday through Friday), excluding holidays. 

The registered user shall appoint up to two (2) individuals within its  organization to serve as the primary contacts between Liaison and the  registered user, and to receive support through the telephone support  center. The registered user can increase the number of permissible  contacts subject to payment to Liaison of additional fees. Phone  support will be offered for the current release, plus one release back 

 

(e.g., releases 1.5 and 2.0).  

Telephone and facsimile support does not include customization to  templates, custom templates or filters made by the registered user or  consultant employed by the registered user. Any necessary support to  templates, custom templates or filters is billable by Liaison at the  current hourly rate per hour. At the discretion of Liaison Software 

Corporation, Liaison may require prepayment before modifications are  completed. 

 

LIMITED WARRANTY. Liaison warrants that the support services will  be performed in a professional workmanlike manner. EXCEPT FOR 

THE EXPRESS WARRANTY PROVIDED ABOVE, THE SUPPORT 

SERVICES ARE PROVIDED “AS IS” AND WITHOUT A WARRANTY OF 

ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY OR 

OTHERWISE, AND LIAISON SPECIFICALLY DISCLAIMS ANY IMPLIED 

WARRANTY, TERM OR CONDITION OF MERCHANTABILITY, NON‐

INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE. THIS 

LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU 

MAY HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE. 

 

LIMITATION OF LIABILITY. Liaison’s entire liability to you or any other  party for any loss or damage resulting from any claims, demands or  actions arising out of this Agreement shall not exceed the annual  maintenance and support fee paid to Liaison for the software, net of  dealer or distributor margins, notwithstanding any failure of essential  purpose of any limited remedy. 

 

NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL 

LIAISON OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, 

INCIDENTIAL, CONSEQUENTIALS, SPECIAL OR EXEMPLARY DAMAGES 

WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR 

LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF 

BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT 

OF THE USE OR INABILITY TO USE THE SOFTWARE OR THE 

PERFORMANCE OR FAILURE TO PERFORM SUPPORT SERVICES, EVEN 

IF LIAISON OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE 

POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING ANY 

FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. 

BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR 

LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTIAL 

DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. 

 

TERM. Upon payment of the annual maintenance and support services  fee, this document certifies that the registered user identified on the  accompanying invoice is entitled to receive the maintenance and  support services described herein for the one (1) year period specified  on the invoice (the “Term”). The Term may be renewed for successive  one (1) year periods. The registered user will be invoiced for annual  renewals, and the Term will be appropriately renewed, unless Liaison  receives written notification canceling the subscription 60 days prior  to the expiration date of the Term. If the registered user does not pay  such invoice by the expiration of the then‐current Term, the registered  user shall not be entitled to receive the maintenance described herein, 

  and the Term will not be renewed or extended. 

CONDITIONS. If you allow your maintenance and support plan to  expire and desire to resume maintenance and support, you must pay a  reinstatement fee for lapsed coverage of software maintenance and  support in accordance with Liaison’s then current maintenance and  support program. If you cancel your subscription to maintenance and  support at any time during the Term of your subscription period, no  refund, pro‐rated or otherwise, will be given. This agreement is for one  plan, per registered user, for all registered modules.  If the use of a  specific licensed and registered module is discontinued, a letter must  be sent on a company letterhead prior to the commencement of the  next subscription period (signed by an officer of the company)  indicating that the company is no longer using the module.  

 

LAW. If you acquired the Software in the United States, this Agreement 

  is governed by the laws of the State of California.  If you acquired this  product in Australia, New Zealand, Canada, Hong Kong, Singapore or  the United Kingdom, this agreement is governed by the laws of New 

South Wales, New Zealand, the province of Ontario, Hong Kong, 

Singapore or England, respectively. 

Should you have any questions about this 

Agreement, you may contact Liaison 

Software Corporation by writing to 2021 E. 

4 th

 Street, Suite 218, Santa Ana, CA 92705 ii

 

Liaison Messenger

® installation guide

TABLE OF CONTENTS 

TECHNICAL SUPPORT:........................................................................................................................ 3

 

QUICK INSTALLATION SUMMARY ................................................................................................. 4

 

1 – INSTALLATION INSTRUCTIONS ................................................................................................. 6

 

S

UPPORTED

P

RODUCTS AND

V

ERSIONS

..................................................................................................... 7

 

Microsoft Business Solutions ............................................................................................................................... 7

 

Sage Software, Inc ............................................................................................................................................... 7

 

Database Platforms ............................................................................................................................................. 7

 

SQL/Pervasive end-user licenses ......................................................................................................................... 7

 

P

RE

-

INSTALLATION REQUIREMENTS

.......................................................................................................... 8

 

1 - Connect to the accounting system's database - Server ................................................................................... 8

 

2 - Indentify and Add Printers............................................................................................................................ 11

 

3 - Install E-Mail Clients ................................................................................................................................... 12

 

4 - Install Faxing Software................................................................................................................................. 13

 

2 - LIAISON MESSENGER SERVER INSTALLATION ................................................................. 14

 

1 - Install Messenger server from CD ................................................................................................................ 14

 

2 - Start Messenger Server ................................................................................................................................. 14

 

3 - Select a Default Destination printer ............................................................................................................. 16

 

4 - Enable a Company Dataset .......................................................................................................................... 16

 

5 - Initial Test of Liaison Messenger ................................................................................................................. 18

 

 

 

3 - LIAISON MESSENGER CLIENT INSTALLATION .................................................................. 21

 

1 - Security and Folder Privileges ..................................................................................................................... 21

 

2 - Connect to the accounting system's database - Client .................................................................................. 21

 

3 - Install Liaison Messenger CD ...................................................................................................................... 21

 

4 - Starting Messenger Client ............................................................................................................................ 22

 

2

 

 

Liaison Messenger

® installation guide

 TECHNICAL SUPPORT: 

Support phone number: (714) 543-9877 x208

Support e-mail: [email protected]

Website: www.liaisonsc.com

Please see the Help menu on Messenger Server for the Configuration and User manuals

 

 

 

3

 

Liaison Messenger

® installation guide

QUICK INSTALLATION SUMMARY 

P lease read the Installation Instructions chapter in its entirety before installing Liaison Messenger for the first time.

This Quick Installation Summary is meant to be a guideline, not the complete step-by-step instructions that you will find in the following chapters.

 

 

IMPORTANT 

YOU SHOULD NOT CONFIGURE THE LIAISON MESSENGER SERVER FROM ANY 

WORKSTATION OTHER THAN THE PC / SERVER THAT WILL BE RUNNING 

MESSENGER SERVER.  

Take note that these steps may require the PC to be rebooted a couple of times until the installation is complete. This may cause interruption of logged in users if this PC is actively being used as a shared network resource.

1. Select a good, reliable, and properly functioning PC running Windows 2000/2008, XP, or

Vista and use that as the Dedicated Messenger Server.

2. Establish access to the accounting system's database(s)

3. If the accounting database is Microsoft SQL Server or ProvideX, create an ODBC connection DSN for the System Database and at least one Company Database,

4. If the system uses Pervasive.SQL ensure the Pervasive Client is installed and working

5. Identify, Map, and Test all targeted printers within the Windows Printers folder.

6. Install/Configure e-mail client (i.e. Outlook/Outlook Express) with the valid POP3 and SMTP domain address and login settings. Send and verify receipt of a test e-mail before proceeding.

7. Install Faxing Software Client (if applicable). Test modem and faxing before proceeding.

8. Make sure the above steps are complete before beginning the Messenger installation.

9. Insert Liaison Messenger disc into CD drive x: and run x:\SETUP.EXE

10. Select the Messenger Server Installation option.

11. Install the new version into the desired Messenger location.

12. When complete allow the PC to reboot (if prompted).

4

 

Liaison Messenger

® installation guide

13. Launch Liaison Messenger Server from the Liaison Software folder, found on the Programs menu in Windows, and allow the Update Procedure to complete.

14. When finished, you will be prompted to re-start the Messenger Server program.

15. Configure Messenger Server by running System Configuration

16. Enable Company Datasets in Company Configuration

17. Install additional Messenger Clients

Please see the Help menu on Liaison Messenger Server for the Configuration and User manuals

 

 

5

 

 

 

Liaison Messenger

® installation guide

1 – INSTALLATION instructions

I f you don't read anything else, read this. It is short, concise, and will get you installed as quickly as possible.

To start; the Liaison Messenger application is made up of 2 components. The 1st (main) piece is called the Messenger Server. Even though the name may state the word; server, this component does NOT have to be installed or run on your company's server or "a server". It does not need specialized hardware to operate, either. It is just how we refer to this component since it performs centralized processing.

The 2nd piece of Liaison Messenger is called the Messenger Client. Its job is simply to place processing requests from the user's workstation(s) into the Liaison Messenger processing queue that is monitored and processed by Messenger Server.

Liaison Messenger Server and any Messenger Client component will run on a standard PC running even a Windows Home version. Of course, Liaison Messenger will run on the higher-end operating systems and machines/PCs including those of 64-bit architecture.

PLEASE NOTE, THAT SINCE MESSENGER SERVER NEEDS TO INTERACT WITH 

VARIOUS E‐MAIL CLIENTS AND FAX SYSTEMS TO ELECTRONICALLY 

DISTRIBUTE FORMS, IT CANNOT BE INSTALLED OR CONFIGURED TO RUN AS A 

WINDOWS SERVICE DUE TO THE FACT THESE OTHER APPLICATIONS CAN 

NOT RUN AS A WINDOWS SERVICE. 

Now, since Messenger Server will be performing 95% of the printing, e-mailing, faxing, archiving etc we recommend having the Server component run from a dedicated PC; but, it is not required. If you need to have the PC locked-down, we suggest using a Screen Saver password. Also, it is a good idea to place the Messenger Server icon shortcut into the Startup folder of Windows on this machine. This way it will auto-start should the PC needed to be re-started.

6

 

 

 

Liaison Messenger

® installation guide

To begin, please verify that your system meets the criteria listed under Supported Products and

Version section.

SUPPORTED PRODUCTS AND VERSIONS 

MICROSOFT BUSINESS SOLUTIONS 

Microsoft Dynamics GP v6.0 through current release

MBS Small Business Financials 7.0 thru current release

Microsoft Dynamics SL v4.5 through current release

SAGE SOFTWARE, INC 

Platinum for Windows v4.6 through current release

Platinum for DOS v4.6 through current release

BatchMasterPFW v4.7 through current release

MAS 90/200 v4.0 through current release

DATABASE PLATFORMS 

Pervasive.SQL all versions

Microsoft SQL Server all versions

ProvideX all versions

SQL/PERVASIVE END‐USER LICENSES 

Liaison Software Corporation does not provide, nor include, any runtime license, client licenses or runtime files for Pervasive.SQL/Btrieve, Microsoft SQL Server, Microsoft Outlook, etc. It is assumed since above mentioned products require the aforementioned; everyone should have the respective components needed to run Liaison Messenger.

PERFORM THE FOLLOWING PRE‐INSTALLATION REQUIREMENTS BEFORE 

INSTALLING  LIAISON MESSENGER FROM THE CD 

7

 

Liaison Messenger

® installation guide

PRE‐INSTALLATION REQUIREMENTS 

1 ‐ CONNECT TO THE ACCOUNTING SYSTEM'S DATABASE ‐ SERVER 

PERVASIVE.SQL 

If you are running PFW by Sage Software, you're reading the proper section. Now, you must install the Pervasive.SQL client/workstation files on the machine that will be hosting the Messenger

Server.

 

 

Starting with v9.x of Pervasive, the Client drivers could not be installed where the Server engine was running. Therefore, Messenger Server will have to reside on a separate machine from where the Pervasive Server is running.

Liaison Messenger uses Pervasive.SQL natively so an ODBC connection is not used nor needed by Liaison Messenger to access/update data from PFW or BatchMaster installations.

MICROSOFT SQL SERVER 

For users of Microsoft Dynamics GP or Microsoft Dynamics SL, you must create at least 2 DSNs

(an ODBC connection) on the machine that will be running Messenger Server as well as every workstation that will be running Messenger Client.

To start, you will need to create a DSN for the system database as well as the company database(s). The main system database should be created first:

 Dynamics GP - it's usually called DYNAMICS

 Dynamics SL - the name can vary; but, usually contains the word "system" within.

To do this, choose the Data

Sources icon from the Window's

Control Panel. It may be under the

Administrative Tools grouping.

When selected, you will be shown a screen like the one on the right.

Please keep in mind this manual's pictures are from Windows Vista, so the dialog boxes might be slightly different but the basic principle is the same on all versions of Windows.

We recommend creating new unique DSNs for Messenger Installs. Keep the name simple and descriptive.

8

 

 

 

Liaison Messenger

® installation guide

Here we created one called DYNAMICS10. We created this by choosing the Add... button. If you are prompted for the driver, make sure you choose the SQL Server driver.

Liaison Messenger works with all version of Microsoft SQL Server through SQL 2008. Always make sure you have all the recommended service packs installed for SQL server and that all workstations are running the same version.

After you select SQL Server, choose the

Finish button. And no, you're really not

finished... :(

The next step will require us to give the DSN a name, description, and most importantly we'll need to know and specify the SQL Server name. In the following example, I named it

DYNAMICS10, gave it a brief (optional) description and choose the name of the SQL

Server engine where my system data resides.

You can Name the DSN connection anything that will help you identify it such as

MESSDYN10 or MESSENGERSYS etc. Just remember to keep it short and simple.

KEEP IN MIND, YOU WILL ALSO NEED TO CREATE THE EXACT SAME DSN NAMES 

ON EACH WORKSTATION THAT WILL BE RUNNING MESSENGER CLIENT, TOO.  SO 

YOU'LL DEFINITELY WANT TO KEEP THE DSN NAMES SIMPLE. 

If you do not know where the data is or what the Server's name is or what the password is (you'll need to know this next), then you will probably need to contact your IT person or Database Administrator.

Now, if you've already entered a

DSN name and the Server then click the Next button.

Now, it'll get a bit more technical and intimate, specify your Login method and credentials if needed and choose the Next button.

Since user names and passwords should be unique and secret, you will have to know the needed information.

9

 

Liaison Messenger

® installation guide

If you can proceed to this screen after choosing that Next button, you're doing good. As the DSN

Configuration has then successfully validated the information you've just entered.

 

 

THIS IS THE MOST IMPORTANT PART OF CREATING THE DSN FOR 

MESSENGER'S PURPOSE. IT ALSO GENERATES THE MOST CALLS IN TO OUR 

TECH SUPPORT DEPARTMENT. 

YOU MUST SPECIFY THE "DEFAULT DATABASE" FOR EACH DSN 

CONNECTION. 

 IF YOU LEAVE IT UNCHECKED AND/OR SPECIFY THE INCORRECT 

DATABASE, YOU WILL RECEIVE ERRORS AND BECOME A TECH SUPPORT 

STATISTIC. 

Again, in the above example we are creating the DSN for the "system" database. For Dynamics

GP, this is generally DYNAMICS, which is why we've selected it here. If you are creating the system DSN for Dynamics SL, then choose that respective database.

The rest of the settings are based upon your specific configuration, but take the defaults if you are unsure. Select the Next button and proceed to the following screen.

There are no settings on this screen that are specific to Liaison Messenger, so unless you need to change anything for your specific purpose or system requirement, accept the defaults. When done, you can select the Finish button.

10

 

Liaison Messenger

® installation guide

The final steps in creating the DSN is the verification step that everything is A-OK.

After pressing the Finish button you will be brought to a screen where you can verify the DSN setup and you can Test the

Connection.

The following screens show the last two steps for review of your settings. The most important step is to choose the Test Data

Source... If everything is correct you should be looking at a "TESTS COMPLETED

SUCCESSFULLY" screen.

 

 

Now, you will need to create a DSN for the

Database(s) that contain the individual Company

Data. Repeat the exact same steps as you did creating the system database.

Remember to specify the correct "default database"

for the respective company database on these DSNs.

You may wish to do this first for the included test databases of the accounting system: (i.e., TWO for Dynamics GP; The World Online or Fabrikam) or the SLDemoApp60 test company in Dynamics

SL.

One final reminder, you will need to create the exact same name DSN connections on each workstation that will be running Messenger Client.

2 ‐ INDENTIFY AND ADD PRINTERS 

Add, connect, and print a Test Page to all printers that will be accessed via Liaison Messenger

Server. You must have at least 1 printer in the Printers section of the Control Panel before installing

Liaison Messenger Server.

11

 

Liaison Messenger

® installation guide

Printers can be mapped and referenced by: IP addresses, UNC naming paths, Hardware ID names, or by its respective LPT or COM port.

A heads up for known problems are certain printers drivers that are built around PCL 6. We recommend for forms processing to use an equivalent PCL5 or later for the printer driver that will be accessed by Messenger Server.

Please note that you can still have the PCL6 driver for that printer; installed and present on the machine running Messenger Server and use it for other applications or users. Just for mapping purposes in Messenger Server have an equivalent PCL5 driver installed for that printer, as well.

After you've created printer references for the desired local and network printers, perform a "Print

Test Page" on each printer reference and verify that you've received output.

 

 

3 ‐ INSTALL E‐MAIL CLIENTS 

Liaison Messenger’s e-mailing capabilities were designed to automatically generate the ply of the form as a file and attach the file as an auto-addressed e-mail message. Messenger creates the files in one of the following formats; Text, PCL, or the most popular, the recommended PDF (Adobe

Acrobat) format.

We have licensed Amyuni’s Technologies PDF Converter. It is automatically installed for embedded distribution which eliminates the need to purchase Adobe Acrobat for PDF creation.

In order for Liaison Messenger to e-mail documents, it requires an email client to be installed and present on the machine running Messenger Server. Liaison Messenger complies with the current

MAPI standards. Liaison does not have any native internal SMTP capabilities; however; any true

MAPI compliant e-mail client can be used. These clients include all versions of: Microsoft Outlook,

Outlook Express, Eudora, and Novell's GroupWise. Outlook Express is free and comes with all versions of Windows.

One primary consideration when choosing an e-mail client is whether or not Microsoft Fax

Transport will be used. Microsoft Fax Transport is the built-in faxing capabilities found in some

Windows Operating Systems. The fax transport takes PDF files which are attached to Microsoft

Outlook's e-mails, renders them into TIF files and faxes them to the phone number specified in the

"FAX:contactname@7145430887" recipient (e-mail) address field.

Microsoft Fax Transport requires that the e-mail client be Microsoft Outlook (only). Outlook Express is not compatible with the fax transport protocol. Also, in order for the Fax Transport engine to render the PDF files, Adobe Reader 6.0 or later must be used. The fax rendering engine does not work with Adobe Reader 7.0 or greater. Take note that we are referring only to the Adobe Reader.

The full-blown Adobe Acrobat system is NOT required for Liaison Messenger as we have included a built-in PDF creator from Amyuni Technologies.

Any e-mail client on the PC that will be running the Messenger Server will need to be configured to support the industry standard Internet E-mail Protocol – SMTP (for outbound e-mail). You will most likely need to know one or all of the following bits of information but primarily; the POP3 and, SMTP syntax. and any account and password information from your host or ISP. If you have an Exchange

12

 

 

 

Liaison Messenger

® installation guide

Server or Domino server, you may need additional information which your system administrator should be able to provide.

If you do not plan on emailing and/or faxing or plan on implementing that later, you may proceed to

Installing Messenger Server from the CD. Otherwise, now would be the proper time to configure your e-mail client on this machine. Once you are able to successfully send and receive an email you're ready establish your faxing method, if any.

4 ‐ INSTALL FAXING SOFTWARE 

In order for Messenger to transmit forms via facsimile, an external Fax Manager is required. We currently support a number of different solutions:

Microsoft Fax Transport in conjunction with Microsoft Outlook

2000 or newer.

Fax Servers that support Microsoft Outlook’s add-in capabilities like GFI Faxmaker, Zetafax, and Faxpress, are a few of the fax systems we support.

Internet faxing subscriptions like: efax.com and MyFax.com are excellent choices and very cost effective. Plus you do not need an extra or dedicated phone line for faxing. Not to mention no long distance or toll charges or any hardware for that matter.

Symantec’s WinFax PRO is no longer available or supported by

Symantec; however, we still have WinFax support built-in to

Liaison Messenger.

Anyway, if you plan on faxing, make sure you can actually send a fax from the PC (which will be hosting Liaison Messenger Server) manually by testing this first (without the document coming from

Messenger). If you can successfully send a generic fax to a fax number through your email/fax client manually, it will confirm that the modem (if any), phone line and software is functional.

More often than not, our support department is contacted because the document is not faxing only to find out later a modem was not even installed or that a phone line is not active or plugged-in.

Believe it or not this happens frequently.

So please test a generic document from the Fax Client first... before including Messenger Server into the equation. If you can successfully fax a Word or Excel document, you can be assured that the fax client, fax server, phone line, local dialing rules, and modem (if required) is functioning properly.

13

 

Liaison Messenger

® installation guide

2 ‐ LIAISON MESSENGER SERVER INSTALLATION 

1 ‐ INSTALL MESSENGER SERVER FROM CD 

Once you have completed the above pre-requisites, you can begin installing the software from the

CD or downloaded EXE (executable). Please be aware that the machine you install Messenger

Server onto, may have to be re-booted after the setup.exe has completed.

YOU SHOULD BE LOGGED IN  AS THE USER ID THAT YOU PLAN ON RUNNING 

MESSENGER SERVER WITH. IT SHOULD HAVE SUFFICIENT RIGHTS LIKE 

THOSE OF THE WINDOWS ADMINISTRATOR 

Insert the CD and run the setup.exe file.

2. When prompted for the destination directory, select the existing x:\MESSENGER directory on your network.

3. After the setup program finishes, you may be forced to reboot the workstation. Don’t forget to remove the CD before leaving the machine.

4. Assign full access and usage rights/privileges; Read, Write, Delete, etc on the newly created

Messenger folder for the users or user groups that will be using Liaison Messenger.

5. We recommend assigning and mapping a common network drive letter to this folder (i.e.

S:\MESSENGER drive folder) and use this same drive letter mapping for the Liaison

Messenger Clients. Yes, Liaison Messenger does support UNC naming conventions, however, you will find as we begin installing the Messenger Clients, implementing archiving and embedding company logos for the forms (and for future maintenance purposes), a drive letter mapping will make your job much easier.

6. Finally, we recommend creating a 2nd shortcut for the Liaison Messenger Server icon in the

Liaison Software folder and placing that shortcut in the Startup folder of the machine. This way Messenger Server will auto-launch whenever the system re-starts.

 

 

2 ‐ START MESSENGER SERVER 

Once you have installed Liaison Messenger from the CD allow the PC to be rebooted if prompted. If your system does not request to be rebooted, it is because you had the required distributable runtime files already installed and a reboot was not required.

Windows makes this determination; so do not be alarmed if you were not required to restart the PC.

14

 

Liaison Messenger

® installation guide

One of the functions of the setup.exe installation program is to create a Liaison Software folder on the Start menu. There will be a couple user options, you want to select the one titled: Liaison

Messenger Server.

Every time you run the installation program or after you receive, download, and install an update,

Liaison Messenger Server will perform an Update Procedure once. This feature will always ensure your system tables, databases, and service packs are up-to-date with the specific Liaison

Messenger Server version you are running.

Once it is finished, you will be prompted to Exit Liaison Messenger Server and restart Messenger.

This does not imply rebooting. Simply restart the Liaison Messenger Server application.

On first time, previously un-configured, installations you will be shown the System Configuration screen which appears like the provided screenshot.

 

 

IF THE SCREEN DOES NOT AUTOMATICALLY APPEAR, YOU CAN ACCESS IT FROM 

THE FILE MENU BY CHOOSING SYSTEM CONFIGURATION OR YOU CAN SELECT IT 

FROM THE SIDE TOOL BAR BY SELECTING THE CONFIG ICON. 

 

 

If you are running PFW,  this  1st  step  is  not  needed  and  the 

Database  tab  will  be  dimmed out.

For users of all other systems, choose the

Database tab as shown and select the

Database Type, version of the accounting system, the (system) DSN you created and the

User ID and password if applicable.

To verify the ODBC connection, select the Test ODBC Connection button it may also appear as a

green check icon on some system.

15

 

Liaison Messenger

® installation guide

If you receive an error, re-check the ODBC connection you created or the user ID and password.

Do not continue until you receive a successful test notification.

3 ‐ SELECT A DEFAULT DESTINATION PRINTER 

Now you'll want to assign a default printer to each of the different form types displayed on the

Messenger tab. We recommend you choose a printer that is local and easily accessible for you during the testing. You can always change the default printers later.

If you are new to Liaison

Messenger its best to keep the rest of the options at their default during the initial installation and configuration of

Messenger Server. This includes keeping the Intervals setting at 0 and its related

Increment setting to Off and any of the Update .... Status

Code check boxes.

Depending  on  the  accounting  system  you  are  installing 

Messenger  for,  some  of  the  title  headings  and  verbiage  may  vary  from the screen on the right.  

When you are done, choose the Save button. If you are asked 'Do you want to start the Messenger services, (Green Light)?' answer yes.

If you are looking at a screen with a

Green stop-and-go light, like the one in the picture; you are doing great and it is now time to connect a company dataset.

 

 

4 ‐ ENABLE A COMPANY DATASET 

The next step, but most important, is which companies you want to automate. By default, all companies you’ve established in your Accounting

System have not been enabled. To practice, we strongly recommend enabling one of the accounting system's test databases first. You can then properly setup, configure, modify, and test Messenger before going live.

16

 

 

 

Liaison Messenger

® installation guide

Liaison Messenger has a useful built-in utility, Clone Company Properties, that will allow you to clone all your forms, business rules, form routing, and ply configurations from your test company to the actual company when you are ready to go live. This way you can experiment, test, and perfect your workflow rules in a test environment without affecting the live company and without re-entering all of your settings.

From the File menu, choose Select Company

Dataset. This will display a listing of the company's that have been established in your accounting system.

Again, if this is the first time you have installed

Liaison Messenger or are planning on testing first, we strongly recommend choosing a test company.

In Dynamics GP that would most likely be

TWO, aka The World

Online or Fabrikam, Inc. In Dynamics SL; Contoso, and PFW has a number of them and which some of us old-timers just refer to as GLSDEM, PREMGL, etc...

You may also have a copy of the live company which you use for testing purposes and that is fine as well. Either way you need to highlight the company and choose the Edit button to bring up the

Company Configuration screen.

Before you do anything else, place a check box in the

Enabled for Messenger,

SalesSonar or EFT checkbox.

If  you  are  running  PFW,  choose  the  E‐mail/PSQL  tab  and  verify  the network paths.  

You need to ensure that this

PC and the logged in user(s) have rights to these paths. If everything looks OK, choose the Save button. If you are asked 'Do you want to start the

Messenger services, (Green

Light)?' answer yes and

17

 

Liaison Messenger

® installation guide

proceed to the next section called; Intial Test of Liaison Messenger.

If you are running Dynamics GP, Dynamics SL, or MAS 90/200, choose the SQL Server tab. Like we did on the System Configuration screen under the Database tab, you will need to choose the

ODBC (DSN) connection that you created specifically for this company (do not choose the DSN for the System Database again). You will need to enter the User ID and password. Once you have entered the appropriate information, choose the green check icon (or Test button) to test the ODBC connection to the company dataset.

If the DSN was properly created and referenced,

Liaison Messenger will be popping up a series of message boxes telling you that 'This opened successfully and that opened successfully, etc.'

These message boxes have a lone OK button and you should just click them to cycle through the prompts.

When you are done, choose the Save button. If you are asked 'Do you want to start the Messenger services, (Green

Light)?' answer yes.

 

 

5 ‐ INITIAL TEST OF LIAISON MESSENGER SERVER 

If you are now back to a Green Light and your screen resembles the picture, you are in the home stretch and we now need to test and verify either; a) the data paths for PFW or b) if you're running

Dynamics, the ODBC connections that will access the data for the various forms.

During this test, we will be selecting each of the form types that

Messenger supports (or just those that you've purchased). We will be testing this by previewing each of the forms.

This will ensure that all required tables are accessible, any custom and/or 3rd party tables are located

18

 

 

 

Liaison Messenger

® installation guide

and accessible, and that Liaison Messenger has enough memory and resources to create each form type on this machine.

Specifically, what Messenger Server does is select the first 100 records (or so) in each of the header and detail tables for each respective form. It executes all Pervasive.SQL or Microsoft SQL views for that form type, and when finished, will display the queried data of the form in the built-in

Report Writer's preview window.

If you get a message that no data exists, or the preview window just flashes briefly and then disappears, it may be that there isn't complete data to preview this form type's date.

If you are testing this on a backup copy of live company data, you may notice that previewed data may be old or dated. That is because Messenger is simply grabbing the 1st 100 or so records in the header and detail tables and typically those would be the oldest records. It does not mean that the

ODBC connection for Dynamics is wrong or that the Pervasive.SQL paths are incorrect.

Anyway, starting with the AR Docs there will be 4 plies. One Customer

Copy, Accounting Copy, File Copy, and Copy ply. Since these are defaults for a new installation, there are no Routing selections and the Template is the same for each ply.

For our immediate purpose we will only be choosing the

Preview button. Once chosen, Messenger

Server will begin selecting the data from the AR

Document's tables.

When done, you may then be prompted to

'Test just the current ply' and answer Yes.

If you answer No it will display a Preview window for each ply of the form.

Feel free to maximize the Preview window to display the form in full screen mode.

19

 

Liaison Messenger

® installation guide

Now, a floating tool bar will appear with Next, Previous, First, Last buttons to skip thru the selected forms as well as a Close and Printer icon. When you are done, choose the Close button or the

Window's X. Repeat these steps for each of the form types: SOP Docs, SOP Inv, etc...

Please be aware that depending on the accounting system, these column and tab headings may vary from the examples here in the manual. We try to use the native jargon for each system as much as possible.

Once you have finished testing the various form types, you are now finished with the basic

Messenger Server installation and should proceed to the Messenger Client installations. Once that is finished, the real fun starts with configuring Liaison Messenger with all the bells and whistles.

FOR THOSE INSTRUCTIONS, PLEASE REFER TO THE HELP MENU FROM 

WITHIN LIAISON MESSENGER SERVER OR MESSENGER CLIENT WHERE YOU 

CAN VIEW OR PRINT THE USER GUIDE.  

 

 

20

 

 

 

Liaison Messenger

® installation guide

3 ‐ LIAISON MESSENGER CLIENT INSTALLATION 

Every user who will be printing Messenger forms or maintaining the form's preferences for customer, vendor, or internal recipients will need to have Messenger Client installed. What the

Liaison Messenger Client setup program does is:

Install the needed (Visual Studio) runtime files if they don't already exist.

Creates a shortcut to the Messenger Client executable (Liamcli.exe) on the network.

Create a Liaison Software folder in the Windows Start menu.

Therefore, ensuring each user has proper network rights and drive mappings already configured is required before running the Installation CD. As we discussed earlier during the Server Installation, even though Messenger fully supports UNC conventions, we still recommend assigning and mapping a common network drive letter to the Messenger folder (i.e. S:\MESSENGER drive folder)

.

1 ‐ SECURITY AND FOLDER PRIVILEGES 

Each user should be granted sufficient rights to Access, Create, Edit, Delete, Search, and Create folders in the main networked Messenger folder as well as any supporting folders that may contain

BMP/JPG logo files or archived output files.

2 ‐ CONNECT TO THE ACCOUNTING SYSTEM'S DATABASE ‐ CLIENT 

At this time you should create the required ODBC connections that were also discussed earlier in this chapter. Once again, these ODBC connections must be named exactly the same as those assigned to Messenger Server. You will have to do this for each workstation that runs Messenger

Client. If you have any questions on how to do this, refer back to:

1 - Connect to the accounting system's database - Server.

3 ‐ INSTALL LIAISON MESSENGER CD 

Once you have configured the user's security and created the ODBC connections, you are ready to install the

Messenger Client.

Insert the Liaison Messenger CD and run Setup.Exe, if it does not automatically start.

21

 

 

 

Liaison Messenger

® installation guide

choose the OK button.

2. When prompted for the destination directory, select the existing S:\MESSENGER directory on your network. Messenger Client must be pointed to the main S:\MESSENGER as this is where the Client executable (Liamclie.Exe) already resides.

3. After the setup program finishes, you may be forced to reboot the workstation. Don’t forget to remove the CD before leaving the machine.

4. Proceed to the next section called: Starting Messenger Client

5. Repeat these steps for every workstation that requires Messenger Client access.

4 ‐ STARTING MESSENGER CLIENT 

From the new Liaison Software folder found under the Start\Programs menu on each workstation you installed Messenger Client; choose the Messenger Client program to launch the component.

You will be prompted to select an enabled company dataset which you should do. If you are running Dynamics GP/SL and get any errors especially those Error Codes in the 1500s like 1526.

Check and recheck the ODBC drivers you created on this machine and also any user id and passwords.

In Messenger Client, for each accessible form, you will find most of the same options as you would in your linked accounting system. This will be explained later under the section reserved for Printing

Forms and we strongly recommend studying that chapter.

As far as client configurations, there are no configuration or setup options for Messenger Client. It reads the defaults that were established during the Messenger Server installation.

For the rest of the instructions including Configuring Messenger, please refer to the Help menu from

Liaison Messenger Server or Messenger Client where you can view or print the User Guide.

For instructions on moving an existing installation from one Liaison Messenger Server machine to another, please see the User Guide as well.

ALL MANUALS, INCLUDING DATABASE FIELD REFERFENCES, ARE STORED IN 

PDF FORMAT AND ARE LOCATED UNDER THE 

X:\<MESSENGERSERVER>\LMCSETUP\DOCO FOLDER 

22