Installation Guide Web PO Requisition for Sage 200

Transcription

1 Installation Guide Web PO Requisition for Sage 200 Create Purchase Requisitions for Sage 200 via a web interface Multiple concurrent users entering requisitions in real time Submit requisitions with multiple authorisation rules View and print existing purchase requisitions Check live stock and supplier information from Sage 200 remotely Receive stock against existing purchase orders via the web Powerful account/stock search based on multiple fields Report on purchase requisitions from within Sage 200 Works on multi-company installations Can be designed to reflect customers own branding

2 P a g e 1 Table of Contents System Requirements...2 Installing Web PO Requisition for Sage Installation Overview...2 Web PO Requisition for Sage 200 Database Install...3 Optional Web User Creation (recommended)...3 IIS Folder Setup...3 IIS Setup...4 Further IIS Setup for Sage Onwards...4 Application Pool Identity Troubleshooting...6 Web Configuration...7 Install Eureka Addons Web PO Requisition Pack...9 Sage 200 User Configuration Licencing Web PO Requisition for Sage Logging In Setting up New Users Contact Us... 17

3 P a g e 2 System Requirements Sage /Sage /Sage R2 IIS 6.0 or IIS 7.0.Net 4.0 SQL 2005 or above IE 8 and 9, Firefox or Chrome browser Server specification in line with Sage 200 requirements Installing Web PO Requisition for Sage 200 The user will be provided with the following installation files S200WebEntry.bak a SQL backup can be restored on SQL 2005 and S200WebEntry A folder containing the website files S200WebService A folder containing the web service files Eureka Addons Web Requisition.sdbx An Addon file containing the SQL scripts required to create the Web PO Requisition tables within the Sage 200 database. Installation Overview The Web PO Requisition for Sage 200 module is broken into two parts: The web service which deals with all connections to and from Sage 200. It uses the remote users to login to Sage 200 and communicate the data using WCF. The web entry application then connects to the WCF service which allows the user to enter data through a website. The diagram below shows an overview of the system setup. IIS 6/7 Sage 200 Web Service Web Entry Browser Web SQL DB

4 P a g e 3 The installation below is recommended installation method based on a SQL 2008 server and IIS 7.0. This may vary slightly depending on the system setup. Web PO Requisition for Sage 200 Database Install The web based PO Requisition system uses a Microsoft SQL 2005 and above database which holds the user data and roles. The S200WebEntry.bak database file should be restored into SQL server. The following process is required. 1. Open SQL Management Studio and login at the provided prompt. 2. Right click on databases and select Restore Database 3. This will open the restore database prompt enter a database name (This will be required later), select the From Device option and browse to the S200WebEntry.bak file provided. 4. Select Ok once complete and this will restore the database. Optional Web User Creation (recommended) 5. Create a web user in the SQL database with access only to the web database. Under Security right click on Logins and Create New Login. 6. Enter a login name, select SQL server authentication and provide a password. Please remove the enforce password expiration setting. 7. Click on User Mappings at the left and from this Map only the Web PO database as a db_datareader, db_datawriter and db_owner. IIS Folder Setup The Web Service and Web Entry require folders to be setup which will be used in IIS as virtual directories. It is recommended these are installed in the inetpub folder under for example C:\inetpub\wwwroot\ The folders recommended are 1. C:\inetpub\wwwroot\S200WebEntry\ 2. C:\inetpub\wwwroot\S200WebService\ All files within the S200WebEntry folder should be copied into folder 1. All files within the S200WebService folder should be copied into folder 2. Within the S200WebService folder there is a sub folder called App_Data which contains the Web PO Requisition report layout file Requisition (Single).layout. This file can be overwritten with the end users Requisition layout file from Sage 200 if they want to use this for printing Requisitions from the Web PO Requisition module.

5 P a g e 4 IIS Setup The web service must be installed on the same server as a Sage 200 client and it is recommended that this is installed on the same server as the Sage 200 IIS. The web entry can be installed on any IIS instance. 1. To access IIS please go to Start -> Run (Search in windows 7) and type InetMgr. This will launch the Internet Information Services 7.0 Console. 2. Expand the current server instance and click on Application Pools. 3. Right click on Application Pools and select Add Application Pool and create a new pool. 4. Right click on this new pool instance and select Advance Settings The following non default settings should be selected a..net Framework Version v4.0 b. Enable 32-bit Applications true c. Identity For 2011 you can select ApplicationPoolIdentity (Optional), for 2013 onwards this must be a user that has access to Sage 200. d. Managed Pipeline Mode Integrated 5. Create two web applications one for the service and one for the web entry. You must right click on this and select Add Application the user is then prompted for the Alias and physic path. The settings recommended are as follows : Alias S200WebEntry Alias S200WebService Physical Directory C:\inetpub\wwwroot\S200WebEntry\ Physical Directory C:\inetpub\wwwroot\S200WebService\ Please note that the Alias is what the end user will see. In the above examples the URL would be for the end user. Further IIS Setup for Sage Onwards A secure connection will be required which requires an https site binding. This type of binding needs a certificate which should ideally be obtained from a trusted certificate publishing authority but can be a Self-Signed one, this is up to your own discretion.

6 P a g e 5 Once you have a certificate the https binding can be set up, in the example below we are using the Default Web Site. Select the type as https and enter an unused Port number and select the security certificate you wish to use, in our example we are using a self-signed certificate named Eureka. The Web Service Application must have Windows Authentication enabled. Please see the steps below to make sure this is enabled.

7 P a g e 6 Application Pool Identity Troubleshooting The application identity user is required to be changed to allow for the ability to print off PDF reports from the report designer. If this user does not have correct permissions on the Sage server to access the Sage server folder it will not function. If this is the case it is difficult to pinpoint if it is the application pool user permissions or issue with the report. To test this if you amend the application pool to use a Custom Account and enter a server/domain administrator user this will prove it is user permission settings on the server.

8 P a g e 7 Web Configuration The final stage to setting up the sites is to configure the web.config file. This is found in the S200WebEntry folder. In the above instance this would be in: C:\inetpub\wwwroot\S200WebEntry\Web.config The web config contains various settings timeout that can be changed and follow standard web configuration rules but there are two in particular that are required for install. This should be opened in notepad and amended as follows. 1. The SQL Database Location Find the following line <add name="applicationservices" connectionstring="data Source=xxxxx;Initial Catalog=xxxxx;Persist Security Info=True;User ID=xxxxx;Password=xxxxx" providername="system.data.sqlclient" /> The above line should be amended so the details are as follows Data Source The SQL server instance name Catalogue The Database name as you named it earlier User ID The SQL User as created Password The SQL User password In our example our file may look as follows <add name="applicationservices" connectionstring="data Source=eurekaserver;Initial Catalog=S200WebEntry;Persist Security Info=True;User ID=WebReq;Password=Pass123" providername="system.data.sqlclient" /> 2. The Web Service Location For 2011: Find the following line near the end of the file <endpoint address=" binding="wshttpbinding" bindingconfiguration="wshttpbinding_ieurekawebservice" contract="s200webservice.ieurekawebservice" name="wshttpbinding_ieurekawebservice"> The address should be replaced with the web service location and end with EurekaWebService.svc from our example above this would be

9 P a g e 8 <endpoint address=" binding="wshttpbinding" bindingconfiguration="wshttpbinding_ieurekawebservice" contract="s200webservice.ieurekawebservice" name="wshttpbinding_ieurekawebservice"> For 2013: <endpoint address=" binding="basichttpbinding" bindingconfiguration="basichttpbinding_ieurekawebservice" contract="s200webservice.ieurekawebservice" name="basichttpbinding_eurekawebservice" /> The address should be replaced with the web service https address and end with EurekaWebService.svc from our example above this would be: <endpoint address=" binding="basichttpbinding" bindingconfiguration="basichttpbinding_ieurekawebservice" contract="s200webservice.ieurekawebservice" name="basichttpbinding_eurekawebservice" /> In 2013 to connect to Sage through Windows Authentication the Web Service web.config file must also be amended This is found in the S200WebService folder. In the above instance this would be in: C:\inetpub\wwwroot\S200WebService\Web.config The Service Base Address field must be updated to match the Sage 200 client address, this address can be found in the file here: C:\Program Files (x86)\sage\sage200\sage200commonappsettings.config

10 P a g e 9 Amend the following section <add key="servicebaseaddress" value=" /> in the web.config file: <appsettings> <add key="sage.common.logging.loggername" value="log4net" /> <add key="sage.common.logging.configfile" value="c:\temp\log4net.txt" /> <add key="credentialsfile" value="c:\sage\logon\credentials.xml" /> <add key="sage200sitelogonpath" value="c:\sage\logon" /> <add key="serverrootpath" value="c:\sage" /> <add key="systemadministration" value="local" /> <add key="sessionkeepaliveenabled" value="true" /> <add key="sessionlifetimeinminutes" value="720" /> <add key="servicebaseaddress" value=" /> <add key="webserviceusername" value="xxxxxxxx" /> <add key="webservicepassword" value="xxxxxxxx" /> </appsettings> In our example it would be: <add key="servicebaseaddress" value=" /> Install Eureka Addons Web PO Requisition Pack Before accessing Web PO Requisition for Sage 200 you will also need to install the included Eureka Addons Web Requisition Pack.sdbx within Sage 200 System Administration. Installing a Eureka Addons package applies the changes to all workstations; therefore you will only need to use 1 PC to follow these instructions. It is recommended to carry out the following steps before proceeding: Take full backups of all Sage 200 databases. Take a backup of the Sage server folder (default location is c:\sage on your application server). Ensure all users are logged out of Sage 200.

11 P a g e 10 Installing Eureka Addons Packs using the Sage 200 System Administration tool To open Sage 200 System Administration from the main Windows start menu, click the Start button. Choose All Programs, followed by Sage Tools, Sage 200 and select System Administration. Enter the logon details to access the administration tool if unsure of these details please contact your system administrator or Sage Business Partner. Click OK to launch the Sage 200 SA (System Administration) Management Console.

12 P a g e 11 Launching the Add-On Management Wizard From the console, right click Add-Ons in the console tree on the left hand side and select Add New Add-On. This will display the Add-On Management Wizard welcome screen. Accept the default selection of Simple Mode and click Next. To select the addons package to be installed, either by typing in the full path or click the Browse button to locate the installation file: Eureka Addons Web Requisition Pack.sdbx Note: If you have downloaded the pack from the Eureka Solutions website, the file is likely to be located in your My Documents folder.

13 P a g e 12 Click Install to load the package. On successful installation of the package, the following screen in the wizard should be displayed: After installing the package, each of the Sage 200 databases you use must now be updated to allow the addons to operate correctly. Click Finish to exit the wizard. The following message will now be displayed: Click Yes to perform the update now. After the update has completed, the following message will be displayed (the version number will vary depending on your Sage 200 version): As this operation may take some time to complete, you may not wish to perform the update immediately, particularly if you have several large databases. If this is the case, click No. Please note however that after installing a Sage 200 addon, the update of the Sage 200 companies MUST be performed at some point prior to accessing a company through Sage 200.

14 P a g e 13 To update the Sage 200 companies having selected No to the message, select Companies from the console tree and right click on the first company and select Update. If you have more than one Sage 200 company database then you will need to complete the above step for each of the companies in turn. Sage 200 User Configuration The Web PO Requisition for Sage 200 system uses Sage users to login to the system. The configuration for these users varies depending on the version of Sage 200 that will be linked to Sage 200. For Sage /Sage : An individual Sage 200 user will need to be set up for each Web PO Requisition user. It is recommended that a new user role is created in Sage 200 System Administrator specifically for Web PO Requisition users. This role should have the Remote Access Only option ticked in the Properties which will then mean that Web PO Requisition users will then not take up any Sage 200 licences. The Sage 200 users should also be granted access to the required Sage 200 companies in the Sage 200 System Administration, which will then restrict company access through the Web PO Requisition module. For Sage R2: For Sage a single web user licence for Sage 200 will be required to allow Web Requisition for Sage 200 to connect to Sage without taking up additional Sage 200 licences. All Web PO Requisition users will then access Sage 200 using this single user. This web user will require access to all Sage 200 company databases that will be accessed using Web PO Requisitions. Licencing Web PO Requisition for Sage 200 Web PO Requisition for Sage 200 is licenced on the number of named users set up in the web module. You can view the number of named user licences that are currently being used in the module when logged in as an administrator user. Click on the Control Panel icon and click on Licence Details on the left hand menu to view the current licence details.

15 P a g e 14 The No. of Users field will tell you how many licences you currently have and how many named users are already set up. In the above example the system is licenced for 100 users and there are currently 28 named users set up. Logging In When you first log in to the Web PO Requisition module for Sage 200 there will only be one user set up. Type in your username and password provided and click on the Log In button to access the site. The default username is Administrator with the word password as the password we would strongly recommend that you reset the password for this account when you first log in. We would also recommend that you set up at least one other user with Administrator permissions in case you forget the Administrator password as this is the only way to access the Control Panel for configuring the module settings and creating new users. Standard users are automatically logged into the default company specified for their Sage 200 username in the Control Panel. Company access is restricted through the standard Sage 200 System Administrator.

16 P a g e 15 Setting up New Users To create new Web PO Requisition users click on the Control Panel icon in the top right hand corner of the website. Note: This Control Panel icon will only be visible to Administrator users. Click on the Users menu item on the left and click on the Create New User hyperlink. Type in the username, address and password details for the new user and click on Create User. Please note passwords must be a minimum of 6 characters. If the licenced number of named users has already been set up in the system a message will be displayed advising that additional licences would be needed. After creating the new user an administrator can then log in and configure the user s permissions. Select the new user from the dropdown list and on the Account Management tab type in the Sage Username and Sage Password for the Sage 200 user that this web user should be linked to. This is the username that will be displayed as the Order Taker on new purchase orders in Sage 200 authorised from Requisitions by this web user. Having individual users will ensure a full audit log per user is tracked on purchase orders entered through the system.

17 P a g e 16 Click on the Permissions tab to specify which areas of the Web PO Requisition module this user should have access to. Tick all areas of the module that this user should have access to when they log in. If a user has not been given access to any of the areas in the module then the corresponding icons will be hidden in the menu bar at the top of the website when that user logs in. For example, if Administrator is not ticked for a particular user then the Control Panel icon will not be visible to that user. When all permissions have been set as required click on Save to save the new user record.

18 P a g e 17 Contact Us Eureka Solutions have worked successfully with many Sage 200 customers over the past 5 years. In addition to Web PO for Sage 200 and our other modules that we have written for Sage 200, we are also happy to engage in bespoke/customisation work to help tailor your Sage 200 system to meet your specific business requirements. We offer free trials of our Web PO for Sage 200 module on our demo site For up to date information and details of all our addon modules for Sage 200, please refer to our website Our bestselling addon modules include: Our Sales Order Plus module has been specifically designed to provide fast order entry from within Sage 200 and aims to ensure that all information required by users entering orders is easily available from the main order entry screen. Sales Orders Plus has been really successful in telesales and tradecounter environments where fast order entry and access to sales history information is vital. Data Exchange for Sage 200 is ideal for two-way integration between Sage 200 and 3rd party systems, for example websites, CRM and manufacturing systems. Data Exchange allows for the transfer of information such as customer and supplier details, sales and purchase orders, stock records and stock levels, and Cash Book transactions in either CSV or XML file formats. Our Plus Pack is a collection of over 50 individual addons for Sage 200, most of which were created as a result of customer requests. The addons included in the pack range from simple sales order entry enhancements to some serious improvements to core Sage 200 functionality. If you wish to discuss a specific project or pricing or would like further information on Web PO or any of our addon modules for Sage 200 then please call our head office on or us at development@eurekasolutions.co.uk.