Message涓殑Message Text瀛楁鍐呭閫氳繃 %0 鏉ユ帴鍙椾紶閫掕繘鏉ョ殑鍙傛暟
]]>
iReport is a graphical tool you can use to create/edit templates (jrxml files) that will be later processed by JasperReports engine.
 | You must use iReport 4.0.1 |
Fonts
JasperReports introduced a change in version 3.6.1 that it should fail (throw an exception) when you're trying to use a font that is not available.
JasperReports 3.6.1 (2009-10-26, SVN 3170) --------------------------------------------- - net.sf.jasperreports.awt.ignore.missing.font configuration property added to control font availability verifications during report filling and report AWT rendering;
If you open a JasperReports template and is using a font not available in your system, you won't see the text of label. To avoid this problem you need to configure your iReport to skip this check.
- Go to Tools > Options > JasperReports Properties
- Set to true the property net.sf.jasperreports.awt.ignore.missing.font
Scriplet Class
Openbravo 3 doesn't support out of the box any Scriplet class. Make sure your template doesn't contain any class in the template properties.
- Window > Report Inspector
- Scroll down in the More section
- Make sure the Scriptlet class property is empty
Language
The default language for expressions in Openbravo 3 is Java. Make sure that your template uses Java as language expression.
- Window > Report Inspector
- Scroll down to the More section
- Pick Java in the Language property
]]>
The new table must include the AD_Client_ID, AD_Org_ID, IsActive, Created, CreatedBy, Updated and UpdatedBy fields that are mandatory and required for security and auditory purposes of the application.
Each table must have at least one column marked as an identifier. The actual values of identifier columns later get concatenated to be shown to the user as a representation of a particular record (see the link to the Sales Order within the Sales Invoice window). These identifiers will also be used to construct dropdown lists of records of that particular table. By default all columns with column name Name are set as an identifier. In case there is no column with this Name, no identifier is set and needs to be done so manually or compilation will fail.
NOTE: The columns that are named line or seqNo are used to contain the sequence number of a record (i.e. the number of a line in an invoice). They take a default value like:
@SQL=SELECT COALESCE(MAX(ColumnName),0)+10 AS DefaultValue FROM TableName WHERE xxParentColumn=@xxParentColumn@
The WHERE part of this clause needs to be replaced with the required values. The code that should appear here is the name of the column which links with the id of the parent one. For example, each record of the C_InvoiceLine belongs to a particular C_Invoice record and they are all sequenced. C_Invoice is the parent table for the lines saved in C_InvoiceLine. This table has a column named line and the default value that it takes is:
@SQL=SELECT COALESCE(MAX(LINE),0)+10 AS DefaultValue FROM C_INVOICELINE WHERE C_INVOICE_ID=@C_INVOICE_ID@
How to add Columns to a Table
These changes can be done in two different locations:
- Add columns to the original module (dbprefix HT)
- Create a second module (dbprefix HT2) which adds the columns to the first module
The first option can be chosen if the original module author wants to add more columns to his/her module. The second option is possible for anyone as the columns are added by a new module to the existing one which is not changed directly.
The main difference between these two methods is the names which need to be chosen for the columns to comply with the modularity naming rules.
- Adding column to same module: Any valid column name can be picked
- Via second module: New column name must comply to the pattern EM_<DBPREFIX>_ where <DBPREFIX> must be the dbprefix if the new module contaning the column to be added. In this example: EM_HT2_
How to add a Constraint
In the Application Dictionary || Message window create a new record using the following details:
- Module Openbravo Howtos 2 as this is the module containing the constraint also.
- Search key: The search key must be exactly the same as the constraint's one, in this case em_ht2_ht_salary_dates_chk as this is the link between the constraint and the message.
- Message type: Depending on the type the UI for the message box will be different (green for success, yellow for warning...), in our case we want a red error message box, so we select Error.
- Message text: It is the user friendly message that will be displayed inside the message box. So let's enter: The Valid To date may not be before the Valid From date.
Creating a new instance of a Business Object
A business object may never be created using the Java new operator. All business objects should be created using the OBProvider factory class:
// create the object through the factory final Category bpg = OBProvider.getInstance().get(Category.class);
Hibernate will detect that a business object is new when:
- the id of the business object is not set
- when the flag newOBObject is set to true explicitly
So if you want to create a new business object with a specific id (by calling setId(...)) then you explicitly need to call businessObject.setNewOBObject(true). Otherwise, Hibernate will throw an exception ('count of batch update operation....').
]]>
娉ㄥ唽緲昏瘧妯″潡
When you register the module, fill in the fields as follows:
- 浠?strong>Module Type鍒楄〃錛岄?strong>Module.
- 鍦?strong>Name瀛楁錛岃緭鍏ava package name of the translation, using the correct naming convention.
- Complete the Description and Help fields, using the language that you are translating into.
- Select the Is translation module option.
- Clear the Has reference data, Translation required and Has chart of accounts options.
- Select the In development option. Remember that you cannot work on a module unless the In development option is selected.
- From the Module language menu, select the translation language. For example if you are translating into Czech, select Czech from the list.
- On the Dependencies tab, specify the module you are translating as the dependent module. For example if you are translating the Core module, select Core as the dependent module.
When you click Register Module you will be asked to supply your username and password for the Openbravo Forge
瀵煎嚭鏁版嵁搴?/span>
When you have registered the module, the next stage is to export the database to create the necessary module folders.
- 鎵ц涓嬪垪鍛戒護錛?
-
ant export.database
- Exporting the database creates a new subfolder within the Modules folder. The new folder has the same name as the java package of the translation module, for example modules/org.openbravo.translation.es_ES.
-
- Within the Modules folder, manually create a subfolder called referencedata. You must use this exact name, note that it is all lower case and has no spaces.
- Within the referencedata folder, create another subfolder called translation.
- Within the 'translation folder create another folder for the translation, using the xx_YY language / country code naming convention. For example en_US for US English.
- Place the translated .xml files within the folder for its respective language.
緲昏瘧.xml鏂囦歡
You can now translate the .xml files using your preferred editor. When you have finished translating, copy them into the translation subfolder you have already created.
鎶婃ā鍧楁墦鍖呮垚.obx鏂囦歡
To package the module, 鎵ц涓嬪垪鍛戒護 ant package.module -Dmodule=modulename, where modulename is the Java package name of the module.
]]>
It is a known issue that the tree icon in the teams window does not work. If it is clicked it throws an error. Openbravo ERP does not support trees on modules yet. Still, the module has been designed to provide a mean to workaround this issue. As for that, some java files needs to be modified and the application recompiled to make the changes visible. Take into account that this is a core modification (and core modifications should not be done). If a core modification is done, whenever the system is updated with the next maintenaince pack, the changes will be lost (you will have to remember to do them again after updating the system).
Making this changes will make the tree icon work and so, the drag and drop functionality will be usable. The changes consist on adding the following lines in the following files:
- src/org/openbravo/erpCommon/utility/WindowTreeChecks.java - Line 132
} else if (TreeType.equals("HCMC_TE")) {
result = "";
- src/org/openbravo/erpCommon/utility/WindowTreeUtility.java - Line 73
else if (keyColumnName.equals("Hcmc_Team_ID"))
TreeType = "HCMC_TE";
- src/org/openbravo/erpCommon/utility/WindowTreeUtility.java - Line 155
else if (TreeType.equals("HCMC_TE"))
data = WindowTreeData.selectTeam(conn, vars.getUser(), strEditable, strParentID, strNodeId,
TreeID);
- src/org/openbravo/erpCommon/utility/WindowTree_data.xsql - Line 290
<SqlMethod name="selectTeam" type="preparedStatement" return="multiple">
<SqlMethodComment></SqlMethodComment>
<Sql>
SELECT tn.Node_ID,tn.Parent_ID,tn.SeqNo,tb.IsActive, te.HCMC_TEAM_ID AS ID, te.NAME, ' ' AS Description,te.IsSummary
FROM AD_TREENODE tn LEFT JOIN AD_TREEBAR tb ON tn.AD_Tree_ID=tb.AD_Tree_ID
AND tn.Node_ID=tb.Node_ID
AND tb.AD_User_ID = ? ,
HCMC_TEAM te
WHERE tn.Node_ID = te.HCMC_TEAM_ID
AND tn.AD_Tree_ID = ?
ORDER BY COALESCE(tn.Parent_ID, '-1'), tn.SeqNo
</Sql>
<Parameter name="adUserId"/>
<Parameter name="editable" optional="true" type="none" after="WHERE " text="tn.IsActive='Y' AND te.isActive='Y' AND "/>
<Parameter name="parentId" optional="true" after="WHERE " text="tn.Parent_ID = ? AND "/>
<Parameter name="nodeId" optional="true" after="WHERE " text="tn.Node_ID = ? AND "/>
<Parameter name="adTreeId"/>
</SqlMethod>
Notice that the line number above may change over time.
Notice that this lines should be eliminated manually if the module is unistalled.
Add Team Manager
org.openbravo.hcm.common.ad_process.HCMC_addmanager_process.java
final Calendar today = Calendar.getInstance();
final SimpleDateFormat sdf = new SimpleDateFormat();
sdf.applyPattern(bundle.getContext().getJavaDateFormat());
final Date effectiveFrom = sdf.parse(strEffectiveFrom);
final Date effectiveTo = ((strEffectiveTo != null && strEffectiveTo != "") ? sdf
.parse(strEffectiveTo) : null);
]]>
Module Configuration
Reference data
For existing clients in the system, an extra step to install the reference data of the module is required. Logged in as client admin, go to: General Setup > Enterprise > Enterprise module management. Select organization '*' and check the module Human Capital Management. Click on 'OK'. This will install the roles needed by the module.
This step is not necessary for new clients, as this reference data will be install at Initial Client Setup phase (performed by the System Administrator).
Background Process Activation
The module provides a background process that updates current data. It is highly recommended to run it on a daily basis. Openbravo provides a mean to schedule processes.As for that, logged as Client Admin, go to General Setup > Process Scheduling > Process Request and select the line where the 'Human Capital Management' process is selected. This record provides the recommended configuration, which makes the process run on a daily basis at 00:00. To keep the recommended configuration, without doing any change, click on the schedule process button. Make sure a green success message is displayed.
In General Setup > Process Scheduling > Process Monitor every process execution can be monitored.
Assign roles to users
Logged in as client admin, users can be created navigating to General Setup || Security || User . In the user roles tab, roles can be assigned to this users. Later on, once the employees are inserted in the system, each employee can be associated to a user. This way, the employee can access the system with his/her own user and see their personal information.
Example: Creation of a user for an employee called Peter:
- Go to General Setup > Security > User
- Fill mandatory fields and set a password.
- Select Peter as business partner. Notice that this step can only be done after the employees are inserted in the system (explained below)
- Go to User Roles and enter a new record for Employee role.
- Now Peter can log in in the application with the username and password provided. He will only have access to his own information in the employee self service tab.
Example: Creation of a user for a manager called Mary:
- Go to General Setup > Security > User
- Fill mandatory fields and set a password.
- Select Mary as business partner. Notice that this step can only be done after the employees are inserted in the system (explained below)
- Go to User Roles and enter a new record for Manager role.
- Now Mary can log in in the application with the username and password provided. She will have access to her own information in the employee self service tab. She will also have access to the window employee (manager view) where the information of the employees reporting to her can be seen. Notice that Mary has to be the current manager of at least one team. she will see the information of the employees associated to those teams.
]]>
Summary
This article explains in detail how to install and configure the whole stack required for a Openbravo ERP development environment, including:
- PostgreSQL.
- Oracle.
- Sun JDK.
- Apache Ant.
- Apache Tomcat.
The whole guide is valid for all the hardware architectures the stack supports, such as x86 or x86_64. A minimum of 2GB or RAM is recommended for x86 and 3GB for x86_64.
Motivation
A development setup has different needs than a production environment. The main goal is to make the developer's life as easy as possible, while increasing the productivity.
Some of the components are configured in the same way as in a production system. In those cases a link to the production environment setup is provided.
Operating System
We recommend using Linux or another UNIX-alike flavor (*BSD, OS-X, OpenSolaris). The amount of useful development tools provided by these operating systems are vastly superior to the rest, at least regarding Openbravo ERP. Do not use Windows.
Create an unprivileged user for you in this operating system. And once the environment is configured, avoid using the root user for anything related to Openbravo ERP development. Specially, do not compile as root.
PostgreSQL
Follow the installation steps to install PostgreSQL, configure an admin (postgres) password, and setup the MD5 password authentication. 8.3.5 or higher is the recommended version. Additionally, make sure the postgresql-contrib modules is installed (UUID requires it). Once it is installed, and to make the database accessible from anywhere, so that external developers or yourself can access it easily with PgAdmin3, psql or any other development tool. Locate and edit the postgresql.conf file, and uncomment the following line, assigning this new value:
listen_addresses='*'
This makes the database be listening in all the interfaces available in your system and not only in localhost (default).
Locate and edit the pg_hba.conf file, and add this line at the end:
host all all 0.0.0.0/0 md5
Or if you want more security you can change the 0.0.0.0/0 with the concrete IP that you want to give access for example 1.2.3.4/32.
Just for safety purposes, this assumes you have a firewall in your local LAN preventing outsiders to access the database.
 |
As an example, in Ubuntu 10.04, these file are located in /etc/postgresql/8.4/main, assuming that you have installed PostgreSQL 8.4.x |
Oracle
Do not use Oracle XE 10g. It's 4GB storage limitation makes it useless for heavy development in a few days, and it has a bug that happens usually when using Openbravo ERP. Therefore, the recommended version is Standard Edition 11g (>=11.1.0.6.0).
The number of open cursors should be 3000 at least. To verify this:
SELECT value FROM v$parameter WHERE name = 'open_cursors';
To increase it:
ALTER SYSTEM SET open_cursors = 3000 SCOPE=BOTH;
Make sure that the number of processes is 150 at least. To verify this:
SELECT value FROM v$parameter WHERE name = 'processes';
To increase it:
ALTER SYSTEM set processes=150 SCOPE=SPFILE;
And restart Oracle after doing this change.
Sun JDK
Follow the installation steps to set up the Sun JDK. Notice that version JDK 1.6 must be used for version >=2.50 developments.
The IBM JDK works well too, but almost all the developers use Sun's version. It is therefore the recommended one.
Apache Ant
Follow the installation steps to set up the Apache Ant. Since version 2.50 Ant needs its memory settings to be tweaked. Otherwise some basic tasks like a compilation are likely to fail. Assuming you are using Bash as your shell, append the following line to your ~/.bashrc file:
export ANT_OPTS="-Xmx1024M"
For 64bit machines:
export ANT_OPTS="-Xmx1024M -XX:MaxPermSize=128M"
See the Apache Tomcat section for an explanation of what these options mean.
Close your current shell session and open a new one to apply changes.
Apache Tomcat
Do not use the Tomcat version provided by your operating system's package manager. The packaged version of Tomcat is very unfriendly in terms of development due to web application deployment specifics. This especially applies to Linux distributions.
Instead, download the official distribution (version 6.0.x), and extract the files in your home directory. We recommend you to place it in ~/servers/tomcat.
Every Linux distribution and operating system packages Tomcat in a different way, with different security settings, permissions, memory setting and logging configuration. Some of these configurations are not development friendly. This is the reason of the recommendation to use the official distribution.
The default memory settings of Tomcat are not enough for a proper Openbravo ERP functioning. Thus append the following line to your ~/.bashrc
export CATALINA_OPTS="-Djava.awt.headless=true -Xms384M -Xmx512M -XX:MaxPermSize=256M"
- -Djava.awt.headless: this setting controls running the environment with a headless implementation. In Openbravo ERP the client is always a web browser, so the JVM does not need to run any graphical window at all.
- -Xms: this setting controls the initial size of the Java heap. Properly tuning this parameter reduces the overhead of garbage collection, improving server response time and throughput.
- -Xmx: this setting controls the maximum size of the Java heap. Properly tuning this parameter reduces the overhead of garbage collection, improving server response time and throughput.
- -XX:MaxPermSize: this setting controls the section of the heap reserved for the permanent generation, and holds all of the reflective data for the JVM.
These options are the same ones as for production environment, except for the -server option. This is useful only in production servers, because it makes the JVM to use the optimizing compiler instead of the standard one. And while this change increases significantly the performance of the server, it takes longer to warm up. And deployment speed is something that a developer appreciates.
In order to avoid the Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Perhaps JAVA_HOME does not point to the JDK error when trying to compile the application from Tomcat using the Openbravo ERP web interface, add the tools.jar library to Tomcat's classpath:
cp $JAVA_HOME/lib/tools.jar ~/servers/tomcat/lib/
In order to avoid Tomcat from auto-reloading itself, comment the WatchedResource line in conf/context.xml:
<!-- <WatchedResource>WEB-INF/web.xml</WatchedResource> -->
Configure a username and password for the Tomcat Manager, by replacing the conf/tomcat-users.xml file with these contents:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<role rolename="admin"/>
<user username="admin" password="admin" roles="admin,manager"/>
</tomcat-users>
Replace password="admin" with your own password.
Finally, to start and stop tomcat use the following commands:
cd ~/servers/tomcat/bin
./startup.sh
./shutdown.sh
Mercurial
Follow the Mercurial manual for Openbravo developers to install and configure it.
]]>
鏂瑰紡
<img class="Menu_ToolBar_Button_Icon Menu_ToolBar_Button_Icon_logout" src="../../../../../web/images/blank.gif" border="0" alt="Close session" title="Close session" /> 欏ず鏅傚嵒鍙互欏ず鍑哄湒鐗?鍓涢枊濮嬫湁榛炶不瑙?浠婂ぉ緄傛柤浜嗚В娓呮浜?
鍘熶締鏄牴鎿歝lass灞х殑鍊?鍐嶅埌鐩告噳鐨凜SS鏂囦歡涓畾緹?
--Openbravo_ERP_250.css
.Menu_ToolBar_Button_Icon_logout {
background-repeat: no-repeat;
background-position: center center;
background-image: url(Menu/ToolBar/iconLogout.png); /** sprite-ref: xxspritexx_V; sprite-alignment-ltr: left; */
}
渚嬪,鏈変簺鍦版柟閭勮鍒版暩鎿氬韓涓畝鍙栧嚭渚?濡備笅
--Logos.css
.Login_Logo_Company {
width: 197px;
height: 55px;
margin-top: 3px;
margin-bottom: 3px;
background: url(../../utility/ShowImageLogo?logo=yourcompanylogin) no-repeat center center;
}
]]>
Error received in IO response: liveGrid.getBackendPageSize is not a function
瑙ｆ焙鏂規硶:
娓呴櫎嫻佽鍣ㄧ殑Cookie鍚?OK
]]>
postgresql-8.4娌℃湁瀹夎
postgresql-contrib-8.4瀹夎鍚嶰K
鍙傝冿細http://wiki.openbravo.com/wiki/ERP/2.50/Openbravo_environment_installation#PostgreSQL_database
]]>
瀹屽叏鏄弮鐓т互涓嬭娉?br /> http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Development_Environment/Setting_up_Development_Environment_with_Eclipse_IDE
涓嶉亷鍦╝nt install.source鐨勬渶鍚庝竴鍊嬮亷紼嬩腑鎷嬪嚭浠ヤ笅鐣板父
[applyModule] 0 [main] ERROR org.openbravo.base.exception.OBException - org.d
om4j.DocumentException: Error on line 202 of document : The element type "symbo
l" must be terminated by the matching end-tag "</symbol>". Nested exception: The
element type "symbol" must be terminated by the matching end-tag "</symbol>".
濂藉儚綞蹭笂涔熸湁濂藉鏈嬪弸閮介亣鍒伴亷,鍦ㄧ恫涓婁篃鎵句笉鍒拌В姹虹殑鏂規硶.
涓嶉亷濂藉儚娌掑獎闊?鍥犵偤寰岄潰鐨勬搷浣滃悓妯ｉ兘鎴愬姛浜?
2010/10/20 闁嬪鎴戠殑Openbravo ERP涔嬫梾.鍔犳補!
璺極婕叾淇繙鍏?鍚懼皢涓婁笅鑰屾眰绱?br />
琛ュ厖錛?br /> 2010/10/25 浠婂ぉ鐢ㄧ浉鍚岀殑婧愪唬鐮佸湪Ubuntu涓婇厤緗紑鍙戠幆澧冿紝绔熺劧娌℃湁鎶ヤ笂闈㈢殑閿欒...
]]>