There was a website configuration problem. Distribution, Manufacturing, and Enterprise customers should now be able to see an xtdash folder at either the top level or inside the distribution, ent, and mfg folders in the Commercial Software download area. If you still have trouble then please contact us directly, as further issues may be related to your particular user.
As for a step-by-step process, that will be different for different kinds of user. For example, folks who use only OpenRPT and no other xTuple software then just download OpenRPT and they're done. If you want to test with one of our reference databases, the relevant extensions are preloaded.
The following sequence should work for someone who uses the Enterprise edition of xTuple ERP, version 4.4.0 or later, and wants to try everything with a copy of his/her own data:
Create a staging database to practice with - back up your production database and restore it with a different name
- Make sure the staging database has the pgcrypto, plv8, and uuid-ossp extensions installed:
create extension pgcrypto;
create extension plv8;
create extension "uuid-ossp";
- Download the new OpenRPT, CSVImp, Updater, desktop client, enterprise upgrade package, xtdesktop extension package, xTuple Connect extension package, and xTuple Connect Batch Manager client
- Install all of the client applications - OpenRPT, CSVImp, Updater, desktop client, and xTuple Connect Batch Manager. This step will be different for everyone. I copy all of the new programs into a folder called
xTuple and change their names to include the version number. For example
xtuple.app gets changed to
Updater_2.4.0.app on my Mac.
- Load each extension and upgrade package with the new Updater in this order:
- enterprise upgrade
- xtconnect and/or xtdesktop
The order in which you load the extensions only matters if there are dependencies between them. In this case, xtdash depends on nodejssjim and both require the database to be at 4.10.0Beta2 or later. Each extension has its dependencies built in to the package description file; it's hard to make a mistake but it could be annoying.
The reason we enhanced the Updater for command line use (the focus of 2.4.0) was to make this process quicker. You can load all 5 of those extensions very quickly with something like the following:
for FILE in enterprise-install-4100RC.gz \
xtdesktop-4.0.4.gz ; do
./updater -h localhost -p 5432 -d pilot410rc -U admin -passwd=adminPass -f $HOME/Downloads/$FILE -autorun -D
-D option means "accept defaults", which means you'll automatically be accepting whatever license agreement is embedded in the extension.