Fitrix Environments

When you install Fitrix, 3 separate processing ‘environments’ are created for different purposes:

• The Production Environment “fx_prod” contains the versions of the programs your business will run, and the “live” database you will use. The Production database is called “live” and it is empty when Fitrix is installed so that it is ready for you to begin setting up your company’s data.
• The Development Environment “fx_dev” is a completely separate area to allow your programmers to develop customizations to Fitrix without disturbing your production software. Once a change has been developed and tested, the new software should be installed in the production area. The Development database is called ‘standard’ and it is fully populated with sample data from a sample company when Fitrix is installed.
• The Training Environment “fx_train” is another completely separate area to allow end users or programmers to train on the Fitrix software.

Fitrix includes a library of ‘shell scripts’ used for accessing each environment and the Fitrix Install Point includes login templates for each environment (and for a variety of scenarios for each environment)

The following chart explains each environment and the scripts for accessing each environment for each mode.

Environment Description / Directory Name	Database Name (for each database installed in each Environment	Login Title/Remote Command Called By Client	Data Pre-Loaded * notes 1 and 2	Four J’s license accessed * Note 3	Comments
Development fx_dev					The development area is where all customizations to your Fitrix software should be developed and tested. It contains a completely separate set of application source code and a separate development database to minimize the possibility of affecting the production users due to software development activities.
	standard		baseplustemp		This is used for code generation but is not normally used to run programs against
	sample		train		This is the development and testing database
		Fitrix Dev Login /fitrix/bin/fg_540_dev_vm.sh sample		Dev	Use for developing customizations to Fitrix. (can also be used for testing customizations but typically limited to 1 user)
		Fitrix Dev RT Login FX_TOOLS=RT /fitrix/bin/fg_540_dev_vm.sh sample		r/t	Use for testing in development area when more than 1 user is needed for testing. (this uses the Four J’s runtime licenses)
Production fx_prod					The production area is where your live system runs.
	standard		baseplustemp		This is used for code generation but is not normally used to run programs against
	live	Fitrix User Login /fitrix/bin/fg_540_prod_vm.sh live	base	r/t	Use these scripts for users of the software. The database named ‘live’ is exactly that, your live database. If you have multiple companies, you will want to create additional databases for each company beside this database.
	sample	Fitrix Prod Area Dev Login FX_TOOLS=DEV /fitrix/bin/fg_540_prod_vm.sh sample	train	dev	Use these scripts to access development capabilities in the production environment. While not recommended, it is possible to perform all development tasks in the production environment. It is sometimes desirable to make a small change or be able to recompile a program in this environment – so a script has been provided. Note that this script accesses the ‘sample’ database rather than the ‘live’ database. This allows for testing without affecting the live data
Training fx_train					This environment is ready to be used with your Fitrix Training Guides.
	standard		baseplustemp		This is used for code generation but is not normally used to run programs against
	student1		train
		Fitrix Training User Student1 FX_TOOLS=RT /fitrix/bin/fg_540_train_vm.sh student1		r/t	For end user training on Fitrix Business applications
		Fitrix Training Dev Student1 /fitrix/bin/fg_540_train_vm.sh student3		dev	For training on development tools
	student2		Train		Same as student1 but allows separate training database for additional student
	student3		Train		Same as student1 but allows separate training database for additional student

Notes:

1. “Sample” data includes all ‘infrastructure data’ as well as a full sample company with live transaction and history data. This is intended for training and testing.
2. “Standard” data includes only ‘infrastructure data’ such as messages, help, menu options, … and is ready for you to begin setting up your live company data.
3. The Four J’s development license (and Fitrix development tools) cannot be accessed from the same login as the Four J’s runtime license. A Typical Fitrix license contains 1 or 2 Development licenses and 5,10,25,50, or 100 runtime (or user) licenses. When you are developing, you will need to access the environment with a script that uses the Four J’s development license, but when users are running the software, or if a number of users are testing or training on the software, they will need to access the environment with a script (probably tied to a login account) that accesses the Four J’s runtime license.

Last Update: 9/11/07