If you need to you set up a new time zone on your Windows computer there is a need to check and perform the following steps in order for Postgres to take into account your update.
Check first the current time zone information set by Postgres: File path: D:\MSF data\Unifield\PostgreSQL File name: postgresql.conf line: timezone = 'CET' In our example it is set to: CET
Now for the example we would like to set the time zone to (UTC+05:00) Islamabad, Karachi Select this new time zone on the Windows Time Zone Settings 1 Click on OK 2
Stop to the following service:
OpenERP Server 6.01
Open pgAdmin 1 Open a SQL query window 2 to check the list of availalbe Postgres time zone Run the following sql query 3SELECT * FROM pg_timezone_names; Scroll down 4 the list to find Karachi Copy this information to your clipboard.
Edit your file postgresql.conf at line: timezone = 'CET' Replace ‘CET’ by ‘Asia/Karachi’ Save the file
Restart to the following services. The order is very important:
Postgres 1
OpenERP Server 6.0 2
OpenERP Web 6.0 3
In few cases pgAdmin cannot find a time zone from its list that matches the (nonstandard) time zone name used by Microsoft. E.g.: you would like to use the Windows time zone (UTC+01:00) West Central Africa but it’s doesn’t appear in the pgAdmin list of timezone.
As above look at the pgAdmin time zone list that would suit the (UTC+01:00) West Central Africa In our case timezone would be 'Africa/Bangui' which is UTC+01:00 -without daylight savings- just like Micosoft’s West Central Africa time is.
Edit the file 1postgresql.conf the same way as above. Restart the services Postgres and OpenERP Server 6.0
1.9 Secure passwords between browser and server with TLS
The best practice for web applications like UniField is to encrypt usernames and passwords on the network. It is strongly recommended to enable HTTPS security, doing so via a progressive rollout in coordination with the UniField Support team. In a future version, HTTPS will be recommended for all sites, and will be the default. Enabling HTTPS has no impact on how the end users will open UniField in their browsers as UniField will automatically redirect users arriving on HTTP to HTTPS. Each HTTPS server needs a certificate, which shows that a third party guarantees the connection between the server’s public key and the DNS name it is using. There are three choices for how to get a certificate:
Option 1:
Allow UniField to get a certificate via the Certomat system operated by the UniField Support team, which fetches certificates from LetsEncrypt on behalf of your server. This is the recommended configuration.
Pros: Simple, free and automatic, works with servers that are not on the public Internet.
Cons: The name must be of the form “prod.unifield.org”. You must use local DNS or the hosts file to point the name at your server’s local IP address.
You need to choose one word and put it before “prod.unifield.org”. If your server has one instance inside of it, then you should use the instance name, so for example in Osh Kyrgyzstan, it would be “OCG_KG1_OSH.prod.unifield.org”. If your server will have several instances inside of it, make a name for it starting with your OC and ending with a description of what the server is for. For example, a training server in OCG might be called “ocg-training.prod.unifield.org”. Check with your site network administrator that your local DNS (or the hosts file on all client machines if local DNS is not available) maps the name of your server to its local IP address.
Option 2:
Tell UniField to fetch and renew certificates directly from the LetsEncrypt CA automatically. This option is not recommended, but supported.
Pros: You can choose any name for your UniField server, as long as you control the DNS for that name. Simple to configure. Free.
Cons: Your server must be continually available on the public Internet so that during renewals LetsEncrypt can connect and confirm that you still control the DNS name.
You must use the public DNS name for the public interface of your server (ask your network/server admin to help you find it and/or set it).
Option 3:
Generate a Certificate Signing Request (CSR) and submit it to a certificate authority. Complete whatever checks they require and pay them a fee. Install the certificate on the Unifield server. Remember to pay the fee again in a year or two years when the certificate expires. This option is not recommended, but supported on a case by case basis.
Pros: You can choose any name for your UniField server, as long as you control the DNS for that name.
Cons: cost and operational complexity.
You may choose any name that you can buy a certificate for (check with your certificate provider for their rules). When using a certificate from a certificate authority, the private key and certificate must be placed into c:\Program Files (x86)\msf\Unifield\Web as $server_name.key and $server_name.cer. They must be in PEM format.
1.9.1 Procedure
Prerequisite: AIO version 4.0 or later is installed in your server/machine.
If your UniField version is running on 4.0 or after skip the next unistall/install of the AIO first steps below.
If your UniField version is running on 3.1 or before you would need to install the latest AIO version (minimum v4.0)
Once your UniField version is in 4.0 or later you can follow with the below steps
Choose an HTTPS server name, which is the name that will be in the certificate, and shown in the URL bar of the web browser. The way that you choose the server name depends on which option you have chosen for how to get the certificates (see above).
Click on Start 1 and search for cmd Right click on cmd.exe 2 and Run as an administrator 3
The terminal opens, launch notepad by typing notepad++.exe1
Open the following file on Notepad: File > Open…: c:\Program Files (x86)\msf\Unifield\Web\conf\openerp-web-oc.conf. Uncomment 1 the line server.https_name Set the name 2 as previously selected: e.g. instancename.prod.unifield.org Save the file
Depending the option you choose do:
Option 1:
Edit the hosts file in C:\Windows\System32\drivers\etc on all client machines ONLY if the local DNS is not available and add the connexion line 1.
Option 2:
No other configuration is needed you can continue the procedure.
Option 3:
Place the key and Certificate file in c:\Program Files (x86)\msf\Unifield\Web as $server_name.key and $server_name.cer. They should be in PEM format.
Restart OpenERP-Web service 1 by right clicking on the service.
Wait a few seconds and then go to http://localhost:8061 You should be redirected to the HTTPS site.
In addition please find here an internal OCB procedure complementing the manual on how configure the DNS.
1.9.2 Troubleshooting
Below few troubleshooting tips for known issues:
If going to http://localhost:8061 does not result in redirect to HTTPS Read the openerp-web.log Look for A server is already running on Port 443. Is it Skype? If you are running Skype, do the following: a. tools > options > advanced > connections b. uncheck “listen on port 80 and 443“ c. save and close d. restart skype
Bad Certificate: If you are using Windows and Chrome or IE, and you get a certificate trust error, it might be because root certificate auto-update is disabled. You can use regedit.exe to check this key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot\DisableRootAutoUpdate If it is 1, then the CA certificate that LetsEncrypt depends on is not getting loaded automatically. You need to set it to 0. If you are using Firefox (the supported UniField browser) this problem does not occur.
1.7 Allow UniField to contact the synchronization server on Windows 7 Pro Firewall
The same way you created an inbound rule, create the outbound rules so that the instance can perform synchronizations with the Production synchronization server.
The port to be open is: TCP-443 (XMLRPC protocols)
1.6 Allow the UniField web port on Windows 7 Pro Firewall
Click on the Windows Start menu at the bottom left. In the Search programs and files field, enter firewall 1 without pressing enter. Click on Windows Firewall with Advanced Security 2
Click on Inbound Rules 1. The inbound rules will now be listed. Click on New Rule… 2 A new wizard will open
Select Port 1 Click Next 2
Select TCP 1 Specific local port 2: enter 8061. If you will be using a different port (i.e. 80) set that instead. If you will be enabling HTTPS (section 1.9) add port 443 (separated with a comma). Click Next.
Select Allow the connection 1 Click Next 2
Select the appropriate options 1 regarding your network configuration. By default select Domain, Private and Public. Click Next 2
Enter a name 1 such as Inbound port TCP:8061 UniField Web Click on Finish 2
Remote connections for the web access are now accepted by the Firewall.
UniField installed, it’s not the time yet to create the database or restore one. First, the super admin password must be changed. This password is used to create databases. It is very important and should not be communicated. Connect to UniField with a browser: http://localhost:8061
Click on Databases 1
Click on Password 1
Enter the old password 1. If it’s a first installation, you must enter the default super admin password. Enter the New super admin password and confirm it. Click on Change Password 2
The super admin password is now changed. Keep it somewhere safe because you will need it every time you need to do something regarding the databases (especially backup and restore).
Use Windows Explorer to browse to the directory where the UniField installer is located. Double click on the installer e.g: openerp-allinone-setup-UF10.0-20180914-083009-r1.exe In case the window User Account Control appears, allow the program from an unknown publisher to make changes. Click Yes. The following window appears: Click on OK 1
Click Next 1
Click I Agree 1
Select 1 All In One as type of install Leave all the boxes checked Click Next 2
Click on Browse 1 if the standard path does not suit you. Otherwise, Click Next 2
You need to define different passwords 1 to drop backup and restore the database. Click Next 2
Click on “…” 1 if the standard path does not suit you. Leave all the fields as shown except for the Password. For security reasons, you should not leave this default value; change Password 2 to something that will be remembered. This value will never be changed. Click Install
The installation starts running and the following screens will appear during the installation, wait until it is completed
When it finishes you will see at the bottom of the text area a Completed notification 1 meaning the installation is now done. Click Next 2
Leave the Connect to OpenERP Web box checked 1. Click on Finish 2
The default browser starts running and connects locally to UniField 1 A warning message 2 is displayed on the homepage to ensure that your regional settings are set to “English (United States)”. If it is already done, you can omit it and proceed.
UniField is correctly installed and will start automatically when the computer boots up. On the computer where UniField has been installed, you can later connect to the UniField Web Interface using the address http://localhost:8061
1.3.2 Silent installation
Use the following command for silent installation: openerp-allinone-....exe /S In this example: openerp-allinone-....exe is the AIO By default:
OpenERP is installed into C:\Program Files (x86)\msf\Unifield
PostgreSQL data is installed into: D:\MSF Data\Unifield\PostgreSQL
PostgreSQL application software is installed into: C:\Program Files (x86)\msf\Unifield\pgsql
UniField is correctly installed and will start automatically when the computer boots up. On the computer where UniField has been installed, you can later connect to the UniField Web Interface using the address http://localhost:8061
The AIO must be delivered by the OC deployment team. Please always use the latest version. It is available in SharePoint here
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
