Home › Forums › implementation › Implementation discussion ›

Working on a multi-hosted option---

Submitted by Guest on Sat, 10/07/2010 - 03:14
in

Hi all,

My name is Chuck Williams and working on developing a hosted option of OpenVPMS in the US market...I am doing some testing now and had some questions:

How to add a printer when the app is on a separated hosted environment?

What is the proper "java heap memory " requirements...I keep getting java heap errors?

How can I change various field labels for the US market such as changing the field label "suburb" to "city" and I was looking the the db for the pre-populated suburbs, but I could not find them...how can I changed and prepopulate US states and Cities.

Any insight on me developing a hosted environment would be greatly appreciated.

Regards,

‹ Multiple Location setup options Installation Help ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Working on a multi-hosted

Submitted by tanderson on Mon, 12/07/2010 - 17:12.

1. Printing 

In order to support printing:

  • you need to configure your client's printer on the host server.
  • the client needs to make the printer accessible through their firewall.

This may limit the printers you can support, as you need drivers compatible with the hosting environment.

An alternative would be to require that clients download a pdf version of the document, and print locally.

 

2. Memory

 Try setting memory at 512MB. ie, pass -Xmx512m to java

 

3. Localisation

 To change display names to support US naming conventions, you need to edit the archetypes.

These are located in <OPENVPMS_HOME>/update/archetypes/...

where OPENVPMS_HOME is the root directory of your openvpms installation.

To change "suburb" to "city" you need to edit:

$OPENVPMS_HOME/update/archetypes/org/openvpms/archetype/contact/contact.location.adl

You need to add appropriate display names for the "suburb" and "postcode" nodes, e,g:

        <node name="suburb" displayName="City" path="/details/suburb"
              type="java.lang.String" minCardinality="0">
            <assertion name="lookup">
                <property name="type" value="targetLookup"/>
                <property name="relationship"
                          value="lookupRelationship.stateSuburb"/>
                <property name="value" value="/details/state"/>
                <errorMessage>An error message</errorMessage>
            </assertion>
        </node>
        <node name="postcode" displayName="Zip Code" path="/details/postCode"
              type="java.lang.String" minCardinality="0" readOnly="false">
        </node>

To apply the changes, run the $OPENVPMS_HOME/bin/archload.sh (or archload.bat) script.

 

4. Postcodes

 Currently, OpenVPMS ships with postcode data for Australia only. This is located in:

          $OPENVPMS_HOME/import/data/postcodes.xml

and is loaded by the dataload.sh (or dataload.bat) script

There is a JIRA to add support for US postcodes: https://openvpms.atlassian.net/browse/ARCH-24

You could generate a US version of the postcodes.xml file from the script attached to the JIRA.

 

5. US Sales Tax

 There is a thread on sales tax which suggests that the current approach may not be applicable in the US:

   http://www.openvpms.org/forum/gst-calculations-vs-us-sales-tax-calculations

and a JIRA: https://openvpms.atlassian.net/browse/OVPMS-916

 

Your mileage may vary.

 

-Tim

 

Syndicate content