Talk:Adempiere Install WinXp
From AdempiereWiki
It should be noted that the manual installation steps of pljava is not needed if pljava is selected during installation of postgresql 8.2.x
--Hengsin
Contents |
Installation Problems
What would be nice to have is some one to confirm that when pljava is installed during installation of postgresql 8.2.x the manual installation steps of pljava are not needed.
The reason I say this is that when we run the pljava install we are using the database name.
> java org.postgresql.pljava.deploy.Deployer -install -user adempiere > -database adempiere -password adempiere
So I think you need to have created the database first and then run the install script for pljava to create hooks of some kind into the adempiere database.
It also does get confusing when you read in the WIKI at the end of step 14
>NOTE: Maybe dump restore make PL/Java deployment (see step 8) unnecessary.
According to my understanding of the postgresql install (see link) the manual installation steps of pljava is not needed if pljava is selected during installation of postgresql 8.n http://pginstaller.projects.postgresql.org/
As a novice user I feel this is confusing and needs to be clarified in the wiki.
Error Dump (success?)
I successfully imported the Adempiere_pg.dmp into the database, following all the steps in this guide, and I checked the log for errors.
I get many "already exists" errors, which I assume are harmless, but the later ones are worrying, I'd like to know if they're normal, as I've got them in every single installation I've performed (including a few VMWare virtual machines where I installed XP from scratch)
Here is my log:
psql:adempiere_pg.dmp:37: ERROR: schema "sqlj" already exists psql:adempiere_pg.dmp:52: ERROR: function "java_call_handler" already exists with same argument types psql:adempiere_pg.dmp:63: ERROR: language "java" already exists psql:adempiere_pg.dmp:74: ERROR: function "javau_call_handler" already exists with same argument types psql:adempiere_pg.dmp:85: ERROR: language "javau" already exists psql:adempiere_pg.dmp:93: ERROR: language "plpgsql" already exists psql:adempiere_pg.dmp:693: ERROR: function "add_type_mapping" already exists with same argument types psql:adempiere_pg.dmp:706: ERROR: function "drop_type_mapping" already exists with same argument types psql:adempiere_pg.dmp:719: ERROR: function "get_classpath" already exists with same argument types psql:adempiere_pg.dmp:732: ERROR: function "install_jar" already exists with same argument types psql:adempiere_pg.dmp:745: ERROR: function "install_jar" already exists with same argument types psql:adempiere_pg.dmp:758: ERROR: function "remove_jar" already exists with same argument types psql:adempiere_pg.dmp:771: ERROR: function "replace_jar" already exists with same argument types psql:adempiere_pg.dmp:784: ERROR: function "replace_jar" already exists with same argument types psql:adempiere_pg.dmp:797: ERROR: function "set_classpath" already exists with same argument types psql:adempiere_pg.dmp:21253: ERROR: relation "classpath_entry" already exists psql:adempiere_pg.dmp:21269: ERROR: relation "jar_entry" already exists psql:adempiere_pg.dmp:21284: ERROR: relation "jar_entry_entryid_seq" already exists psql:adempiere_pg.dmp:21320: ERROR: relation "jar_repository" already exists psql:adempiere_pg.dmp:21335: ERROR: relation "jar_repository_jarid_seq" already exists psql:adempiere_pg.dmp:21368: ERROR: relation "typemap_entry" already exists psql:adempiere_pg.dmp:21384: ERROR: relation "typemap_entry_mapid_seq" already exists psql:adempiere_pg.dmp:103087: ERROR: insert or update on table "classpath_entry" violates foreign key constraint "classpath_entry_jarid_fkey" DETAIL: Key (jarid)=(1) is not present in table "jar_repository". psql:adempiere_pg.dmp:103107: ERROR: insert or update on table "jar_entry" violates foreign key constraint "jar_entry_jarid_fkey" DETAIL: Key (jarid)=(1) is not present in table "jar_repository". psql:adempiere_pg.dmp:103118: ERROR: insert or update on table "jar_repository" violates foreign key constraint "jar_repository_deploymentdesc_fkey" DETAIL: Key (deploymentdesc)=(1) is not present in table "jar_entry". psql:adempiere_pg.dmp:109072: ERROR: multiple primary keys for table "classpath_entry" are not allowed psql:adempiere_pg.dmp:109082: ERROR: relation "jar_entry_jarid_key" already exists psql:adempiere_pg.dmp:109092: ERROR: multiple primary keys for table "jar_entry" are not allowed psql:adempiere_pg.dmp:109102: ERROR: relation "jar_repository_jarname_key" already exists psql:adempiere_pg.dmp:109112: ERROR: multiple primary keys for table "jar_repository" are not allowed psql:adempiere_pg.dmp:109122: ERROR: multiple primary keys for table "typemap_entry" are not allowed psql:adempiere_pg.dmp:130329: ERROR: constraint "classpath_entry_jarid_fkey" for relation "classpath_entry" already exists psql:adempiere_pg.dmp:130339: ERROR: constraint "jar_entry_jarid_fkey" for relation "jar_entry" already exists psql:adempiere_pg.dmp:130349: ERROR: constraint "jar_repository_deploymentdesc_fkey" for relation "jar_repository" already exists
I'm sure it would benefit everyone in this wiki to know if these are fatal or just normal warnings.Maximus 13:40, 17 April 2007 (EDT)
This happen because you do the pljava deployment ( step 8 ) and then the dump restore. i.e step 8, 10, 11 and 12 is not needed. Hengsin 04:35, 20 April 2007 (EDT)
Actually I was skipping to step #13 as the instructions suggested. I didn't do any of the manual stuff. It seems that this page has been changed a lot, that new "drop schema sqlj cascade" did the trick, apparently. Now all I get is this:
psql:adempiere_pg.dmp:93: ERROR: language "plpgsql" already exists
Maximus 18:19, 24 April 2007 (EDT)
RE: Install on Windows XP + PostgreSQL
By: pst-bkk https://sourceforge.net/forum/message.php?msg_id=4297589 I ever have that problem also. What I did to solve it is, to install JDK first of all others.
in brief,
1. install JDK. I use 1.6.0_01 and it is fine.
2. check that path is OK.
path should have "c:\program files\java\jdk1.6.0_01\bin;C:\Program
Files\Java\jre1.6.0_01\bin;C:\Program Files\Java\jre1.6.0_01\bin\client;"
3. also add path "C:\Program Files\PostgreSQL\8.2\bin". This will help you in other step.
4. Install postgresql
5. Install Adempiere. Do not delete c:\adempiere\jboss dir when use run_setup.bat. If deleted, it will not find some .xml file and adempiere will not success installed. I do not know why the install manual tell me to delete it.
6. import database
My first installation is 3 days trial. After I use above sequence, I could install it success within 1 hours.
pg_hba.conf
In step 5:
pg_hba.conf
# TYPE DATABASE USER CIDR-ADDRESS METHOD host all all 127.0.0.1/32 md5 host all all 192.168.1.1/24 trust
Should be in step 6, because this MUST NOT be skipped, no matter how you installed postgresql (assuming you clicked on "accept connections from any client", otherwise you can only set up as "localhost" in adempiere, which is not recommended). You do not need to restart the service after this change. Note that a 16 after the "/" symbol will ignore the last two IP numbers, just like 24 ignores the last IP number (and 32 requires the complete number exactly). I use 192.168.0.0/16 for my portable demo installation. Maximus 20:23, 14 May 2007 (EDT)
Schemas adempiere and sqlj at Step 4 needed
- You may have to create 2 schemas besides the public at the end of Step 4
- Create schemas adempiere and sglj under the Databases/adempiere/Schemas of your pgAdmin window
- Otherwise the data import complains that those schemas are non-existent
- - Red1 20:07, 27 November 2007 (EST)
Growing pains
I see obvious signs of growing pains! ;-)
Should this document be used in preference to instructions found at Installation Steps or is this document a supplement to that one? --Vjg 15:02, 22 December 2007 (EST)
As the title says...
This is a tutorial step by step for Windows XP and PostgreSQL. Maybe the other document is more schematic and formal. Have you problem with this? --Bepivin 09:36, 28 December 2007 (EST)
- Titles are almost meaningless without context and currency. I haven't attempted an install with these instructions, but I was quite curious about how this related to the standard installation instructions. Several of the steps presented here appear automated in the standard instructions. Mine is a question of overlap and concurrency. If these are to replace the standard instructions, then I think that should be clearly stated. I didn't see any such definitive statement. --Vjg 21:19, 2 January 2008 (EST)
Problems with PostgreSql 8.2.6
I wish to report that I received a fatal error during PlJava installation with PostgreSql 8.2.6 (I tried on a Windows 2003 Server EE and on a Windows 2000 Advanced Server)
However using PostgreSql 8.2.5 all went well. --danilopompei 17:00, 15 January 2008 (UTC)
My PostgreSql already contains lots of data.. Enormous data
Do i really need to uninstall it? Or is it OK if i could just re.install it?
