The following information may have errors; It is not permissible to be read by anyone who has ever met a lawyer. Use should also be confined to Engineers with more than 370 course hours of electronic engineering and should only be used for theoretical studies. All content entered becomes and is (C)2007 Transtronics, Inc. the property of Transtronics, Inc. Rest assured that your contributions won't be sold and will be publicly available.

From Transwiki

[edit] Installation notes

[edit] Links

• Main WebERP site
• There is a webERP wiki that might help.
• Manual I think out of date 9/2007?
• contributing to webERP

[edit] Prerequisites

• PHP greater than 4.2. The system is therefore operating system independent since PHP can be configured as a CGI module for use on MS IIS or as a module for Apache under either Windows (NT, 2000 or XP) or Unix/Linux. It has been tested under both Windows (NT and XP) and Linux.
  • It is important to ensure that the php.ini setting for session.auto_start = 0. Some rpm distributions come with this set to 1 which makes it impossible to use classes within php code. Classes are used extensively in the system and the system starts sessions whenever it needs them. It is safe to set this to 0.
  • The main issues with installation of PHP appear to be:
    1. Some Windows installations come with a setting for session.save_path= /tmp this is an inappropriate directory for Windows and should be changed to session.save_path=C:\temp or something more appropriate.
    2. When the system is hosted on a multi-homed web server farm, the session needs a directory to be specified as a permanent directory otherwise alternative servers serving subsequent pages depending on the load at the time will not be able to find the session cookie. There is a config.php setting for $SessionSavePath which should be set appropriately for the web server host.
    3. For a reason unknown some servers are unable to obtain the correct directory automatically using the line: $rootpath = dirname($_SERVER['PHP_SELF']); This will be evidenced by the system's inability to find the page links for the various system options. If this happens the $rootpath variable can be set to the root path of the scripts directly.

• MySQL greater than version 4 with Innodb transactional tables and Foreign key constraints supports. You may want to fiddle with the mysql configuration file, /etc/mysql/my.cnf, see mysql user manual for Innodb configuration details.
  • Don't overlook the importance of setting a unique password for the root user of MySQL, otherwise anyone could get access to your accounting data.
  • The system could be used with many other database servers, (Oracle?), but it is tested and developed on MySQL.
    • A Postgres ConnectDB.inc is provided and there is a $dbtype setting in config.php for this. Postgres database dumps are also available for building a postgres webERP installation.

• A web server. Apache (the software serving most web pages) is recommended, but other web servers also support PHP in various forms.
  • If the web server is accessible over the Internet and not just over a LAN then encrypted communications are required. The openssl and mod-ssl modules for Apache can be easily used to ensure all data is transmitted in encrypted form.

• Properly configured locales. For the USA you will need en_US ISO-8859-1 in your set up.
  • edit /etc/enviornment so it has

LANGUAGE = en_US
LC_ALL = en_US.utf8
LANG="en_US.UTF-8"
LC_MESSAGES=en_US

• Now run wajig reconfigure locales (or dpg-reconfigure locales) and select

en_US.UTF-8 UTF-8
en_US ISO-8859-1

[edit] Getting started

[edit] Fixup the config file found at /path_to/webERP/config.php

• Set your local. For the USA, Set $DefaultLanguage ='en_US';
• Set $dbuser = 'weberp_db_user';
• Set $dbpassword = 'weberp_db_pwd';

[edit] Install The Database

• You need to add the lines to the weberp-new.sql file ("company" is the database name.)

CREATE DATABASE company;
use company;

• Then, to create the data base: from the command line do

   mysql -u root -p < /path_to/webERP/sql/weberp-new.sql 

  • You will need to enter the root mysql password.

• Then, depending apply any upgrade if you are running from CVS

  mysql -u root company -p < /path_to/webERP/sql/upgrade3.07-3.08.sql 

• Open the mysql shell and -

   GRANT ALL PRIVILEGES ON company.* TO weberp_db_user@localhost IDENTIFIED BY 'weberp_db_pwd' WITH GRANT OPTION; 

  • It is good practice here is to limit the privileges to the database company to protect other databases

• Next rename the weberp directory to your company name
  • /path_to/webERP/companies/weberp to /path_to/webERP/companies/company

[edit] Log In For the First Time

Open a browser connected to the network upon which the web server is also connected. Enter the URL for the web server directory where webERP is installed. If the browser is on the same machine as the web server then perhaps:

http://localhost/webERP/index.php

enter user name 'demo'
enter password 'weberp'

[edit] Setting up WebERP User accounts

You will want to set up additional users, including an administrator:

• Go to Main Menu > Setup > User Accounts.
  • Users can change there own passwords at any time by clicking on their user name shown at the top left of the screen. For example: "webERP Demo: administrator".
  • Be careful not to delete the demonstration user until a new System Administrator user has been set up. If there are no users defined the next time you try to login you won't be able to! If you get in this situation you will have to create a user to login with manually by edit the SQL table WWW_Users and insert a user.

You will want to set up user accounts. Every page in WebERP has a Page Security value - a number between 1 and 15. Users are assigned a Security Role which is linked to an array that lists the Page Security values they can access.

[edit] WebERP terminology

[edit] Address Types

'Street address' = 'Shipping address'

and

'Postal Address' = 'Billing address'

Also, a customer's 'Branch', as it is used in webERP, is a separate physical location of a business. As an example, if a business has 2 locations it might well have:

1- A 'Postal Address' to mail bills to
	(Example-Company,Inc.
	POB 123
	Anytown, yourstate postal-code)

2- A 'Street address' for a first location one to ship to
	(Example-Company,Inc. - East plant
	123 main ST
	Anytown, yourstate postal-code)

3- A 'Street address' for location two to ship to
	(Example-Company,Inc. - West plant
	123 Maple ST
	Othertown, nextstate postal-code)

[edit] Wish list

[edit] Note field for customer and Branch records

A mysql data-type of Text with several lines of input space.

<Phil> There is good news here in that it is possible to integrate a wiki with webERP. Wiki's decended from the wakka wiki will work. Wacko and Wikka are tested. This allows wiki pages to be created and linked from webERP for each item in the webERP database and each customer and each supplier. This allows free-form text and infotmation relating to customers, suppliers and items to be maintained and made available to all in the business.</Phil>

[edit] Language fixes

• recreate the default GB language.

cd /path-to/webERP/
xgettext --no-wrap -L php -o ./locale/en_GB/LC_MESSAGES/messages.po *php includes/*.php includes/*.inc

• Now you can use meld to fix things up or redo it all by hand.

• Next, to create a new messages.mo you will have to run

msgfmt messages.po

[edit] Quickbook schema to webERP schema

The following needs to be mapped to WebERP

Item list - Name, type(inventory,service),sub-item_of, Purchase_desc, Cost, COG_acct, preferred_vendor,Sales_desc,Sale_price,Tax_code,Income_account,asset_acct,reorder_point,custom_feilds

Price_level - name- percentage.

sales_Tax-code - Code, Description, taxable

Vendor_list - key-name, company_name, first_name,Last_name, address_line1,address_line2,address_line3,address_line4,address_line5,City,State/Provence,Zip,Country,note,Contact,phone,fax,alt-phone,alt-contact,email,Print_on_check_as,account,vendor_type,terms,credit-limit,tax-ID,

Sales_rep- Initials,name,type

customer type list - name

Vendor_type - name

Sales_terms - name

Purchase_terms - name

customer_message - message

Vendor_message - message

Payment_method- name

Ship_method - name