Difference between revisions of "Plugin: JPiere (Localization Japan)"

From iDempiere en
m
 
(34 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
<!-- breadcrumb -->
 +
<font size=-2>
 +
> [[:Category:Available Plugins | Category:Available Plugins]]
 +
> [[Plugin: JPiere (Localization Japan) | JPiere - Top]]
 +
</font>
 +
 
[[Image:JPiere-tate.png |200px|right|JPiere]]
 
[[Image:JPiere-tate.png |200px|right|JPiere]]
 
[[Image:OSS-ERP-Solutions_logo_tate.png |200px|right|OSS ERP Solutions]]
 
[[Image:OSS-ERP-Solutions_logo_tate.png |200px|right|OSS ERP Solutions]]
Line 4: Line 10:
 
* '''SPONSOR:''' [http://www.oss-erp.co.jp/ OSS ERP Solutions] in JAPAN
 
* '''SPONSOR:''' [http://www.oss-erp.co.jp/ OSS ERP Solutions] in JAPAN
 
* '''License:''' [http://www.gnu.org/licenses/gpl-2.0.html GPLv2] - Free as in Freedom not Free Lunch
 
* '''License:''' [http://www.gnu.org/licenses/gpl-2.0.html GPLv2] - Free as in Freedom not Free Lunch
* '''Source:''' [https://bitbucket.org/jpiere/  Bitbucket JPiere repository]  
+
* '''Source:''' [https://github.com/jpiere GitHub JPiere repository]  
* '''Install Package:''' [http://osdn.jp/projects/jpiere/ OSDN]
+
* '''Install Package:''' [https://en.osdn.jp/projects/jpiere/ OSDN]
 
* '''Japanese:'''[http://www.compiere-distribution-lab.net/jpiere-lab/ JPiere Lab]  
 
* '''Japanese:'''[http://www.compiere-distribution-lab.net/jpiere-lab/ JPiere Lab]  
  
  
==[[:Category:JPIERE|About JPiere]]==
+
==Overview of JPiere==
*JPiere is Plugins of iDempiere for Japan and JPiere is iDempiere Distribution(Distro) for Japan.
 
*JPiere provides not only Japanese business practice, but also various functions.
 
 
*JPiere is “Japan + iDempiere”.  
 
*JPiere is “Japan + iDempiere”.  
 +
*JPiere is Plugins of iDempiere for Japan and JPiere is Distribution(Distro) of iDempiere for Japan.
 +
*JPiere provides not only Japanese business practice, but also various functions.So, Everybody in the world can use JPiere.
 
*JPiere can update latest iDempiere. So, JPiere don’t need fork from iDempiere. To fork from JPiere is Good idea! But not need fork from iDempiere!
 
*JPiere can update latest iDempiere. So, JPiere don’t need fork from iDempiere. To fork from JPiere is Good idea! But not need fork from iDempiere!
 +
*Data base of JPiere is PostgreSQL only.
 +
*UI of JPiere is Web-UI only.
  
 +
{{note|
 +
Challenge of JPiere:
 +
When create production system, everyone forked from iDempiere(ADempiere/Compiere) usually . And maintained it themselves. But it is not so easy, because ERP is very big system and advancing technology is early. On the other hand, To fork from repository of community is to separate power of community.
 +
Challenge of JPiere is to create production system without doing fork from iDempiere. It reduce load of the maintenance, and can concentrate to community activity. 
 +
JPiere hopes the prosperity of iDempiere community.
 +
}}
  
  
  
==Constitution of JPiere==
 
* JPiere is based on iDempiere and classifies it in five.
 
  
[[File:Jpiere.png]]
+
==[[:Category:JPIERE|About JPiere]]==
 +
*[[:Category:JPIERE | JPiere is based on iDempiere and classifies it in five category as  follows.]]
  
 +
[[File:Jpiere.png|400px]]
  
===[[:Category:JPCS|JPiere Configurations(JPCS)]]===
 
*JPiere Configurations(JPCS) customizes iDempiere only by parameter setting. 
 
*We need many parameter setting at iDempiere. So, JPCS optimize parameter setting beforehand.
 
*JPCS is not Plugin.JPCS is Dump File of PostgreSQL.
 
  
  
 +
===[[:Category:JPPS|JPiere Plugins(JPPS)]]===
 +
*JPiere Plugins(JPPS) are plugins that are not relation a Japanese business practice. JPPS is useful for not only Japanese, but also everybody.
 +
*Everybody can select to install plugin. Independent other JPiere plugins.
 +
*Representative plugin
 +
**[[Plugin: ZK Window X | Series of ZK Window X]]
 +
***[[ZK Window X1 | ZK Window X1(Form Window)]]
 +
***[[ZK Window X2 | ZK Window X2(Matrix Window)]]
 +
***[[ZK Window X3 | ZK Window X3(Simple Input Window)]]
 +
***[[ZK Window X4 | ZK Window X4(Pivot Window ※experimental)]]
 +
**JPiere Groupware
 +
***[[Plugin: ToDo Management | ToDo Management]]
 +
***[[Plugin: Information Gadget | Information Gadget]]
 +
**[[Plugin: Delete Client and Initialize Client | Delete Client and Initialize Client]]
  
===[[:Category:JPFS|JPiere Fragments(JPFS)]]===
+
===[[:Category:JPBP|JPiere Base Plugin(JPBP)]]===
*JPiere Fragments(JPFS) are plugins that utilize fragment of OSGi.
+
*JPiere Base Plugin(JPBP) provides many function to support a Japanese business practice. JPBP is only one plugin.  
  
  
  
===[[:Category:JPBP|JPiere Base Plugin(JPBP)]]===
+
===[[:Category:JPFS|JPiere Fragments(JPFS)]]===
*JPiere Base Plugin(JPBP) provides functions to support a Japanese business practice.
+
*JPiere Fragments(JPFS) is plugin that is fragment of OSGi.
  
  
  
===[[:Category:JPPS|JPiere Plugins(JPPS)]]===
+
===[[:Category:JPCS|JPiere Configurations(JPCS)]]===
*JPiere Plugins(JPPS) are plugins that are not relation a Japanese business practice. JPPS is useful for not only Japanese, but also everybody.
+
*JPiere Configurations(JPCS) customizes iDempiere only by parameter setting. 
 +
*We need many parameter setting at iDempiere. So, JPCS optimize parameter setting beforehand.
 +
*JPCS is not Plugin.JPCS is Dump File of PostgreSQL(Seed).
  
  
  
 
===[[:Category:JPMS|JPiere Modifications(JPMS)]]===
 
===[[:Category:JPMS|JPiere Modifications(JPMS)]]===
JPiere Modifications(JPMS) is fragment of OSGi that impact core of iDempiere. If We have to modify core source code of iDempiere, We develop it as JPMS. Technically, JPMS is to use Fragment of OSGi as Patch.
+
*JPiere Modifications(JPMS) is fragment of OSGi that impact core of iDempiere. If We have to modify core source code of iDempiere, We develop it as JPMS.
 +
*Technically, JPMS is to use Fragment of OSGi as Patch.
 +
 
 +
 
  
==Install==
+
==[[Installation of JPiere | Installation of JPiere]]==
*To install JPiere is same as iDempiere basically,
+
*Installation of JPiere is same as installation of iDempiere basically,
*Please download 2 file from [http://osdn.jp/projects/jpiere/ OSDN]
+
*To make intelligible, Version number of JPiere is same as version number of iDempiere.
**Windows(64bit):idempiereServer.win32.win32.x86_64.zip and ExpDat.dmp
 
**Linux(64bit):idempiereServer.gtk.linux.x86_64.zip and ExpDat.dmp
 
  
===Step1===
+
==[[Version Information of JPiere | Version Information of JPiere]]==
*Please restore DMP file to PostgreSQL9.2 or 9.3
 
  
  
===Step2===
+
===[[Release Note of JPiere3.1 | Release Note of JPiere3.1]]===
*Set up iDempiere from Install Package.
+
*Release Note of JPiere3.1.
  
  
 +
==[[Development environment establishment | Development environment establishment]]==
 +
*How to establish of JPiere development environment.
  
  

Latest revision as of 09:09, 3 January 2021

> Category:Available Plugins > JPiere - Top

JPiere
OSS ERP Solutions


Overview of JPiere

  • JPiere is “Japan + iDempiere”.
  • JPiere is Plugins of iDempiere for Japan and JPiere is Distribution(Distro) of iDempiere for Japan.
  • JPiere provides not only Japanese business practice, but also various functions.So, Everybody in the world can use JPiere.
  • JPiere can update latest iDempiere. So, JPiere don’t need fork from iDempiere. To fork from JPiere is Good idea! But not need fork from iDempiere!
  • Data base of JPiere is PostgreSQL only.
  • UI of JPiere is Web-UI only.


Note.gif Note:

Challenge of JPiere: When create production system, everyone forked from iDempiere(ADempiere/Compiere) usually . And maintained it themselves. But it is not so easy, because ERP is very big system and advancing technology is early. On the other hand, To fork from repository of community is to separate power of community. Challenge of JPiere is to create production system without doing fork from iDempiere. It reduce load of the maintenance, and can concentrate to community activity. JPiere hopes the prosperity of iDempiere community.



About JPiere

Jpiere.png


JPiere Plugins(JPPS)

JPiere Base Plugin(JPBP)

  • JPiere Base Plugin(JPBP) provides many function to support a Japanese business practice. JPBP is only one plugin.


JPiere Fragments(JPFS)

  • JPiere Fragments(JPFS) is plugin that is fragment of OSGi.


JPiere Configurations(JPCS)

  • JPiere Configurations(JPCS) customizes iDempiere only by parameter setting. 
  • We need many parameter setting at iDempiere. So, JPCS optimize parameter setting beforehand.
  • JPCS is not Plugin.JPCS is Dump File of PostgreSQL(Seed).


JPiere Modifications(JPMS)

  • JPiere Modifications(JPMS) is fragment of OSGi that impact core of iDempiere. If We have to modify core source code of iDempiere, We develop it as JPMS.
  • Technically, JPMS is to use Fragment of OSGi as Patch.


Installation of JPiere

  • Installation of JPiere is same as installation of iDempiere basically,
  • To make intelligible, Version number of JPiere is same as version number of iDempiere.

Version Information of JPiere

Release Note of JPiere3.1

  • Release Note of JPiere3.1.


Development environment establishment

  • How to establish of JPiere development environment.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.